feat(plan): plan_version 1.9 is the current target, the file first on every line [skip-docs]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

agents/plan-critic.md

@@ -134,7 +134,7 @@ questions, which defeats the purpose.
 - Are there assertions about behavior that have no corresponding test?
 - Do the verification steps cover error paths, not just happy paths?
 - Are the verification commands correct and runnable?
-- `plan_version: 1.8`: does every step's `Test first:` name a test that would
+- `plan_version` 1.8 or later: does every step's `Test first:` name a test that would
   FAIL before the step and pass after it (not a test that already passes)?
 - Does any step consist of only tests — every file in its `Files:` a test —
   for behaviour an earlier step delivered? Its tests pass at its start point,

agents/planning-orchestrator.md

@@ -215,14 +215,19 @@ Write a comprehensive implementation plan including:
   criterion must be an executable command or observable condition
 - **Estimated Scope** — file counts and complexity
 
-**Plan-version header:** Include `plan_version: 1.8` and the brief's
+**Plan-version header:** Include `plan_version: 1.9` and the brief's
 `ceremony:` in the metadata line below the title. This signals to trekexecute
 that the plan includes per-step verification manifests and enables strict
 audit mode. Plans without this marker are treated as legacy v1.6 with
 synthesized minimal manifests. 1.8 adds `Test first:` on every step, one
 `End-to-end:` step, the optional `Interface in:` / `Interface out:` /
 `Review focus:` fields and, for an architectural plan, `## Design`
-(`commands/trekplan.md` Phase 8 is the full text). 1.7 plans stay valid.
+(`commands/trekplan.md` Phase 8 is the full text). 1.9 adds the file first on
+every line: each `Files:` entry and each `Test first:` `File:` line opens with
+its backticked path(s), and everything after the first other text is
+description, so every path stands before any annotation
+(`` `src/a.mjs`, `src/b.mjs` (new) ``, never `` `src/a.mjs` (new), `src/b.mjs` ``).
+1.8 and 1.7 plans stay valid.
 
 ### Mandatory step format — copy this exactly
 
@@ -335,7 +340,7 @@ Internally the validator enforces (same checks as before, now in one place):
 - Step count == manifest count
 - Zero forbidden narrative headings (`### Fase N`, `### Phase N`, `### Stage N`,
   `### Steg N`)
-- `plan_version` 1.7 or 1.8 declared (warning only if older / missing)
+- `plan_version` 1.7, 1.8 or 1.9 declared (warning only if older / missing)
 - From 1.8: `Test first:` per step, an `End-to-end:` step, non-empty optional
   fields, a valid `ceremony`, and the design part for an architectural plan