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
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=dc86a023605d00fccca1b9679b4cdad96373bdee.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Settings plaintext loses to secret_keys, so replacing the env key did not change the key a conversation actually sent.
Evidence: python3 -m unittest tests.test_svc.SvcDbRecoveryTests.test_seed_replaces_old_system_secret tests.test_svc.SvcDbRecoveryTests.test_seed_warns_when_old_secret_stays_active tests.test_svc.SvcDbRecoveryTests.test_seed_puts_without_credentials_when_auth_off (SELF).
Impact: Embedded databases now compare the active system secret fingerprint after seeding, and the backend gitlink carries the adoption fix.
Refs: fix/model-key-secret-overlay
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=919f75cf7b39ca357e212a08a0ba5ba3d9a79b51.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=692735e91d6a9ab07ddd3686feb60a56b270728a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The dev service is an rdm build, so startup skipped model seeding and kept the old MiniMax chat model. Later starts need the saved env file applied even without an admin key command.
Evidence: seed and rdm launcher tests passed. The live dev database now uses the four-model chat route and keeps the original MiniMax endpoint as reserve.
Impact: Restart of a service with envfile set rewrites system model settings. HTTP seeding is unchanged for builds that can mint an admin key. MiniMax is stored separately because fallbacks cannot switch gateways.
Refs: .task/feature-four-model-vision.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Turn the approved multi-CLI routing design into independently testable Cursor implementation units without another manual plan gate.
Evidence: The plan self-review found R1-R10 coverage, stable interfaces, five review-focus tests, and no placeholders or whitespace errors.
Impact: Authorizes U1-U5 execution through fresh Cursor Agent runs while the host retains scope, verification, integration, and delivery control.
Refs: docs/superpowers/specs/2026-10-15-project-agent-execution-design.md
Why: Let each project route expensive implementation work across available Agent CLIs while the host model retains planning and delivery control.
Evidence: The specification passed placeholder, consistency, scope, path, and whitespace self-checks; implementation and runtime validation remain NOT_RUN.
Impact: Defines a review-only R1-R10 design for Markdown configuration, adapters, run-everything execution, receipts, recovery, and host fallback without enabling the new route.
Refs: .task/feature-goal-first-delivery.md
Why: Chat, lightweight, fallback and vision settings need a seed path, and the backend now sends current-turn images only to models declared capable of seeing them.
Evidence: The backend change is cfde38d. The seed test covers fallback and vision settings. A local image conversation on each builtin profile returned the pictured content from the expected model, and removing the chat model from the capable list switched that turn to the vision model.
Impact: New runs can use the four builtin profiles and image input. Secrets stay in the ignored env file. The live 8788 process is unchanged.
Refs: .task/feature-four-model-vision.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: deploy needs to choose registered plugins and ship them inside one agent-system, then refuse the release when they are not active.
Evidence: python3 -m unittest tests.test_svc_plugins tests.test_svc_user_help tests.test_svc tests.test_svc_u2 (SELF, 63 passed, 1 skipped). Real compose build and make test-lifecycle are NOT_RUN.
Impact: --with is mutually exclusive with --from rdm and --from release. Existing non-interactive deploys stay without plugins unless plugins= is already recorded. Changing the plugin id set on a live service requires --allow-source-switch.
Refs: .task/feature-svc-plugin-compose.md modules/documents/docs/proposals/2026-10-14-svc-plugin-compose-deploy.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=4f84c2e1630cd0311643529fae1c3a99f1dd5d64.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Operators need the approved no-password initialization and owner-confirmed recovery contract, and stage 6 reviewers need an exact component/evidence map.
Evidence: SELF task-card precheck and make test-governance receipts; component receipts listed in the task card with separate source identities.
Impact: svc rejects obsolete credential commands before storage binding, help points to protected delivery and recovery proposals, and the task card records stage 6 scope with formal pin/CI dependencies still pending.
Refs: IAM U3 r1 Documents c236d309; Backend 3e01614; RDM 265d33e; Frontend a961b19
weichenandCursor