Why: backend main advanced to 528e3a4 (surface conversation required,
card backfills); the backend task branch merges it into the batch-1
line and the Dev pin follows.
Evidence: integration transport success (gitlink5-run.json); backend
build green on the merge; full make test re-run follows.
Impact: one component gitlink.
Refs: feature/agent-stack-audit-remediation-b1
Why: close out the batch-1 audit trail before review and PR.
Evidence: make test exit=0 on the fully repinned combination
(verify-combo-make-test4.json).
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b1
Why: the U3B sqlite repair advanced the squad container to 0f1daa8 and
backend's nested-squad pin follow-up moved backend to 1f61131.
Evidence: integration transport success (gitlink4-run.json); full
make test re-run follows on this branch.
Impact: two component gitlinks.
Refs: feature/agent-stack-audit-remediation-b1
Why: check-pins requires each container's nested gitlinks to equal the
Dev top-level pins; the batch-1 bumps left native/squad/backend
containers pinned at pre-batch sibling versions.
Evidence: integration transport success (gitlink3-run.json); full
make test re-run follows on this branch.
Impact: three component gitlinks.
Refs: feature/agent-stack-audit-remediation-b1
Why: the backend branch advanced to 49c1259 with the U6 boundary
repair (admission test reworked behind intentgate helpers).
Evidence: repair receipt success; verify-u6r2 exit=0; combination
make test re-run follows on this branch.
Impact: one component gitlink.
Refs: feature/agent-stack-audit-remediation-b1
Why: land U1-U7 and U10 across agent-native (5c0d2d8), agent-squad
(23f161b), agent-intent (765a7e7), agent-command (fe7987d) and
modules/backend (4030449) per the approved remediation plan.
Evidence: per-unit SELF receipts under /tmp/agent-stack-b1 all exit=0;
combination verification (make test) recorded next on this branch.
Impact: five component gitlinks; no other Dev paths.
Refs: docs/superpowers/plans/2026-10-21-agent-stack-audit-remediation-plan.md
Why: all ten batch-1 units implemented and individually verified.
Evidence: verify-u3b exit=0 (race).
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b1
Why: keep the per-unit audit trail current.
Evidence: verify-u6 exit=0; U3B first run failed-unknown on a
pre-session cursor TLS failure (553B log, zero changes, workspace
preserved), reconciled as environmental and re-dispatched.
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b1
Why: keep the per-unit audit trail; U10 first run failed-unknown
(pi attempt exited 0 without a decodable terminal record), workspace
preserved for reconciliation and the unit re-dispatched with a corrected
packet (nested deps gitlinks materialized).
Evidence: verify-u2/u4/u4b exit=0; no code change.
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b1
Why: carry authorization, scope, wave plan and receipt tables for the
agent-per-unit implementation of U1-U7 and U10.
Evidence: card + receipts under /tmp; no code change.
Impact: task metadata only (exempt path).
Refs: docs/superpowers/plans/2026-10-21-agent-stack-audit-remediation-plan.md
Why: record the audited findings and the batched remediation contract
(U1-U11) that subsequent implementation units must satisfy.
Evidence: document-only change; no code paths touched.
Impact: docs only; plan is the scope authority for the remediation task.
Refs: feature/agent-stack-audit-remediation-b1
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-agent-stack-audit-remediation-b1.md; R0=d9e9c0560a2767539f4415b579adbeff86a22ba6.
Impact: task metadata only; the feature workspace starts at d9e9c0560a.
Refs: .task/feature-agent-stack-audit-remediation-b1.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=a736d5a420370cff052bd946f6d6397d4c354547.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/fix-genui-prod-upgrade-followups.md -> .task/archive/fix-genui-prod-upgrade-followups.md; status 已完成（合入前闭合）; PR #681https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/681.
Impact: task metadata only; the card is archived within PR #681 and lands with its merge commit.
Refs: task.sh close --self
Why: the card must carry results, evidence and review before closing.
Evidence: make evidence entry for tests.test_svc_identity (31 OK, 1 skipped).
Impact: task card only.
Refs: fix/genui-prod-upgrade-followups.
Co-authored-by: Cursor <cursoragent@cursor.com>
Move modules/documents to 75e43e1 (Documents #120), which replaces the
NOT_RUN GenUI acceptance note with the 2026-10-21 prod rerun result and
records that admin cannot create projects until a role is assigned.
Why: the Dev pin should carry the updated GenUI prod record.
Evidence: Documents #120 CI success at f5417fb; agent-exec unit dev-genui-prod-followups-repin (cursor, attempt 1, terminal=success).
Impact: documentation pin only.
Refs: Dev task fix/genui-prod-upgrade-followups.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the card must state authorization, goals and unit receipts.
Evidence: agent-exec receipts under /tmp/genui-followups-20261021.
Impact: task card only.
Refs: fix/genui-prod-upgrade-followups.
Co-authored-by: Cursor <cursoragent@cursor.com>
svc.sh adopt always printed db_marker=established, even when the installed
artifact lacked identity capability and the marker stayed pending. It now
reads the marker back and warns when identity was not established.
The deploy identity gate reported a pre-v27 database (identity table
missing) as a foreign row or mismatch. It now explains that the schema
predates the identity table and gives the backup, stop, migrate and
redeploy steps. It still refuses before stopping the old service and never
migrates on its own.
Why: both messages misled the 2026-10-21 GenUI prod upgrade.
Evidence: agent-exec unit dev-svc-identity-adopt-gate-messages (cursor, attempt 1, terminal=success); python3 -m unittest tests.test_svc_identity: 31 tests OK (1 skipped).
Impact: svc.sh operator messages for adopt and the deploy identity gate; no change to success paths.
Refs: Dev task fix/genui-prod-upgrade-followups.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-genui-prod-upgrade-followups.md; R0=ccb6dfaa9cdf7e69eb15d7df024dee55f37b8df1.
Impact: task metadata only; the feature workspace starts at ccb6dfaa9c.
Refs: .task/fix-genui-prod-upgrade-followups.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ccb6dfaa9cdf7e69eb15d7df024dee55f37b8df1.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/fix-svc-db-card-merge-backfill.md -> .task/archive/fix-svc-db-card-merge-backfill.md; status 已完成（合入前闭合）; PR #680https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/680.
Impact: task metadata only; the card is archived within PR #680 and lands with its merge commit.
Refs: task.sh close --self
Why: the card in main still reads "待定 / 未评审 / NOT_RUN" even though its
PR #342 merged on 2026-10-11. The backfill text was written on
feature/svc-db-record-backfill but never landed, leaving that branch as an
orphan with its only unmerged content being this bookkeeping.
Evidence:
Gitea API (re-checked today): PR #342 merged=true, merge commit
452f00e6d9, which is an ancestor of
origin/main; PR #346 closed-unmerged, PR #347 merged — both consistent
with the backfill text.
Triage receipt /tmp/triage-svcdb-cardbackfill-20261021.json (NEW).
The "CI test/test-pg 双 success" statement is carried over from the
task's own record; that run is outside the API's recent-60 window and was
not re-verified today.
Impact: 4 bookkeeping fields in one archived card. No code change.
Refs: PR #681; fix/svc-db-card-merge-backfill
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-genui-prod-upgrade-docsync.md -> .task/archive/feature-genui-prod-upgrade-docsync.md; status 已完成（合入前闭合）; PR #679https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/679.
Impact: task metadata only; the card is archived within PR #679 and lands with its merge commit.
Refs: task.sh close --self
Why: The card must carry the authorization, the out-of-repo upgrade steps,
the verification results and the agent-exec receipts for both units.
Evidence: Receipts /tmp/genui-prod-upgrade-doc/{docs,dev}-run.json;
Documents #119 CI success at 518e381.
Impact: Task card only.
Refs: Documents #119
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-svc-db-card-merge-backfill.md; R0=e634608d97333354c3ead85d47c9e9e368a992a0.
Impact: task metadata only; the feature workspace starts at e634608d97.
Refs: .task/fix-svc-db-card-merge-backfill.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-genui-prod-upgrade-docsync.md; R0=e634608d97333354c3ead85d47c9e9e368a992a0.
Impact: task metadata only; the feature workspace starts at e634608d97.
Refs: .task/feature-genui-prod-upgrade-docsync.md
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/fix-multi-instance-test-failure-diagnostics.md -> .task/archive/fix-multi-instance-test-failure-diagnostics.md; status 已完成（合入前闭合）; PR #678https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/678.
Impact: task metadata only; the card is archived within PR #678 and lands with its merge commit.
Refs: task.sh close --self
Why: the test-hygiene change needs its scope, the review verdict and the
real-PostgreSQL evidence recorded before delivery.
Evidence:
/tmp/mi-diag-impl-r1-20261021.json: cursor, success (single file)
/tmp/mi-diag-review-r1-20261021.json: pi-glm, success (PASS, 6 non-blocking)
Real-PG runs: idle 15.1s and 96-load 17.4s, both ok (fsync=on cluster
on 127.0.0.1:54331); the Backend fix is already in main via PR #237/#674.
Impact: card metadata only; no behaviour change.
Refs: PR #679; fix/multi-instance-test-failure-diagnostics
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-multi-instance-test-failure-diagnostics.md; R0=5360884e9283d962caf945d944df05b5e5059177.
Impact: task metadata only; the feature workspace starts at 5360884e92.
Refs: .task/fix-multi-instance-test-failure-diagnostics.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=096b74b4775e81cfb2864f98cae2e9fc9d9c1a44.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-genui-prod-ops-docsync.md -> .task/archive/feature-genui-prod-ops-docsync.md; status 已完成（合入前闭合）; PR #677https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/677.
Impact: task metadata only; the card is archived within PR #677 and lands with its merge commit.
Refs: task.sh close --self
Why: The card must carry the delivery scope, the out-of-repo ops facts and
the agent-exec receipts for both units.
Evidence: Receipts /tmp/genui-prod-docsync/{docs,dev}-run.json; Documents
#118 CI success at 244477e.
Impact: Task card only.
Refs: Documents #118
Why: Documents PR #118 updated the GenUI closure doc so its prod deploy
entry matches the current runtime layout (prod manual via prodctl.sh,
pg1 managed by svc in the main checkout).
Evidence: agent-exec unit dev-genui-prod-ops-docsync-repin (cursor,
attempt 1, terminal=success); gitlink 82b4619 -> fcea466.
Impact: Documentation pin only; also carries the already-merged IAM U1-U7
record (Documents #117).
Refs: Documents #118; task feature/genui-prod-ops-docsync
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/fix-remaining-hardcoded-ports.md -> .task/archive/fix-remaining-hardcoded-ports.md; status 已完成（合入前闭合）; PR #676https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/676.
Impact: task metadata only; the card is archived within PR #676 and lands with its merge commit.
Refs: task.sh close --self
Why: the card must carry the helper's design boundary, the (r1 scope-expansion
-> granted expansion -> r2 success) trajectory, the independent review verdict
and the runtime evidence before delivery.
Evidence:
/tmp/ports-load-20261021.json: helper test under 64-load OK
/tmp/ports-svc-tests-20261021.json: tests.test_svc 23 OK
/tmp/ports-governance-20261021.json: 527 OK (18 skipped)
/tmp/remaining-ports-impl-r2-20261021.json: cursor, success
/tmp/remaining-ports-review-r1-20261021.json: pi-glm, PASS
Impact: card metadata only.
Refs: PR #676; fix/remaining-hardcoded-ports
weichen
