Close three text gaps left after #80 #81

Goal

Close three text gaps that remain in the plan-lifecycle plugin after #80: the yolo temporary-worktree teardown, the red baseline after a review fix changes a spec test, and the contract advice list for an empty Research section.

Mode: plan-and-implement

Research

Repository facts (paths relative to the repository root):

• plugins/plan-lifecycle/skills/productivity/yolo/SKILL.md, Commits item 2, ends the temporary worktree recipe with git worktree remove -- <path>. Landing step 9 continues with git worktree prune, and the root AGENTS.md says: "Teardown is git worktree remove followed by git worktree prune; removing the directory by hand leaves an orphan admin record."
• Same file, Red baseline item 4: "When a spec test is wrong, record the reason in Verification Results, fix the test, and run the baseline again." It does not say whether this applies to a review fix, or which line to record. In the Close yolo, contract, and helper gaps from #78 #79 trial, a code-review fix changed a spec assertion, and the run wrote no new Red baseline line. The run quoted tdd-workflow: "Test assertions are read-only during Phases 3–5", and that skill says to escalate a wrong test to the user.
• plugins/docks/skills/engineering/tdd-workflow/SKILL.md (Phase 2): "A test that passes prematurely is broken - fix the test, then re-run." (Rules): "If a test is wrong ... STOP and escalate to the user."
• plugins/plan-lifecycle/skills/productivity/plan-manager/references/plan-contract.md, advice paragraph: "a Research section that holds only _Not researched yet._ after drafting". The helper (plan.mjs, researchFilled and printAdvice) also prints that advice for an empty Research section. The Close yolo, contract, and helper gaps from #78 #79 code review reported this mismatch as LOW.
• node scripts/skills/content-hash.mjs --backfill plugins/plan-lifecycle/skills refreshes content_hash in yolo/SKILL.md and plan-manager/SKILL.md.

Decisions:

• Worktree teardown: add git worktree prune after git worktree remove in Commits item 2. Rejected: leaving it to Landing, because Commits item 2 runs earlier and in a loop.
• Review fix that changes a spec test: Red baseline item 4 applies to it. Run the changed test against the code before the fix; it must fail on the changed assertion. Record Red baseline, step <id>, review round <k>: <command>: <k> failed, <m> passed. The yolo invocation answers the user escalation that tdd-workflow asks for; the record replaces it. Rejected: escalate to the user, because a yolo run asks only the merge question.
• Contract advice: say "a Research section that is empty or holds only" the placeholder. Rejected: change the helper to skip empty Research, because the status gate already refuses empty Research, and the advice should match the gate.
• Release: a patch, after the merge, because only text changes.

Steps

Acceptance

Do not touch

Plugin manifest and marketplace version fields (scripts/release.mjs bumps them after the merge). plan.mjs behavior. Skills of the docks plugin.

Open questions

Verification Results

• A1: node scripts/ci.mjs --plugin plan-lifecycle passed on each commit (1436679e, 260302ab).
• A2: grep -n "git worktree prune" on yolo SKILL.md prints two lines: Commits item 2 and Landing step 9.
• A3: a fresh read-only agent answered: "The review fix changes a spec assertion, so yolo Red baseline item 5 applies ... Run the changed test against the code before the fix. It must fail on that assertion" and "Yolo item 4 replaces that step on purpose: "This record replaces the user escalation that tdd-workflow asks for."" It found that the line format used <k> for both the round and the failed count. The committed text uses review round <r>.
• A4: grep -n "is empty or holds only" on plan-contract.md prints one line in the advice paragraph.