@erclx/canon 5.37.0 → 5.39.0

package/claude/skills/draft-ready/SKILL.md

@@ -41,7 +41,11 @@ canon tasks next-label --claim --json
 
 The claim reserves the label under `.canon/ordinal-locks/`, so a second session allocating at the same moment gets the next one. A bare read reserves nothing and can return a label a live claim already holds.
 
-Branch on the record's `reason` rather than on the exit code, taking `label` from a record that carries one. `label-contended` means re-run the claim. Report the verb as unavailable and stop when the installed binary carries no `next-label` subcommand, or when an unknown `--claim` prints no record, since that binary predates the flag. Never fall back to a bare read or a label picked by hand, which reopens the collision the claim exists to prevent.
+Branch on the record's `reason` rather than on the exit code, taking `label` from a record that carries one.
+
+- `label-contended` means re-run the claim
+- Report the verb as unavailable and stop when the binary carries no `next-label` subcommand, or prints no record for an unknown `--claim`, since it predates the flag
+- Never fall back to a bare read or a label picked by hand, which reopens the collision the claim exists to prevent
 
 ## Step 3: write the overview
 
@@ -71,7 +75,9 @@ Run the match check in `${CLAUDE_SKILL_DIR}/references/assembly.md` before going
 
 ## Step 6: write the task
 
-Write `<main-root>/.canon/tasks/<label>-<slug>.md` by heredoc, from the label Step 2 claimed, without calling the verb again, since a second call would claim a different label. Its frontmatter, H1, and `## Outcomes` follow `${CLAUDE_SKILL_DIR}/../task-board/references/tasks.md`. Write a `Ready:` line beside the `Plan:` line pointing at the folder, then point the task at the plan through the verb:
+Write `<main-root>/.canon/tasks/<label>-<slug>.md` by heredoc from the label Step 2 claimed, never calling the verb again, which would claim another. Its frontmatter, H1, and `## Outcomes` follow `${CLAUDE_SKILL_DIR}/../task-board/references/tasks.md`.
+
+Write a `Ready:` line beside the `Plan:` line pointing at the folder, then point the task at the plan through the verb:
 
 ```bash
 canon tasks plan-link <task-stem> .canon/plans/feature-<slug>.md --json
@@ -79,13 +85,19 @@ canon tasks plan-link <task-stem> .canon/plans/feature-<slug>.md --json
 
 Branch on the record rather than on the exit. The `Ready:` line orients a worker reading the task, and `canon tasks archive` reads it to move the folder on ship.
 
-A task file with no row is a dropped task, so place the row in the same pass. The plan exists, so the row takes `## Run now`, per the tests in `${CLAUDE_SKILL_DIR}/../task-board/references/board.md`. A path `canon tasks plan-reach` reports as claimed is a shared file rather than a hold. Name each one and its holder wherever the row is reported below, so whoever controls the board decides whether a contract, a relocation, or a sweep moves the row to `## Up next`.
+### Place the row
+
+A task file with no row is a dropped task, so place the row in the same pass. The plan exists, so the row takes `## Run now`, per the tests in `${CLAUDE_SKILL_DIR}/../task-board/references/board.md`.
+
+A path `canon tasks plan-reach` reports as claimed is a shared file rather than a hold. Name each one and its holder wherever the row is reported, so whoever controls the board decides whether a contract, a relocation, or a sweep moves the row to `## Up next`.
+
+### Check the roster
 
-Check the roster the way `canon:task-board` Step 4 does, reading `canon sessions list --self --json` for this session and `canon sessions list --json` for a row from the same repository, under another `sessionId`, whose `name` starts with `orchestrator-`. Treat a refused read as a roster read that failed.
+Check the roster the way `canon:task-board` Step 4 does, reading `canon sessions list --self --json` for this session and `canon sessions list --json` for a same-repository row under another `sessionId` whose `name` starts with `orchestrator-`. A refused read counts as failed.
 
-- **Orchestrator found.** Write neither file. Message that session with the row's title, the plan link, and the group with its reason, so it places the row itself rather than two sessions writing the board at once.
-- **Not found, and this session's name starts with `worker-` or `planner-`.** Write neither file, since both role bodies ban a board write with no exception. Report the row and its group in Step 8.
-- **Not found otherwise, or the roster read fails.** Write the row into `priority.md` through the same `Bash` route the task file took. A failed read looks like a solo project, and stopping would strand the task on the one path with nobody to place it.
+- **Orchestrator found.** Write neither file. Message that session with the row's title, the plan link, and the group with its reason, so two sessions never write the board at once.
+- **Not found, and this session's name starts with `worker-` or `planner-`.** Write neither file, since both role bodies ban a board write. Report the row and its group in Step 8.
+- **Not found otherwise, or the roster read fails.** Write the row into `priority.md` through the task file's `Bash` route, since a failed read looks like a solo project and stopping strands the task.
 
 Say which branch fired in Step 8.
 

package/claude/skills/draft-screencast/SKILL.md

@@ -10,8 +10,9 @@ metadata:
 ## Guards
 
 - If no topic is provided, stop: `❌ No screencast topic. Describe what you are recording.`
-- Draft, then hand off. Do not edit video or generate captions, and do not drive the application. A recording is another skill's job rather than something forbidden: write the draft, name `record-screencast` as the next step, and stop.
-- Stack-agnostic in the draft. Never name a recording tool, an editing tool, a font, or a window manager. Keep selectors, URLs, wait conditions, and timings out of the beats too, since those four are exactly what the compiler adds in a plan of its own. A beat carrying them stops being a document a person can read and edit down.
+- Draft, then hand off. Do not edit video, generate captions, or drive the application, since a recording is `record-screencast`'s job. Name it as the next step and stop.
+- Stack-agnostic in the draft. Never name a recording tool, an editing tool, a font, or a window manager.
+- Keep selectors, URLs, wait conditions, and timings out of the beats, since the compiler adds those four in a plan of its own and a beat carrying them stops being readable
 
 ## Step 1: read the project context
 
@@ -45,118 +46,11 @@ Build a 2-to-4-word kebab-case slug from the topic and discovery answers. Exampl
 
 Create `demos/<slug>/beats.md` at the project root, creating the folder if it does not exist. The file is committed with the rest of the demo's sources, so a recording can be rebuilt from the folder alone.
 
-Write all nine sections. Pre-seed every section with concrete content so the draft is shippable as-is. The user edits down rather than fills blanks.
+### Fill the template
 
-Load `canon:video-craft` for every zoom and caption value the draft names, and report it rather than proceeding silently when it does not resolve. The template below states none, since each number there traces to a source that skill records.
+Write all nine sections from `${CLAUDE_SKILL_DIR}/references/beats-template.md`, read on reaching this step. Pre-seed every section with concrete content so the draft ships as-is, and the user edits down rather than fills blanks. A run stopped at discovery skips it.
 
-```markdown
-# Screencast: <short title>
-
-## 1. Header
-
-- Audience: <from discovery>
-- Length: <from discovery>
-- Hero moment: <from discovery>
-- Pitch: <one sentence, derived from project context>
-
-## 2. Pre-recording checklist
-
-- [ ] Browser at 1920x1080 with notifications silenced
-- [ ] Session storage and history cleared for the recorded surfaces
-- [ ] Cursor highlighter on
-- [ ] Live URLs and fixtures verified healthy
-- [ ] <one or two project-specific items derived from context>
-
-## 3. Beat sheet
-
-Five beats. Each uses five fields. Add a sixth `Transition out` only when non-default.
-
-### Beat 1: Cold open
-
-- On screen: <derived from hero moment>
-- Action: <one verb, derived>
-- Watch for:
-- Emphasis: zoom onto the action, scale and speed per `canon:video-craft`
-- Caption:
-
-### Beat 2: Setup
-
-- On screen:
-- Action:
-- Watch for:
-- Emphasis: none
-- Caption:
-
-### Beat 3: Hero moment
-
-- On screen: <hero moment from discovery>
-- Action:
-- Watch for:
-- Emphasis: highlight overlay
-- Caption:
-
-### Beat 4: Payoff
-
-- On screen:
-- Action:
-- Watch for:
-- Emphasis: none
-- Caption:
-
-### Beat 5: Outro
-
-- On screen:
-- Action:
-- Watch for:
-- Emphasis: zoom out to full frame
-- Caption:
-
-## 4. Sequencing notes
-
-- Hover before click. The cursor needs a beat to register.
-- Do not cut mid-reset. Let state changes complete on screen.
-- Cut on action, not on stillness.
-- <one or two project-specific gotchas derived from context>
-
-## 5. Production notes
-
-- Resolution: 1920x1080
-- Frame rate: 30fps
-- Container: mp4 H.264
-- Zoom: only on an action too small to read at full frame, scale, speed, and dwell per `canon:video-craft`, zoomed out before every cut
-- Highlight overlay: ~1.5s soft glow
-
-## 6. Captions
-
-- Each caption names what its beat's frame shows, at most two lines of 42 characters, per `canon:video-craft`
-- Hold and reading rate per `canon:video-craft`, splitting a caption across beats rather than shortening its hold
-- Placed off the element the beat acts on
-
-## 7. Distribution
-
-Where the recording ships. Strike rows that do not apply.
-
-- [ ] Native upload to social platform
-- [ ] Canonical host (long-form video platform)
-- [ ] Linked from project README or release notes
-
-## 8. Resolved decisions
-
-Pre-seeded with the common picks. Strike or rewrite as needed.
-
-- Audio: silent plus captions
-- Language: English
-- Chip order: <leave for user, derived from beats>
-- Thumbnail: hero-moment frame
-
-## 9. Wrap
-
-What surrounds the take in the finished video. Each row carries a proposed default. Write `none` on every row to ship the raw take.
-
-- Intro: <proposed title card of two to three seconds naming the subject, or `none`>
-- Outro: <proposed closing card naming where to go next, or `none`>
-- Music: none
-```
+Load `canon:video-craft` for every zoom and caption value the draft names, and report it rather than proceeding silently when it does not resolve.
 
 ## Step 5: output
 

