open/voyage
1
0
Fork 0
Code Issues Releases 13 Activity

docs(plan): Handover 4, the planner and the template follow the 1.9 fixes

Browse source 
Operator decisions 20 and 22.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-10-13 19:10:37 +02:00
commit 5fa956b974
Signed by: ktg
SSH key fingerprint: SHA256:JakMjO6FTBBzN0Bhfj9saOoEjaFxlSdYuZQQpM/lF9Q
4 changed files with 133 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

18
commands/trekplan.md
View file

@ -691,11 +691,21 @@ Do NOT write this synthesis to disk. It is internal working context only.
> is description and is never read. So every path stands before any annotation:
> `` `src/a.mjs`, `src/b.mjs` (new) ``, never `` `src/a.mjs` (new), `src/b.mjs` ``
> (the second path would be description); two test files share one line,
> `` File: `a.test.mjs`, `b.test.mjs` (new) ``. A 1.9 step always names a file:
> an entry that does not open with a backticked path, `none`, or an empty
> `` File: `a.test.mjs`, `b.test.mjs` (new) ``. A line that is no list item
> continues the entry above it, so a list wrapped after a comma keeps its
> paths (`` `src/a.mjs`, `` with `` `src/b.mjs` `` on the next line names both)
> and a wrapped description stays description. The `File:` line may open with
> `-`, `*`, `+`, `1.` or `1)`, and any list item (the `Verifies:` line too)
> ends it. A 1.9 step always names a file:
> an entry that does not open with a backticked path, the bare word none
> (written without backticks), or an empty
> `Files:` is `PLAN_STEP_PATH_NOT_FIRST`; a leading span that is no path (a
> call, an option, a URL) is `PLAN_STEP_PATH_NOT_A_PATH`. The canonical step
> above already opens each line with its path.
> call, an option, a URL) is `PLAN_STEP_PATH_NOT_A_PATH`.
> So is a backticked placeholder (`` `none` ``, `` `TBD` ``, `` `TODO` ``,
> `` `TBA` ``, `` `N/A` ``, `` `NA` ``, `` `...` ``) and a mixed-case bare name such as
> `` `Parser` `` (no `.` or `/`, neither in capitals like `LICENSE` nor a build
> file like `Makefile`), by operator decision 22: write `./Name` for such a
> file. The canonical step above already opens each line with its path.
>
> **Two step rules at every plan_version** (no version bump; a plan without
> the field is unchanged): the optional `Regression:` field (K10) holds ONE