@erclx/canon 5.48.0 → 5.49.0

package/claude/skills/review-ui/references/close-out.md

@@ -20,7 +20,7 @@ gh api --paginate 'repos/{owner}/{repo}/pulls/<number>/reviews?per_page=100' --j
 
 ## Write the replacement
 
-Write the full body for this pass to the file `post.md` names, with the heading, the count line, and the Passed table regenerated from what this pass drove. Patching only the marker would leave a count line and an address naming the old head.
+Write the full body for this pass to the file `post.md` names, with the heading, the count line, and the Passed table regenerated from what this pass drove. Patching only the marker would leave a count line and an address naming the old head. A loopback address reads as a local preview here too, as on a first post.
 
 Add one line under the count line, reading the prior head off the standing verdict's marker and the commit count off the compare:
 

package/claude/skills/review-ui/references/drive-copy.md

@@ -0,0 +1,38 @@
+---
+title: Drive a throwaway copy
+description: Steps 4 and 7 of review-ui, which rebuild the copy a preview saves into before the browser opens and check the worker's worktree for a tracked change before the post
+---
+
+# Drive a throwaway copy
+
+Steps 4 and 7 of `review-ui`. A preview that saves what the pass drives would otherwise write the worker's tracked files, and a drag would land in a committed fixture.
+
+A project names the folders its preview writes in `canon/config/preview.json`. The worker starts its server reading a copy of them, and the pass rebuilds that copy at every head so the last pass's drags never reach this one.
+
+## Before the browser opens
+
+Rebuild the copy and record the worktree's state:
+
+```bash
+canon pr drive-copy <number> --baseline --json
+```
+
+Branch on `reason` rather than on the exit code.
+
+- `copied` means the address serves a throwaway copy rebuilt from the worker's worktree. Keep `copied` for the comment.
+- `no-config` means the project declares no preview writes, so drive as usual. The check below still runs.
+- `no-worktree` means no local worktree holds the branch, as for a cloud worker's. Drive, and say in the comment that the worktree check did not run.
+- Any other refusal stops the pass with nothing posted, naming the `reason` and `message` for the dispatcher, since a broken `canon/config/preview.json` would send the drives into the real folders
+
+## Before the post
+
+At the start of Step 7, with the browser closed since Step 6, read whether the drives changed anything git tracks in the worker's worktree:
+
+```bash
+canon pr drive-copy <number> --check --json
+```
+
+- `clean` continues with the post
+- `changed` stops the pass. Step 7 posts it open with every path in `paths` named, and Step 8 ticks nothing, since the boxes ran against a tree the drives rewrote.
+- Leave each changed path as it stands. The worktree is the worker's, so the pass reports a change and never reverts it.
+- A refusal, `no-worktree` and `no-baseline` among them, means the check did not run. Say so in the comment rather than reading it as clean.

package/claude/skills/review-ui/references/post.md

@@ -11,7 +11,7 @@ Step 7 of `review-ui`.
 
 The heading reports whether the branch owes anything, the way the code review's does.
 
-- `## UI review` when a box failed, the sweep found a console error or an overflow, a box was not driven for a cause on the page, or the pass drove no box at all.
+- `## UI review` when a box failed, the sweep found a console error or an overflow, the worktree check read `changed`, a box was not driven for a cause on the page, or the pass drove no box at all.
 - `## UI review closed` otherwise.
 
 A needs-eyes box leaves the review closed, and so does a box not driven for a cause off the page, such as an address that did not answer or a `(local only)` box on a hosted preview, as long as something else was driven.
@@ -24,7 +24,7 @@ A needs-eyes box leaves the review closed, and so does a box not driven for a ca
 
 A pass with 0 failed, 0 need your eyes, 0 passed, and any box not driven looked at nothing, so it has not covered the head. It takes `## UI review` whatever the cause, including a checklist of only `(local only)` boxes on a hosted preview.
 
-- Put a line naming the cause directly under the count line, such as the addresses tried and what each returned, ahead of the address line
+- Put a line naming the cause directly under the count line, such as the addresses tried and what each returned, ahead of the address line, naming a loopback address as A loopback address says
 - The cure is a re-drive on an address that answers, which Step 1 of `review-ui` allows past this verdict
 - Message the controller with the cause and send the worker no `review-address`, since the verdict holds no box a fix worker could change
 - `canon pr lift` refuses a close of this shape as `ui-undriven`, so a violation holds the draft mark
@@ -47,6 +47,10 @@ Driven at `<short-sha>` on <address>, rendered by <renderer>.
 
 ![box <n>](link)
 
