Skip to content

feat(plugins): bake native route phrases into the remaining sweep units - #5570

Merged
kyle-sexton merged 14 commits into
mainfrom
feat/native-phrases-sweep-rest
Sep 30, 2026
Merged

kyle-sexton merged 14 commits into
mainfrom
feat/native-phrases-sweep-rest

Conversation

@kyle-sexton

@kyle-sexton kyle-sexton commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

No related issue: operator-directed batch of the remaining native description-phrase sweep units, tracked in the sweep PRs listed under Related.

Summary

Ships the five remaining description-phrase sweep units (context-budget, evals, playbooks, prototype, visualization) as one PR, per operator direction.

Fix

  • context-budget 0.6.47: /context-budget:audit description routes a plain-language account of this session's tokens to the bundled explain-usage skill; this skill keeps startup cost, per-tool attribution, and before/after checks.
  • evals 0.3.8: /evals:methodology description routes the model-and-effort sweep over an existing suite to claude-api's hillclimb; this skill keeps suite and criteria design.
  • playbooks 0.15.2: /playbooks:fable-5 description routes current model, price, and API facts and the cost audit to the bundled claude-api skill.
  • prototype 0.13.5 and visualization 0.8.3: the bundled design skill is model-invocation-disabled in 2.1.285, so both rows move from route to suggest. The description phrase is dropped and the Boundary offers /design to the person.
  • Boundary bullets follow the - ** (<class>)**: what it does template and no longer assert availability.
  • docs/native-surfaces/records.json: the three route rows carry baked.description_phrase: true; the two design rows are suggest with suggest_sentence: true. docs/native-surfaces.md regenerated with overlap.py generate.
  • /design evidence: a targeted string search of the 2.1.285 binary shows the design registration is a user-only design-Artifact creator ("Make a new Design artifact from a brief"), not the claude.ai/design hub (now a separate ClaudeDesign tool). The canvas behavior in both skills is restated from the commands and artifacts docs fetched 2026-09-30; the converted design rows drop budget_caveat and the "versioned" claim.
  • context-budget:audit gains a suggest row and a ## Boundary section for the built-in /context command (2.1.285: builtin-command, "Visualize current context usage as a colored grid", argument hint [all], gated, model invocation disabled), with four-part records in reference/native-context.md.
  • Two dismissals recorded with overlap.py dismiss:
    • Bash (builtin-tool) vs bash-format:check: "Name overlap only: bash-format:check is a read-only check that the shfmt and shellcheck binaries resolve for the bash-format hook; the built-in Bash tool executes shell commands. Different jobs, no routing."
    • PowerShell (builtin-tool) vs powershell-format:check: "Name overlap only: powershell-format:check is a read-only check that pwsh, PSScriptAnalyzer, jq and node resolve for the powershell-format hook; the built-in PowerShell tool executes PowerShell commands. Different jobs, no routing."
  • native-references convention: one 3.3.5 CHANGELOG entry and updated Adopters rows.

Verification

  • overlap.py generate --check: in sync (64 rows, 78 dismissals). overlap.py self-check: degraded on the two standing advisories only (older extraction versions, no --upstream-sha).
  • overlap.py detect against the 2.1.285 inventory: 0 resurfaced dismissals, 0 orphaned, 0 unruled discovered pairs.
  • git grep -i 'ships with Claude Code' over the five plugins' SKILL.md files: empty.
  • validate-plugin-contracts.mjs, check-changed-skills.sh origin/main (7 skills, 0 failed), check-skill-description-voice.sh (5 PASS), check-changelog-parity.sh --check, --check-bump, --check-order, --check-preserved, check-skill-portability.sh, check-purged-em-dashes.sh, and markdownlint-cli2 on the touched files: all pass.
  • node scripts/generate-catalog.mjs: in sync.

Related

🤖 Generated with Claude Code

Ships the remaining description-phrase sweep units as one change:

- context-budget 0.6.47: /context-budget:audit description routes the
  session-token account to the bundled explain-usage skill.
- evals 0.3.7: /evals:methodology description routes the model-and-effort
  sweep over an existing suite to claude-api's hillclimb.
- playbooks 0.15.2: /playbooks:fable-5 description routes current model,
  price and API facts and the cost audit to the bundled claude-api skill.
- prototype 0.13.5 and visualization 0.8.3: the bundled design skill is
  model-invocation-disabled in 2.1.285, so both rows move from route to
  suggest; the description phrase is dropped and the Boundary offers
  /design to the person.

Boundary bullets follow the `- **`<name>` (<class>)**: what it does` template
and no longer assert availability. records.json marks the three route
rows baked.description_phrase true; native-surfaces.md is regenerated;
the native-references convention takes one 3.3.5 entry and updated
Adopters rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton
kyle-sexton marked this pull request as ready for review September 30, 2026 04:29
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-30T17:23:06.097642Z 91e39e3 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 3m 5s —— View job


Claude finished the code review

  • Gather context (PR diff, changed files)
  • Understand the request (/review:code-review on PR 5570)
  • Review changed files for correctness/maintainability
  • Post findings

No findings. This is a coordinated documentation/routing sweep across five plugins (context-budget, evals, playbooks, prototype, visualization) plus the shared docs/native-surfaces inventory and the native-references convention docs. I checked it for internal consistency rather than just trusting the PR body's claims:

  • Verified the three route rows (context-budget:audit, evals:methodology, playbooks:fable-5) each gained a matching description-phrase clause, a Boundary bullet rewritten to the - ** (<class>)**: what it does template with the ships-with-Claude-Code assertion dropped, and a docs/native-surfaces/records.json baked.description_phrase flip to true for the matching pair.
  • Verified the two design rows (prototype:explore-directions, visualization:visualize) consistently move route→suggest: the description's design clause is removed, the Boundary section gains a four-part verification record (claim/basis/as-of/recheck, per .claude/rules/skill-bodies-state-current-rules.md) citing the 2.1.285 extraction, and records.json's integration, baked.description_phrase/suggest_sentence, observation, and recheck fields for both pairs move together. plugins/prototype/context/discipline.md and both plugin READMEs were updated to match (no longer implying model-side routing).
  • Cross-checked docs/native-surfaces.md's summary table: bundled-skills route 20→18 / suggest 7→9 matches exactly the two rows that flipped; the Baked 22 total correctly stays unchanged since all five rows already had boundary_section: true before this PR.
  • Checked for a stale-fingerprint gap: records.json only carries fingerprint blocks on dismissed overlap pairs, not on adopted pairs. Of the dismissal entries, only the one keyed to prototype:explore-directions (the Explore agent dismissal) needed its component fingerprint refreshed after this PR's edits, and it was. No dismissal entries reference context-budget:audit, evals:methodology, playbooks:fable-5, or visualization:visualize, so there's nothing stale there.
  • Spot-checked version bumps (all patch) against each CHANGELOG.md entry and docs/catalog.md's regenerated blurb for visualization — all consistent.

One purely cosmetic thing I noticed but am not flagging as a finding: two lines land noticeably longer than their neighboring wrapped lines in a couple of the touched files (e.g. plugins/playbooks/skills/fable-5/SKILL.md and plugins/prototype/skills/explore-directions/SKILL.md, in the "Boundary" / "Design canvas" paragraphs). MD013 (line length) is explicitly disabled repo-wide in .markdownlint-cli2.jsonc, and rendered Markdown collapses the wrapping either way, so this has no functional or lint effect — just a minor source-formatting inconsistency, below this lane's bar.

Note on verification: I did not independently re-run overlap.py generate/detect/self-check, check-changelog-parity.sh, check-skill-portability.sh, or generate-catalog.mjs — the sandbox here doesn't allow executing those scripts, so the PR body's tool-output claims are author-reported and unverified by me. Everything I could check by reading the diff and cross-referencing the affected files was consistent.

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 1m 10s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: all 25 changed files (gh pr diff 5570), against the review:security-review skill's criteria and the instruction-surface lens.

Findings: none.

This PR is documentation/description-only: skill description: frontmatter, ## Boundary prose, CHANGELOG.md/README.md entries, plugin.json version bumps, and the docs/native-surfaces/records.json + docs/native-surfaces.md ledger. No executable code, scripts, workflows, or input-handling paths are touched, so there's no injection, auth, or secret-handling surface to review.

Instruction-surface lens applied. The diff narrows presence-check/gating language in plugins/prototype/skills/explore-directions/SKILL.md, plugins/visualization/skills/visualize/SKILL.md, and their reference/context files (removing the "listed-description presence check" and "don't invoke a shadowing skill" rules for the bundled design skill). I checked this against the protected classes in docs/conventions/instruction-exception-register/README.md (irreversible-action, secret-handling, data-integrity, external-publication, legal-compliance, agent-authority).

