docs: apply the fleet-wide prompt-audit against Claude Fable 5.1

.claude/rules/skill-bodies-state-current-rules.md

@@ -0,0 +1,36 @@
+---
+description: "Skill and agent bodies state the current rule and its reason, never the incident, PR, or model that motivated it; read before editing any skill body"
+paths:
+  - "plugins/*/skills/**"
+  - "plugins/*/agents/**"
+---
+
+# Skill bodies state current rules
+
+A skill body is read by the model on every invocation. Its authority is the behavior it
+prescribes, not the incident that motivated it, so the body carries the rule and the reason and
+nothing about how the rule got there. This follows the bundled `/claude-api prompt-audit` guide
+(Group 2, "Brittle skill files"), applied fleet-wide in the 2026-09 audit recorded in
+[`docs/specs/prompt-audit-skills-2026-09.md`](../../docs/specs/prompt-audit-skills-2026-09.md).
+
+Keep out of a skill or agent body:
+
+- Issue and pull-request numbers from this repository, incident IDs, and past-tense narration of
+  why a rule exists ("this was added after ...", "an earlier version claimed ...").
+- Pinned model names in behavioral guidance. A rule that only holds on one model belongs in the
+  `playbooks` model-adaptation chapters, not in a skill body.
+- Date-conditional guidance ("before 2026-08 ...", "until version X ships ...").
+- Hardcoded paths, flags, and version numbers stated as bare fact with no verification.
+
+Keep in the body:
+
+- The rule, stated in the present tense, with the reason beside it.
+- A pointer to an external upstream source (an official doc page, an upstream issue) when the rule
+  restates a volatile specific it cannot defer to at read time, recorded as the four-part
+  verification record the
+  [upstream-drift convention](../../docs/conventions/upstream-drift/README.md) defines: claim,
+  basis, as-of date, recheck trigger. A dated verification with a trigger is the correct form; an
+  undated claim is the defect.
+
+History belongs in the plugin's `CHANGELOG.md`, the commit message, and `docs/adr/`. A reader who
+needs the archaeology finds it there; the model reading the skill does not need it to act.

.claude/rules/worktree-base-ref.md

@@ -0,0 +1,22 @@
+---
+description: "This repository sets no worktree.baseRef; new worktrees branch from the remote default branch (Claude Code's default). Never add worktree.baseRef: head back, even when a reviewer says a merge dropped it"
+paths:
+  - ".claude/settings.json"
+  - ".claude/settings.local.json"
+---
+
+# No worktree.baseRef in this repository
+
+Claude Code's `worktree.baseRef` setting picks the ref a new worktree branches from. Unset, it
+is `fresh`: the repository's default branch as fetched from the remote, so every worktree
+starts from the latest `main`. The value `head` branches from the local checkout's HEAD
+instead, which spawns worktrees from whatever a session happens to have checked out.
+
+The operator withdrew the `head` override on 2026-09-02 (topic-docs convention 3.1.0, in
+[`docs/conventions/topic-docs/CHANGELOG.md`](../../docs/conventions/topic-docs/CHANGELOG.md)),
+and the setting stays absent on purpose. Do not add `worktree` to either settings file, and do
+not "restore" it because a diff against another branch shows it missing: `origin/main` can carry
+it for a while after a branch that removed it opens, and a review comment reading that diff
+will call the removal a regression. It is not. Before restoring any key a review says a merge
+dropped, run `git log -S'"<key>"' -- .claude/settings.json` on the branch and read the commit
+that removed it.

.claude/settings.json

@@ -18,9 +18,6 @@
       }
     ]
   },
-  "worktree": {
-    "baseRef": "head"
-  },
   "enabledPlugins": {
     "actionlint@melodic-software": true,
     "adhd@melodic-software": true,

AGENTS.md

@@ -26,6 +26,11 @@ context, read the file directly.
 | `.claude/rules/catalog-taxonomy.md` | `.claude-plugin/marketplace.json` | Where the marketplace category taxonomy lives; read before adding or changing a plugin's category |
 | `.claude/rules/hook-budget.md` | `plugins/*/hooks/**` | Marketplace-wide latency budget for always-on hooks; read before adding or widening a hook |
 | `.claude/rules/ruff-pin.md` | `**/*.py` | Python linting runs through the pinned ruff wrapper, never a bare ruff on PATH |
+| `.claude/rules/skill-bodies-state-current-rules.md` | `plugins/*/skills/**, plugins/*/agents/**` | Skill and agent bodies state the current rule and its reason, never the incident, PR, or model that motivated it; read before editing any skill body |
+| `.claude/rules/worktree-base-ref.md` | `.claude/settings.json, .claude/settings.local.json` | This repository sets no worktree.baseRef; new worktrees branch from the remote default branch (Claude Code's default). Never add worktree.baseRef: head back, even when a reviewer says a merge dropped it |
+| `plugins/autonomy/AGENTS.md` | `plugins/autonomy/**` | autonomy plugin: contributor conventions |
 | `plugins/machine-health/skills/audit/AGENTS.md` | `plugins/machine-health/skills/audit/**` | machine-health audit skill: contributor conventions |
+| `plugins/provenance/skills/audit/AGENTS.md` | `plugins/provenance/skills/audit/**` | Editing the provenance audit skill: contributor conventions |
+| `plugins/work-items/skills/work-loop/AGENTS.md` | `plugins/work-items/skills/work-loop/**` | work-loop: contributor conventions |
 
 <!-- END GENERATED: instruction-placement rules index -->

docs/adr/0028-audit-skill-bodies-fleet-wide-against-the-current-model-and-apply-directly.md

@@ -0,0 +1,119 @@
+# Audit skill bodies fleet-wide against the current model and apply the findings directly
+
+- Status: accepted
+- Date: 2026-09-02
+- Supersedes: [ADR-0004](0004-rightsize-instruction-surfaces-by-incumbent-first-arbitration.md) decisions D-1 and D-3, for the skill-body audit lane only; the promotion gate of [ADR-0006](0006-scope-model-doctrine-per-version-behind-a-promotion-gate.md) as retained by [ADR-0007](0007-host-per-model-doctrine-outside-skill-private-surfaces.md), for applied prompt-audit findings only
+
+## Context
+
+Claude Code ships a `prompt-audit` procedure inside its bundled `claude-api` skill. It reads
+an instruction surface against a named target model, classifies each dated pattern into one
+of four groups (obsolete scaffolding, brittle history and volatile specifics, worked examples
+that constrain, and request-building code the model executes by hand), and prescribes a
+concrete action per finding: remove, rewrite, move, replace with an API feature, add, or flag.
+Its keep list is as binding as its pattern tables, and it states that an audit which finds
+nothing changes nothing.
+
+In September 2026 the operator ran that procedure over every skill in this marketplace with
+Claude Fable 5.1 as the target model. The run is recorded in
+[`docs/specs/prompt-audit-skills-2026-09.md`](../specs/prompt-audit-skills-2026-09.md): one
+fresh-context auditor per plugin, one report per plugin, the lead's per-finding decisions, one
+commit per plugin with a patch bump and evals updated in step, and a follow-up inventory. The
+sweep closed on 2026-09-05 over all 74 plugins: 63 took a commit and 11 were clean (one
+single-skill plugin and ten whose only in-scope file the setup lane had audited). Across the
+64 reports the lead applied 805 finding ids and withheld 207, the withheld set listed in the
+record by plugin. The branch changed 694 files under `plugins/`, and no skill lost a step, a
+gate, or a safety refusal in the record's five-skill behavioral spot-check.
+
+Three accepted decisions stood in the way, and the operator ruled before the first wave that
+none of them binds this lane:
+
+- **ADR-0004 D-1, the incumbent-first gate.** No remediation ships until it proves no existing
+  skill already covers it. A prompt-audit finding is a text defect at a `file:line`; its
+  remediation is the hunk the procedure prescribes. An incumbent search per hunk would cost
+  more than the hunk and answer a question the procedure already answered (the pattern table
+  is the incumbent).
+- **ADR-0004 D-3, no bulk sweep of `plugins/**`.** Findings were to land as checks in the
+  plugin that owns each surface, never as a sweep. That decision was written for a
+  practitioner article whose claims were a third unbacked. The prompt-audit guide is the
+  vendor's own procedure for the vendor's own model, and its findings are edits, not
+  criteria. Landing them as checks would leave every body unchanged.
+- **ADR-0006's promotion gate, retained verbatim by ADR-0007.** Doctrine sourced from a single
+  model's guide is model-scoped by default and reaches fleet-wide only when a model-agnostic
+  upstream document states the claim or several model guides converge on it. The audit labels
+  every finding `fleet` or `fable-5-1`. Applying only the `fleet` set would leave the
+  `fable-5-1` set, which exists precisely because the target model changed, unapplied on the
+  model it targets.
+
+ADR-0004 D-15, arbitration over blanket deletion, was honored in form: every applied finding
+carries the constraint's rationale and why it no longer holds for the target model, and the
+guide's keep list (exact scripts for fragile operations, safety gates, working redundancy)
+was applied as written. Two further ADRs were checked and left accepted:
+[ADR-0005](0005-bound-instruction-surface-work-by-question-not-population.md) bounds
+instruction-surface work by the question it asks, and this lane asks one question (is this
+passage a dated prompting pattern for the target model), so it is consistent.
+[ADR-0008](0008-admit-only-present-text-defects-to-the-instruction-audit-catalog.md) governs
+what enters the `audit-instructions` catalog; this lane edits bodies and records catalog gaps
+without adding rows, so it is consistent. Whether either should retire on other grounds is the
+operator's call at PR time and is not decided here.
+
+## Decision
+
+**A skill-body audit against the current model runs as a fleet-wide sweep and applies its
+high and medium confidence findings directly**, one commit per plugin, without an
+incumbent-first gate and without scoping applied findings to the model that motivated them.
+
+The procedure is the bundled `prompt-audit` guide at the Claude Code version that ran it,
+with the target model named at Step 0. Where the migration guide carries guidance for a prior
+model and none for the target, the prior model's guidance applies; on conflict the target
+model wins.
+
+Three rules travel with the decision:
+
+1. **Labels are recorded, not gated.** Every finding carries `fleet` or `fable-5-1`. Both are
+   applied. The label exists so a consumer on another model can read what changed and why;
+   it does not decide whether the change ships. The promotion gate of ADR-0006 continues to
+   govern the `playbooks` model-adaptation chapters and the `audit-instructions` catalog's
+   `Model scope` rows, which are doctrine surfaces. It does not govern edits to skill bodies
+   that remove a pattern the target model no longer needs.
+2. **Repo conventions yield to the procedure inside the lane.** A CI gate or a static check
+   that blocks a warranted change is changed in the same commit, and the change is recorded in
+   the run's record. The first instance is `skill-quality`'s check 3, which hard-failed any
+   dropped trigger phrase and so blocked the guide's Group 2 fix for trigger-case
+   enumeration; it is now advisory.
+3. **Skill bodies state current rules.** The path-scoped rule
+   `.claude/rules/skill-bodies-state-current-rules.md` codifies the guide's Group 2 for
+   `plugins/*/skills/**` and `plugins/*/agents/**`: a body carries the rule and its reason
+   in the present tense, and history belongs in the CHANGELOG, the commit, and `docs/adr/`.
+
+Mechanism changes the audit exposes (extracting a hand-executed shell block into a script,
+adding a pre-compute block, parameterizing a hardcoded vendor) are follow-ups, not audit
+hunks. The record inventories them and the PR body carries them verbatim.
+
+## Consequences
+
+**Bodies change fleet-wide in one PR, and the diff is large.** The record is the reviewable
+unit: each plugin's row names its commit, its applied and withheld finding ids, and the
+trigger phrases it deliberately dropped. A reviewer who wants the archaeology reads the
+report the record points at; the body no longer carries it.
+
+**The incumbent-first gate loses its blanket status.** ADR-0004 D-1 still binds lanes that
+propose new machinery, where a duplicate is the risk. It no longer binds text-defect lanes
+whose remediation is a prescribed hunk. The cost is that a future sweep can apply a hunk an
+existing check would have caught differently; the record's catalog-gaps section is where that
+shows up, and the `audit-instructions` catalog is extended from it under ADR-0008's
+admission rule.
+
+**Fable 5.1-specific edits are live on every model.** A consumer running an older model reads
+bodies tuned for the current one. The label in the record says which edits those are, and the
+`playbooks` adaptation chapters remain the place to counter-steer per model. This is the
+trade the operator chose over leaving the target model under-served.
+
+**Trigger phrases can be dropped on purpose.** Check 3 warns instead of failing, so a
+description that consolidates near-synonyms into an intent category ships with the warning
+recorded. A reviewer confirms the intent is still named or restores the phrase; the check no
+longer decides.
+
+**The audit repeats per model change.** The playbooks' own regeneration trigger fired with
+Fable 5.1 (record follow-up F14). Each future target model re-runs this lane from the
+record's method section, with the previous run's withheld items as the first candidates.

docs/conventions/topic-docs/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog — topic-docs convention
 
+## 3.1.0 — 2026-09-02
+
+Minor under the Versioning rule: no tier moves, no `topic-docs.yaml` key is renamed, the slug
+spec is untouched, and no visibility guarantee an implementer may rely on changes. The contract
+already forbade any skill, gate, or audit from assuming the `worktree.baseRef: "head"` override
+was in force, so withdrawing it changes the matrix's shape, not what a context may rely on
+seeing.
+
+- **The `worktree.baseRef: "head"` mechanism is withdrawn.** This repository no longer sets it
+  in `.claude/settings.json`, and the convention no longer asks consuming repositories to. A
+  worktree Claude Code creates branches from the repository's default branch on the remote,
+  which is Claude Code's default, `"fresh"`, per the official worktrees page fetched
+  2026-09-02. The native mechanisms are now three: `.worktreeinclude`, by-value worker returns,
+  and the tracker as the cross-lane index.
+- **Visibility matrix**: the "spawned from local HEAD" row is gone. The remaining worktree row
+  describes the default base, with the memory column still conditional on a `.worktreeinclude`,
+  and the consequences paragraph now says a contract document reaches a spawned worktree only
+  once merged to the default branch.
+- **Consumer adoption** materializes one file, `.worktreeinclude`. The committed-settings
+  snippet and its untracked-settings pull-collision rollout caveat are removed with it.
+
 ## 3.0.0 — 2026-09-01
 
 Major under the Versioning rule: the memory tier's slice shape, the reserved-name set, and the