package/claude/skills/draft-screencast/references/beats-template.md

@@ -0,0 +1,119 @@
+---
+title: Beats template
+description: The nine-section template draft-screencast writes to demos/<slug>/beats.md, pre-seeded so the draft ships as-is
+---
+
+# Beats template
+
+Applies to the draft `draft-screencast` Step 4 writes. Fill every placeholder from the project context and the discovery answers. The template states no zoom or caption value, since each traces to a source `canon:video-craft` records.
+
+## Template
+
+```markdown
+# Screencast: <short title>
+
+## 1. Header
+
+- Audience: <from discovery>
+- Length: <from discovery>
+- Hero moment: <from discovery>
+- Pitch: <one sentence, derived from project context>
+
+## 2. Pre-recording checklist
+
+- [ ] Browser at 1920x1080 with notifications silenced
+- [ ] Session storage and history cleared for the recorded surfaces
+- [ ] Cursor highlighter on
+- [ ] Live URLs and fixtures verified healthy
+- [ ] <one or two project-specific items derived from context>
+
+## 3. Beat sheet
+
+Five beats. Each uses five fields. Add a sixth `Transition out` only when non-default.
+
+### Beat 1: Cold open
+
+- On screen: <derived from hero moment>
+- Action: <one verb, derived>
+- Watch for:
+- Emphasis: zoom onto the action, scale and speed per `canon:video-craft`
+- Caption:
+
+### Beat 2: Setup
+
+- On screen:
+- Action:
+- Watch for:
+- Emphasis: none
+- Caption:
+
+### Beat 3: Hero moment
+
+- On screen: <hero moment from discovery>
+- Action:
+- Watch for:
+- Emphasis: highlight overlay
+- Caption:
+
+### Beat 4: Payoff
+
+- On screen:
+- Action:
+- Watch for:
+- Emphasis: none
+- Caption:
+
+### Beat 5: Outro
+
+- On screen:
+- Action:
+- Watch for:
+- Emphasis: zoom out to full frame
+- Caption:
+
+## 4. Sequencing notes
+
+- Hover before click. The cursor needs a beat to register.
+- Do not cut mid-reset. Let state changes complete on screen.
+- Cut on action, not on stillness.
+- <one or two project-specific gotchas derived from context>
+
+## 5. Production notes
+
+- Resolution: 1920x1080
+- Frame rate: 30fps
+- Container: mp4 H.264
+- Zoom: only on an action too small to read at full frame, scale, speed, and dwell per `canon:video-craft`, zoomed out before every cut
+- Highlight overlay: ~1.5s soft glow
+
+## 6. Captions
+
+- Each caption names what its beat's frame shows, at most two lines of 42 characters, per `canon:video-craft`
+- Hold and reading rate per `canon:video-craft`, splitting a caption across beats rather than shortening its hold
+- Placed off the element the beat acts on
+
+## 7. Distribution
+
+Where the recording ships. Strike rows that do not apply.
+
+- [ ] Native upload to social platform
+- [ ] Canonical host (long-form video platform)
+- [ ] Linked from project README or release notes
+
+## 8. Resolved decisions
+
+Pre-seeded with the common picks. Strike or rewrite as needed.
+
+- Audio: silent plus captions
+- Language: English
+- Chip order: <leave for user, derived from beats>
+- Thumbnail: hero-moment frame
+
+## 9. Wrap
+
+What surrounds the take in the finished video. Each row carries a proposed default. Write `none` on every row to ship the raw take.
+
+- Intro: <proposed title card of two to three seconds naming the subject, or `none`>
+- Outro: <proposed closing card naming where to go next, or `none`>
+- Music: none
+```

package/claude/skills/draft-slides/SKILL.md

@@ -38,15 +38,18 @@ Each slide is a full HTML document laid out at 1280 by 720 CSS pixels. Position
 
 The render injects the project's token stylesheet ahead of each slide's own styles, so the deck takes the project's design rather than the toolkit's.
 
-- Use the project's custom properties, such as `var(--color-accent)`, for every color, face, and spacing value the stylesheet defines. Read the names from `.claude/design/base.css` and any overrides under `.claude/design/project/`. When neither exists, say the deck renders unstyled rather than inventing values to cover it.
-- Leave the `--color-*` roles to the stylesheet rather than redefining them in a slide. The master reads its colors off the first slide's `<html>`, and a slide body computing its own `--color-text` is reported, since the bands keep the master's colors.
+- Use the project's custom properties, such as `var(--color-accent)`, for every color, face, and spacing value, read from `.claude/design/base.css` and overrides under `.claude/design/project/`
+- When neither exists, say the deck renders unstyled rather than inventing values to cover it
+- Leave the `--color-*` roles to the stylesheet. The master reads its colors off the first slide's `<html>`, so a slide computing its own `--color-text` is reported, since the bands keep the master's.
 - Vary the composition across slides. Never repeat a title over bullets on every slide. Reach for columns, a row of large numbers, a grid of cards, a chart, a pull quote, and section dividers.
 
 ### Fit and shapes
 
+Text and shapes have to survive the conversion.
+
 - Keep titles short and lines tight, so text fits its box at the size the design sets rather than overflowing the frame.
 - Never write centered body text.
-- Prefer CSS the converter maps to native shapes. An element computing a property it cannot map is drawn as a picture of itself and reported on stderr, so a slide full of gradients and filters stops being editable.
+- Prefer CSS the converter maps to native shapes. An unmappable property is drawn as a picture and reported on stderr, so a slide full of gradients and filters stops being editable.
 
 ## Render
 
@@ -64,7 +67,7 @@ Read every `✗` line the render prints. A picture fallback, a refused link, cha
 
 Run this once after the first render, then stop.
 
-1. Convert the deck to images: `soffice --headless --convert-to pdf <deck>.pptx` then `pdftoppm -r 90 -png <deck>.pdf slide`. If `soffice` or `pdftoppm` is missing, skip the image pass and say so. Do not fail the render.
+1. Convert the deck with `soffice --headless --convert-to pdf <deck>.pptx`, then `pdftoppm -r 90 -png <deck>.pdf slide`. If either is missing, skip the image pass and say so rather than fail the render.
 2. Open and inspect every rendered image in this session, checking each slide for overlap, overflow, low contrast, and empty regions.
 3. Fix the reported issues and the `✗` lines in the slide files once, re-render, and stop. Do not loop indefinitely on aesthetics.
 

package/claude/skills/git-branch/SKILL.md

@@ -31,6 +31,8 @@ Run these commands in parallel to gather git context:
 
 ### Preview
 
+Output the preview first.
+
 - **Current:** <current_branch>
 - **Suggested:** <suggested_name>
 - **Length:** <count>/50
@@ -55,8 +57,6 @@ git branch -m <current> <suggested>
 
 ## After execution
 
-Respond with exactly one line:
+Respond with exactly one line and add no other text:
 
 `✅ Renamed: <current> → <suggested>`
-
-Do not add any other text.

package/claude/skills/git-commit/SKILL.md

@@ -30,6 +30,8 @@ Run these commands in parallel to gather git context:
 
 ### Preview
 
+Output the preview first.
+
 - **Files:** <if ≤3 list all, if >3 show first 3 + "+N more">
 - **Message:** `<type>(<scope>): <subject>`
 - **Length:** <count>/72
