feat(board): give the plan a paste= line the operator can actually use
--plan shipped with dir= and command= as separate fields. That is right for a driver, which moves the pane itself and then types the command, and unusable for a person: the first operator to read a block could not act on it at all. Joining an absolute path from one field with a command from another is not a saved line of output. It is the step where a session gets started in the wrong repository - the same failure the absolute dir= exists to prevent, moved from the machine to the human. paste= is the two already joined, cd <dir> && <command>, one thing to select. Both forms stay: the two consumers want the same fact shaped differently, and neither shape serves both. Emitted only alongside command=, never once per block. A `paste=cd X && ` with nothing after it would run the cd and then a bare newline, which fails SILENTLY - the operator ends up in the right directory with no session started and no error to notice. board-selftest: 86 -> 89 checks. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011eKRzhD1RqY2MxvDEkrJAM
This commit is contained in:
parent
6d0fe14d0f
commit
5bea1f8651
10 changed files with 76 additions and 9 deletions
|
|
@ -17,7 +17,7 @@ description: >-
|
|||
user names no repo and no tool — choosing *between* repos is this skill. Not for
|
||||
"where were we" inside the current repo: that is this repo's own STATE.md,
|
||||
already injected at session start.
|
||||
version: "0.16.0"
|
||||
version: "0.17.0"
|
||||
---
|
||||
|
||||
# board — which repo deserves the next session
|
||||
|
|
@ -155,6 +155,14 @@ Blocks are `key=value` and comment lines start with `#`, because a separate driv
|
|||
repo consumes this output. That format is a contract with a consumer outside this
|
||||
repo: never reformat it, and never hand-edit a block before passing it on.
|
||||
|
||||
**Point the operator at `paste=`, not at `dir=` + `command=`.** Those two exist
|
||||
for a driver, which cd's the pane itself and then types the command; `paste=` is
|
||||
the same thing already joined, and it is the only line a human should ever copy.
|
||||
Telling someone to "cd to `dir=` and then paste `command=`" asks them to assemble
|
||||
two fields by hand, which is exactly how a session gets started in the wrong repo.
|
||||
A block with `command_missing=` has no `paste=` at all — say so for those repos
|
||||
rather than letting the operator hunt for a line that is not there.
|
||||
|
||||
## Coverage gaps you must name
|
||||
|
||||
A ranking is only as honest as its inputs, and two gaps are invisible in the answer
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ description: >-
|
|||
covers retiring a broadcast that has become wrong or obsolete: "retract that
|
||||
broadcast", "that announcement is outdated, pull it", "trekk tilbake kringkastingen",
|
||||
"den broadcasten er utdatert".
|
||||
version: "0.16.0"
|
||||
version: "0.17.0"
|
||||
---
|
||||
|
||||
# coord-send — natural-language front door for inter-repo messages
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ description: >-
|
|||
the operator names no model and no tool — choosing the model for the next
|
||||
session IS this skill. Not for choosing which REPO gets the next session:
|
||||
that is the `board` skill.
|
||||
version: "0.16.0"
|
||||
version: "0.17.0"
|
||||
---
|
||||
|
||||
# route — what the next session should run with
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue