Task card: .task/feature-governance-v2-closeout.md (the card is the PR description; evidence rows are written by make evidence).
Dev adoption (batch A): deps/development-manager pinned to 0552b73; scripts/dm, scripts/task thin entries; .task/templates/task-card.md; policy/guidelines-adoption.md (active, defers to policy/adoption.md); CI step scripts/dm governance check --repo . in ci / test; PROJECT.md verification note. make task-* stays the authoritative lifecycle.
Development-Guidelines adoption record and evidence: docs/superpowers/plans/2026-10-17-guidelines-governance-adoption.md (Guidelines CONTRIBUTING.md keeps process records out of that repository).
Master record docs/superpowers/plans/2026-10-16-development-governance-v2-master.md: Phase 5–7 status, adoption matrix with PR links and main CI, two-key branch-protection commands for the owner, non-blocking follow-ups.
Implementation via agent-per-unit (r2 receipt on the card); no business code changes.
Task card: `.task/feature-governance-v2-closeout.md` (the card is the PR description; evidence rows are written by `make evidence`).
- Dev adoption (batch A): `deps/development-manager` pinned to 0552b73; `scripts/dm`, `scripts/task` thin entries; `.task/templates/task-card.md`; `policy/guidelines-adoption.md` (active, defers to `policy/adoption.md`); CI step `scripts/dm governance check --repo .` in `ci / test`; PROJECT.md verification note. `make task-*` stays the authoritative lifecycle.
- Development-Guidelines adoption record and evidence: `docs/superpowers/plans/2026-10-17-guidelines-governance-adoption.md` (Guidelines CONTRIBUTING.md keeps process records out of that repository).
- Master record `docs/superpowers/plans/2026-10-16-development-governance-v2-master.md`: Phase 5–7 status, adoption matrix with PR links and main CI, two-key branch-protection commands for the owner, non-blocking follow-ups.
Implementation via agent-per-unit (r2 receipt on the card); no business code changes.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-governance-v2-closeout.md; R0=3227dec8918dd36cbd4f8906a05ed62ffa98f3df.
Impact: task metadata only; the feature workspace starts at 3227dec891.
Refs: .task/feature-governance-v2-closeout.md
Why: Development-Guidelines stores no process records (CONTRIBUTING.md), so its Phase 6 adoption card and evidence live with the governance master record in Dev.
Evidence: docs/superpowers/plans/evidence/guidelines-adoption/00-02 (SELF): governance check --guidelines-self, agent-exec validate, adoption cases ALL PASS.
Impact: planning records only.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the r2 implementation unit succeeded and was integrated with scripts/agent-exec apply.
Evidence: .task/feature-governance-v2-closeout.md (SELF): governance check, agent-exec validate, adoption cases ALL PASS on 271d95f.
Impact: task card only.
Refs: .task/feature-governance-v2-closeout.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Guidelines PR #9 review repairs ran through the shared executor; repair-r2 fail-stopped and was redone as r3.
Evidence: docs/superpowers/plans/evidence/guidelines-adoption/03-04 (SELF): governance check --guidelines-self and agent-exec validate on 7cafc7d.
Impact: planning record and evidence only.
Refs: docs/superpowers/plans/2026-10-17-guidelines-governance-adoption.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Phase 6 adoption PRs merged across the formal repositories; the master record still showed PLANNED rows.
Evidence: merge commits and main CI per repository (GATE, Gitea statuses); make test-governance 421 tests OK on 2b2268f (SELF).
Impact: planning record and task card evidence only.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Task card:
.task/feature-governance-v2-closeout.md(the card is the PR description; evidence rows are written bymake evidence).deps/development-managerpinned to 0552b73;scripts/dm,scripts/taskthin entries;.task/templates/task-card.md;policy/guidelines-adoption.md(active, defers topolicy/adoption.md); CI stepscripts/dm governance check --repo .inci / test; PROJECT.md verification note.make task-*stays the authoritative lifecycle.docs/superpowers/plans/2026-10-17-guidelines-governance-adoption.md(Guidelines CONTRIBUTING.md keeps process records out of that repository).docs/superpowers/plans/2026-10-16-development-governance-v2-master.md: Phase 5–7 status, adoption matrix with PR links and main CI, two-key branch-protection commands for the owner, non-blocking follow-ups.Implementation via agent-per-unit (r2 receipt on the card); no business code changes.