+### Changed in the worktree
+
+- `<path>`
+
 ### Needs your eyes
 
 **<n>. <box> (taste)**
@@ -90,10 +94,19 @@ The post takes the length limits alone, with a box's reason under 350 characters
 
 The body opens on its count line, in that order, so the operator reads what they owe before anything else. The second line carries the address, the head, and the renderer, and says the address was driven unverified when it came from the local rung or the launch.
 
-- Drop each section holding no box, along with its heading. Order is fixed: Failed, Needs your eyes, Not driven, then the folded blocks.
+- Drop each section holding no box, along with its heading. The order is fixed as Failed, Changed in the worktree, Needs your eyes, Not driven, then the folded blocks.
 - A box takes exactly one section by its verdict, so a box that fails and also ends in `(taste)` appears once, under Failed
 - Quote page text in backticks as content, never as the pass's own words
 
+### A loopback address
+
+A loopback address has `localhost`, `127.0.0.1`, `0.0.0.0`, or `[::1]` as its host, with any port. It never appears in the post, so the second line reads ``Driven at `<short-sha>` on a local preview, unverified, rendered by <renderer>.`` instead.
+
+- The cause line of a pass that drove no box, and every Not driven entry, name a loopback address it tried as a local preview with its port, such as `a local preview on port 4211`
+- A hosted address posts as written, since it outlives the session, and the close drops it from the evidence comment
+- The evidence comment carries the local link while the pull request is open, for an operator on the same machine
+- `canon pr local --remove` masks a loopback address left on a review's `Driven at` line when the pull request closes
+
 ### A failed box
 
 A box in a section opens on its number and the box as written, in bold, with the reading beneath it in words. A failed box that rests on a read has no image.
@@ -102,6 +115,14 @@ A box in a section opens on its number and the box as written, in bold, with the
 - That link names the frame's path on the frames branch, which stays put while other pull requests' frames are dropped and carries this pass's stamp
 - A later pass therefore never changes the image
 
+### The drive copy and the worktree check
+
+The two `canon pr drive-copy` reads at the start of Steps 4 and 7 each leave a mark on the body, so the operator knows what the drives touched.
+
+- When Step 4 read `copied`, add `Drove a throwaway copy of <copied paths>.` as its own line directly under the address line, naming each path in backticks
+- When Step 7's check read `changed`, list every path from `paths` under Changed in the worktree, in backticks, with no reading beside it. The heading opens, and Step 8 ticks nothing.
+- When either read refused, add `Worktree check did not run, <reason>.` on a line of its own under the address line, so a skipped check never reads as a clean one
+
 ### A needs-eyes box
 
 A needs-eyes box shows its dark and light shots in a two-cell table ahead of anything else it carries, since the operator decides from them without opening the app. A box whose evidence holds one theme still renders both cells.

package/claude/skills/review-ui/references/verb-absent.md

@@ -0,0 +1,18 @@
+---
+title: Resolve the pull request without the verb
+description: Step 1 of review-ui on a target whose CLI predates canon pr head, which reads the number and the head straight off the REST pulls endpoint
+---
+
+# Resolve the pull request without the verb
+
+Step 1 of `review-ui`, read when `canon pr head` returns no record.
+
+Every read here runs on REST, since `gh pr` runs on GraphQL and a cloud session's proxy refuses it. A target whose CLI predates the verb gets no record back, so read the pull request directly:
+
+```bash
+gh api "repos/{owner}/{repo}/pulls?head={owner}:$(git branch --show-current | jq -Rr @uri)&state=open" --jq '.[].number'
+gh api repos/{owner}/{repo}/pulls/<number> --jq .head.sha
+```
+
+- With no number named, take the open pull requests on the current branch, and stop when that prints anything but one number
+- A named number skips that lookup, since this checkout's branch need not be the pull request's

package/claude/skills/role-orchestrator/SKILL.md

@@ -38,10 +38,11 @@ No surface carries cross-version sequencing, so report none, since reasoning spa
 
 ## Runbooks on request
 
-A compaction is a moment this skill cannot detect, so the human asks for each side of it and this skill reads the matching runbook.
+The human asks for each side of a compaction, and this skill reads the runbook.
 
 - On a request to write the handoff, follow `${CLAUDE_SKILL_DIR}/references/orchestrator-handoff.md`. It sends the generic half to `canon:session-map` and adds decisions taken under delegated authority.
 - That map follows `${CLAUDE_SKILL_DIR}/../session-map/references/session.md`. Write nothing to the handoff that the board, a task file, or a groundwork folder already carries.
+- Hand launch: `${CLAUDE_SKILL_DIR}/references/orchestrator-hand-launch.md`
 - A lesson about how to work goes to the owning task's Findings, as a bold-labeled line per `${CLAUDE_SKILL_DIR}/../task-board/references/tasks.md`
 - On a request to resume after a compaction, read `${CLAUDE_SKILL_DIR}/references/orchestrator-resume.md`, which reads that file back with the board and the groundwork behind the live work
 
@@ -108,7 +109,7 @@ The handback runbook holds how the message is addressed and worded, what to do w
 
 ### Constraints from the tracks in flight
 
-A plan written here targets a tree several branches are changing, so it names each in-flight track's file set as a constraint, read from that track's Touches column. State for each set which of the two acts it forbids, per Constraints in `${CLAUDE_SKILL_DIR}/../plan-feature/references/plan.md`.
+A plan written here targets a tree several branches are changing, so it names each in-flight track's file set as a constraint, read from the plan its row links. State for each set which of the two acts it forbids, per Constraints in `${CLAUDE_SKILL_DIR}/../plan-feature/references/plan.md`.
 
 - A bare path list leaves the worker guessing, and can end up forbidding the repair of a citation the change broke
 - A shared path forbids an act only where the conflict check in `orchestrator-dispatch.md` holds the pair. Otherwise it names what the second branch to merge rebases over.

package/claude/skills/role-orchestrator/references/orchestrator-dispatch.md

@@ -125,7 +125,7 @@ No practitioner source serializes on a shared file. Each builds in parallel and
 Read `canon sessions list --json` for the branches in flight as well as the board, since a hand-launched track carries no row, and read the plan of any branch no row names.
 
 - `canon tasks validate` and `canon tasks plan-reach` report the paths two rows share, a candidate list for the five holds and the paths a dispatch names
-- A shared folder means a Touches cell claimed it bare, so narrow that cell rather than reading the folder as a sweep
+- A shared folder means a plan declared it bare, so narrow that plan's list rather than reading the folder as a sweep
 - A declared set predicts rather than bounds, since `canon:context-fold`, `canon:docs-sync`, and the drift stages write past every plan
 - Such a crossing changes what the second branch rebases over, not whether a row holds, and `canon tasks plan-reach` at `canon:git-ship` step 5 names it
 

package/claude/skills/role-orchestrator/references/orchestrator-hand-launch.md

@@ -0,0 +1,60 @@
+---
+title: Orchestrator hand launch
+description: The one lean prompts file the orchestrator writes when the operator launches sessions by hand, with its path, overwrite rule, shape, and a filled example
+---
+
+Run this when the operator launches sessions by hand rather than through `claude --bg`. The rules every launch shares stay in `orchestrator-launch.md`.
+
+# Hand launch
+
+When the operator launches sessions by hand, write every prompt to one file, `.canon/tmp/dispatch/prompts.md`, and overwrite it at each wave. It lists every row with a session not yet launched. A row launched from an older copy and again from a newer one would build twice, and the branch check in `orchestrator-dispatch.md` catches that.
+
+The operator opens the file, reads one lead line, and pastes one fence per session. The shape is fixed:
+
+- An H1, `# Dispatch prompts`, then one lead line carrying the measured head, the merge order, and the folder to open each session in
+- An H2 per task as `## <label>: <title>`, an H3 per role as `### Worker` or `### Reviewer`, a `Model: <model>.` line, and a `text` fence
+- In the fence, the command at position zero, then `Controller: <sessionId>`, then only context the plan does not carry, one line each
+
+Keep the command at position zero per `### Position zero` in `orchestrator-launch.md`, and carry only what `### What the brief may carry` there allows. Leave out the answer-slot default and anything else the plan states.
+
+The `Controller:` line replaces the background template's message clauses, which `role-worker` and `session-relay` already own. `auto-ship` Step 0 loads `role-worker`, so the fence needs nothing more.
+
+- A reviewer launched by hand takes the `### Reviewer` H3 under its row's H2, with the sibling facts `orchestrator-reviewer-launch.md` lists
+- Its `<number>` exists once the worker opened its pull request, so a later wave carries `### Reviewer` alone under the row, and the launched worker's H3 is gone
+
+The first wave carries the worker. The wave after its pull request opens carries the reviewer alone.
+
+````markdown
+# Dispatch prompts
+
+Head `<head>`. Merge `<label-a>` first, then `<label-b>`. Open each session in the repository root.
+
+## <label-b>: <title>
+
+### Worker
+
+Model: opus.
+
+```text
+/canon:auto-ship .canon/plans/feature-<slug>.md
+Controller: <sessionId>
+<branch-a> edits the section of <file> this plan leaves alone. Rebase over it when told.
+```
+````
+
+````markdown
+# Dispatch prompts
+
+Head `<head>`. Merge `<label-a>` first, then `<label-b>`. Open each session in the repository root.
+
+## <label-b>: <title>
+
+### Reviewer
+
+Model: opus.
+
+```text
+Run /canon:role-reviewer, then /canon:review-pr <number>
+Controller: <sessionId>
+```
+````

package/claude/skills/role-orchestrator/references/orchestrator-launch.md

@@ -12,6 +12,7 @@ Run this once `orchestrator-dispatch.md` has cleared a row, or from its planning
 - [Dispatch to address a review](#dispatch-to-address-a-review)
 - [Dispatch to plan a row](#dispatch-to-plan-a-row)
 - [Dispatch a talk session](#dispatch-a-talk-session)
+- [Hand launch](#hand-launch)
 - [Dispatch a reviewer](#dispatch-a-reviewer)
 
 ## Dispatch
@@ -156,6 +157,10 @@ Read the session's `sessionId` off the launch output, carry it in this session's
 
 The map exists only once the handoff writes it, so this session's own launches, read with the prior map, are what the first wind-down reads talk sessions from.
 
+## Hand launch
+
+Read `${CLAUDE_SKILL_DIR}/references/orchestrator-hand-launch.md` when the operator launches sessions by hand. It states the single prompts file at `.canon/tmp/dispatch/prompts.md`, the lean shape of each fence, and a filled example, while the background templates above keep their full controller paragraph.
+
 ## Dispatch a reviewer
 
 Read `${CLAUDE_SKILL_DIR}/references/orchestrator-reviewer-launch.md` when `orchestrator-review-dispatch.md` sends a pull request to a dispatched reviewer, for the code, cloud, and UI reviewer shapes.

package/claude/skills/role-orchestrator/references/orchestrator-parked.md

@@ -32,7 +32,7 @@ The blocker cell states what the row waits on, and each kind is tested different
 
 ### A hold behind a track in flight
 
-The validator tests the file the cell cites against the Touches column of every `## Run now` row. A track that merged since the row was parked is no longer in flight, whatever the sets still share.
+The validator tests the file the cell cites against the files every `## Run now` row's plans declare. A track that merged since the row was parked is no longer in flight, whatever the sets still share.
 
 - Re-test the cell under the conflict check in `orchestrator-dispatch.md` too, since a row parked on a shared file alone holds on nothing and moves up
 - A cell naming the file in prose rather than backticks cites nothing, so rewrite the hold in the board's spelling and the next run picks it up

package/claude/skills/role-orchestrator/references/orchestrator-reviewer-launch.md

@@ -9,7 +9,7 @@ Run this once `orchestrator-review-dispatch.md` has sent a pull request to a dis
 
 `review-pr` is a single pass rather than a role, so a launch naming it alone reaches no `role-reviewer` and owes no message. Reach the role first on this launch, the way the planning shape in `orchestrator-launch.md` reaches `role-planner`. `orchestrator-review-dispatch.md` decides whether a pull request takes this shape at all.
 
-No branch and no worktree are entered here. The reviewer reads the pull request at the head `review-pr` resolves and writes the comment and its body file alone.
+No branch and no worktree are entered here. The reviewer reads the pull request at the head `review-pr` resolves and writes the comment and its body file alone. A reviewer the operator launches by hand takes the `### Reviewer` H3 that `orchestrator-hand-launch.md` states.
 
 ```bash
 claude --bg --model <model> -n "reviewer-<project>-<number>" "Run /canon:role-reviewer, then /canon:review-pr <number>. Your controller is the session whose sessionId is <dispatcher-id>. Resolve its current name from that id through canon sessions list --json, which carries sessionId per row, at the moment you send, and never resolve an addressee by name prefix. When the pass posts under ## Review, message the worker holding the branch to run review-address, carrying your own sessionId, and send it to the controller instead when no worker resolves. When it posts ## Review closed, run canon pr lift <number> --json and message the controller with the heading, the count line, and the reason the verb returned, unless that reason names the UI review as still open or missing. Message the controller again if you stop on a question."

package/claude/skills/role-planner/SKILL.md

@@ -39,7 +39,7 @@ Each item below is something a record needed and a launch string did not carry.
 - The task file, and its `## Findings` before deciding anything, since a row can carry its own disproof under a title still stating the original claim
 - The source files themselves, opened rather than summarized. Never a count quoted from the task file, which goes wrong or stale.
 - `CLAUDE.md` and the context entries the row touches, for the decision and the alternative it was taken against rather than for the decision alone
-- `.canon/tasks/priority.md` for the row's Touches column and its blocker. Read it for the shared-path lines and holds of the constraint block, never as a gate a plan must clear.
+- `.canon/tasks/priority.md` for the row's blocker and the plan each running row links. Read those plans for the constraint block's shared paths and holds, never as a gate a plan must clear.
 
 ### Reads for a feature plan alone
 

package/claude/skills/role-worker/SKILL.md

@@ -50,6 +50,8 @@ A painted pull request needs a server in this worktree for `canon pr local` to f
 - Wait up to 60 seconds for the verb to read `ok`, then ship either way. A stack with no `dev` script gets no start, and `pr-evidence` reports `no-server`.
 - Never detach it with `nohup`, `setsid`, or `disown`, since the owning session is the stop. `canon worktrees reclaim` ends any listener left in a worktree it removes.
 
+Run `canon pr drive-copy --json` before starting `dev`. On `copied`, start it with `env` set to `copyRoot`, so the operator's address serves the copy. On `no-config`, start it as it is. On a refusal, start nothing and send the controller the `reason`, since a broken config would send drives into tracked folders.
+
 A hand-run `git-ship` or `git-pr` starts no server, since only a worker has a lifetime to own one.
 
 ### Building against a design reference
@@ -86,7 +88,7 @@ The controlling session cannot watch this one build, so the messages below are o
 
 ### The pull request announcement
 
-Announce the pull request as the ship chain's pull request step returns, carrying the number, the branch, and the task it closes. That transition is the one moment only this session knows, and the controller's review poll no longer starts on a dispatch.
+Announce the pull request as the ship chain's pull request step returns, carrying the number, the branch, the head sha, the CI state, the task it closes, and each departure from the plan. That transition is the one moment only this session knows, and the controller's review poll no longer starts on a dispatch.
 
 - Carry the reach in that message, being the paths this branch wrote that another live plan or `## Run now` row holds, and who holds each, which `canon tasks plan-reach` reports as `claimed`
 - Report each as a rebase the controller should order, never as a breach, since sharing a path is not a hold
@@ -123,7 +125,7 @@ A worker that improvised this read polled issue comments, never saw a UI close p
 
 ### Addressing
 
-Address the session the launch named, and the reviewer by its dispatch's sessionId, each as a `sessionId` rather than a name. `canon:session-relay` turns that id into an address and carries the send, falling back to a copyable block where no send tool exists.
+Address the session the launch named, and the reviewer by its dispatch's sessionId, each as a `sessionId` rather than a name. `canon:session-relay` turns that id into an address and carries the send, falling back to a copyable block where no send tool exists. A `Controller: <sessionId>` line names the controller.
 
 Ask the operator when the launch named nobody and a person is there, putting candidate rows through the structured question surface. The halt is the cheaper error, since a message sent to the wrong session reports success and is lost.
 

package/claude/skills/session-compact/references/handoff-note.md

@@ -39,7 +39,9 @@ Name what was not touched too. A session that changed no source says so, since a
 
 One bullet per decision, each naming what it beat. A decision with no rejected alternative reads as arbitrary and gets reopened by the next session that dislikes it.
 
-Where a decision rests on a measurement, give the number rather than the conclusion. `27 spacing values became 7` survives a reader disagreeing with it, where `the spacing was tidied` does not.
+- Keep each bullet under 200 characters, and give a decision needing more an H3 of its own and a short paragraph
+- The note holds to the six criteria under `### Structure` in `${CLAUDE_SKILL_DIR}/../plan-feature/references/plan.md`
+- Where a decision rests on a measurement, give the number rather than the conclusion. `27 spacing values became 7` survives a reader disagreeing with it, where `the spacing was tidied` does not.
 
 ### `## What is open`
 

package/claude/skills/session-map/references/session.md

@@ -66,7 +66,7 @@ Three sections form the core, in this order, and every session fills all three.
 - `## Mistakes worth not repeating`: what went wrong and the rule it yields
 - `## Standing cautions`: commands that lie, tools that measure the wrong tree, and anything unbacked
 
-Add a section only for content that fits none of the three and would otherwise be lost.
+Add a section only for content that fits none of the three and would otherwise be lost. Every section holds to the six criteria under `### Structure` in `${CLAUDE_SKILL_DIR}/../plan-feature/references/plan.md`.
 
 ## Writing one
 

package/claude/skills/task-board/references/board.md

@@ -91,9 +91,9 @@ A collision with running work blocks a task only where no merge settles it, bein
 
 ### The `Touches` cell
 
-A `Touches` cell is the first three paths of its plan's `**Files to touch:**` and a count of the rest, the union in line order for a sliced task. It states what the branch sets out to write, and a running branch outgrows it.
+A `Touches` cell counts its plans' declared files and names the two fullest folders, as in ``12 files under `src/tasks/`, `claude/skills/` ``. The linked plan holds the file list, which the overlap checks read.
 
-- `canon tasks plan-reach <plan>` reads the current reach off the branch's diff
+- `canon tasks plan-reach <plan>` reads the reach a running branch grew to
 - Change the plan's list to change the cell. A worker never edits this board.
 
 ### Cell width

package/claude/skills/task-board/references/tasks.md

@@ -83,7 +83,7 @@ Two headings, `## Outcomes` and `## Findings`. Outcomes are future and checkable
 
 - Add no third heading. Status stays inline on an outcome rather than becoming an "In progress" section.
 - Outcomes stay a checklist, since the board tools read them by their `- [ ]` line
-- Open each finding with a bold label naming its source and date, as in `- **planner, 2026-10-11:** <finding>`. Keep it to a few sentences, moving anything longer into the plan or groundwork folder.
+- Open each finding with a bold label naming its source and date, as in `- **planner, 2026-10-11:** <finding>`. Past 200 characters it becomes a paragraph, and the plan holds anything longer.
 
 ### Sizing outcomes
 

package/docs/agents/records.md

@@ -57,5 +57,5 @@ Branch on `reason` in the `--json` record, not the exit code.
 ## See also
 
 - `canon records ordinal <kind> <slug> --claim`: reserve the next intake or groundwork ordinal
-- `canon records validate <kind> --help`: where a record folder disagrees with its standard
+- `canon records validate <kind> [record] --help`: where a record disagrees with its standard, plus a `structure` report that never sets the exit
 - `canon records stale --help`: when the requirements record was last reviewed

package/docs/workflow/parallel-features.md

@@ -32,7 +32,7 @@ Assert the orchestrator role in one warm session with `canon:role-orchestrator`.
 
 - To pick otherwise, rewrite that line as `overridden at execution to <pick>,` plus the measurement, and add one line to the open task's `## Findings`
 
-- `canon records validate plans` reports a plan breaking its standard, and takes `groundwork`, `intake`, and `teach`
+- `canon records validate plans [plan]` reports a plan breaking its standard, plus `structure` misses that never set the exit, and takes `groundwork`, `intake`, and `teach`
 - `canon records push` and `canon records pull` carry `.canon/` to and from a private repository. See [records](../agents/records.md).
 - `canon records size`, `canon records prune-tmp`, and `canon records stale canonical` report folder size, idle scratch, and releases since the requirements review
 - `canon tasks archive` moves a shipped plan to `.canon/plans/archive/` and retargets the task's `Plan:` line
@@ -58,6 +58,6 @@ Merge order matters only when two branches touch the same file. Expect to rebase
 - A parked row is reported when its cited task reached the trunk, whether the cell links it or names its bare label
 - A group header must be the columns the group owns, a `Touches` cell must match its plan, and a `Waiting on` cell renders at most 120 characters
 
-`canon:task-board` creates a task file, and `canon:task-complete` marks outcomes. The `post-merge` hook archives the task a merged pull request closed, with its plan, and a `post-rewrite` hook does the same for a rebase pull. Both archive only when the merge carried a PR number and the task is closed.
+`canon:task-board` creates a task file, and `canon:task-complete` marks outcomes. The `post-merge` hook archives the task a merged pull request closed, with its plan, and a `post-rewrite` hook does the same for a rebase pull. Both archive a closed task whose merge carried a PR number, and a slice merged before then moves only its own plan.
 
 `CANON_SKIP_RECLAIM`, `CANON_SKIP_UPGRADE`, and `CANON_SKIP_PLUGIN_UPDATE` turn off the three hook steps that act on the machine.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/canon",
   "type": "module",
-  "version": "5.48.0",
+  "version": "5.49.0",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
   "license": "MIT",
   "bin": {