@@ -38,14 +40,14 @@ After outputting the preview, execute the final command immediately. Claude Code
 
 ### Final command
 
+Run it as soon as the preview is out.
+
 ```bash
 git commit -m "<type>(<scope>): <subject>"
 ```
 
 ## After execution
 
-Respond with exactly one line:
+Respond with exactly one line and add no other text:
 
 `✅ Committed: <type>(<scope>): <subject>`
-
-Do not add any other text.

package/claude/skills/git-followup/SKILL.md

@@ -16,18 +16,25 @@ its own reply, so skip the comment in step 7. The push and body sync still run.
 
 - If `git branch --show-current` returns `main`, stop: `❌ On main. Switch to a PR branch first.`
 - If `git status --porcelain` is empty, stop: `❌ No changes to ship.`
-- Resolve `<number>` once, here, through `canon pr head --json`, reading the record's `number`. Every later step names this `<number>` rather than resolving it again. A record refusing with `ambiguous-pull` stops: `❌ Two open PRs on this branch. Name the one to update.`
-- When no record comes back, or it carries no `number`, read the open pull requests on the branch over REST instead. The branch is encoded so a `/` in its name reaches the query as `%2F`:
+- Resolve `<number>` once, here, through `canon pr head --json`, reading the record's `number`. Every later step names this `<number>` rather than resolving it again.
+- A record refusing with `ambiguous-pull` stops: `❌ Two open PRs on this branch. Name the one to update.`
 
-  ```bash
-  gh api "repos/{owner}/{repo}/pulls?head={owner}:$(git branch --show-current | jq -Rr @uri)&state=open" --jq '.[].number'
-  ```
+### Fallback lookup
 
-  Nothing printed stops: `❌ No open PR for this branch. Use git-ship to open one.` More than one number takes the `ambiguous-pull` stop above rather than the first, since two open pull requests on one head against different bases leave nothing to say which one this push updates.
+When no record comes back, or it carries no `number`, read the open pull requests on the branch over REST instead. The branch is encoded so a `/` in its name reaches the query as `%2F`:
 
-Every read and write in this skill runs on REST, since the `gh pr` subcommands run on GraphQL and a cloud session's GitHub proxy refuses it. A cloud worker answering a review reaches this skill through `review-address`, so one GraphQL call here breaks that whole leg.
+```bash
+gh api "repos/{owner}/{repo}/pulls?head={owner}:$(git branch --show-current | jq -Rr @uri)&state=open" --jq '.[].number'
+```
+
+- Nothing printed stops: `❌ No open PR for this branch. Use git-ship to open one.`
+- More than one number takes the `ambiguous-pull` stop rather than the first, since two open pull requests on one head leave nothing to say which one this push updates
+
+### REST and the tracking ref
+
+Every read and write in this skill runs on REST, since the `gh pr` subcommands run on GraphQL and a cloud session's GitHub proxy refuses it. A cloud worker reaches this skill through `review-address`, so one GraphQL call breaks that whole leg.
 
-A missing tracking ref is no longer a guard. An open pull request proves the branch reached the remote, and a branch created by worktree entry has been measured carrying an open pull request with no tracking ref, where the old guard reported that the branch still needed pushing. That message describes a state the branch is not in, so the run stopped on a diagnosis nobody could act on. Step 4 sets the ref instead.
+A missing tracking ref is not a guard, since an open pull request proves the branch reached the remote. A branch created by worktree entry carries an open pull request with no tracking ref, so step 4 sets the ref instead.
 
 ## Sequence
 
@@ -40,7 +47,7 @@ A missing tracking ref is no longer a guard. An open pull request proves the bra
 
    The lease is what stops the force from overwriting a commit this session never read. Run the ancestry test only where an upstream resolves, since it reads `@{u}`.
 
