fix(songwriting): adjudicate form, song-forms, process, and co-writing against Writing Better Lyrics chapters 20-24 + appendix

plugins/songwriting/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "songwriting",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "Songwriting craft companion — nine concern-scoped lyric-craft skills (workflow router, rhyme, object-writing, metaphor, meter-prosody, song-form, co-write, diagnose, practice) applying Pat Pattison's methods, with an object-writing agent that performs the sensory exercise itself and per-skill emission boundaries that route generation to the skill that owns it, plus Suno v5.5 prompt engineering (style prompts, tagged lyrics, genre templates, troubleshooting).",
   "author": {
     "name": "Melodic Software",

plugins/songwriting/CHANGELOG.md

@@ -3,6 +3,122 @@
 All notable changes to the `songwriting` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.8.2]
+
+A source-fidelity pass over `process.md`, `co-writing.md`, and the co-write
+session-opener template against *Writing Better Lyrics* (2009) Chapter 24 and
+the Appendix, both read in full with Chapter 24's two figures. **This finishes
+Book 2.** Paraphrase only; no chapter prose, example writes, or student work
+reaches this public repository.
+
+### Fixed
+
+- **The No-Free-Zone method was attributed to Pat throughout; it is Stan
+  Webb's.** The Appendix is emphatic — Webb taught it to Pat in his first
+  professional co-write, and the Appendix thanks him by name. Pat carried it
+  into Berklee and added two rules of his own (stay inside the song; no
+  technical talk). `co-writing.md` and the printable opener now credit Webb,
+  and the opener's title line no longer calls the method Pat's.
+- **The session opener collapsed Webb's two distinct rules into one and lost a
+  rule in the process.** "Say everything" and "nobody says no / silence means
+  more" are separate rules doing separate jobs; merging them under a single
+  `No "no."` heading left "write crap" occupying a numbered slot as if it were
+  a third rule rather than the encouragement attached to the first two. The
+  four numbered rules now match `co-writing.md`.
+- **`co-writing.md`'s inner-critic section and its solo-applications section
+  contradicted each other** on which rules apply when writing alone — two of
+  four versus all four. The Appendix supports the looser reading (the
+  discipline helps every time Pat writes; the inner critic is his most frequent
+  co-writer), so the disagreement is now stated explicitly with the Appendix's
+  own evidence rather than left for a reader to trip over.
+
+### Added
+
+- **`co-writing.md`: the causal claim the rule rests on.** The chain is dumb
+  idea → less dumb → decent → great, and the Appendix reports its own session's
+  best part came from its dumbest idea. The file had the mechanism but not the
+  claim that censoring the first link forfeits the last.
+- **`co-writing.md`: what the closed door actually buys** — nobody defends
+  anything, so surviving ideas are the ones both writers love; no arguments and
+  no compromise.
+- **`co-writing.md` + opener: technical talk is fear wearing academic robes.**
+  The Appendix diagnoses it as a writer dressing up a line they suspect is
+  weak, which makes it a signal to read rather than a lapse to scold.
+- **`process.md`: five named rejection criteria from Chapter 24's worksheet
+  walk-through**, including the "seems to mean more than it conveys" clunker
+  test, plus the rule that the rhyming syllable should carry primary and not
+  secondary stress. None of these existed anywhere in the plugin.
+- **`process.md`: pattern lock as a named failure mode.** Chapter 24's bridge
+  came out in the verses' common meter on autopilot; the chapter also catches
+  itself borrowing a specific Paul Simon bridge structure and notes that
+  loving the source does not make the borrow work.
+- **`process.md`: the form option that LOST and why.** Dumping a verse is
+  tested first and rejected on cause — form repairs are subject to scene logic,
+  so a leaner form that breaks cause is not an improvement.
+- **`process.md`: the worksheet is a brainstorming device, not a rhyme-finding
+  device** — stated outright in Chapter 24, with Sondheim cited as a working
+  practitioner.
+- **`process.md`: Chapter 24's worksheet figure is load-bearing.** The prose
+  lists the five column headings and nothing under them; the columns exist only
+  in `image_rsrcAUJ.jpg`, which independently confirms the
+  one-undifferentiated-column-per-core-word layout recorded in `worksheets.md`.
+
+## [0.8.1]
+
+A source-fidelity pass over `song-forms.md` and `form.md` against *Writing
+Better Lyrics* (2009) Chapters 20-23, all four read in full — including
+Chapter 20's figure and all four of Chapter 21's split spine items. Paraphrase
+only; no chapter prose, example writes, or student work reaches this public
+repository.
+
+### Fixed
+
+- **A late-appended block in `song-forms.md` restated the Chapter 22 and 23
+  repair strategies and got four of the six wrong**, each one contradicting the
+  correct statement earlier in the same file. Chapter 22's third repair merges
+  two verses into one larger verse that shifts internally, leaving two verses;
+  the block described giving four verses four different jobs, which preserves
+  the very `v/v/ch/v/v/ch` shape the chapter exists to dismantle. Its second
+  repair kept "same content" when the chapter requires changing both structure
+  and the kind of information, the distinction that separates a bridge from a
+  renamed verse. Chapter 23's second alternative replaces the third verse; the
+  block had verse three still building normally. Its third alternative converts
+  to AABA precisely so all three verse ideas survive as verses; the block said
+  to drop the third verse — the opposite of the condition that selects the
+  form. Each repair now states its resulting form explicitly so the two
+  descriptions cannot drift apart again.
+- **"Four times is a lot." was attributed to the wrong book and labelled a
+  paraphrase.** It is verbatim from *Writing Better Lyrics* (2009), Chapter 22.
+  The claim that *Essential Guide to Lyric Form and Structure* (1991)
+  Chapter 6 shares the warning is left standing but remains unverified — that
+  chapter has not been read.
+- **The chapter title was rendered "Im(potent) Packages"**, parenthesising the
+  wrong half of Pat's pun. It is "(Im)potent Packages".
+
+### Added
+
+- **`form.md`: Pattison's own naming of the two form-follows-function
+  readings.** Applied to one section the rule *is* prosody; applied to two
+  sections compared against each other it *is* contrast. The file had the
+  mechanics of both but had dropped the link to the plugin's own prosody
+  vocabulary.
+- **`form.md`: the musical-bar mechanism behind the "Years" chorus.** The file
+  had the stress arithmetic balancing at six and six, but the prosody lives in
+  the setting — both groups get four bars, so three phrases occupy the space
+  two had, and the final phrase is compressed to a single bar exactly where the
+  lyric says time moves fastest.
+- **`form.md`: a contrast-audit caution drawn from the "Southern Comfort"
+  chorus.** Three-stress phrases and a "3+" opening can look like contrast
+  while still leaning toward the common meter the verse established, because
+  three stresses is that meter's balancing length.
+- **`song-forms.md`: an AABA song's last system is bridge/verse, not a lone
+  verse** (Chapter 23) — the pairing supplies the contrast against the opening
+  A sections, so an unearned-feeling return should be diagnosed across the
+  whole B-to-final-A unit.
+- **`song-forms.md`: the cost Chapter 23 attaches to its first alternative** —
+  inserting a bridge before a third verse returns to a full verse before the
+  last chorus, so the lyric can still seem long.
+
 ## [0.8.0]
 
 ### Removed

