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: combo make test against frontend pin 8b59998 (Frontend #104 merged)
is green; evidence row tool-written before opening the Dev PR.
Evidence: evidence row on this card (SELF).
Impact: task card only.
Refs: rollout I4
Why: the canonical e2e.sh run (frontend c9ba344 + duty-based seed) passed
13/13 plus plain-base 2/2 — the I4 acceptance scenarios are green and the
evidence row is tool-written.
Evidence: evidence row on this card (SELF, sha256 in record).
Impact: task card only.
Refs: rollout I4
Why: branches merged into their immediate or root target had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-development-governance-v2.md(PR#585 into main) — merges verified via git log --merges plus Gitea API squash lookup against each card's origin target.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: The archived child cards still showed NOT_RUN for review, merge and cleanup although all three happened.
Evidence: PR #595/#596 review comments (REPLAY) and CI (GATE); task-finish exit 0 for both child worktrees.
Impact: Archived task cards only.
Refs: PR #585, PR #595, PR #596
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: branches merged into their immediate or root target had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-development-governance-v2-triage-hardening.md(PR#595 into feature/development-governance-v2) — merges verified via git log --merges plus Gitea API squash lookup against each card's origin target.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: branches merged into their immediate or root target had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-development-governance-v2-target-integrity.md(PR#596 into feature/development-governance-v2) — merges verified via git log --merges plus Gitea API squash lookup against each card's origin target.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: Phase 4 requires task-sync and the final initiative PR check before review and merge.
Evidence: make evidence SELF receipts for make task-sync (changed=0, sync_base aa3c7ea) and make task-pr-check PR=585 FINAL=1 (PR_CHECK_OK kind=initiative).
Impact: Task card only.
Refs: PR #585
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Phase 3 requires evidence that real children flowed child -> initiative and that a frozen initiative rejects new children.
Evidence: make evidence SELF receipt for task-triage (NEW) and forced JOIN refusal (exit 7); PR #595/#596 Review and CI records.
Impact: Task card only.
Refs: PR #585, PR #595, PR #596
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Both required children (#595, #596) are merged; the initiative must stop accepting new requirements before final delivery.
Evidence: PR #596 merged as 41bf47c with test/test-pg/svc-realcombo green on 00ae760.
Impact: Task card only; triage no longer offers this initiative as a JOIN candidate.
Refs: PR #585, PR #596
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U2.4 completed with the documented local-clone gitlink pattern; the child is ready for review.
Evidence: make evidence test-governance (1 environmental port conflict) and check-pins (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-target-integrity.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: vite dev server (4174) login returns 401 with credentials that succeed
via direct curl to the same serve - a separate proxy-forwarding anomaly in
the dev-server path, recorded so the next session uses the canonical
e2e.sh-managed preview instead.
Evidence: p10 probe (401 via dev proxy) vs direct curl 200 on the same
serve/data, same credentials.
Impact: card bookkeeping.
Refs: rollout I4
Why: include the current parent initiative baseline before verification.
Evidence: resolved feature/development-governance-v2=208f4e8db73cb7f99f62b173000898da3136a0d2.
Impact: integrate parent initiative changes without rewriting task history.
Refs: task-sync
Why: the instrumented run (render-log build) confirms the DOM-vs-state
contradiction and adds the instance-remount hypothesis with the missing
done-log evidence.
Evidence: probe logs show RENDER/EFFECT/FETCH-resolved complete but
setProjects-done absent, select=0 at t+3s and t+8s.
Impact: card bookkeeping.
Refs: rollout I4
Why: the cockpit hang is now isolated to the React commit layer - the
component's fetch resolves (rows=2, cancelled=false, setProjects called)
but the DOM keeps rendering the loading state. This contradiction needs
interactive React DevTools work; documented with the reproduction path.
Evidence: trace.zip (run 20261016-160406 and the 013103 preview rerun);
console capture shows resolved rows=2 while the DOM snapshot shows 加载中.
Impact: card bookkeeping; no code change this commit.
Refs: rollout I4
Why: The worker initialised the submodule, which changed git administration state in its private clone.
Evidence: /tmp/gov2-receipt-u24-r1.json terminal failed-unknown, no transport (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-target-integrity.md
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: U2.2 completed on a fresh run after a scope-expansion stop and was applied by transport.
Evidence: make evidence run of task/recovery/evidence/triage/pr-check tests (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-target-integrity.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: multiple 加载中 hangs traced to preview restarts without
PLAYWRIGHT_API_TARGET (proxy landing on the shared dev RDM at 8787);
recorded so the next session verifies the preview environment first.
Evidence: manual probes with/without the env var (login 401 vs entry
visible) on the same seed data.
Impact: card bookkeeping only.
Refs: rollout I4
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-development-governance-v2-target-integrity.md; R0=aa3c7eae40264ee47d5505a162074cfd77b1a099.
Impact: task metadata only; the feature workspace starts at 3524ffd3cc.
Refs: .task/feature-development-governance-v2-target-integrity.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=aa3c7eae40264ee47d5505a162074cfd77b1a099.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Phase 2 needs a second child created through the new triage flow, and --final needs a child registry.
Evidence: PR #595 merged into the initiative as ba029e4 (GATE run 3488).
Impact: Initiative task card only; intake is closed again after the second child merges.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U2.3 completed and was applied by transport; the first run was rejected before start.
Evidence: make evidence run of test_task_pr_check and test_ci_credentials (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-triage-hardening.md
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
agent-exec-transport