@erclx/canon 5.46.0 → 5.48.0

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

@@ -21,11 +21,12 @@ The third trigger reaches a window the first two cannot. A session with three wo
    - A finding that changes a rule goes to the standard or rule that states it
    - One that changes another task goes to that task's Findings, and one that overturns a groundwork lean to that folder marked answered
 3. Archive what closed.
-   - A task whose outcomes are all `[x]` and whose pull request merged is archived by the `post-merge` hook through `canon tasks archive`, plans included
+   - A task whose outcomes are all `[x]`, or all `[x]` beside `Operator check:` lines, and whose pull request merged is archived by the `post-merge` hook through `canon tasks archive`, plans included
    - Run `task-complete` to archive one the hook left in place
    - A task whose outcomes are standing policy never closes, so hand it to a worker to encode the policy where it is enforced, then cut the outcomes with the reason and archive once that branch merges
    - Encoding it from this session would write a tracked file, which `## Boundaries` in the skill body forbids
-   - A merged task whose only open outcomes need the operator or another repository never archives, since `canon tasks archive` refuses `open-outcomes`. Strike each one on the task file as `- ~~<outcome>~~ <reason>`, with the reason on the same line, then archive. The task files are gitignored scratch, so this session may edit them.
+   - An outcome marked `- [ ] Operator check: <outcome>` never blocks the archive. The hook prints no record, so read the archived file's `Operator check:` lines into the report's `Operator checks:` line and leave them unticked.
+   - A merged task whose only open outcomes another repository owes, or that an operator owns and nobody marked, never archives, since `canon tasks archive` refuses `open-outcomes`. Strike each one on the task file as `- ~~<outcome>~~ <reason>`, with the reason on the same line, then archive. The task files are gitignored scratch, so this session may edit them.
    - Strike only an outcome the operator or another repository owes. An open outcome this repository owes stays on the board, and the task stays with it.
    - Send a struck outcome that another repository owes to that repository's orchestrator through `session-relay`, which resolves the address, and let the receiver file it with `task-board` on its own board. `task-board` here would file it on this board. Name it in the report for the operator when no such session is live.
    - List every struck outcome in the report's `Struck:` line, so the work is carried by a named owner rather than lost to the strike
@@ -45,6 +46,7 @@ The third trigger reaches a window the first two cannot. A session with three wo
 Findings placed: <finding> → <destination>
 Archived: <task>
 Struck: <outcome>, owed by <operator or repository>, <reason>
+Operator checks: <outcome>, left unticked on <task>
 Promoted: <task>, touches <surfaces>, parallel with <task>, sharing <paths or none>
 Serialized: <task> behind <task>, held on <dependency, contract, relocation, sweep, or reason>
 Backlogged: <task>, because <what stopped being near-term>

package/claude/skills/role-reviewer/REQUIREMENT.md

@@ -14,7 +14,7 @@ Each launch also restates the reviewer's bounds, though they belong to the role.
 ## Must
 
 - The role is asserted, with writes bounded to the comment and body file the pass posts, and the tracked file, branch, worktree, board, and commit named as outside them
-- Every file read a finding rests on goes through `git show <head>:<path>` at the resolved head, and launch-carried cross-branch facts are inputs
+- Every file read a finding rests on goes through `git show <head>:<path>` at the resolved head, and launch-carried cross-branch facts are inputs. A task list, if the host has one, tracks each step.
 - The fix, a draft lift by any route but `canon pr lift`, and the merge are refused whoever asks, naming each owner, and the lift runs after a close is posted
 - An open pass sends the worker the `review-address` dispatch and this session's id, else the controller the cause, and a close sends the lift's reason unless the other review is open or missing
 - A re-review stays with the reviewer that took the first pass while it is live, and a block is messaged before it becomes an interactive prompt

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

@@ -31,6 +31,8 @@ The session writes its comment and nothing tracked. Each kind of reviewer writes
 - Resolve `.canon/plans/`, `.canon/tasks/`, and `.canon/tmp/` at the main worktree root, and send the body file as a heredoc, the main-root route `session-worktree` states
 - Report a plan or task that fails to resolve there as unreadable, naming the path, rather than reviewing as though the branch had none
 
+Keep a task list from launch, one item per step of the pass, and tick each as it completes. Skip it on a host that offers no list tool, since the list is for the operator watching and not a gate.
+
 Review the pull request the launch named. Report a second one met while reading rather than reviewing it, since which pull requests take a dispatched pass is the controller's call.
 
 ## What to read and what to leave