plugins/songwriting/context/pat-pattison/research/co-writing.md

@@ -4,6 +4,9 @@ Pat Pattison - *Writing Better Lyrics* (2009), Appendix; extended via
 patpattison.com "Co-Writing" article for explicit four-rule No-Free-Zone
 session opener and seminar copy on technical-talk discipline.
 
+**The No-Free-Zone method originates with Stan Webb**, not with Pat — see
+§ Core idea. Credit it accordingly.
+
 ## Image inventory
 
 - *Writing Better Lyrics* (2009) Appendix: no linked images.
@@ -16,9 +19,31 @@ until both writers hear something worth keeping.
 
 > Silence is a request for more, more, more.
 
-Pattison frames the ideal co-writing room as a no-free zone: no idea is argued
-down in the moment. If a collaborator likes something, they say yes. If they do
-not like it, they stay silent and let more ideas arrive.
+The no-free zone: no idea is argued down in the moment. If a collaborator likes
+something, they say yes. If they do not like it, they stay silent and let more
+ideas arrive.
+
+**The method is not Pat's, and the Appendix is emphatic about that.** It is
+Stan Webb's — Pat's first professional co-writer, who taught it to him at the
+start of a Nashville session, and whom the Appendix thanks by name. Pat's
+contribution is carrying it into Berklee's classrooms and adding rules 3 and 4
+below — stay inside the song, and no technical talk. In the Appendix those two
+arrive as a single piece of advice about not talking craft in the room; the
+four-rule opener splits it in two. Attribute the method to Stan Webb when
+coaching from this material; a writer told "Pat's rule" is being told something
+the source takes visible care to credit elsewhere.
+
+Two details of the original telling that carry the rule's logic:
+
+- **The dumbest idea is load-bearing, not merely tolerated.** The chain runs
+  dumb idea → less dumb idea → decent idea → great idea, and the Appendix
+  reports that its own session's best part came out of its dumbest idea. The
+  claim is causal: censor the first link and the last one never arrives.
+- **The closed door is literal before it is a metaphor.** Webb opened the
+  session by physically shutting the door and saying that nobody outside needs
+  to know how dumb either writer sounds. What it buys is named precisely:
+  nobody has to defend anything, so the only ideas that survive are the ones
+  both writers actively love — no arguments and no compromise.
 
 ## Closed-door safety
 
@@ -110,7 +135,9 @@ to lecture about it.
 - If the room freezes, restate that silence means "keep throwing ideas."
 - If someone starts defending a line, return to generation and ask for more
   options.
-- If the session becomes a craft lecture, ask what the character says next.
+- If the session becomes a craft lecture, ask what the character says next —
+  and read it as someone protecting a line they do not trust, not as a
+  discipline problem.
 - If compromise appears, keep generating until both writers can say yes.
 - If writing alone, park critique until the draft has enough material to revise.
 
