Selection-scoped install bundle + tracker gap closure (post-#344)

[dean0x]

Summary

Follow-up to the pluggable-tracker wave (#321 tracking; phases #322–#325; PR #344 is Phase 3). A six-way audit on 2026-09-19 found the GitHub path functionally preserved but surfaced a design divergence and six Jira/Linear blockers that this issue closes in one PR on a fresh branch off main after #344 merges.

Scope

Half A — selection-scoped bundle. Skills become plugin-scoped via a hand-declared requires: field per plugin with a bidirectional closure guard; /code-review language focuses become presence-gated. The installer overlays only {github} ∪ {selected provider} tracker references (13 for github, 24 for jira/linear), _mcp.md and the Tracker agent file only for jira/linear. devflow tracker --set converges every artifact in both directions. Build still compiles all 34 references.

Half B — gap closure. Six Jira/Linear blockers: provider-neutral gather-release-evidence (currently dead under jira/linear), _mcp.md loaded unconditionally per spawn under non-github, observable Tracker-agent claim outcome (CLAIMED/LOST), Reference Rendering default Refs {KEY}-{n} so ensure-pr-ready/create-release stop emitting permanent DEGRADED, two-server per-capability MCP scoping, corroboration scan replaced by the OD-9 prohibition. GitHub fixes: resolve-review-threads rate-limit thresholds restored, {ISSUE_REF} output templates, /implement and Code agent provider-aware PR-link handling, github-api.md defers to the D9 gate. Then: delete ~2,200 lines of transition test scaffolding (containment exemptions, baseline tree, guard census), collapse the phase-named byte ceilings once (authorised), third golden re-capture (authorised), docs rewritten as end state, ADR-026 via the learning pipeline.

Delivery

One PR, ~27 commits in six sequential Code-agent phases (P1 installer/registry/CLI → P2 test-scaffolding deletion → P3a git-agent surface → P3b tracker agent + command layer → P4 golden re-capture + ceiling collapse → P5 docs/KB/ADR). Golden byte-equality tests are red by design from P3a until P4 commit 1.

Not in scope

Release back-links compliance gate; per-repo provider key as a true override; EC-19 revert; the 108-item docs-approval package; _jira/_linear module collapse; FEATURE_OWNED_AGENTS; install-time conditional hook Section 3; comment_cap() hoist (#343).

Refs #321 #325 #343 #345 #346

[dean0x]

Implementation Plan (from ensure-traceable-issue)

---

title: Selection-scoped install bundle + tracker gap closure
date: 2026-09-19
status: approved
execution-strategy: SEQUENTIAL_CODE_AGENTS
context-risk: HIGH
base-branch: main
refs: [321, 325, 343, 345, 346]

Plan: Selection-scoped install bundle + tracker gap closure

Status: DRAFT (Gate 0 confirmed 2026-09-19; Gates 1 and 2 pending)

Context

A two-week wave (PRs #327, #334, #338, #339 merged; PR #344 open on
feat/325-tracker-phase-3-init-selected-provider) made devflow's issue
tracker pluggable (github | jira | linear). A six-way audit on 2026-09-19
found the GitHub path functionally preserved but surfaced:

• Design divergence: nothing is bundled at init. The build compiles all
  three providers and the installer overlays all 34 generated references onto
  every install. Selection is one manifest string; the Git agent picks a
  directory at spawn time. A GitHub user gains 21 files / 73 KB they cannot
  reach. Skills also install universally regardless of plugin selection
  (rules and agents are already plugin-scoped).
• Six blockers in the Jira/Linear paths (release evidence dead by
  construction, _mcp.md unreachable for half the ops, Tracker agent claim
  gate indistinguishable branches, permanent DEGRADED from an unfillable
  schema section, two-server ambiguity, non-executable corroboration step).
• One GitHub regression (resolve-review-threads lost its rate-limit
  thresholds) and several pre-existing GitHub-path defects (/implement
  hardcodes #, github-api.md contradicts the D9 gate).
• ~2,200 lines of transition test scaffolding that the project's own
  end-state rule (ADR-003) says should not survive the merge.

Summary (read this first)

What ships: one PR on a fresh branch off main after #344 merges, 27 commits in six sequential Code-agent phases, Closes #<N> (tracking issue filed at output).

Half A — selection-scoped bundle. Skills become plugin-scoped via a hand-declared requires: field per plugin (src/core/plugins.ts) with a bidirectional closure guard whose corpus spans commands, agents AND skill bodies; /code-review's language focuses become presence-gated. The installer overlays only {github} ∪ {selected provider} references (13 for github, 24 for jira/linear), _mcp.md only for jira/linear, and the Tracker agent file only for jira/linear — via a pure installedReferenceManifest({provider}) in mds-variants.ts, a new tracker-install.ts mirroring compliance-install.ts, a pure resolveSkillInstallPlan for install/remove/dormant-shadow sets, and a devflow tracker --set that converges every artifact both directions (overlay before manifest, abort on failure). Hook Section 3 stays installed and runtime-gated. Build still compiles all 34 references (tarball floor unchanged).

Half B — gap closure. git.mds edits in byte-funding order (Operations-table column cut first, −1,328): _mcp.md unconditional load for non-github, corroboration scan replaced by the OD-9 prohibition, one project-key alphabet, mismatch DEGRADED split by cause, provider-neutral gather-release-evidence (keyword-anchored KEY-N with project-key equality), {ISSUE_REF} templates, rate-limit pointer restored, Reference Rendering rule in _mcp.md with per-provider default Refs {KEY}-{n}; _mcp.mds gains two-server per-capability scoping, a rate-limit signals section, and the hoisted ref_preflight_head; _jira/_linear post the plan as content; tracker.md claim gate becomes observable (CLAIMED/LOST), compose chain fail-closed, one heartbeat; implement.mds/code.md get provider-aware PR-link handling; github-api.md defers to D9. Then: delete the containment scaffolding (five live describes re-homed first), collapse the phase-named ceilings once (authorised), third golden re-capture (authorised), docs rewritten as end state, ADR-026 via the learning pipeline.

Critical files: src/core/plugins.ts, src/targets/claude-code/installer.ts, src/targets/claude-code/tracker-install.ts (new), src/core/mds-variants.ts, src/cli/commands/{init,tracker,skills,uninstall}.ts, src/assets/agents/git.mds, src/assets/mds/tracker/{_mcp,_jira,_linear,_github,_common}.mds, src/assets/agents/tracker.md, tests/tracker/byte-budget.test.ts, tests/fixtures/numeric-floors.json.

Verification: per-phase targeted vitest + npm run build; full suite (excluding eager-memory-refresh) at end of P1 and P4; scratch-HOME e2e (init --tracker github|jira|linear, diff -r, --set round-trip, uninstall --plugin); goldens re-captured once in P4 commit 1; byte-budget table copied into every P3 handoff.

Risk: HIGH overall (P3a is the peak). Golden tests are red by design from P3a until P4 commit 1.

Gate 0 — confirmed scope (user decisions, 2026-09-19)

Decision	Answer
Bundle scope	Full selection-scoped bundle. Tracker: only the selected provider's references; _mcp.md, Tracker agent and hook Section 3 only for jira/linear. Skills become plugin-scoped like rules. Every installed file traces to a selection.
Delivery	Merge #344 as-is first, then one gap-closure PR on a fresh branch off main. No release until the follow-up merges.
Release back-links	Stay compliance-gated (NOT reversed).
Per-repo provider key	Stays NARROWS-only (NOT a true override).
Transition test scaffolding	Delete (containment exemptions, baseline tree, guard-census, phase-named ceilings, soften exact-prose pins).
Jira/Linear plan artifact	Post the plan content, not a pointer.
EC-19 reversal	Keep (tracker directive suppressed outside git repos).
Docs-approval package (108 items)	Discard; rewrite CLAUDE.md / README / CHANGELOG / KB docs as end-state prose in one pass.

Audit findings feeding this plan (2026-09-19)

Blockers

1. src/assets/agents/git.mds:543-544 — gather-release-evidence parses only #[0-9]+ and filters "digit-only" in the provider-neutral body → SHIPPED_ISSUES always empty under jira/linear; backlink-shipped-issues + create-release jira/linear mechanics are dead code. Provider-scope guard is one-directional (never checks GitHub grammar leaking into neutral body).
2. _mcp.md named only by 5/10 jira/linear provider files and by nothing in git.md → fetch-issue, fetch-issues-batch, ensure-pr-ready, create-release, gather-release-evidence run tracker calls without the transport prohibition / trust discipline.
3. src/assets/agents/tracker.md:100 — claim gate win (:) and loss (exit 0) branches produce identical observable output; losing agent proceeds until ln EEXIST backstop.
4. tracker.md ## Reference Rendering has no probe, no documented default, never fillable → permanent # UNRESOLVED: → ensure-pr-ready/create-release emit DEGRADED forever for every jira/linear user.
5. _mcp.md selects tools by description with no server scoping → two connected MCP servers can create the issue in the wrong tracker.
6. git.md:37 ref-grammar corroboration: no command named, "closing refs" undefined, "60% share" no denominator, KEY-N cannot distinguish jira/linear; "first hit wins" wrong (rung 1 needs rung 2).

Should-fix (wave)

• resolve-review-threads lost X-RateLimit-Remaining <10 STOP / <50 backpressure (moved to a file this op never loads). GitHub regression.
• Linear 400 RATELIMITED correction only in backlink-shipped-issues.md; D4 generic 4xx rule continues into the penalty window for every other Linear op.
• git.md:62 "never #-prefixed" vs nine #{number} Output templates (8 sibling PR placeholders are real). Make templates {ISSUE_REF}.
• tracker configuration mismatch names two causes (config.json narrowing vs tracker.md frontmatter).
• tracker.md:315 heredoc compose is an unchecked first link; shape gate greps ## Dedup Strategy but claims to bracket the last heading (### Substitutions, conditional).
• Bare-number DEGRADED string differs by op under jira (ambiguous issue reference vs grammar-mismatch).
• git.md:38 "the documented neutral default" for project key defined nowhere; jira/setup-task.md:13 says DEGRADED instead. $ARGUMENTS is slash-command vocabulary in an agent prompt.
• Assignee/Tech Debt sentinel-vs-constant three-way ambiguity in tracker.md; write-less exit does not say whether claim is deleted; heartbeat over-specified (~19 touches).
• Prompt hygiene: ADR-007/PF-003 in git.md:46,899; [DR-09] in jira/linear backlink files (source _mcp.mds:99); [DR-02]/(PF-003) in tracker.md:393,401; "Phase 5/9" at git.md:722; devflow test path in tracker.md:50; uninstall rationale tail on git.mds:60; §14.9 in hook comments.
• Duplication: _jira.mds/_linear.mds ~0.85 similar; ref-grammar preflight head ×14; reference_rendering_gate + dedup_ladder missing from SHARED_RULES guard; 7 lines triplicated across all three providers (COMPLIANCE policy, </untrusted-issue-body> control, manage-debt bullets).
• src/core/tracker.ts basename constants unused by uninstall.ts:403-405 (literals duplicated); TRACKER_GITHUB_OPS alias with 21-line JSDoc; trackerConventionsBackupName/Path exported but internal.
• CLAUDE.md Tracker paragraph 9.5 KB single block, 11 internal IDs, --no-tracker absence stated twice.
• init.ts:217 install summary never names the active provider; settings.json key order churns on re-init.
• reference-overlay.test.ts:289 comment overclaims regression-guard power.

Beyond the wave (pre-existing, user asked for all gaps)

• dist/commands/implement.md:63 drops any arg not starting with #; :478 hardcodes Closes #{ISSUE_NUMBER}; code.md:98 GitHub-only shape check. Silent evidence loss under jira/linear.
• src/assets/skills/git/references/github-api.md:678 "resolve on FALSE_POSITIVE/BY_DESIGN" contradicts D9 gate git.md:667 (pre-wave, confirmed at e726874).
• Machine-wide provider + corroboration cannot detect #N history → no remedy hint when a GitHub repo resolves jira/linear.
• Linear permanent dedup unavailable — duplicate possible (kept as-is; honest; note in docs).
• LEGACY_SKILLS_V2 / *_V2 identifiers in legacy.ts/post-install.ts (pre-existing residue; out of scope unless cheap).

Test scaffolding to delete/rename

• tests/fixtures/containment-exemptions.ts (919 L), tests/tracker/containment.test.ts (1,192 L), tests/fixtures/tracker/baseline/.
• tests/guards/guard-census.test.ts; phase labels in tests/guards/retired-wording.test.ts.
• BUDGET_GIT_MD_P3, BUDGET_LOADED_SET_P3, PREAMBLE_CHARS_P2 → collapse to one ceiling each; strip §14.x/P3a-S14 from messages.
• 23 narrating description fields in tests/fixtures/numeric-floors.json.
• ~80 exact-prose toContain pins in tests/tracker-agent.test.ts / tests/shell-hooks-tracker.test.ts → regex/behavioural.

Constraining decisions (from .devflow/learning/)

• ADR-003 end-state not transition; ADR-013 core/CLI split; ADR-014 state-aware re-init; ADR-024 prove-you-wrote-it ownership; ADR-025 classify guard literals individually.
• PF-009 install fan-out per-item isolation; PF-012 legacy lists frozen; PF-015 multi-artifact toggle must converge every artifact in both directions; PF-018 non-vacuous tests; PF-023 validate at the sink; PF-027 containment controls must stay always-loaded; PF-058; PF-060 never init against real HOME; PF-063 heading tokens in generated refs; PF-064 absence-based guards; PF-066 security shell chains in prose; PF-067 prohibition + exemption registry one authority; PF-068 rename-to-claim; PF-071 declared type is the retention policy.

Gate 1 — confirmed (2026-09-19)

Decision	Answer
Golden github-status-lines.txt	Third one-time re-capture authorised for Blocker 1, rate-limit restore, and {ISSUE_REF} template neutralisation. One fixture-only commit; frozen again after. AC-3.1 template-freeze rationale + schema-scope claim-6 third clause + companion arm retired.
Byte ceilings	One-time re-baseline: collapse *_P3/PREAMBLE_CHARS_P2 pairs to one ceiling each, set just above post-change measurement, record what the raise bought; companion gate retired; re-derive downward thereafter.
Install set	{github} ∪ {selected provider} references (24 files for jira/linear, 13 + 0 extra for github). github is the floor.
Skill closure	Hand-declared requires: per plugin in src/core/plugins.ts + bidirectional guard (every devflow:<skill> ref in a plugin's command/agent sources resolves inside skills ∪ requires; nothing in requires unreferenced). No generated map.

Orchestrator decisions on agent consensus: hook Section 3 stays installed and runtime-gated (no install-time variant); Tracker agent stays declared in devflow-core-skills.agents, filtered at install time (no FEATURE_OWNED_AGENTS); D-TRACKER-CONVERGE extended with a fourth owner (reference subtree + _mcp.md + agent file) — manifest write first, mechanics before sentinel, never inverted; _jira.mds/_linear.mds stay separate, ref-grammar preflight head hoisted as a parameterised _mcp.mds define, new _common.mds partial for the triplicated lines; Reference Rendering rule/gate in _mcp.md, default value in each provider file; two-server scoping rule in _mcp.md with per-capability (not per-group) qualification and unique-winner-else-DEGRADED; claim-gate fix is observability only (primitive already exclusive-create — verified at tracker.md:100).

Artifacts: exploration synthesis scratchpad/exploration-synthesis.md; gap reports scratchpad/gap-completeness.md, scratchpad/gap-security.md, plans-dir siblings *-agent-ade411dfd818584c7.md (performance), *-agent-a822e88e3ba59e687.md (architecture); gap synthesis scratchpad/gap-synthesis.md (canonical DEGRADED registry §4, funding table + end-state ceilings §5).

Implementation synthesis (Phase 9): /Users/dean/.claude/plans/okay-let-s-go-ahead-sequential-badger-agent-adec9a023453d5e15.md — every file:line, signature, byte delta, per-plugin requires: table, deletion ripple, guard-clone targets, nine sequencing constraints (§5).

Additional orchestrator decisions (Phase 8/9): language skills presence-gated in /code-review (probe ~/.claude/skills/devflow:{focus}/SKILL.md, mirroring COMPLIANCE_SKILL_INSTALLED), never in requires; the Skill(skill="devflow:{focus}") template is the ONE classified guard exception. tracker --set order: probe git skill present → overlay against installedReferenceManifest({provider}) (failure ⇒ exit 1, nothing changed) → rename conventions → persist manifest → converge agent file → rearm → sentinel (only if converged). init order: installViaFileCopy (overlay inside) → manifest → agent converge → rearm → sentinel. Heartbeat: one touch at probe→compose; rationale replaced. Over-cap plan: TRACEABILITY: DEGRADED (plan artifact exceeds comment cap). PR-link default Refs {KEY}-{n} for jira and linear. Jira grammar gains ASCII-upper normalisation (stated behaviour change). Branch-name ref source dropped (delete the claim at _jira.mds:188/_linear.mds:226). Corroboration scan deleted for the OD-9 prohibition. Blocker 3 is observability-only (claim primitive already set -o noclobber).

Implementation Steps (Phase 10 — ordered, 28 steps, 23 commit units)

Branch / PR shape

Wait for #344 to merge. git checkout main && git pull, then git checkout -b feat/selection-scoped-bundle-tracker-gaps. One PR, conventional-commit subjects. Every install test uses a mkdtemp HOME (PF-060). Every DEGRADED literal added/split/retired lands in/leaves LIVE_REASONS (tests/tracker/schema-scope.test.ts:596) in the commit that adds/retires its emitting site. Closes the tracking issue filed at Phase 14.

NOT in scope

Release back-links compliance gate; per-repo key as true override; EC-19 revert; the 108-item docs-approval package; C7 reply-template relocation; _jira/_linear collapse; FEATURE_OWNED_AGENTS; install-time conditional hook Section 3; *_V2 renames (one-line PF-012 comment only); comment_cap() hoist (#343); DEGRADED registry item 5 (tracker configuration contradicted by repository history) — its only emitter is deleted.

Part A — installer / registry / CLI (6 commits, steps 1–9)

A1 feat(plugins): hand-declared requires: per plugin with a bidirectional closure guard

1. src/core/plugins.ts — add requires: readonly string[] to PluginDefinition (insert :49) with JSDoc stating the guard and the one classified exception; fill the 13-row table from the synthesis (language plugins []; compliance never in requires). Add pure skillsOf(plugins), skillOwners(name): string[], buildScopedSkillsMap(plugins) (key set = ⋃ skills ∪ requires; unowned required key → skillOwners()[0]); buildFullSkillsMap (:484) becomes a thin wrapper. RED: tests/registry-integrity.test.ts new guard cloned from Guard 1/2 (:37, :80, collectAgentSourceNames :99-112) — forward, reverse, unreferenced-requires arms with synthetic probes; tests/plugins.test.ts Guard 1/2 gain requires arms; unit: buildScopedSkillsMap([explore]) = 12 keys, explore.requires ∋ review-methodology.
2. src/assets/commands/code-review.mds — language focuses presence-gated (probe before spawning; mirrors COMPLIANCE_SKILL_INSTALLED :39-41, :151, :168). Same commit. RED: gate sentence present; no language skill in any requires.

A2 feat(mds-variants): installedReferenceManifest — {github} ∪ {provider}, _mcp.md iff MCP-backed
3. src/core/mds-variants.ts — installedReferenceManifest({provider}): filter expandVariants pairs by dirname ∈ {tracker/github, tracker/${provider}, ``}; append tracker/_mcp.md iff `MCP_BACKED_PROVIDER_SUBDIRS.includes(...)` (predicate shape of :531). `tests/fixtures/numeric-floors.json` — add `installed-reference-count-github`=13, `installed-reference-count-provider`=24 (sourceFile `tests/installer/reference-overlay.test.ts`); annotate the two 34-entries as build/tarball-scoped, values untouched. RED: reference-overlay tests github→13/31,399 B, jira→24, linear→24, `_mcp.md` biconditional, no provider literal in the function.

A3 feat(tracker-install): convergeTrackerArtifacts owns the tracker agent file and the scoped reference overlay
4. New src/targets/claude-code/tracker-install.ts mirroring compliance-install.ts (:22-39, :276, :282-286, :300-303, :306-341, :390): options/result per synthesis; agent file {claudeDir}/agents/devflow/tracker.md copied from agentSourceDirs() iff provider ≠ github, removed otherwise; exported overlayInstalledReferences({claudeDir, provider, warn}) reusing the installer's one overlay spelling; warn-not-throw; converged=false on failure. tracker stays declared in devflow-core-skills.agents. RED: new tests/installer/tracker-install.test.ts — biconditional both directions, isAbsolute precondition, permission failure ⇒ converged=false, agent-roster-count 17 unchanged.

A4 feat(installer,init): selection-scoped skills map, gated pre-clean, provider-scoped overlay, tracker-aware summary (co-commit: trackerProvider becomes required)
5. src/targets/claude-code/installer.ts — FileCopyOptions gains required trackerProvider (after warn? :1219); overlay :1453-1461 passes manifest: installedReferenceManifest({provider}); skills pre-clean :1318-1334 iterates skillsMap.keys() gated !isPartialInstall, with a comment that the orphan sweep :1311-1315 (full registry) and the pre-clean (scoped) are deliberately opposite; explicit deselection removal set = skillsOf(DEVFLOW_PLUGINS) \ skillsOf(selected) \ FEATURE_OWNED, full-install only, never readdir; compute install set first, then shadows (:1436-1447); new InstallReport.dormantShadows. Agents copy/sweep :1378-1411 unchanged.
6. src/cli/commands/init.ts — hoist resolvePluginList (:2394) to after :1663 → effectivePlugins; :1666 → buildScopedSkillsMap(effectivePlugins); manifest plugins: effectivePluginNames; agentsMap/rulesMap stay on pluginsToInstall; call site :1718-1731 adds trackerProvider; TrackerLifecycleIO :405-415 gains convergeArtifacts; persistManifestThenConvergeTracker :469 order = manifest → rename → agent converge → rearm → sentinel (only if converged); D-TRACKER-CONVERGE JSDoc :442-466 recounts four owners; export describeOverlayFailureState (:246); formatOverlaySummary :207 gains provider; summary rows Tracker: {provider} (+ (default)/ (was {previous})), Tracker assets: +{n} reference(s), −{m} reference(s){, tracker agent installed|removed}, and when removal set non-empty AND plugin list unchanged: Removed {n} skill(s) no selected plugin requires: {names}. Re-run devflow init and select the plugin that provides them to keep them.; dormant-shadow line Shadow for {name} is inactive — the plugin that uses it is not selected. RED (installer-new.test.ts :255-271 + reference-overlay :244-287 shapes): --plugin=X removes nothing; full re-init removes exactly the set difference; --reset = full; 34-ref tree prunes to 13/24 and stale tracker agent disappears under github; shadow outside scope dormant, never deleted; self-heal prints (was jira); default install 40→32 skills, --plugin=devflow-explore = 12; settings.json key order stable across two inits (fix or state cosmetic).

A5 feat(tracker): --set converges the scoped bundle in the fixed order; --status reports installed mechanics
7. src/cli/commands/tracker.ts — --set order per the orchestrator decision; overlay failure ⇒ describeOverlayFailureState, Tracker: not changed — {provider} assets could not be installed, exit 1 (comment the asymmetry vs warn-only rename/rearm/sentinel at :17); git skill absent ⇒ manifest+sentinel, "devflow:git is not installed; run devflow init", exit 0, no references/ husk; outcome Tracker: {provider} — {n} installed, {m} removed / (unchanged); idempotent same-provider still runs the overlay. --status gains Mechanics: installed ({n} file(s)) / MISSING — run devflow init / unreadable ({errno}). RED: recording TrackerLifecycleIO stub asserting call sequence; overlay failure leaves prior 24 files + manifest intact; missing skill creates no husk; jira→linear swaps subtree and keeps github 13; --status three arms.

A6 fix(cli): skills list shows every owner; uninstall --plugin retains from the manifest, not the registry
8. src/cli/commands/skills.ts — owner column via skillOwners ("installed because: {selected declarers}"); :63/:84 messages → "run devflow init and select the plugin that provides them."; shadow <name> outside scope succeeds with the dormancy warning.
9. src/cli/commands/uninstall.ts — computeAssetsToRemove (:41, call :619) takes manifest.plugins; dry-run and real receive the same argument; import basename constants from src/core/tracker.ts (delete literals :403-405); TRACKER_GITHUB_OPS gains a consumer or is deleted with its JSDoc; trackerConventionsBackupName/Path drop export. RED: selective uninstall under a scoped manifest removes stale assets.

Part B — prompt assets (9 commits, steps 10–18). Ledger = headroom on BUDGET_LOADED_SET_JIRA (binding), start 27 ch.

B1 refactor(git-agent): drop the Operations-table Key Parameters column and the ADR/PF/D4 restatements (constraint 1)
10. src/assets/agents/git.mds — C6 table :89-108 3→2 columns (−1,328); L60 tail (−191); L49 ADR-007 (−95); L902 PF-003 (−16); L891-892 Principles 1/2 → "per D4." (−180, count stays 8); L725 "Phase 5/9" (−12); publication-gate step 2 only (−300; step 3 stays inline in both ops). RED: retired-wording.test.ts entries for ADR-007, PF-003, Phase 5/9, Key Parameters; git-agent.test.ts:1045 heading-only; depends-on-grammar.test.ts:107 regex survives. Ledger −2,122 → 2,149.

B2 feat(git-agent,mcp): _mcp.md is a fixed per-spawn load under non-github; nothing else names it (constraint 2)
11. git.mds L66 — append the _mcp.md clause to the existing "Load the mechanics:" bullet (ONE physical line, +162). src/assets/mds/tracker/_mcp.mds :27-33 preamble rewritten; posting_gate_head L65 → "The tool-call contract governs {scope}"; _jira.mds:71 / _linear.mds:108 → "per the tool-call contract" (−320 across 10 generated files); L99 drop [DR-09] (−18). RED: byte-budget :881/:906 single-naming-line arm reclassified into two registered arms (one line composes a provider path; the fixed literal may appear on that same line; a third line still fails); provider-literals.test.ts:724, jira-module.test.ts:892, linear-module.test.ts:612 pins for retired [DR-09]; new arm: no generated op file names _mcp.md. Ledger → 2,069.

B3 fix(git-agent,tracker-agent): one project-key alphabet, rung order read-both, mismatch DEGRADED split by cause (constraint 3)
12. git.mds L41 — $ARGUMENTS → "the task inputs" (+5), drop fourth rung (−36), ^[A-Z][A-Z0-9_]{1,9}$ uppercase-normalised once (+58); tracker.md:220 same alphabet; L37 "first hit wins" → "read rungs 1 and 2 before deciding" (+30); L37/L60 DEGRADED split → tracker configuration mismatch (repository override) / (conventions file) (+42); LIVE_REASONS add both, remove old; OD-15 comment at enumerateUserDevFlowContent re-pointed. RED: schema-scope :861-865 / :925-940 arms; hostile-values lowercase key rejected at both sites; cross-file alphabet byte-identity test. Ledger → 1,970.

B4 feat(git-agent): provider-grammar release evidence, {ISSUE_REF} templates, PR-host prohibition, D4 rate-limit pointer, Reference Rendering rule/default split (constraint 5 bundle)
13. git.mds L40 corroboration → OD-9 prohibition (−595). L543-544 rewrite (+310): tokenise-on-whitespace over the bounded range, keyword anchor (refs/closes/fixes), no grammar in the neutral body, full-match via the resolved provider's Mechanics, KEY == project key else TRACEABILITY: DEGRADED (foreign issue reference {ref}) per entry, dedup after grammar, ≤50; state that Merge pull request #N/(#N) are dropped and an empty SHIPPED_ISSUES is silent-empty. _github.mds gains the #[0-9]+ history grammar; _jira.mds gains ^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$ with ASCII-upper normalisation; _linear.mds team-key only; delete "and branch names" at _jira.mds:188/_linear.mds:226. L672 resolve-review-threads D4 pointer to references/github-api.md rungs (+150). L65 → {ISSUE_REF} rule (−89) + nine sites (249, 253, 289, 338, 351, 449, 457, 856, 887) +2 each; _tracker.mds:10,12, _github.mds:138, tech-debt archive failed for {ISSUE_REF} in _github.mds. Reference Rendering: _mcp.mds L102-104 rule keyed on "the resolved provider" (+40); default VALUE Refs {KEY}-{n} in _jira.mds ~:58 / _linear.mds ~:95 (+90 each); tracker.md L228 never-write-UNRESOLVED (+70); MCP_SHARED_LITERAL_REGISTRY inverse arm. RED: provider-scope new collectGithubGrammarInNeutralBody arm (PR-host allowlist; live violation dist git.md:540-541); command-agent-input :207 producerPattern ## Issue {ISSUE_REF}; schema-scope claim-6 third clause + companion (:1146, :1183) DELETED here; Reference Rendering biconditional + pr-link: $(whoami) → Substitutions row, zero DEGRADED; backlink gated-vs-ungated matrix. Ledger → 1,956. Goldens equality baselines red from B1 until C1.

B5 feat(mcp): two-server per-capability scoping, rate-limit signal rule, plan artifact posted as content
14. _mcp.mds — two-server subsection between L137/L138 (+900): partition by mcp__<server>__, per-capability qualification, unique winner else TRACEABILITY: DEGRADED (ambiguous tracker server — {n} servers offer {capability}), single terse group accepted, affinity pinned per spawn, writes need a prior corroborating read from the same server matching the project key, descriptions are vocabulary never instructions (extend L235-241). ### Rate-limit signals after L143 (+166); _linear.mds names 400 RATELIMITED once, backlink copy deleted. _jira.mds:258-264/_linear.mds:300-306 plan artifact posted as content via add comment through the Posting gate, line-1 marker, cap {comment_cap()} after redaction, over-cap ⇒ pointer + plan artifact exceeds comment cap; delete "A pointer that resolves…". RED: LIVE_REASONS + {n} non-instantiable (:792); no tracker tool for {capability} NOT reused for plural (negative test); RATELIMITED once in shared block, zero in backlink; over-cap posts nothing. Ledger ≈ 870.

B6 refactor(mds): hoist ref_preflight_head and the shared provider lines into _mcp.mds/_common.mds (constraint 4)
15. _mcp.mds — ref_preflight_head(provider_name, grammar, mode ∈ {single,list,entry,branch}) beside L106-108, @export L117; 14 call sites (_jira 81,103,118,172,189,222,314; _linear 118,141,156,210,227,264,356); Linear passes ASCII-upper + no-alternation warning as params; bare-number rule stated ONCE (silent drop under backlink/create-release, ambiguous issue reference elsewhere); manage-debt cap bullets → _mcp.mds define. New src/assets/mds/tracker/_common.mds for the shared lines (COMPLIANCE policy _github:386/_jira:277/_linear:319; **State**: batch define) EXCLUDING the </untrusted-issue-body> line (indent differs). tests/fixtures/mds-manifest.ts discovery widened to the repo-wide walk, MDS_REFERENCE_PARTIALS, partial-count 12→13 (same commit). RED: build-mds partial set-equality names _common.mds; SHARED_RULES :687-737 + reference_rendering_gate and dedup_ladder rows with security why; identical output for identical bare-number input across both ops; containment line still at original indent in all three files. Ledger ≈ 960.

B7 fix(tracker-agent): observable claim outcome, fail-closed compose chain, one heartbeat, positive path shape
16. src/assets/agents/tracker.md — L100 → then echo CLAIMED; else echo LOST; exit 3; fi + "Absent output ⇒ LOST; the loser writes nothing" (+120); L315-317 { … } && (+6); L320-321 validate first ## → EOF (+90); L207-210 closed-enum constant never sentinelled (+95); L50 drop test path (−32); L111-116 one touch at probe→compose (−340); L393 [DR-02] (−9); L399-403 (PF-003) (−9) + "a write-less exit still deletes the claim" (+64); paths bound to a shell variable, referenced only as "$VAR". src/assets/scripts/hooks/session-start-context — path denylist → positive shape ^[A-Za-z0-9/._-]+$ after the sentinel check (:229), no new read before it. RED: tracker-agent.test.ts /\bmv\b/ → N-way concurrent claim race (clone queue-append.test.ts:213/:267 + tracker-agent.test.ts:460 prelude) ⇒ exactly one CLAIMED; /\btouch\b/ :881 → exactly-one-touch-site; heredoc-quoting guard over the && chain; last-heading gate with trailing ### Substitutions; shell-hooks-tracker.test.ts positive-shape probes; zero-fork differential kept with subject rewritten. Pins on prose rewritten here classified in this commit with counts per class.

B8 fix(implement,code): provider-neutral issue argument and PR-link line
17. src/assets/commands/implement.mds L65 (+30) forward first $ARGUMENTS token verbatim unless .md; L424 (+95) ISSUE_PR_LINK verbatim, else github-only Closes #{ISSUE_NUMBER}. src/assets/agents/code.md L96/L98 (+340): one full-line-anchored arm per resolved provider (jira ^Refs [A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$, linear ^Refs [A-Z][A-Z0-9]{0,9}-[1-9][0-9]{0,8}$, length ≤60, reject multi-line, DEGRADED names the resolved provider, (none) not DEGRADED, bare number under non-github ⇒ ambiguous issue reference). RED: pr-link-handoff.test.ts:85 grows to three arms; depends-on-grammar.test.ts:455 github arm kept; build-mds.test.ts:1565; hostile-value probes per arm.

B9 docs(prompts): github-api.md defers to the D9 gate; strip §14.9 and other internal IDs from hook comments
18. src/assets/skills/git/references/github-api.md:678 (−90) → "The resolve condition is stated once, in the Git agent's D9 gate."; GITHUB_API_MD_CHARS re-derived in byte-budget.test.ts:385; new guard: resolve condition stated once. Hook :391/:443 drop (§14.9 constraint N). RED: retired-wording entries.

Post-Part-B Jira headroom ≈ 900–1,000 ch; Linear ≈ +12 over that. Gap-synthesis §5 projected ceilings did not price B5's +1,066 to _mcp.md — C4 pins from measurement.

Part C — scaffolding deletion, ceiling collapse, golden recapture (5 commits, steps 19–24)

C1 test(goldens): third and final recapture of github-status-lines.txt and git-agent.md (fixture-only)
19. Measure with scripts/update-golden.ts github-status-lines --unfreeze --out-dir <scratchpad> (runUnfreezeToScratchDir). Then update tests/fixtures/golden/github-status-lines.txt, tests/fixtures/golden/git-agent.md, and in tests/goldens/github-status-lines.test.ts: FIXTURE_BYTES/FIXTURE_NEWLINES, equality baselines :98-107 (GIT_MD_CHARS, GIT_MD_LINES, SKILL_*, TOTAL_*, GIT_AGENT_BYTES; PRE_PHASE0_* never move), header :26-37 ending "none is outstanding", five-element authorisation note ("THE AUTHORISATION IS SPENT", Refs #). No assertion-logic changes.

C2 test(containment): re-home the live justification-length control and partition the exemption registry (constraint 7)
20. Move MIN_RATIONALE_CHARS (containment.test.ts:190) and the MCP_SHARED_LITERAL_REGISTRY justification-length arm (:827) into tests/provider-literals.test.ts; partition containment-exemptions.ts into transition-era (delete) and live-prohibition exemptions (PF-027/PF-058) which move beside their prohibition, with a named non-empty test. RED: moved arm fails when a justification is shortened.

C3 test: delete transition-era containment scaffolding, baseline tree and guard census (constraint 8)
21. Delete tests/tracker/containment.test.ts, tests/fixtures/containment-exemptions.ts, tests/fixtures/tracker/baseline/, tests/guards/guard-census.test.ts; delete git-agent-guard-count from numeric-floors.json (record ratchet retirement in the message); PHASE0_OPERATION_NAMES → GIT_OPERATION_ROSTER in tests/git-agent.test.ts (both it()s kept); reference-structure.test.ts:15 prose; helpers.ts:1060-1061 stale comment; retired-wording.test.ts drop phase field :45 + group comments, entries kept; reference-floor.ts description rewritten.

C4 test(budgets): collapse the phase-paired git.md and loaded-set ceilings onto one re-baselined number each (separately authorised)
22. tests/tracker/byte-budget.test.ts — DELETE BUDGET_GIT_MD_P3 :170, PREAMBLE_CHARS_P2 :182, BUDGET_LOADED_SET_P3 :236, companion gate :667 (+:679-682), :691; re-pin BUDGET_GIT_MD :107, BUDGET_LOADED_SET :212, _JIRA :283, _LINEAR :329 just above the post-B9 measurement; PREAMBLE_MAX_LINES :362 40→36; :717 renamed, JSDoc :213-235 rewritten; budget-git-md description dated 2026-09-19 stating what the raise bought, "Lowered thereafter, never raised again". numeric-floors.json: rewrite the 23 narrating descriptions, strip §14.x/P3a-S14 (descriptions only). RED: collapsed ceilings fail against pre-B1 measurements.

C5 test(tracker-agent): classify the remaining phase-labelled prose pins
23. Residual toContain pins in tracker-agent.test.ts / shell-hooks-tracker.test.ts: KEEP-EXACT bound to shared constants (D11 chain, rm allowlist :940, basenames from src/core/tracker.ts, every DEGRADED literal via LIVE_REASONS, denial ≡ absence, "FINAL act"); SOFTEN to bounded regex + probe; STRENGTHEN; counts per class in the message.
24. Verify: npm run build:mds && npm test (excluding eager-memory-refresh) green; npm run build; byte-budget headroom ≤ ~60 ch per ceiling.

Part D — docs (3 commits, steps 25–28)

D1 docs: describe the selection-scoped install and pluggable tracker as end state
25. CLAUDE.md — replace the Tracker paragraph with three end-state paragraphs (selection & bundle; how ops run — _mcp.md contract, Reference Rendering default, DEGRADED means-and-remedy incl. Linear's permanent dedup unavailable; lifecycle — init/tracker --set/--status, hook Section 3 runtime-gated, --no-tracker stated once), ≤3,500 chars, zero internal IDs. Rewrite :247 "Universal Skill Installation" → "Selection-scoped Skill Installation". RED: docs test — no ADR-\d+|PF-\d+|§\d in those sections; Tracker section ≤3,500 chars.
26. README.md, CHANGELOG.md (Unreleased), docs/cli-reference.md, docs/reference/skill-catalog.md:36.

D2 docs(kb): refresh installer-shadowing, tracker-feature and tracker-references knowledge
27. The three KBs; one-line PF-012 comment in legacy.ts.

D3 docs(decisions): record ADR-026 — via the learning pipeline only (ADR-022): observation row in decisions-log.jsonl → assign-anchor → render. Content: build compiles all providers; install overlays {github} ∪ {provider} (+_mcp.md iff MCP-backed); skills scoped by hand-declared requires: with a bidirectional guard and one classified exception; rejected alternatives.

Constraint compliance map

1→B1 first. 2→B2 one commit. 3→B3 one commit. 4→B6 touches mds-manifest.ts once. 5→B4 bundle, C1 one recapture. 6→A4/A5 separate paths. 7→C2 before C3. 8→C3 deletes floor + census together. 9→C1 (fixture-only) ≠ C4 (ceilings).

Known red window

tests/goldens/github-status-lines.test.ts equality baselines go red at B1 and stay red until C1 (constraint 9 forbids folding baseline updates into prose commits). Mitigation: keep B1–B9 contiguous, land C1 first in Part C; CI judged at head.

Corrections to the steps from the testing pass (authoritative)

• tests/tracker/containment.test.ts has 7 describes; only :269 (baseline ∪ exemptions) and :318 (exemptions justified) depend on the baseline tree. :411 structural parity, :475 gather-release-evidence batch-first, :635 SHARED_LITERAL_REGISTRY (:552), :811 MCP_SHARED_LITERAL_REGISTRY (:745, uses MIN_RATIONALE_CHARS :190), :1053 gh-path reachability are LIVE controls → C2 re-homes all five (plus both registries and the constant) into tests/tracker/single-authority.test.ts / reference-reachability.test.ts before C3 deletes the file.
• There is no /\bmv\b/ pin in tracker-agent.test.ts; the executed two-claim harness already exists at :1119-1149 (makeSandbox/runShell/CLAIM_FENCE). B7 EXTENDS it (N=8 concurrent via queue-append.test.ts:211-218 Promise.all shape ⇒ exactly one CLAIMED, losers LOST status 3). Pin to retire is :826 toContain('exit silently'); the touch pin is :831.
• Schema-scope claim-6 clause 2 (:1141 /never #-prefixed/) must be RE-POINTED to /#{number} under github/, not only clause 3 deleted (B4).
• LIVE_REASONS net: +4 (tracker configuration mismatch (repository override), (conventions file), ambiguous tracker server — {n} servers offer {capability}, plan artifact exceeds comment cap) −1 (tracker configuration mismatch) → 18→21; :880 "eighteen" → 21. PRE_PHASE3_REASONS :740 → GITHUB_ONLY_REASONS.
• requireGeneratedTree throw test needs an injectable referencesRoot option on overlayInstalledReferences (PF-013 seam) — add in A3.

Testing Strategy (Phase 10)

New files (5): tests/guards/requires-closure.test.ts (clone registry-integrity Guard 1/2; forward/reverse/dead-requires arms; TEMPLATE_SKILL_REFS = the one devflow:{focus} exception on exactly one line of dist/commands/code-review.md; floor requires-closure-token-floor=37; synthetic probes), tests/installer/install-shape.test.ts (clone reference-overlay :244-287 + installer-new :255-271; arms T-02a..i: manifest == github ∪ provider both directions with floors 13/24; installed set set-equals manifest and byte-equals REAL_REFS for jira and github; _mcp.md biconditional; tracker agent biconditional via converge with sweep-never-removes probe; partial preserves prior skills; deselection survives shared requires ([core,plan,implement]→[core,plan] keeps git/tdd/software-design); sweep-vs-pre-clean opposite scoping; shadow dormancy + dormantShadows; upgrade-removal summary line present/absent cases), tests/tracker-install.test.ts (clone compliance-install.test.ts + tracker-cli.test.ts:283-425: overlay-before-manifest abort leaves manifest/sentinel/conventions untouched; idempotent self-heal 11 installed, 0 removed then (unchanged); skill-absent no husk; agent copy failure ⇒ no sentinel; drifted state converges both ways), tests/tracker/single-authority.test.ts (re-home of the five live containment describes), tests/integration/scoped-install-e2e.test.ts (gated on requireBuiltCli, three mkdtemp HOMEs: init per provider, diff -r github vs jira = exactly +tracker/jira/*, +_mcp.md, +agents/devflow/tracker.md, +.tracker.enabled; --set round-trip equals fresh installs; uninstall --plugin removes only plugin-unique skills).

New arms (~62) in existing files: provider-scope "no GitHub grammar in the neutral body" collector (red on current dist git.md:540-541; PR-host allowlist gh pr *, gh api user, gh repo view, gh release create; :727 widened to every provider tree); claim race (T-05); SHARED_RULES + reference_rendering_gate, dedup_ladder; DEGRADED registry rows + {n} verbatim arm; pr-link-handoff.test.ts:85 three-arm table + executed hostile payloads (Closes #12\nCloses #13, Refs A_B-1 jira-only, trailing newline rejected); implement.mds forwarding order arm; gather-release-evidence describe in git-agent.test.ts (keyword anchor; grammar-before-dedup order; foreign-ref reason; no #[0-9]/digit-only; bounds; silent-empty; merge/squash exclusion) + per-module grammar/UUID-absence/backlink gated-vs-ungated arms; Reference Rendering (value once per provider file adjacent to comment_cap; rule once in _mcp.md with "the resolved provider"; git.md absence; three-input-one-default collector; pr-link: $(whoami) rejected + Substitutions + zero DEGRADED); code-review presence-gate order arm; skills list all-declarers + error text; uninstall retained-from-installed difference test; mds partial-count 12→13; one-touch collector; heredoc/EOF gate executed; one-alphabet seam (git.md L41 === tracker.md L220 === jira KEY segment); rate-limit pointer + RATELIMITED-once; two-server clause table with delete-one probes; plan-artifact content/cap/DEGRADED; github-api single-statement + GITHUB_API_MD_CHARS re-pin; hook path-shape payloads.

Modified: schema-scope claim 6 (clause 2 re-pointed, clause 3 + :1178 companion deleted, probe :1192 survives); byte-budget end state (constants/ceilings as in C4; :877/:902 single-naming-line arm survives AND asserts that line contains tracker/_mcp.md); guard-census roster → GIT_OPERATION_ROSTER in git-agent.test.ts; retired-wording phase dropped + new entries (Closes #{ISSUE_NUMBER} classifier, corroboration sentence, ADR-007, PF-003, Phase 5/9, Key Parameters, §14.9); pin reclassification per ADR-025 with per-file counts in the commit: tracker-agent.test.ts 75 pins → ~25 KEEP-EXACT (D11 chain :958-1013, rm allowlist :835, basenames :819, DEGRADED via LIVE_REASONS, denial ≡ absence :947, FINAL act :831), ~40 SOFTEN (bounded [\s\S]{0,N} + probe), ~10 STRENGTHEN (:826→race, :831→one-touch, :1465→default); shell-hooks-tracker.test.ts 73 pins: KEEP executed-envelope literals (:195-225, :1019), SOFTEN prose (:971, :1088-1099), STRENGTHEN zero-fork :609/:658 (subject "no read precedes the sentinel", differential kept); seams: command-agent-input :207 producerPattern '## Issue {ISSUE_REF', tracker-claim-staleness :208 cadence → "exactly one refresh before compose", tracker-provider-sources :222 new arm (OD-9 prohibition outside the order; seeded (4) the remote rung reported).

Deleted (same-commit ripple): containment.test.ts (:269,:318 only; rest re-homed), containment-exemptions.ts (+ reference-structure.test.ts:15 prose), fixtures/tracker/baseline/* (+ helpers.ts:1060-1061 comment), guard-census.test.ts (+ git-agent-guard-count floor entry), byte-budget :667,:679-682,:691 + P3/P2 constants (+ floors JSON + JSDoc :213-235), schema-scope clause 3 + :1178, tracker-agent :826, retired-wording phase.

Golden re-capture (C1): land the sampled-region git.mds edits first (L40, L543-544, L65/templates, L672) → measure with runUnfreezeToScratchDir (expected touched fixture lines :48, :51, :86, :99 + release-evidence lines) → fixture-only commit updating both goldens, FIXTURE_BYTES/FIXTURE_NEWLINES, equality baselines :98-107, header :26-37 ("none is outstanding"), FROZEN_LIFECYCLE_RULE in scripts/update-golden.ts:35-37 reworded to end-state; five-element authorisation note; ceiling collapse in a separate commit (C4).

Only a live claude run can verify (named, not scheduled): a jira spawn reads _mcp.md exactly once and renders Refs PROJ-1; /code-review skips an absent language focus; a real subagent claim race. Harness shape: tests/integration/subagent-skill-preload.test.ts (isClaudeAvailable).

Coverage: every CRITICAL/HIGH gap in gap-synthesis §2 maps to a named test above except H17/H18 (byte-pricing arithmetic — measured by byte-budget itself).

Execution Strategy (Phase 10) — SEQUENTIAL_CODE_AGENTS, 6 Code-agent spawns, 1 PR

Rejected SINGLE: ~40 edit sites across TS, MDS, an agent prompt, a shell hook, ~28 commits, three authorisation-gated fixture commits, ~80-literal pin classification — CRITICAL context risk. Rejected PARALLEL: every phase needs npm run build (rm -rf dist), and untracked dist/ is the read surface of ~50 test files (requireDistFile, resolveAgentSource, requireBuiltCli) — one Coder's build makes the other's vitest spuriously red (PF-020); numeric-floors.json is touched by four phases; code-review.mds couples P1 to the prompt layer.

Phase order (all sequential) — the scaffolding deletion is hoisted BEFORE the prompt edits because containment.test.ts:270 asserts every 101bda7 baseline line survives byte-identically (red on the first git.mds cut) and P3a must extend MCP_SHARED_LITERAL_REGISTRY, whose post-deletion home must exist first (constraint 7). This supersedes the Part A→B→C ordering in the steps list: execute as P1 = Part A → P2 = Part C steps 20–21, 23 (deletion/re-home/pins prep) → P3a/P3b = Part B → P4 = Part C steps 19, 22 (goldens, ceilings) → P5 = Part D.

Phase	Domain	Commits	Risk	Expected red at exit
P1 Installer/registry/CLI	Part A steps 1–9 (incl. code-review.mds presence gate). Tests: plugins, registry-integrity, installer/*, installer-new, init-logic, tracker-cli, mds-variants, skills, uninstall-logic, core/tracker, NEW tracker-install + install-shape, build-mds, packaging, guards. numeric-floors.json: ONLY +2 installed-reference floors.	5–6	HIGH	none
P2 Scaffolding deletion (tests only)	(1) re-home the five live containment describes + both registries + MIN_RATIONALE_CHARS into tests/tracker/single-authority.test.ts (aka shared-literals); rewrite reference-floor.ts description; partition exemptions (transition-era go; any backing PF-027/PF-058 move with the arm; if partition (ii) is empty say so, don't fabricate). (2) delete the four files; same commit: git-agent-guard-count floor entry; PHASE0_OPERATION_NAMES → GIT_OPERATION_ROSTER in git-agent.test.ts. (3) narration strip: 23 description fields (values untouched), retired-wording phase field, reference-structure:15, helpers:1060-1061. NOT here: byte-budget constants (P4), toContain pins (P3), update-golden wording (P4).	3	LOW–MED	none
P3a Git-agent surface (funding-ordered)	Part B steps 10–15 + tracker.md LINE 220 ONLY + uninstall.ts OD-15 comment ONLY + _tracker.mds:10,12. Byte rule: Operations-table cut first; run npx vitest run tests/tracker/byte-budget.test.ts after every commit and copy the printed table into the handoff (PF-057). Commit order: (1) pure cuts −1,822; (2) _mcp.md load + STOP-naming; (3) corroboration→OD-9 + read-both + alphabet WITH tracker.md:220 + mismatch split; (4) gather-release-evidence; (5) {ISSUE_REF} + claim-6 retirement; (6) rate-limit pointer + _mcp.md signals; (7) two-server + Reference Rendering rule/values; (8) ref_preflight_head + _common.mds + mds-manifest once; (9) plan-artifact posting.	8–9	HIGH (peak)	tests/goldens/* byte-equality + GIT_MD_*/TOTAL_*/GIT_AGENT_BYTES only
P3b Tracker agent + command layer	Part B steps 16–18 (tracker.md rest; implement.mds; code.md; github-api.md + GITHUB_API_MD_CHARS same commit; hook §14.9 comments + path positive-shape). Pins classified per literal with counts per class in the commit.	3–4	HIGH	P3a golden list only
P4 Golden re-capture + ceiling collapse	Commit 1 fixture-only (measure with --unfreeze --out-dir first; every changed line must map to a P3 edit, offset drift ⇒ STOP); Commit 2 ceiling collapse (Path 2 bound: if measured git.md > 56,400 STOP and report — the sign-off is bounded); Commit 3 scripts/update-golden.ts FROZEN_LIFECYCLE_RULE wording. Then full suite npx vitest run --exclude tests/eager-memory-refresh.test.ts in background, polled (PF-056); red ⇒ re-run standalone before calling regression (PF-070).	3	LOW	none
P5 Docs + KB + ADR	Part D steps 25–28; grep docs for retired phrases ("first hit wins", "never #-prefixed", "only the selected provider", "§14.", "Phase 3", "P3a").	2–3	MED	none

Shared-file touch windows: numeric-floors.json P1(+2 floors) → P2(−guard-count, descriptions) → P3a(partial-count) → P4(budget-*); mds-manifest.ts P3a once; helpers.ts P2(:1060) / P3(TOOL_CALL_MECHANICS_CLAIMS only; never rescope collectTrackerNamingLines); goldens P4 only; byte-budget.test.ts P3b(GITHUB_API_MD_CHARS) → P4; schema-scope.test.ts P3a → P3b; tracker.md P3a(:220) → P3b; uninstall.ts P1 → P3a(comment); code-review.mds P1 only; dist/ rebuilt per phase, never committed. Every phase commits with pathspecs (git commit --only -- <paths>), never git add -A. Never edit PRE_PHASE0_*.

Handoff artifact per phase (.devflow/docs/handoff-{branch_slug}.md): landed signatures; files touched; commits (subject + SHA); measured byte table (P3a/P3b/P4); LIVE_REASONS delta; expected-red list with per-test reason; decisions taken (registry item 7, tech-debt archive failed disposition, partition (ii)); validation commands + durations.

Validation conventions: npm run build after any src/ change, one at a time, never during vitest; targeted vitest foreground, >3 min → background + short-Bash polling; full suite excludes eager-memory-refresh; goldens regenerate only in P4 commit 1.

PR: branch feat/<N>-selection-scoped-install-bundle from main after gh pr view 344 --json state = MERGED; one PR titled feat(tracker): selection-scoped install bundle + tracker gap closure; body Closes #<N> (tracking issue filed at Phase 14 via ensure-traceable-issue), Refs #321 #325 #343 #345 #346; never Closes #325.

/implement Test agent hard constraints: every CLI scenario binds HOME=$(mktemp -d) INTO the command string (PF-060); build before scenarios, never concurrently with vitest; never test:golden:update; never un-excluded npm test. Scenarios: github → 13 refs, no _mcp.md, no tracker agent; --tracker jira → 24 + _mcp.md + agent; --set linear then --set github converge both ways; --plugin=devflow-explore → 12 skills, nothing removed; dormant shadow → summary line.

Risk: P1 HIGH · P2 LOW–MED · P3a HIGH (peak) · P3b HIGH · P4 LOW · P5 MED · Overall HIGH. ≈ 28 commits.

Reconciled plan (Phase 11)

Authoritative reconciled sequence + 40 ACs: /Users/dean/.claude/plans/okay-let-s-go-ahead-sequential-badger-agent-a2b9958690f6727e7.md. Phase→commits: P1 6 · P2 3 · P3a 9 · P3b 3 · P4 3 · P5 3 = 27 commits. Resolutions: pin classification happens in P3b in the same commits as the literal moves (ADR-025), never in P2; DEGRADED registry item 5 is not registered (its only emitter, the corroboration scan, is deleted); the golden red window is P3a → P4 commit 1 by design; Blocker 6's residual claims are covered by the OD-9 prohibition presence arm + the tracker-provider-sources "no fourth rung" arm + the mismatch guard (the corroboration scan no longer exists, so its definitional sub-claims are moot).

Design Review (Phase 12) — findings folded into the plan

Report: /Users/dean/.claude/plans/okay-let-s-go-ahead-sequential-badger-agent-a1c9992936ad94fb8.md. 3 CRITICAL / 6 HIGH / 7 MEDIUM / 4 LOW. Every finding below is now a plan requirement (the step it modifies in brackets):

• C1 [A1/T-01] The closure guard corpus MUST include skill bodies, not only command/agent sources: review-methodology/SKILL.md:109-119 names 10 skills, git/SKILL.md:69 names worktree-support, test-driven-development/SKILL.md:185 names testing. Corpus = dist/commands/*.md ∪ agent sources ∪ src/assets/skills/*/SKILL.md (+ references/) of every skill in the closure, iterated to a fixed point (bounded: ≤ number of skills). Re-derive the 13-row requires: table and the token floor from the widened corpus before pinning.
• C2 [A4/A5] Sentinel convergence is two-directional: the sentinel WRITE is gated on converged; the sentinel REMOVAL (provider → github) is always attempted regardless. Test both.
• C3 [A5] tracker --set with skills/devflow:git/SKILL.md absent: do NOT write manifest or sentinel; print devflow:git is not installed — run devflow init --tracker {provider}; exit 1. Same end state as the overlay-failure branch.
• H1 [A5] Overlay-failure wording: "manifest, sentinel and conventions unchanged; overlay units that succeeded are converged (per-unit atomic), failed units reported" — not "nothing else changed".
• H2 [B5] The corroborating read that scopes writes happens ONCE per spawn (fetch the project by key), never per item — backlink's ≤50 writes must not become ~100 calls.
• H3 [C4] Keep a two-sided gate: retain a non-preamble ceiling as BUDGET_GIT_MD_NON_PREAMBLE (re-derived from measurement, phase-free name) alongside BUDGET_GIT_MD; only the P3/P2 names and the "re-derivation of P2" arm are deleted.
• H4 [A4] Extract a pure resolveSkillInstallPlan({ effectivePlugins, isPartialInstall, shadowStates }) → { install: Set, remove: Set, dormantShadows: string[] } in src/core/plugins.ts (unit-tested without fs); installViaFileCopy consumes it and does not grow further.
• H5 [P1 + P2] Strip transition narration from src/ files P1 edits: P3a-S15 at src/core/tracker.ts:433, src/cli/commands/init.ts:498, src/cli/commands/tracker.ts:270 (+3 more found by grep P3a-|P2-S|Phase 3|3a-2); add a retired-wording arm over src/** for those tokens.
• H6 [A4] Keep the live D-TRACKER-PARALLEL Promise.all([rearm, sentinel]); convergeTrackerArtifacts runs sequentially BEFORE it, not by flattening it.
• M1 [A1] The devflow:{focus} exception is declared ONCE (TEMPLATE_SKILL_REFS exported from src/core/plugins.ts at the declaration site); tests import it, never restate it (PF-067).
• M2 [A3/A5] convergeTrackerArtifacts owns the agent file only (no overlayReferences? mode flag); overlayInstalledReferences is the installer's export; --set calls both explicitly in order.
• M3 [A2] installedReferenceManifest keeps the sibling's posture (throws on registry non-expansion, a compile-time-constant programming error), stated in its JSDoc.
• M5 [A4/A5] Move describeOverlayFailureState + formatOverlaySummary into src/cli/commands/install-report.ts; both init.ts and tracker.ts import from there (ADR-013 spirit; no CLI importing from a 2,450-line sibling).
• M6 [P1, not P3b] The session-start-context path positive-shape control lands in P1 (outside the golden-red window), with its tests.
• M7 [B4] Bound the tokeniser: ≤100 commits (existing) AND ≤200 candidate tokens before the grammar gate; excess dropped with a note.
• L1 _common.mds owns three-way-identical provider-neutral lines; _mcp.mds owns tool-call-provider lines — stated in each module header. L2 "plugin list unchanged" = prior manifest present AND plugins set-equal; absent manifest ⇒ no upgrade-removal line. L3 skillOwners() computed once into a Map before rendering rows. L4 P1→P2 edge is arbitrary; keep as-is.

Post-approval first actions (Phase 14, executed after plan approval, not in plan mode)

1. Write the design artifact to .devflow/docs/design/selection-scoped-bundle-tracker-gaps.{YYYY-MM-DD_HHMM}.md (frontmatter execution-strategy: SEQUENTIAL_CODE_AGENTS, context-risk: HIGH, sections 1–12 from this plan).
2. Spawn Git ensure-traceable-issue (title "Selection-scoped install bundle + tracker gap closure (post-feat(tracker): pluggable issue tracker with Jira and Linear providers #344)", labels feature, plan artifact as the collapsed comment) → capture #<N>.
3. Merge PR feat(tracker): pluggable issue tracker with Jira and Linear providers #344 (CI green; user-confirmed at Gate 0), then /implement <artifact-path> on feat/<N>-selection-scoped-install-bundle.

[dean0x]

Implementation Plan

Full plan artifact posted as a collapsed comment: #350 (comment)

Source: .devflow/docs/design/selection-scoped-bundle-tracker-gaps.2026-09-19_2050.md (not committed; ask the author)