planning: plan close-out and tracker-write phases emit gh-hardcoded tracker writes; close-out hardcodes docs/adr + docs/specs

[kyle-sexton]

Plugin: planning · Categories: side-effect surface (3), minor hardcoded opinion (1)
Source: work-readiness sweep (read-only audit vs docs/PLUGIN-PHILOSOPHY.md + docs/MIGRATION-PLAYBOOK.md)

Findings

• plugins/planning/skills/plan/SKILL.md:109 — tracker-write phases → gh issue create; :313-316 — close-out promotes durable outcomes ("Actionable follow-ups go through the work-item tracker seam") and hardcodes git mv targets docs/adr/ / docs/specs/
• plugins/planning/skills/plan/context/plan-template.md:300-325 — phase-entry check hardcodes gh issue create / gh issue comment (:319)

Assessment

The create paths are gated — plan approved at Step 5, close-out explicitly invoked, search-before-create dedup mandated (plan-template.md:309-315). Remaining gaps: (a) still tracker writes, so they need the same consume-only guard as wayfind (sibling issue) for read-only environments; (b) GitHub/gh hardcoded — same backend coupling as the wayfind issue; (c) minor category-1: close-out hardcodes docs/adr/ / docs/specs/ while interview.md:125 correctly defers ("if none is declared, offer and defer — never prescribe a location") — internal inconsistency.

Fix direction

Fold tracker-write phases and close-out follow-up filing under the same tracker-write userConfig gate + work-item-tracker seam as wayfind; let ADR/specs subpaths be consumer-declared, as interview already does.

[kyle-sexton]

This was generated by AI during triage.

Triage → needs-human. Wayfind tracker cluster (#416, #417). Folds plan tracker-writes + close-out follow-up filing under the same seam + consume-only gate as wayfind, plus a minor category-1 fix: let docs/adr + docs/specs sub-paths be consumer-declared (as interview already does). The ADR/specs deferral is independently shippable; the tracker-write portion is coupled to #416. Priority: high.

[kyle-sexton]

Decision made on carrier #416: plan's tracker-write phases route through the seam (reads portable, writes exit-6 + outward_write_mode-gated per #440); include the close-out docs/adr + docs/specs consumer-declared-subpath rider. See #416 for the record.

[kyle-sexton]

This was generated by AI during triage. · Category: side-effect surface (3) + minor hardcoded opinion (1) · Priority: priority: high (week north-star). Self-labeled severity: create paths already gated; residual is posture + coupling.

Blocked by #440 decision (primary aspect). This issue spans two of this cycle's decisions:

1. Consume-only guard (its category-3 aspect) — the tracker-write phases + close-out follow-up filing need the same write-suppression guard as the rest of the cluster. This is the part blocked by source-control: no read/consume-only posture — "safe" babysit tier and pull-request monitor write to GitHub autonomously #440 (the cross-plugin write_mode contract; members planning: wayfind tracker mutations have no consume-only mode or userConfig kill-switch #417, session-flow: clean-stop creates PRs and files issues unattended once invoked — no consume-only seam #431, source-control: no read/consume-only posture — "safe" babysit tier and pull-request monitor write to GitHub autonomously #440, this issue). Hold until the carrier decision lands, then implement the chosen contract in plan's tracker-write phases.

2. Tracker-backend agnosticism + hardcoded paths (its category-1/coupling aspect) — the gh-hardcoded writes are the same seam-routing work as planning: wayfind hardcodes GitHub Issues/gh as the only tracker backend, bypassing the work-item-tracker seam #416 (routed status: ready), and the hardcoded docs/adr/ / docs/specs/ close-out targets are an internal inconsistency vs interview.md's "offer and defer — never prescribe a location". These parts are not gated on source-control: no read/consume-only posture — "safe" babysit tier and pull-request monitor write to GitHub autonomously #440 — implement them alongside planning: wayfind hardcodes GitHub Issues/gh as the only tracker backend, bypassing the work-item-tracker seam #416's seam-routing and make the ADR/specs subpaths consumer-declared. No separate decision needed for this aspect (architecturally mandated by MIGRATION-PLAYBOOK, same as planning: wayfind hardcodes GitHub Issues/gh as the only tracker backend, bypassing the work-item-tracker seam #416).

Net: the issue as a whole waits on #440 for its posture aspect; its agnosticism/path-hardcoding aspect is actionable now with #416. Split at implementation time accordingly.