@@ -142,7 +169,17 @@ someone slips.
    room they let writers defend lines with vocabulary instead of
    making lines better.
 
-> "Write crap. Lots of it. All the time. The more the better." — Pat
+Rules 3 and 4 are Pat's addition to Stan Webb's original two (say everything;
+silence means more, `yes` advances). The Appendix gives the reason they are
+needed, and it is diagnostic rather than stylistic: technical talk is usually
+**fear wearing academic robes** — a writer dressing up an idea they suspect is
+weak. Naming the effect does not improve the line. The Appendix's own phrasing
+is that a dumb idea is still dumb with professorial robes on. When a room
+starts explaining craft, treat it as a signal that someone is protecting a line
+they do not trust, not as a discipline lapse to be scolded.
+
+> "Don't be afraid to write crap — it makes the best fertilizer." — Pat
+> (*Writing Better Lyrics* (2009), Appendix)
 
 The rules are not soft suggestions. The room actually says them out
 loud at the start of the session. See
@@ -222,15 +259,26 @@ generative-self and critic-self:
   bad ideas without being shut down by critic-self
 - **Rule 2** (silence = more) — when critic-self is silent on an idea,
   generative-self keeps going
-- **Rule 3** (stay inside) — critic-self does not get to talk about
-  technique mid-write; it stays inside the song and the character
+- **Rule 3** (stay inside the song and the characters) — critic-self
+  stays with the character and the scene rather than rising to
+  commentary about the draft
 - **Rule 4** (no technical talk) — critic-self does not derail into
   craft analysis during drafting; that's a separate revision pass
 
-Pat: most writer's block is the inner critic refusing to honor Rule 1 or
+Most writer's block is the inner critic refusing to honor Rule 1 or
 Rule 4. The discipline is the same in co-write or solo — separate
 generation from revision; do not let critique kill the generative phase.
 
+**This section and § Solo applications above disagree, and § Solo applications
+is the stricter reading.** That section calls rules 2 and 3 co-write-only and
+maps just rules 1 and 4 onto solo work; this one maps all four. The Appendix
+supports the looser reading — it says outright that the discipline helps every
+time Pat writes, not only when co-writing, and names the inner critic as his
+most frequent co-writer. Treat all four as applicable solo, with the caveat
+that rule 2's spoken `yes` has no literal solo equivalent beyond keeping the
+line. What the Appendix does not do is rank them, so neither should coaching
+built on it.
+
 ## Cross-references
 
 - [templates/co-write-session-opener](../templates/co-write-session-opener.md)

plugins/songwriting/context/pat-pattison/research/form.md

@@ -73,6 +73,11 @@ can match each other because verses usually share the same developmental job.
 A chorus should normally change design because it comments, summarizes, or
 arrives.
 
+Pattison names both readings rather than leaving them implicit: applied to a
+single section, form-follows-function *is* the principle of
+[prosody](prosody.md); applied to two sections compared against each other, it
+*is* the principle of contrast. Same rule, one object or two.
+
 ## Rhyme as accelerator
 
 Rhyme spacing changes perceived speed:
@@ -190,6 +195,21 @@ If the chorus opening does not change at least one major variable, revise the
 opening before polishing later lines. The first contrast teaches the listener
 that the song has moved into a new job.
 
+Sameness can hide from a quick count. In the "Southern Comfort" chorus most
+phrases carry three stresses and the opening carries "3+", which reads as
+contrast on the page — but three stresses is common meter's balancing length
+and "3+" is an ordinary variant of its four-stress line, so the section still
+leans toward the meter the verse has already established at length. Where a
+chorus is meant to contrast with a common-meter verse, check what its
+balancing phrases are doing, not only whether the numbers differ.
+
+On how many verse phrases that is: Chapter 20 reads the verse as two complete
+common-meter systems varied by an extra stress in its last phrase, while
+[song-forms-examples](song-forms-examples.md) reads the 1991 treatment of the
+same song as seven phrases with the closing eighth deceptively withheld. Those
+are two readings of one verse in two books, not a contradiction to resolve —
+cite whichever book is in hand and do not merge the counts.
+
 Useful revision moves:
 
 - Shorten the chorus opening if the verse is long and narrative.
@@ -223,6 +243,14 @@ effect: balanced total, built-in acceleration
 This is form-level juggling: the chorus comments on the long, loose verse
 material by becoming more compact, balanced, and focused.
 
+The musical setting is what completes the prosody, and the stress arithmetic
+alone misses it. The song gives both groups the same four bars — but three
+phrases now have to fit the space two phrases had, and the final phrase gets
+only one bar. The lyric says years go fast; the setting compresses the last
+phrase into the smallest space in the section. When checking a chorus like
+this, ask how much musical time each group occupies, not just how many
+stresses it contains.
+
 ## Phrase-count balance
 
 *Writing Better Lyrics* (2009), Chapter 21 adds a plain section-level lever: assuming phrase lengths and rhyme