-5. Post the evidence comparison, on every invocation including `reply-owned`, since this comment is not the reply step 8 owns. Run `canon pr evidence <number> --json` and read `reason` on the record rather than the exit code.
+5. Post the evidence comparison on every invocation, `reply-owned` included, since it is not step 8's reply. Run `canon pr evidence <number> --json` and read `reason` rather than the exit code.
    - `no-evidence`: nothing changed under an `evidence/` segment this push. Say nothing and move on.
    - `ok`: write `body` to `.canon/tmp/pr/evidence/body-<number>.md` at the main worktree root (resolved the way `session-worktree` does), then post the comment with `gh api -X POST repos/{owner}/{repo}/issues/<number>/comments -F body=@<main-root>/.canon/tmp/pr/evidence/body-<number>.md --silent` when the record carries no `commentId`, or edit the existing one in place with `gh api -X PATCH repos/{owner}/{repo}/issues/comments/<commentId> -F body=@<main-root>/.canon/tmp/pr/evidence/body-<number>.md` when it does. Clean up the tmp file only after the call reports success.
    - Any other reason is one of the mirrored git refusals (`gh-missing`, `gh-failed`, `no-base`, `unreadable-changes`, `would-empty`). Report it and continue without stopping the chain.

package/claude/skills/git-issue/SKILL.md

@@ -33,6 +33,8 @@ Then gather repo context in parallel:
 
 ### Preview
 
+Output the preview first.
+
 - **Title:** `<type>: <subject>`
 - **Label:** <bug or enhancement>
 - **Analysis:** <one line on what the issue captures>
@@ -41,9 +43,10 @@ After outputting the preview, execute the final command immediately. Claude Code
 
 ### Pre-publish scan
 
-Before running the final command, run the scan in `${CLAUDE_SKILL_DIR}/../git-pr/references/publish.md` against the title and body. The title and body go straight to the remote with nothing checking them on the way, so this scan is the only gate. It covers the phase-label check as well as the characters, since both go to a reader who has no task board. It applies on top of the banned phrases in `${CLAUDE_SKILL_DIR}/references/issue.md`.
+Before running the final command, run the scan in `${CLAUDE_SKILL_DIR}/../git-pr/references/publish.md` against the title and body, on top of the banned phrases in `${CLAUDE_SKILL_DIR}/references/issue.md`.
 
-The `pull_request` check the git-pr surface carries reads a pull request's own title and body alone, so an issue reaches no check behind this scan either.
+- The title and body go straight to the remote, and the `pull_request` check reads a pull request alone, so this scan is the only gate
+- It covers the phase-label check as well as the characters, since both reach a reader who has no task board
 
 ### Final command
 
@@ -60,8 +63,6 @@ rm -rf .canon/tmp/issue
 
 ## After execution
 
-Respond with exactly one line:
+Respond with exactly one line and add no other text:
 
 `✅ Issue: <url>`
-
-Do not add any other text.

package/claude/skills/git-issue/references/issue.md

@@ -53,17 +53,18 @@ Does not govern:
 ### Feedback
 
 - One `## Toolkit feedback` wrapper holds every field as a nested `###` heading. A flat `##` field is not recognized.
-  | Field | Holds |
-  | --- | --- |
-  | `### From project` (optional) | the reporting project's name or kind. |
-  | `### Surface` (required) | the toolkit surface and its type, and the specific file or name when known. |
-  | `### Observed` (required) | the observed behavior. |
-  | `### Expected` (optional) | the expected behavior, or `unclear`. |
-  | `### Repro` (optional) | repro details, or `none`. |
-  | `### Proposed fix` (required) | a proposed fix, or `open` when the session settled on no direction. |
+
+  | Field                            | Holds                                                                                                                        |
+  | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+  | `### From project` (optional)    | the reporting project's name or kind.                                                                                        |
+  | `### Surface` (required)         | the toolkit surface and its type, and the specific file or name when known.                                                  |
+  | `### Observed` (required)        | the observed behavior.                                                                                                       |
+  | `### Expected` (optional)        | the expected behavior, or `unclear`.                                                                                         |
+  | `### Repro` (optional)           | repro details, or `none`.                                                                                                    |
+  | `### Proposed fix` (required)    | a proposed fix, or `open` when the session settled on no direction.                                                          |
   | `### Suggested shape` (optional) | the template, output, or field list the change should take, inside a `<details>` block. Omit the heading when there is none. |
-  | `### Why` (optional) | the reasons for the fix, one bullet each. Omit the heading when there are none. |
-  | `### Links` (optional) | the issues, pull requests, or documents the report cites, one per line. Omit the heading when there are none. |
+  | `### Why` (optional)             | the reasons for the fix, one bullet each. Omit the heading when there are none.                                              |
+  | `### Links` (optional)           | the issues, pull requests, or documents the report cites, one per line. Omit the heading when there are none.                |
 
 - A required field is refused when present but empty. Write the fallback literal for From project, Expected, and Repro rather than leaving one blank.