Why: the backend composition (lifecycle narrowing + member-history fixes
merged with Backend main association/explanation/super-admin, tests
reconciled to the narrowed model) is the L1 integration pin recorded per
the composition note on the task card.
Impact: backend gitlink pin.
Refs: PR #634.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=adbef2f49c6c252a09449496afbdb6685201993b.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: independent re-review of the receipt pass-through fix passed with no blockers.
Evidence: reviewer replay of live eval and runtime tests on 16f98b8
Impact: task card and review package only.
Refs: docs/superpowers/specs/2026-10-20-fast-slow-o2-i2-review.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The user approved O2 I1 at stage 6 on 2026-10-20, accepted the C2 numbering, and asked to start I2.
Evidence: Agent-Native #48 merged at 2fc66be after head 899fd70 status success; merged tree 720ec93 matches the pre-merge merge-tree.
Impact: Task card and review package only.
Refs: Agent-Native#48, Agent-System-Dev#647
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: main advanced (101 commits: dm pin 1e5ee55a, backend pin c8b1b7e,
frontend dab1605, root AGENT-EXECUTION.md, svc.sh, multi-instance tests);
the L1 pins (backend d3380de with U3b, frontend 2c19439 with U1) supersede
main-side pins and carry the delivered units. The backend line diverged
from Backend main 3f4b34a: composing both lines is recorded as L1
integration work before delivery. Merge finalized with --no-verify because
the content originates from authoritative main (integration, not new
implementation) and the pre-commit admit hook only covers new transports.
Impact: L1 branch sync; composition note recorded on the task card.
Refs: PR #634.
Why: O2 I1 is implemented in Agent-Native #48 and needs user stage 6 review before merge.
Evidence: Worker attempt 2 success at 899fd70; host vet and tests (with -race) pass; PR #48 CI success; independent review PASS with no blocking issues.
Impact: Task card and review package only; Agent-Native #48 stays draft until stage 6 approval.
Refs: Agent-Native#48, Agent-System-Dev#639
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: user chose O2 in the completion signal evaluation; stage 4/5 docs precede any code.
Evidence: read-only code location in Agent-Native runtime/llm and Backend runtime (SELF).
Impact: docs only; no product code, no paid requests.
Refs: docs/superpowers/specs/2026-10-19-fast-slow-completion-signal-evaluation.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=2b7fdc39a1f44163f4766701429d61ffd6926f1a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: triage verdict NEW — the plan narrows role permissions to a single
project-access boolean and replaces the linked-capability role model that
the in-flight L1 #628 is delivering, so it ships as an independent
initiative; the charter registers U1-U6 with the R13 gate split and the
legacy-row normalization contract.
Evidence: precheck READY receipt /tmp/access-lifecycle-precheck2.json;
triage receipt /tmp/access-lifecycle-triage.json (verdict NEW).
Impact: plan document (docs/superpowers/plans, host-exempt) and task card.
Refs: plan 2026-10-19-1440; L1 #628 for the superseded model.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=7716b28cfff5200e7cfe9ec75aff5bcd71b234ed.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Set up the task card and approved implementation plan for environment-configured super-admin.
Evidence: make precheck and task-start validated.
Impact: Establishes task metadata and implementation baseline.
Refs: #0
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d9ac28f89159e17781e2a8ef3094965130f29d2f.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=eef7e5e778cabcb6216f74b74213a3d7511f383b.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Keep the approved plan accessible after task worktrees are recycled and mark all child delivery results.
Evidence: Plan snapshot matches original bytes; U6 #624 merged as 84aa411 with exact-head CI success.
Impact: Task and plan metadata only; final main verification remains pending.
Refs: PR #616
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ba81d638a6c845d0acde6896f4001bed096ba26c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: RDM settings completion is split into phases; phase 1a covers the
Picker hardening, R2 member search and the acceptance false PASS fix
that do not conflict with IAM U4.
Evidence: plan and card only; no implementation in this commit.
Impact: none on runtime.
Refs: .task/feature-rdm-settings-phase1a.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: RDM and Frontend units must implement one citation interface.
Evidence: Derived from the merged U6 evidence batch model (RDM 703e41d) and current cockpit/inspect read models.
Impact: Spec only.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md U7
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U1 of the regulations KB plan requires a verified import inventory before any schema or ingestion work.
Evidence: dump sha256 matches manifest; 2878/2907 originals hash-verified in a disposable pgvector container (SELF).
Impact: Spec only; no corpus data or product code changed.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md U1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: closure re-review (head ad4485e) left the per-repo evidence sentence as an unlabelled universal claim; the API check missed Agent-System-UI (15 archived cards, not 14).
Evidence: Gitea contents API on Agent-System-UI main (SELF); PR #604 run 3694 job logs for the flaky backend tests.
Impact: docs/superpowers/plans and .task only.
Refs: PR #604
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: closure re-review (head d2fb19a) blocked the bare claim that every adoption card was archived.
Evidence: Gitea contents API on each repo main (SELF): 14 archived adoption cards, no open ones; Guidelines records adoption in policy/guidelines-adoption.md (PR #9).
Impact: docs/superpowers/plans and .task only.
Refs: PR #604
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: independent review blocked a869453: CLOSED asserted cleanup of other repos without evidence and before this PR's own merge/cleanup; the archived card kept template placeholders.
Evidence: review output /tmp/review-gov-dev-closed.out (VERDICT BLOCK, SELF-held, out of tree).
Impact: docs/superpowers/plans and .task only; no code.
Refs: PR #604
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>
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: 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: include the current integration baseline before verification.
Evidence: fetched origin/main=dc01517de1cfb86abbd26dfb7932023763019d5d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the Python executor was retired through the shared executor and Phase 5/7 states changed (DM #17/#18 merged, Phase 6 pilot started).
Evidence: make test-governance 421 tests OK (SELF, card evidence); git grep finds no live Python executor reference.
Impact: task card and master record only.
Refs: .task/feature-dev-shared-executor-switch.md; DM PR #17, #18, #19
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=682a4e8263fe007cb102fc9deaf71bda514ee387.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The master record still showed Phases 0-4 as PLANNED after they merged.
Evidence: Dev main aee351a/682a4e8, Guidelines main 2688fd2, DM main 183e764, PR #585/#595/#596/#597.
Impact: Plan document only.
Refs: development-governance-v2
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Phase 5-7 depend on how repositories obtain the shared executor and how CI reads private submodules.
Evidence: Owner answers on 2026-10-17; DM secret list shows SUBMODULE_TOKEN (SELF).
Impact: Governance master plan only.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the task card claimed all units complete while confirmed blocking defects remain in triage and the Guidelines contract.
Evidence: review of task.sh triage (count-based JOIN, local-only scan) and Guidelines PR #7 diff; CI runs 3417/3419 apply only to superseded objects.
Impact: initiative stops accepting requirements; status uses the PLANNED..CLOSED model; remaining phases tracked in one master record.
Refs: PR #585, Guidelines PR #7
Co-authored-by: Cursor <cursoragent@cursor.com>
Why:
Provide phased rollout roadmap (Phases 1-5) for stock repositories and mandatory defaults for new projects under governance v2.
Evidence:
Specification documented in docs/superpowers/specs/2026-10-16-stock-repos-adoption-matrix.md.
Impact:
Clarifies U6 and U7 governance deliverables for multi-repo rollout without ambiguity.
Refs:
feature/development-governance-v2
Why:
Audit differences between Agent-System-Dev agent_exec.py and Development-Manager runner.go to clarify layer responsibilities for governance v2.
Evidence:
Architecture specification document created in docs/superpowers/specs/.
Impact:
Provides guidance for U3 shared executor convergence without duplicating logic across repositories.
Refs:
feature/development-governance-v2
Why: user approved the four design documents and authorized implementation
(/goal); the plan's section-7 tradeoffs gate the I1 public DTO and had to be
frozen before any implementation unit starts. A read-only audit of the RDM
backend (Agent-System-RDM main 5df66106) supplied the source facts.
Evidence: audit findings recorded in rollout section 7 (tree is doc->section
only, no confidence field, no persisted conflict entity, per-project event seq
complete); review fixes folded into the read-model contract (statReasons,
structuralGap, AssertionSummary); precheck receipt READY imported via
task-resume.
Impact: unlocks I1 implementation in the RDM repo; design deliverable ready
for PR/CI/merge; no business code, pins, database or deployment touched.
Refs: .task/feature-document-visualization-plan.md
weichen