@@ -54,11 +56,12 @@ Nobody watches this pass, so the messages below are owed and nothing else. The w
 
 ### The address-review dispatch
 
-Send it to the worker holding the branch as `review-pr` Step 5 returns an open `## Review`, or as `review-ui` reports an open `## UI review`.
+Send it to the worker holding the branch as `review-pr` Step 5 returns an open `## Review`, or as `review-ui` reports an open `## UI review` that drove a box. A `## UI review` that drove no box goes to the controller with its cause instead, per `${CLAUDE_SKILL_DIR}/../review-ui/references/post.md`.
 
 - Carry the pull request number, the heading, that step's count line verbatim, and this session's own sessionId for the worker's reply
 - Resolve the worker with `canon sessions list --branch <branch> --json`, where `<branch>` is the pull request's head branch
 - Send to it only when exactly one session comes back with its confidence reading `confirmed`
+  - Count a row reading `via: "listener"` as confirmed, since its messaging socket accepted a connection. Never read it as `via: "socket"`, which rests on a socket file existing alone.
 - On zero, on any other count or confidence, or on a refusal, send the same message to the controller, naming the cause the roster read gives
   - Say the roster rests on sockets from another pid namespace, so the worker may be live and unconfirmed, when a row reads `via: "socket"` or an empty roster carries a `foreignDead` count above zero
   - Say the roster rests on a pid answering alone, since start times could not be read, when the confidence reads `unverified` and no row reads `via: "socket"`

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

@@ -13,7 +13,7 @@ The channel fails on the worker's side. Blocks open prompts nobody is attached t
 
 ## Must
 
-- Session scratch resolves at the main worktree root, and a plan that fails to resolve is reported unreadable from there rather than absent
+- Session scratch resolves at the main worktree root, and a plan that fails to resolve is reported unreadable from there rather than absent. A task list, where the host has one, tracks each slice.
 - The announcement carries the number, branch, task, reach, any uncleared spend, and any row the build turned up, and a painted diff has its preview server running before the pull request opens
 - A block goes out as a message before it becomes a prompt, a fan-in member's done message carries its branch and head commit, and a review wait that times out reaches the controller
 - The plan's scope freezes at dispatch, and a late ask is sorted into a defect, a follow-up row, or an addition on the operator's word

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

@@ -23,6 +23,7 @@ This body states the role, the boundaries, and the channel, and starts no step o
 - Resolve `.canon/plans/`, `.canon/tasks/`, `.canon/review/`, and `.canon/ready/` at the main worktree root, never the linked worktree. Being gitignored, they are absent there rather than empty.
 - Report a plan that fails to resolve as unreadable from here, naming the main-root path. Reporting the task as having no plan is wrong about the world, and a reader cannot tell the two apart.
 - Build the plan the launch named. Never write a second one when the path fails to resolve, since a row citing a plan already has one.
+- Keep a task list from launch, one item per slice, and tick each as its slice lands. Skip it on a host that offers no list tool, since the list is for the operator watching and not a gate.
 
 ### Ready folders and the draft mark
 

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

@@ -33,11 +33,11 @@ A successful decline returns one record whose fields match `canon tasks archive`
 | -------------------- | ------------------------------------------------------------------------ |
 | `from`, `to`         | The task's old and new path                                              |
 | `priorityRowRemoved` | Whether a `priority.md` row was dropped                                  |
-| `backlogRowRemoved`  | Whether a `backlog.md` row was dropped, a field archive lacks            |
+| `backlogRowRemoved`  | Whether a `backlog.md` row was dropped                                   |
 | `indexRegenerated`   | Whether the index was rewritten                                          |
 | `plans`              | A `from` and `to` per live plan the task last cited, empty if none moved |
 
-`backlogRowRemoved` is decline's own, since a task can be declined straight off `backlog.md` and archive never checks that file.
+A task can be declined straight off `backlog.md`, so decline checks that file as well as `priority.md`. Archive does the same and reports the same two fields.
 
 ## Step 3: route on a refusal
 

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

@@ -198,7 +198,7 @@ Session history and ordering both have homes off the task file.
 
 ## Archiving
 
-Never delete a task file. A shipped task moves to `.canon/tasks/archive/` under its own name through `canon tasks archive`, and the live index regenerates without it. What the verb does and refuses on is at `canon tasks archive --help`, and a flat `.claude/task-archive/` names an older binary rather than a second archive.
+Never delete a task file. A shipped task moves to `.canon/tasks/archive/` under its own name through `canon tasks archive`, and the live index regenerates without it. What the verb does and refuses on is at `canon tasks archive --help`.
 
 ### The plan and ready folder
 
@@ -209,4 +209,6 @@ Archiving a task archives its plan alongside it when the task is that plan's las
 
 ### Open outcomes
 
-A task with an open outcome stays on the board, and so does its plan. Close it, or cut an abandoned outcome by striking its body, as `- ~~<outcome>~~ <why>`, which reads as cut whatever its checkbox holds, so a task of cut outcomes still archives.
+A task with an open outcome stays on the board with its plan. Close it, or cut an abandoned one by striking its body, as `- ~~<outcome>~~ <why>`, which reads as cut.
+
+An operator-only check outside this repository takes `- [ ] Operator check: <outcome>`, written before the pull request opens. It closes unticked.

package/claude/skills/task-complete/SKILL.md

@@ -43,6 +43,7 @@ For each unchecked outcome, decide whether the diff shipped the behavior it name
 
 - Mark only outcomes already written on the board. Never infer a new task from the diff.
 - Match on the behavior an outcome describes, not on filenames or commit subjects. The path match above only narrowed which task files to open.
+- Never tick an outcome marked `Operator check:`, since a diff cannot prove a check only the operator can run.
 - Leave an outcome `[ ]` when the diff is ambiguous. An unmarked shipped outcome costs one manual edit, while a wrongly marked one hides work that never happened.
 - Do not touch task files the diff does not relate to.
 

package/claude/skills/task-complete/references/archive.md

@@ -8,7 +8,7 @@ description: How task-complete confirms a task's work reached main, runs canon t
 The Archive mode of `task-complete`. The session reads this file when the request names a task file already shipped.
 
 - The `post-merge` git hook archives the task a merge closed, so a request here is usually one the hook could not resolve. Run the steps against whatever it left in place.
-- `canon tasks archive` moves the file, edits `priority.md`, and regenerates the index as one unit. The hook calls the same command, so a hand-rolled move drifts from the unattended path.
+- `canon tasks archive` moves the file, edits `priority.md` and `backlog.md`, and regenerates the index as one unit. The hook calls it too, so a hand-rolled move drifts from the unattended path.
 
 ## Step 1: confirm the work reached main
 
@@ -45,6 +45,7 @@ A successful archive returns one record naming what moved.
 | -------------------- | --------------------------------------------------------------------- |
 | `from`, `to`         | The task's old and new path                                           |
 | `priorityRowRemoved` | Whether a `priority.md` row was dropped                               |
+| `backlogRowRemoved`  | Whether a `backlog.md` bullet was dropped                             |
 | `indexRegenerated`   | Whether the index changed                                             |
 | `plans`              | A `from` and `to` per live plan the task last cited, in `Plan:` order |
 
@@ -55,7 +56,8 @@ An empty `plans` means the task cited no live plan, or a sibling still holds eve
 Each reason has one resolution, and none of them is to archive around it.
 
 - `open-outcomes`: the named outcomes are unmarked or genuinely open. Run `task-complete` when the work shipped unmarked, and leave the task on the board when the outcome is real.
-  - An outcome only the operator or another repository can close is the exception. The orchestrator's merge sweep strikes it with its reason and lists it in the report, per `${CLAUDE_SKILL_DIR}/../role-orchestrator/references/orchestrator-refill.md`, and the archive then runs. An outcome this repository owes is never struck for that.
+  - An outcome only the operator can check is marked `- [ ] Operator check: <outcome>` rather than struck, which the archive passes and the record lists under `operatorChecks`. The mark has to land before the pull request opens.
+  - Abandoned work, an outcome another repository owes, and an operator outcome nobody marked in time take the strike. The orchestrator's merge sweep strikes it with its reason and lists it in the report, per `${CLAUDE_SKILL_DIR}/../role-orchestrator/references/orchestrator-refill.md`, and the archive then runs. An outcome this repository owes is never struck for that.
 - `ambiguous`: two tasks name one pull request, the misfile `${CLAUDE_SKILL_DIR}/references/tasks.md` rules out. Resolve the citation by hand, since no sweep repairs it.
 - `earlier-slice`: the number is listed on the task but is not the last. Leave the task on the board, and its last slice's merge archives it.
 
@@ -80,4 +82,4 @@ Leave `TASK-ARCHIVE.md` alone when it is present in the archive folder. It recor
 
 ## Step 4: clear prose naming the task
 
-The command drops the row from `.canon/tasks/priority.md` and leaves prose alone. Remove any sentence that still names the archived task or counts the changed rows, since a stale count reads as board state.
+The command drops the row from `.canon/tasks/priority.md` and the bullet from `.canon/tasks/backlog.md`, and leaves prose alone. Remove any sentence that still names the archived task or counts the changed rows, since a stale count reads as board state.

package/claude/skills/ui-checklist/SKILL.md

@@ -23,11 +23,11 @@ An automatable change already covered by a test written during implementation is
 
 ## The checklist
 
-Group visual items by feature area. Use `- [ ]` checkbox syntax, and write each item as the action and the result a person is looking for, so a reviewer who did not build the change can run it.
+Group visual items under a bold label per feature area, at most five boxes a group, and split a larger area into two labels. Use `- [ ]` checkbox syntax, and write each item as the action and the result a person is looking for, so a reviewer who did not build the change can run it.
 
-```markdown
-**What to verify visually:**
+The evidence comment already heads the list with `## What to look at`, so the file opens on its first feature label with no heading line of its own.
 
+```markdown
 **<Feature area>**
 
 - [ ] <route>[, <width>]: <verb> <target> → <expected visual result>

package/docs/agents/migrate.md

@@ -18,13 +18,13 @@ kind: reference
 | `rule-layout`      | A flat installed-rule layout onto the `canon/`-wrapped one                                                                                  |
 | `scratch-evidence` | A folder a durable record cites out of `.tmp/`, with its citations                                                                          |
 | `record-layout`    | Review receipts, memory archives, feedback, renders, picks, and evidence into their current folders                                         |
-| `session-defaults` | The seeded session defaults into an existing `.claude/settings.json`: `Agent` and `Task` denied, auto memory off                            |
+| `session-defaults` | The seeded session defaults into an existing `.claude/settings.json`: `Agent`, `Task`, and both merge commands denied, auto memory off      |
 
 - `skill-names` takes no `--scope`, and skips the changelog, eval transcripts, and the pointer each renamed `draft-` skill leaves at its old name
 - `surface-roots` leaves `rules/`, `skills/`, `hooks/`, and `settings.json` where Claude Code reads them
 - `rule-layout` classifies each flat file against the stamp as clean, edited, or unclaimed. Clean and edited files move untouched, and an unclaimed name stays.
 - `record-layout` labels each evidence folder `(pick)` or `(evidence)` in the dry run
-- `session-defaults` adds a key only when absent. It never removes a deny entry or changes a set `autoMemoryEnabled`, and a missing settings file is nothing to do.
+- `session-defaults` adds a key only when absent, merge entries included, and each older project runs it once. `--write` restores a removed `Agent` or `Task` and never removes a deny entry.
 
 ## Output
 

package/docs/target/migrations.md

@@ -150,9 +150,9 @@ The wireframes record is retired, and nothing deletes what a project holds.
 
 The toolkit no longer seeds `canon/ARCHITECTURE.md`, and a held file and its `CLAUDE.md` import stay. Move a trap a session would hit into that domain's `## Gotchas`, then delete the file and its `@canon/ARCHITECTURE.md` line.
 
-## Deny subagents and turn auto memory off, once
+## Deny subagents and merges, and turn auto memory off, once
 
-The seeded `.claude/settings.json` now denies the `Agent` and `Task` tools and sets `autoMemoryEnabled` to `false`. `canon claude sync` never rewrites a settings file you hold, so it warns while the file holds neither default. Removing the deny later to allow subagents draws no warning.
+The seeded `.claude/settings.json` now denies the `Agent` and `Task` tools and both merge commands, and sets `autoMemoryEnabled` to `false`. `canon claude sync` never rewrites a settings file you hold, so it warns while the file holds no default or lacks a merge entry. Removing `Agent` and `Task` later draws no warning.
 
 ```bash
 canon migrate session-defaults --json
@@ -161,6 +161,8 @@ canon migrate session-defaults --write --json
 
 The verb only adds a key that is absent. A person who wants auto memory back sets it in their own `.claude/settings.local.json`.
 
+The verb adds `Bash(canon pr merge:*)` and `Bash(gh pr merge:*)` so a session cannot merge. A project migrated before them runs `--write` once more, which also restores `Agent` and `Task` for a person who removed them to allow subagents, so remove them again after.
+
 ## Move the capture cases out of the harness, once
 
 A web project's `e2e/screenshot.ts` is a config, so sync overwrites it. It now loads `CASES` from a seeded `e2e/capture/cases.ts` that sync copies once and never overwrites. Cases edited in the old harness leave the working tree on the first sync and stay in git history.

package/docs/workflow/operating-model.md

@@ -32,9 +32,9 @@ One warm session holds the cross-feature call and reviews. Cold worker sessions
 5. The reviewer tells the session holding the branch to run `review-address`, found with `canon sessions list --branch`, once a pass posts a finding at any severity.
 6. The worker addresses the findings, rebases onto `origin/main` if a sibling landed on its files, pushes, and asks that reviewer for a re-review of the added commits.
 7. A pass posts `## Review` while anything is open and `## Review closed` when nothing is. The reviewer then runs `canon pr lift`.
-8. The human merges. The orchestrator tells any trailing worker whose files the merge touched to run `review-address`, which rebases.
+8. The human merges with `canon pr merge <number>`. The orchestrator tells any trailing worker whose files the merge touched to run `review-address`, which rebases.
 
-Each worker halts at the PR, and the merge stays a human gate.
+Each worker halts at the PR, and the merge stays a human gate. `canon pr merge` squashes with the body's Summary, Key changes, and Technical context as the message, and the seeded deny rule covers the forms an agent writes by default. The merge button stays for a bot's pull request, such as a dependency bump or a release.
 
 ## The review layer
 

package/docs/workflow/zshrc-aliases.md

@@ -17,6 +17,7 @@ A hand-written block without markers is detected through its `alias clp=` line,
 ```zsh
 # >>> canon aliases >>>
 TOOLKIT="/path/to/toolkit"
+export CLAUDE_CODE_ENABLE_TODO_TOOLS=1
 
 alias cl='claude'
 alias clr='cl -r'
@@ -32,6 +33,8 @@ alias clpac='clpa --cwd .'
 # <<< canon aliases <<<
 ```
 
+The export gives a session started from your terminal the task tools, which Claude Code reads before it starts, so workers and reviewers can show their checklist on `Ctrl+T`. A background session has them without it.
+
 To opt out, delete the block and run `bun install` and `bun link` yourself. Bash takes the block unchanged in `~/.bashrc`, pasted by hand. Bootstrap writes `~/.zshrc` alone.
 
 ## What each one does

package/package.json

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

package/scripts/core/bootstrap.sh

@@ -26,6 +26,7 @@ alias_block() {
   cat <<EOF
 $MARKER_OPEN
 TOOLKIT="$PROJECT_ROOT"
+export CLAUDE_CODE_ENABLE_TODO_TOOLS=1
 
 alias cl='claude'
 alias clr='cl -r'

package/src/commands/claude.ts

@@ -673,6 +673,10 @@ async function runSync(target: string): Promise<number> {
     logWarn(
       'settings.json lacks the session defaults. Run `canon migrate session-defaults --write`',
     )
+  } else if (defaults.kind === 'planned' && defaults.plan.lacksMergeDeny) {
+    logWarn(
+      'settings.json lacks the merge deny entries. Run `canon migrate session-defaults --write`',
+    )
   }
 
   logStep('Scanning .gitignore')

package/src/commands/labels.ts

@@ -6,6 +6,12 @@ import { gitEnv } from '@/git/env'
 import { diffLabels } from '@/labels/apply'
 import { type LabelAuditRefusal, auditLabels } from '@/labels/audit'
 import { checkClosing } from '@/labels/closing'
+import {
+  bodyDensity,
+  isPost,
+  POST_HEADINGS,
+  postDensity,
+} from '@/labels/density'
 import { resolveScanInput } from '@/labels/event'
 import { checkTitleFormat, type TitleFormatIssue } from '@/labels/format'
 import { MAP_REL } from '@/labels/map'
@@ -241,7 +247,27 @@ export function register(program: Command): void {
         'It grades the body of an ordinary pull request against the closed',
         'section list: a level-two heading outside it, or a missing',
         '## Summary or ## Key changes, fails. A review, a release-please body,',
-        'and a scan carrying no title skip this check. It also fails a banned',
+        'and a scan carrying no title skip this check.',
+        '',
+        'It reports the density of that same body per section under `density`,',
+        'without failing on it: a bullet past 200 characters, more than 5 plain',
+        'bullets or 2 paragraphs in a row, a paragraph past 350 characters, any',
+        'H3 or deeper heading, and Technical context mixing bullets with',
+        'paragraphs. A bold label alone on a line splits a Key changes run, a',
+        'bold-led paragraph starts a new Technical context run, and Testing',
+        'takes the heading limit alone. Each finding carries its section, kind,',
+        'line in the whole body, value, and limit.',
+        '',
+        'A body the section check skips is graded as a post under the same',
+        '`density` key when its first level-two heading is one of',
+        `${POST_HEADINGS.map((heading) => `## ${heading}`).join(', ')}.`,
+        'A post takes the same length and run limits, allows an H3, and',
+        'measures a nested item as a bullet of its own. The footer, the',
+        'marker, and a table never report, a block inside <details> takes the',
+        'length limits alone, and a checklist box under ## What to look at',
+        'takes no length limit. Post density never fails the scan.',
+        '',
+        'It also fails a banned',
         'character, an em dash or a semicolon, in the title or body of a pull',
         'request or a review, outside a code span or a link.',
         '',
@@ -692,6 +718,44 @@ async function runScan(opts: ScanOptions): Promise<number> {
     }
   }
 
+  // Reported and never gated yet. New bodies come back clean under the
+  // shape in pr.md first, so an older open pull request fails no edit event.
+  // A post is never gated, since CI reads one only after it is published.
+  const post = !sectionsChecked && isPost(resolved.body)
+  const density = sectionsChecked
+    ? bodyDensity(resolved.body)
+    : post
+      ? postDensity(resolved.body)
+      : []
+
+  logStep(
+    !sectionsChecked && !post
+      ? 'Density not checked'
+      : density.length === 0
+        ? 'Clean'
+        : 'Density finding found',
+  )
+  if (!sectionsChecked && !post) {
+    logInfo(
+      'only an ordinary pull request body or a post opening on a post heading is graded for density',
+    )
+  } else if (density.length === 0) {
+    logInfo('every section is within its length, run, and heading limits')
+  } else {
+    logWarn(
+      `${plural(density.length, 'density finding')} in the ${post ? 'post' : 'body'}. Regroup the section under bold labels or split the long item rather than cutting a path.`,
+    )
+    for (const finding of density) {
+      const measured =
+        finding.value === null
+          ? ''
+          : ` (${finding.value} over ${finding.limit})`
+      logWarn(
+        `line ${finding.line} in ${finding.section ?? 'the opening'}: ${finding.kind}${measured}`,
+      )
+    }
+  }
+
   const banFindings = [
     ...scanBans(
       [{ number: 1, text: resolved.title, fenced: false }],
@@ -781,6 +845,7 @@ async function runScan(opts: ScanOptions): Promise<number> {
         sessionLinks: result.sessionLinks,
         titleFormatIssues,
         sections: { checked: sectionsChecked, ...sections },
+        density,
         bannedCharacters,
         missingClosures: closing.missing,
         strayClosures: closing.stray,

package/src/commands/migrate.ts

@@ -1421,10 +1421,11 @@ export function register(program: Command): void {
       'after',
       [
         '',
-        'Adds Agent and Task to permissions.deny in .claude/settings.json,',
-        'appending to the list without reordering it, and sets',
-        'autoMemoryEnabled to false only when the key is absent. A deny entry',
-        'is never removed and an existing autoMemoryEnabled is never changed.',
+        'Adds Agent, Task, Bash(canon pr merge:*), and Bash(gh pr merge:*) to',
+        'permissions.deny in .claude/settings.json, appending only the ones',
+        'the list lacks without reordering it, and sets autoMemoryEnabled to',
+        'false only when the key is absent. A deny entry is never removed and',
+        'an existing autoMemoryEnabled is never changed.',
         '',
         'A missing settings file is nothing to do. A file that is not valid',
         'JSON, or whose permissions or deny has an unexpected shape, is',