No finding: the removed checks existed to gate model-initiated invocation of the bundled design skill (avoiding an accidental invoke of a shadowing local skill). Per the PR's stated basis (2.1.285 extraction reading design as model_invocation_disabled: true), that invocation path no longer exists — both skills' new Boundary sections state explicitly "This skill never runs it" (plugins/visualization/skills/visualize/SKILL.md#L839, plugins/prototype/skills/explore-directions/SKILL.md#L656). The mutation gate is strictly tighter than before (unconditional "never invoke," replacing a conditional "invoke only on explicit user choice"), so this reads as a faithful update to a capability change rather than a guardrail deletion.

Also checked and clean: no pull_request_target/workflow_run or Actions changes, no permission-widening, no dependency/action pin changes (this PR touches no .github/workflows).

@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 564afebba1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/native-surfaces/records.json Outdated
A targeted string search of the 2.1.285 binary shows the `design`
registration is a user-only design-Artifact creator ('Make a new Design
artifact from a brief'), the 2.1.263 canvas strings are gone, and the
claude.ai/design hub text now belongs to a separate ClaudeDesign tool.
The records.json design rows and both skills' verification records now
state this instead of leaving the identity open.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

Failed to set up container
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

Failed to set up container
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 1m 5s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: synchronize event — reviewed the new commit 2f92eea (fix(plugins): record the 2.1.285 design registration's identity) against /review:security-review's criteria, on top of the already-reviewed 564afeb.

Findings: none.

2f92eea only replaces evidence/reason prose in four already-touched files — docs/native-surfaces.md, docs/native-surfaces/records.json, plugins/prototype/skills/explore-directions/reference/bundled-design.md, and plugins/visualization/skills/visualize/context/decision-matrix.md — adding a targeted string-search result that resolves the design registration's identity (a user-only design-Artifact creator, not the Claude Design hub). This is in response to Codex's earlier P2 comment on the registration's identity.

It does not change the route→suggest classification, the integration field, or either skill's ## Boundary mutation-gate text; those were already shipped in 564afeb and reviewed clean. No executable code, workflow, or instruction-surface deletion is touched by this commit — it only strengthens the verification record's evidentiary basis, which is exactly what the earlier finding asked for.

Re-checked the instruction-surface lens (docs/conventions/instruction-exception-register/README.md present in this checkout): this commit adds evidence, it does not delete, narrow, or soften a standing instruction, so no new finding applies here beyond what the prior two reviews already covered for the rest of the diff. No .github/workflows files are touched.

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 2m 48s —— View job


Code review — PR #5570

  • Gather context (PR diff via gh pr diff, changed files, .claude/rules/skill-bodies-state-current-rules.md)
  • Run /review:code-review skip-gate check — PR is open, not draft, and the head (2f92eea) has new commits since the last review from this lane, so a fresh pass applies
  • Review changed files for correctness/maintainability
  • Post findings

2 findings posted inline, both on the same theme: the second commit (2f92eea, "record the 2.1.285 design registration's identity") responds to the earlier Codex review comment by establishing that the design registration is not the Claude Design hub, but it doesn't establish that /design still behaves as the artboard/pan-zoom/hand-editable canvas the skill bodies still describe unchanged. The new evidence's resolved description — "Make a new Design artifact from a brief" — reads as a one-shot generator, and the same evidence paragraph notes the old canvas strings ("Draft a design on a canvas", "Create a design canvas") no longer occur in the binary. That's the "even that /design <scope> still creates the persistent canvas Artifact" half of the original Codex comment, and it's still open:

  1. plugins/prototype/skills/explore-directions/reference/bundled-design.md#L14 — SKILL.md still asserts artboards/pan-zoom/hand-edit mechanics this row's evidence doesn't back.
  2. plugins/visualization/skills/visualize/context/decision-matrix.md#L181-L189 — same gap on the sibling row.

Everything else in the diff (description-phrase/Boundary/records.json changes for the three route rows, version bumps, CHANGELOG entries, catalog blurb) is internally consistent and matches the PR body's description; I did not re-verify the author's tool-output claims (overlap.py, check-changelog-parity.sh, etc.) since I have no way to run them here — treat those as author-reported and unverified by this review.
· Branch

Comment thread plugins/prototype/skills/explore-directions/reference/bundled-design.md Outdated
Comment thread plugins/visualization/skills/visualize/context/decision-matrix.md Outdated
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 2f92eead88

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

The prototype and visualization Boundary bullets and design-canvas
offers restated 2026-09-11 canvas mechanics (pan/zoom, properties panel,
save-gated editing, research preview). The commands and artifacts pages
fetched 2026-09-30 describe artboards on one canvas published as a
Claude Design artifact, edited in a desktop browser with edits saved
automatically, PNG or PDF export per artboard, v2.1.265 or later, and
an account where the Design template is available. The skill bodies and
both verification records now state that.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 2m 48s —— View job


Code review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:code-review skill per custom instructions
  • Review changed files for correctness/maintainability
  • Post findings

Scope. Diffed 0f2a19d (pre-PR base) against f68d6ba (HEAD) — matches the PR's own stated 25 files / +286/-184. Gave the latest commit (f68d6ba, "state /design's canvas behavior from the current docs") the closest look since it's a direct follow-up to the earlier Codex/Claude review comments about the unverified artboard/pan-zoom behavior.

2 findings posted inline, both about the verification-record convention this PR is otherwise carefully following:

  1. plugins/visualization/skills/visualize/context/decision-matrix.md:196 — the old > Verified 2026-09-11 ... blockquote (through line 224) was never removed when the newer > Re-verified 2026-09-29 ... block was added above it back in this PR's first commit. It still asserts the pre-2.1.285 mechanics ("hand-editable where saving is enabled," "v2.1.234 or later") that directly contradict both the new block and the current prose two paragraphs up ("edits save automatically," "v2.1.265 or later"). Two back-to-back "Verified" records disagree on the same fact — exactly the kind of drift the PR's two follow-up commits (2f92eea, f68d6ba) were trying to eliminate, but this one slipped through all three commits.
  2. plugins/prototype/skills/explore-directions/reference/bundled-design.md:16 — minor: the claim cell was edited to say "as of 2026-09-30" but the row's own "As of" column still reads 2026-09-11 and its Basis (the changelog page) wasn't re-fetched; the 2026-09-30 fact actually belongs to row 1's re-verification.

Everything else checked clean. The three route-row description/Boundary edits (context-budget:audit, evals:methodology, playbooks:fable-5) are mechanical and consistent. docs/native-surfaces/records.json's diff for the two suggest-flip rows and three description_phrase flips matches the PR body's claims exactly, with no stray fields. The prototype/visualization SKILL.md and README edits are internally consistent with each other. I did not re-run overlap.py, check-changelog-parity.sh, check-skill-portability.sh, or generate-catalog.mjs — those tool-output claims in the PR body are author-reported and unverified by me.
· Branch

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 47s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: delta review of the new commit f68d6ba ("fix(plugins): state /design's canvas behavior from the current docs") on top of the already-reviewed 2f92eea/564afeb, per the skill's skip-gate (a head with a prior successful review only needs the new delta re-checked).

Findings: none.

f68d6ba touches four files, all already-reviewed documentation surfaces:

It replaces the 2026-09-11 canvas description (pan/zoom, versioned artifact, "hand-editable where saving is enabled", research-preview rollout flag) with the 2026-09-30 commands/artifacts-page description (artboards on one canvas, edited in a desktop browser with autosave, PNG/PDF export per artboard, v2.1.265 floor, Design-template account gate). This is the fix for the two earlier code-review findings on this PR (the "artboard/pan-zoom mechanics unconfirmed" gap on the prototype and visualization rows) — it re-sources the behavioral claims from current first-party docs instead of leaving them unverified.

Instruction-surface lens applied (per this skill's criteria, since the diff edits ## Boundary prose): the mutation gate itself is untouched and reaffirmed verbatim in both files — "It is reserved for the person to run as /design; the model does not invoke it" (prototype) and "It is reserved for the person to run; the model does not invoke it" (visualization). Nothing about model-invocation, presence-checking, or the route→suggest classification changes in this commit; only descriptive prose about what the canvas does once the person runs it. No guardrail is deleted, narrowed, or softened, so no instruction-surface finding applies.

No executable code, workflow, script, or config is touched by this commit (or by the PR as a whole — it remains a documentation/description sweep). Combined with the two prior clean security reviews on this branch (564afeb, 2f92eea), the full PR at head f68d6ba has no outstanding security findings.
· Branch

Comment thread plugins/visualization/skills/visualize/context/decision-matrix.md Outdated
Comment thread plugins/prototype/skills/explore-directions/reference/bundled-design.md Outdated
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

The visualize decision-matrix kept the 2026-09-11 verification block
after the 2.1.285 record above it, so the two contradicted each other on
editing and the version floor. The block now keeps only its still-current
facts (artifacts Availability gates, changelog, design-sync pointer).
The prototype record's changelog row no longer borrows the docs' version
floor with a date its own As-of column does not carry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 30s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: delta review of the new commit 6fd31c3 ("fix(plugins): drop the superseded 2026-09-11 canvas record") on top of the already-reviewed f68d6ba/2f92eea/564afeb, per the skill's skip-gate (a head with a prior successful review only needs the new delta re-checked).

Findings: none.

6fd31c3 touches two files, both already-reviewed documentation surfaces:

This is the fix for the code-review lane's two open findings on this branch (the mismatched "as of 2026-09-30" claim-cell date, and the stale 2026-09-11 v2.1.263-canvas blockquote contradicting the newer re-verification block above it). The commit removes the superseded 2026-09-11 canvas-mechanics claims from both files, leaving the version-floor and availability-table facts that are still current, and pointing to docs/native-surfaces/records.json for the historical registration evidence rather than restating it inline.

Instruction-surface lens applied: this commit deletes stale verification-record prose, not a standing instruction, rule, or mutation gate — the "reserved for the person to run" / "the model does not invoke it" gate text is untouched (it was edited by the earlier f68d6ba commit, already reviewed clean). Nothing here narrows or removes a guardrail.

No executable code, workflow, script, or config is touched. Combined with the three prior clean security reviews on this branch (564afeb, 2f92eea, f68d6ba), the full PR at head 6fd31c3 has no outstanding security findings.
· Branch

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6fd31c3291

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/native-surfaces/records.json Outdated
…ize design row

The 2026-09-30 docs describe the /design canvas as saving edits
automatically and say nothing of version history, so the records.json
reason no longer calls it versioned; native-surfaces.md is regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 59s —— View job


Code review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Run /review:code-review skip-gate check — PR is open, not draft; head (feb9215) has two new commits since this lane's last review (of f68d6ba), so a fresh delta pass applies
  • Review the new commits (6fd31c3, feb9215) for correctness/maintainability
  • Post findings

Scope. Delta review of the two commits landed since this lane's last pass on f68d6ba:

  • 6fd31c3 — fixes this lane's two prior findings (stale contradictory > Verified 2026-09-11 canvas-mechanics block in decision-matrix.md, and the mismatched "as of 2026-09-30" date in bundled-design.md's changelog row).
  • feb9215 — fixes Codex's P2 finding on 6fd31c3 (the records.json/native-surfaces.md reason field for the design→visualization:visualize row still called the canvas Artifact "versioned," which the 2026-09-30 docs evidence doesn't support; it now says "whose edits save automatically").

Findings: none.

Verified both fixes directly:

  • 6fd31c3 removes the old v2.1.263-era canvas description (research preview, hand-editable-where-saving-enabled, v2.1.234 floor) from decision-matrix.md while keeping only the facts that are still current (Availability table gates, the changelog check, the design-sync-family pointer into records.json). No contradiction with the > Re-verified 2026-09-29 ... block above it remains. The bundled-design.md changelog row (L16) now points at "the one the docs state (first row)" instead of restating a 2026-09-30 figure its own As of column (2026-09-11) didn't carry — internally consistent now.
  • feb9215 is a two-line, single-field change confined to records.json's reason string and the matching regenerated line in native-surfaces.md; the evidence, integration, and verdict fields are untouched, and no other file (SKILL.md, Boundary text, CHANGELOG) asserted "versioned" for this row to begin with — git grep -n versioned across the touched plugin/doc paths turns up only two unrelated pre-existing hits (a different verdict entry for audit-instructions, and a historical prototype/CHANGELOG.md entry from a prior release, neither touched by this PR).

Both commits are narrowly scoped to the exact lines the review comments identified, and I didn't find any new inconsistency they introduced. I did not re-run overlap.py generate/detect/self-check or the other validation scripts cited in the PR body — no way to execute them here — so those tool-output claims remain author-reported and unverified by this review.
· Branch

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 2m 1s —— View job


Code review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:code-review skill per custom instructions
  • Run skip-gate check — PR is open, not draft; head (2891271) has one new commit since this lane's last review (of a1da570), so a fresh delta pass applies
  • Review the new commit (2891271) for correctness/maintainability
  • Post findings

Scope. Delta review of 2891271 ("fix(plugins): reconcile user-only /context and hidden /design shadows"), the fix for Codex's two open P2 comments on a1da570:

  1. context-budget:audit's Purpose/scope-boundary text said to "run [/context] and read the tables" while its Boundary said the model never invokes it — a direct contradiction.
  2. The /design offer in prototype/visualization checked only the model's own skill listing for a shadowing design skill, missing the case where a local design skill also disables model invocation and is therefore invisible to that same check.

1 finding posted inline, low severity:

  • plugins/context-budget/skills/audit/SKILL.md:92 — the new mutation-gate sentence says the engine's headless /context capture is "covered under the engine's rungs below," but the rungs table lives in a separate file (reference/engine.md), linked only once much earlier in the doc — nothing about "rungs" appears further down in this file. The underlying claim is correct (rung 2 in reference/engine.md really does spawn <binary> -p "/context"), so this is just a dangling "below" pointer, not a factual error.

Everything else checked clean:

  • The context-budget:audit fix directly closes the flagged contradiction: Purpose now says "The model cannot invoke it in this session, so for those, ask the person to run it," matching the Boundary section's existing "the model does not invoke it," and the scope-boundary bullet now says "which the person runs."
  • The /design-shadow fix is logically sound and consistently worded across all three touched files (prototype/SKILL.md, visualization/SKILL.md, visualization/context/decision-matrix.md): when a design entry is in the model's listing, it's still treated as a certain shadow (withhold, name it) since the bundled one never appears there; when it's not in the listing (bundled-but-invisible, genuinely absent, or a model-invocation-disabled local shadow that's also invisible), every offer now adds the instruction to have the person confirm /design's description reads "Make a new Design artifact from a brief" before trusting it as the canvas. This is a real closure of the gap Codex flagged, not just a rewording.
  • No records.json/native-surfaces.md changes in this commit, so no sync risk there.

I did not re-run overlap.py, check-changelog-parity.sh, or the other validation scripts cited earlier in this PR's history — no execution access in this sandbox; those remain author-reported and unverified by this review.
· Branch

Comment thread plugins/context-budget/skills/audit/SKILL.md Outdated
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2891271608

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread plugins/context-budget/skills/audit/SKILL.md
The /context suggest sentence names "the verification record below" as
its gate basis; the Boundary now carries that four-part record in the
SKILL.md itself, and the headless-capture note points at the cli-parse
rung in reference/engine.md instead of a section that does not exist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 49s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: delta review of the new commit e62584e ("fix(context-budget): inline the /context verification record") on top of the already-reviewed 2891271/a1da570/0ab162d/e0f987f/feb9215/6fd31c3/f68d6ba/2f92eea/564afeb, per the skill's skip-gate (a head with a prior successful review only needs the new delta re-checked).

Findings: none.

e62584e touches one already-reviewed documentation surface, plugins/context-budget/skills/audit/SKILL.md. It is the fix for both open Codex/code-review P2 comments on 2891271:

  1. The mutation-gate sentence's dangling "covered under the engine's rungs below" now names the actual location, reference/engine.md's cli-parse rung.
  2. The /context suggest sentence's "gate basis: the verification record below" now has a real four-part record inline in this section (claim / basis / as-of / recheck), rather than pointing at a record that lived only in a separate reference file not shown to the person.

Instruction-surface lens applied: this commit only adds a verification record and fixes two dangling pointers; it does not delete, narrow, or soften the mutation-gate text itself — "This skill never runs /context in the person's session" is reaffirmed verbatim. No guardrail is touched.

No executable code, script, workflow, or config is touched. Combined with the nine prior clean security reviews on this branch, the full PR at head e62584e has no outstanding security findings.
· Branch

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 1m 17s —— View job


Code review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:code-review skill per custom instructions
  • Run skip-gate check — PR is open, not draft; head (e62584e) has one new commit since this lane's last review (of 2891271), so a fresh delta pass applies
  • Review the new commit (e62584e) for correctness/maintainability
  • Post findings

Scope. Delta review of e62584e ("fix(context-budget): inline the /context verification record"), a 12-line change to plugins/context-budget/skills/audit/SKILL.md. This is the fix for two open findings on this branch:

  1. Codex's P2 "Replace the dangling /context gate basis" — the Routing sentence named "the verification record below" but no record followed in SKILL.md (it lived only in reference/native-context.md, not visible to the person reading the offer).
  2. This lane's own earlier finding that "the engine's rungs below" pointed nowhere in this file (the rungs table lives in the separate reference/engine.md).

Findings: none.

Verified both fixes directly:

  • SKILL.md:92 now names the concrete file and rung: "the cli-parse rung in reference/engine.md". I checked reference/engine.md's degradation-ladder table — rung 2 is indeed cli-parse, so the pointer resolves correctly now.
  • SKILL.md:99-105 adds a same-file "Verification record, /context" paragraph (claim/basis/as-of/recheck), so the Routing sentence's "gate basis: the verification record below" now resolves within the same document instead of only in reference/native-context.md.
  • Cross-checked the new inline record's facts against docs/native-surfaces/records.json (gated: true, user_invocable: true, model_invocable: false, extraction date 2026-09-29, docs cross-check 2026-09-30) and against reference/native-context.md — all three agree, no drift introduced.
  • The remaining detail table in reference/native-context.md is left intact and the new sentence correctly calls it out as "the remaining records," since it still carries two claims (optimization-suggestions content, current-session-only scope) not restated in the new inline summary — no duplication problem.

No executable code, workflow, script, or config is touched. Combined with the nine prior clean review passes on this branch, the full PR at head e62584e has no outstanding code-review findings from this lane.
· Branch

@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e62584ebd8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/native-surfaces/records.json Outdated
The design rows' decisive evidence is the 2026-09-30 targeted search of
the 2.1.285 binary, so recheck.verified now reads 2026-09-30 on both;
native-surfaces.md regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: b30a60f053

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…weep-rest

# Conflicts:
#	plugins/evals/CHANGELOG.md
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 1m 41s —— View job


Code review — PR #5570

  • Gather context (PR diff, custom instructions)
  • Invoke /review:code-review skill per custom instructions
  • Run skip-gate check against head a80f67a — PR is open, not draft; this lane's last review covered e62584e, so the new delta (b30a60f plus the origin/main merge) needs a fresh pass
  • Review new delta for correctness/maintainability
  • Post findings

Scope. Two things landed since this lane's last review (of e62584e):

  • b30a60f — fixes Codex's P2 comment on e62584e ("Date the design rows' recheck to the identity check"): bumps recheck.verified from 2026-09-29 to 2026-09-30 for both design→prototype:explore-directions and design→visualization:visualize rows in docs/native-surfaces/records.json, with docs/native-surfaces.md regenerated to match.
  • The merge of origin/main into this branch (head a80f67a), which brought in ~330 unrelated files from other merged PRs.

Findings: none.

Verified the b30a60f fix directly: the two design rows' decisive evidence is the targeted string search that resolved the design registration's identity, which happened on 2026-09-30 (per the evidence text already in both rows), not the 2026-09-29 binary extraction date the verified field previously carried. The fix correctly moves both rows' recheck.verified to 2026-09-30 in records.json (L547, L589) and the matching (verified 2026-09-30) text in docs/native-surfaces.md (L664, L683). No other field in either row changed, and a scan for other design-related rows with a stale 2026-09-29 verified date (e.g. design-sync) found none that share this trigger text, so the fix is complete and scoped correctly.

Checked the origin/main merge for accidental loss of this PR's own changes: docs/catalog.md is the only one of this PR's 26 changed files touched by the merge diff, and comparing origin/main...a80f67a shows this PR's own edit (dropping the "design skill" clause from the visualization blurb) survived intact — the merge only layered in an unrelated session-flow skill-count bump from a separately-merged PR. No conflict markers, no reverted content.

This lane has now reviewed every commit on this branch with no outstanding findings.
· Branch

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 44s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: delta review of the new commit b30a60f ("fix(plugins): date the design rows' recheck to the identity check") on top of the already-reviewed e62584e/2891271/a1da570/0ab162d/e0f987f/feb9215/6fd31c3/f68d6ba/2f92eea/564afeb, per the skill's skip-gate (a head with a prior successful review only needs the new delta re-checked). The head merge commit a80f67a merges origin/main cleanly and introduces no further changes to this PR's own files (git diff b30a60f a80f67a on the PR's touched paths is empty), so b30a60f is the only new content to review.

Findings: none.

b30a60f touches two already-reviewed generated-data surfaces:

This is the fix for Codex's P2 comment on e62584e: the two design rows' recheck.verified date read 2026-09-29 (the extraction date) even though the decisive identity-resolving evidence was a targeted search performed 2026-09-30. The commit moves both dates to 2026-09-30 in records.json and the matching regenerated native-surfaces.md rows, keeping the generated file and its source in sync. No other field changes.

Instruction-surface lens applied: this is a two-field date correction in generated registry data, not a standing instruction, rule, or mutation gate — no ## Boundary text or guardrail is touched. docs/conventions/instruction-exception-register/README.md is present in this checkout and was consulted; it has no bearing here since nothing instructional is deleted, narrowed, or softened.

No executable code, workflow, script, or config is touched. Combined with the ten prior clean security reviews on this branch, the full PR at head a80f67a has no outstanding security findings.
· Branch

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a80f67a285

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread plugins/prototype/skills/explore-directions/SKILL.md
…nges

Both /design offers quote the bundled command's description as the
identity check, so every design verification record and both records.json
rows now recheck when a release changes that description.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton

Copy link
Copy Markdown
Contributor Author

@codex review

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 51s —— View job


Security review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:security-review per custom instructions
  • Post findings / summary

Scope: delta review of the new commit 91e39e3 ("fix(plugins): recheck the design rows when the quoted description changes") on top of the already-reviewed a80f67a/b30a60f/0ab162d/a1da570/2891271/e62584e/e0f987f/feb9215/6fd31c3/f68d6ba/2f92eea/564afeb, per the skill's skip-gate (a head with a prior successful review only needs the new delta re-checked).

Findings: none.

91e39e3 touches six already-reviewed documentation/generated-data surfaces:

This is the fix for Codex's latest P2 comment ("Recheck the exact /design identity string"): both design-adjacent verification records (records.json, native-surfaces.md, both SKILL.md Boundary sections, bundled-design.md, decision-matrix.md) now add "changes its description (the identity string both Boundary offers quote)" as an explicit recheck trigger, so a future release that keeps design user-only and gated but changes its displayed description will correctly invalidate these records instead of going unnoticed.

Instruction-surface lens applied: this commit only adds a recheck trigger to existing verification records — it doesn't delete, narrow, or soften the mutation-gate text (both "the model does not invoke it" / "This skill never runs..." sentences are untouched) or any other standing instruction. docs/conventions/instruction-exception-register/README.md is present in this checkout and was consulted; it has no bearing here since nothing instructional is removed.

No executable code, workflow, script, or config is touched. Combined with the eleven prior clean security reviews on this branch, the full PR at head 91e39e3 has no outstanding security findings.
· Branch

@claude

claude Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @kyle-sexton's task in 1m 11s —— View job


Code review — PR #5570

  • Gather context (PR diff, changed files, custom instructions)
  • Invoke /review:code-review skill per custom instructions
  • Run skip-gate check — PR is open, not draft; head (91e39e3) has one new commit since this lane's last review (of a80f67a), so a fresh delta pass applies
  • Review the new commit (91e39e3) for correctness/maintainability
  • Post findings

Scope. Delta review of 91e39e3 ("fix(plugins): recheck the design rows when the quoted description changes"), the fix for Codex's P2 comment on the prior commit ("Recheck the exact /design identity string") — the two design rows' recheck triggers covered invocability/gating/registration-shape changes but not a change to the quoted description string itself, even though both skills' offers now tell the person to verify /design by that exact string ("Make a new Design artifact from a brief").

Findings: none.

Verified the fix is complete and consistent across all six touched locations:

Confirmed no site quoting the identity string was missed: git grep -n "Make a new Design artifact from a brief" turns up exactly these row/record pairs plus the two evidence-log entries in native-surfaces.md/records.json (historical evidence text, not a recheck condition — correctly left alone), and the two skill-body offer sentences that already point at these updated Boundary sections rather than carrying their own separate trigger. The wording differs slightly by file ("the identity string the offer quotes" vs. records.json's "the identity string both Boundary offers quote," reflecting that one records.json row backs two skills' offers) but the two are consistent restatements of the same condition, not drift.

This is a narrowly-scoped, purely additive fix with no functional or structural change beyond the previously-requested recheck trigger. Combined with the eleven prior clean review passes on this branch, the full PR at head 91e39e3 has no outstanding code-review findings from this lane. I did not re-run overlap.py, check-changelog-parity.sh, or the other validation scripts cited earlier in this PR's history — no execution access in this sandbox; those remain author-reported and unverified by this review.
· Branch

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 👍

Reviewed commit: 91e39e3314

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@kyle-sexton
kyle-sexton merged commit fa4142d into main Sep 30, 2026
19 checks passed
@kyle-sexton
kyle-sexton deleted the feat/native-phrases-sweep-rest branch September 30, 2026 17:23
kyle-sexton added a commit that referenced this pull request Sep 30, 2026
)

No related issue: records one native-overlap dismissal; no tracked
issue.

## Summary

Records a dismissal of the built-in `worker` agent against
`session-flow:tidy-work` in the native-surfaces store and regenerates
the registry view.

## Fix

Name overlap only ('work'): tidy-work is a user-only skill that tidies
the gitignored .work memory tiers; the built-in worker agent executes
delegated tasks. Different jobs, no routing. Added via `overlap.py
dismiss`, then `overlap.py generate`.

## Verification

- `overlap.py detect`: 23 candidates, 0 with `store_verdict` null, 0
resurfaced.
- `overlap.py self-check`: degraded only on its 2 standing advisories.
- `scripts/check-changelog-parity.sh --check` and `--check-bump
origin/main`: pass, no bump needed.
- `node scripts/generate-catalog.mjs`: catalog already in sync.

## Related

#5447 (added tidy-work), #5570

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kyle-sexton added a commit that referenced this pull request Sep 30, 2026
…laude Design projects (#5610)

No related issue: operator ruling on 2026-09-30 to record the built-in
ClaudeDesign tool as route rows with Boundary sections; no tracker item
was filed for it.

## Summary

Claude Code 2.1.285 ships a model-invocable built-in tool,
`ClaudeDesign`, that reads and writes files in an existing
claude.ai/design project. Two of our skills,
`/prototype:explore-directions` and `/visualization:visualize`, produce
the same kind of output (mockups, decks, layouts). Until now nothing
told the model to use the tool when the person points at an existing
project. The operator ruled on 2026-09-30 that these become `route` rows
with Boundary sections, because the tool is in the shipped binary and
the model can use it, documented or not.

## Fix

- `docs/native-surfaces/records.json`: two new rows, `ClaudeDesign`
(`builtin-tool`, markers `gated`), verdict `complementary`, integration
`route`, one against each skill. Evidence records that the extraction
reports the tool's description as unresolved (a separate PR fixes the
extractor) and gives the string found by a targeted binary search.
- Both skills get a Boundary entry for the tool: `- **`ClaudeDesign`
(built-in tool)**: ...`, the routing split, and a mutation gate. The
gate says: write only to the project the person named, and only after
they asked; report the tool's approval and refusal cases and never retry
around them. The four-part records are in
`reference/claude-design-tool.md` (prototype) and
`context/claude-design-tool.md` (visualization).
- Both descriptions start with a phrase that states the whole routing
condition: when the person names or links an existing claude.ai/design
project, or asks for the work to go into one, and the tool resolves in
this session, use the tool; otherwise the skill renders its own output
as today. Two restating clauses were cut from each description to stay
under the 1,024-character limit (visualize is at 1,000,
explore-directions at 975).
- These rows are separate from the `design` bundled-skill rows: `design`
creates a new Design artifact and only the person can run it, while
`ClaudeDesign` works on an existing project.
- The native-references Adopters table was updated and that convention's
CHANGELOG is now at 3.3.6. prototype is at 0.13.6 and visualization at
0.8.4, each with a CHANGELOG entry.
- `Explore -> prototype:explore-directions` came back from detect after
the description change. It was dismissed again with its original reason.

Affected store rows (quoted, reason field):

> The built-in tool reads and writes files in an existing
claude.ai/design project; ours builds throwaway variants on the real
stack or as a local HTML mockup and keeps only the winning-variant key.
When the person names or links an existing claude.ai/design project, or
asks for the work to go into one, and the tool resolves in this session,
use the tool; otherwise this skill builds its variants as today.

> The built-in tool reads and writes files in an existing
claude.ai/design project; ours picks a visual form and medium and
renders its own output (inline, a local file, or a published Artifact).
When the person names or links an existing claude.ai/design project, or
asks for the work to go into one, and the tool resolves in this session,
use the tool; otherwise this skill renders its own output as today.

## Verification

- `overlap.py generate`: wrote docs/native-surfaces.md (66 rows, 79
dismissals). `node scripts/generate-catalog.mjs`: catalog already in
sync.
- `overlap.py detect --inventory
<main>/.work/native-surfaces-2-1-284/inv-2.1.285.json --repo .` (exit 3,
degraded inventory): one pair resurfaced, `Explore ->
prototype:explore-directions`, and it was dismissed again. The re-run
shows 0 resurfaced, 79 suppressed and no unrecorded candidates for
either plugin.
- `overlap.py self-check`: `SELF-CHECK degraded: 2 advisory(ies), 66
row(s) checked`. Both advisories are pre-existing: older extraction
versions and upstream SHA not checked. No problems.
- `validate-plugin-contracts.mjs`, `check-changed-skills.sh origin/main`
(both skills PASS), `check-skill-description-voice.sh`,
`check-changelog-parity.sh --check-bump origin/main`, markdownlint and
typos all pass.
- The binary facts were cross-checked by string search of
`/home/kyle/.local/share/claude/versions/2.1.285`: the description
string, the operation names, the `plan_token` flow and the
interactive-approval reason.

## Related

- #5570, the route-phrase sweep for these plugins
- The sibling `design` (suggest) and `design-sync` (defer) rows in the
same store

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kyle-sexton added a commit that referenced this pull request Sep 30, 2026
…plugins (#5629)

Closes #4661

## Summary

Eight listed skill descriptions in plugins the issue names were still
over 500 characters on `origin/main` (description plus `when_to_use`,
whitespace-normalised, YAML-parsed). This PR trims them, so no listed
skill in the issue's 18 plugins is over 500. The prior drain PR (#5422)
covered `architecture` and `improvement:find`; the native-route sweeps
(#5556, #5570) then re-grew several descriptions by prepending a `When
the bundled <x> skill resolves ... prefer ...` clause.

## Fix

Frontmatter only. Each skill keeps its native-route phrase in shortened
form, its quoted trigger phrases and its sibling boundary. No rename,
merge or `disable-model-invocation` change, no `plugin.json` description
change.

| Skill | Before | After |
|---|---|---|
| `claude-config:audit-instructions` | 838 | 494 |
| `claude-config:audit-permission-state` | 677 | 497 |
| `claude-config:audit` | 623 | 474 |
| `context-budget:audit` | 767 | 439 |
| `claude-ops:observability` | 721 | 456 |
| `claude-ops:inventory` | 522 | 464 |
| `code-tidying:audit-dead-code` | 501 | 439 |
| `fleet:reach` | 1112 | 475 |

Patch bumps with a CHANGELOG entry: `claude-config` 0.55.1, `claude-ops`
0.77.3, `context-budget` 0.6.48, `code-tidying` 0.25.3, `fleet` 0.2.1.

## Verification

- `check-listing-budget.sh plugins/*/skills` aggregate: 131638 chars
before (`origin/main`), 129613 after.
- Measured by YAML parse over the issue's 18 plugins: 8 skills over 500
on `origin/main`, 0 on this branch.
- `check-changelog-parity.sh --check`, `--check-bump origin/main` and
`--check-order`: pass.
- `validate-plugins.sh`: pass. `validate-plugin-contracts.mjs`: pass (59
setup skills, 4976 files).
- `check-changed-skills.sh origin/main`: 8 skills checked, 0 failed.
- `check-purged-em-dashes.sh --check`: no em dashes. `markdownlint-cli2`
on 13 changed files: 0 issues.
- `affected-tests.sh`: no suites selected (every changed file is a
no-suite class).
- Diff against `origin/main` shows only modified files and no `name:` or
`disable-model-invocation` change.

## Related

- #4657 (parent), #5422 (earlier trims), #5288 (deleted the
cap-exceptions doc), #5556 and #5570 (native-route phrases kept here),
#5561 (edits the `claude-config:audit` body, not its frontmatter).
- Not covered here: listed skills over 500 in plugins the issue does not
name. On this branch that is 82 skills across `adhd`, `ai-slop`,
`animation`, `attribution`, `bugs`, `claude-memory`, `codebase-health`,
`computer-use`, `context7`, `coupling`, `debugging`, `disk-hygiene`,
`domain-driven-design`, `education`, `evals`, `event-storming`,
`firecrawl`, `gaming`, `github`, `kindle-dedrm`, `machine-health`,
`mcp-tools`, `mutation-testing`, `naming`, `pixel-art`, `playbooks`,
`playgrounds`, `playwright`, `plugin-quality`, `prototype`,
`repo-fleet-hygiene`, `repo-hygiene`, `review`, `skill-quality`,
`songwriting`, `source-control`, `tdd`, `testing`, `toolchain`,
`verification`, `visualization`, `wizard`, `writing` and `x`. This PR
does not trim them.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant