write-plan: a plan shown on a standing answer is often not written to its plan file first #119

What happens. decision-points.md, "What does not change", says a gate approving a plan links the plan file, written before the gate is asked. skills/using-github/issues.md says the same for .review/github-plan.md, since step 8 copies each sent text verbatim from that file.

In #116's sandbox runs on haiku, every run that filed an issue wrote the file first (7/7). Runs that stopped at the gate because the person gave only a standing answer ("Take the recommended answer on every question") mostly showed the plan inline and wrote no file:

• tracker-gh-ticket-draft-blanket: 2/5 wrote it.
• tracker-gh-ticket-draft-standing-answer: 1/5 wrote it.

Nothing is written to GitHub in those runs, so the loss is the gate's link to the plan, and any later step that reads the file.

To find out

1. Does Jira's .review/jira-plan.md (skills/using-jira/write-plan.md) have the same gap? Run the Jira tracker pack's ticket-draft scenarios with a standing answer at the gate.
2. Is the cause the wording ("before every showing"), or the model treating a stopped plan as not worth a file? Try one wording fix in write-plan.md, which both trackers cite, and check it with a scenario on each tracker.

Landing. A wording change to write-plan.md is a behavior change for every skill that writes a plan, so it needs scenario evidence on both trackers, an adversarial review, and the Origin, Sandbox and Canary lines.

Origin: #116's round-4 evidence. Run copies: the #59 PR B sandbox runs, evidence-r4.