Why: all batch-2 units implemented, repaired and verified; full make
test green on the final pinned combination.
Evidence: verify-combo.json exit=0; component branches pushed
(native cff6935, squad 9edb6ba, backend 9b40595).
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b2
Why: the backend branch tip 9b40595 additionally pins the nested
agent-squad (and its nested native) so the composed chain carries the
batch-2 event fields end to end.
Evidence: integration transport success (gitlinkb-run.json); full
make test re-run follows on this branch.
Impact: one component gitlink.
Refs: feature/agent-stack-audit-remediation-b2
Why: land U8, U9 and U11 across agent-native (cff6935), agent-squad
(9edb6ba) and modules/backend (race-repair tip) per the approved plan.
Evidence: per-unit SELF receipts under /tmp/agent-stack-b2 (all
exit=0); full make test re-run follows on this branch.
Impact: three component gitlinks.
Refs: docs/superpowers/plans/2026-10-21-agent-stack-audit-remediation-plan.md
Why: per-unit audit trail for U8/U9/U11a/U11b/U11c including the
fail-stop redispatches and the frame-order repair.
Evidence: per-unit SELF receipts under /tmp/agent-stack-b2.
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b2
Why: carry authorization, the discovered composition regression
(#682 reset batch-1 pins) and its restoration, plus the wave plan.
Evidence: restoration transport success (pinrestore-run.json).
Impact: task metadata only.
Refs: feature/agent-stack-audit-remediation-b2
Why: PR #682 (f23f5bb0) merged a stale branch whose tree carried
pre-batch component pins, silently reverting the batch-1 composition
on main; batch 2 (U8/U9/U11) is defined on top of batch 1.
Evidence: restoration transport success (pinrestore-run.json); batch-1
tips pushed on all five component origins.
Impact: five component gitlinks restored to the audited batch-1 tips.
Refs: feature/agent-stack-audit-remediation-b2
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-agent-stack-audit-remediation-b2.md; R0=f23f5bb01a8b96ab90686d3a1b07791d7f473de2.
Impact: task metadata only; the feature workspace starts at f23f5bb01a.
Refs: .task/feature-agent-stack-audit-remediation-b2.md
Why: the RDM materialization fix landed separately as PR #684, so this branch
now takes main's version of the workflow and carries only the pin change. The
conflict resolution keeps the fix (submodule update per pin, language-agnostic
fail-loud assertion) and drops the pin-specific comment that described a
first-parent distance belonging to the other pull request.
Impact: workflow resolves to main's already-merged content; this commit's own
contribution is the rdm.pin prev_sha correction.
Refs: PR #682, PR #684
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-agent-stack-audit-remediation-b1.md -> .task/archive/feature-agent-stack-audit-remediation-b1.md; status 已完成（合入前闭合）; PR #685https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/685.
Impact: task metadata only; the card is archived within PR #685 and lands with its merge commit.
Refs: task.sh close --self
Why: the independent review approved batch 1 (APPROVE, 0 blockers);
the first CI run failed at checkout because the five pinned component
commits were local-only and are now pushed.
Evidence: review4-run.json (pi-glm success); component remote refs
created; this commit retriggers CI.
Impact: task metadata only.
Refs: PR #685
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=b25846d2.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
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: include the current integration baseline before verification.
Evidence: fetched origin/main=5a907f42944af56dbca68b6a058cc4f0bc2681d7.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
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: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/fix-svc-superadmin-envfile-surface-conv.md -> .task/archive/fix-svc-superadmin-envfile-surface-conv.md; status 已完成（合入前闭合）; PR #683https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/683.
Impact: task metadata only; the card is archived within PR #683 and lands with its merge commit.
Refs: task.sh close --self
Why: the card must carry results, evidence and the authorized rerun receipts before closing.
Evidence: make evidence for svc unittest suite (51 OK, 1 skipped) on HEAD 3c0faf76.
Impact: task card only.
Refs: fix/svc-superadmin-envfile-surface-conv.
Co-authored-by: Cursor <cursoragent@cursor.com>
Move modules/backend to 528e3a4 (Backend #239), which rejects empty or
foreign conversationId when creating a surface via POST /api/surfaces.
Why: Dev must carry the Backend conversation-required fix.
Evidence: Backend #239 CI success at 954e744; agent-exec unit
dev-svc-superadmin-surface-backend-repin (cursor, authorized fresh rerun,
terminal=success).
Impact: documentation pin / gitlink only.
Refs: Dev task fix/svc-superadmin-envfile-surface-conv.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the pin materialization fix did its job - all three pins now build and the
missing-go.sum error is gone - so the failure relocated to the real combination
lifecycle gate, where svc.sh cannot git fetch from CI's shallow RDM clone.
That is a different component's concern and outside this pin advance.
Evidence: run 4714 job 7830 - svc-realcombo and test green; three lifecycle
cases fail on svc.sh's git fetch against the shallow RDM source clone.
Impact: task card only.
Refs: PR #682
Why: the card must state authorization, goals and unit receipts including the failed-unknown and authorized Backend rerun.
Evidence: agent-exec receipts under /tmp/svc-sa-surface-20261021.
Impact: task card only.
Refs: fix/svc-superadmin-envfile-surface-conv.
Co-authored-by: Cursor <cursoragent@cursor.com>
Auth-on agent services need super-admin credentials at every launch, but
svc only forwarded them from the current environment, and recover/watchdog
relaunch with a cleared environment, so a bare restart or recovery failed
closed. svc now records only the absolute path of AGENT_SYSTEM_ENV_FILE as
superadmin_envfile= after checking it is a regular, owner-only (0600) file
before stopping anything, and forwards that path when no explicit
credentials are set. An empty AGENT_SYSTEM_ENV_FILE clears the record. The
file content is never read, copied or printed.
Why: prod restarts and recovery required re-exporting AGENT_SYSTEM_ENV_FILE.
Evidence: agent-exec unit dev-svc-superadmin-envfile-persist (cursor, attempt 1, terminal=success); unittest test_svc_superadmin_envfile + test_svc_recover + test_svc_identity: 51 OK (1 skipped).
Impact: svc.sh agent launch and svc.env gain superadmin_envfile; docs/svc.md 4.2 note.
Refs: Dev task fix/svc-superadmin-envfile-surface-conv.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the fail-loud assertion worked as intended and named the real cause -
RDM's pins set grew from four to six, so the CI step that checks out and builds
all three pins no longer sees a consistent layout. My prev_sha choice was
wrong and I did not check layout consistency when writing the unit.
Evidence: run 4711 job 7821 - 'rdm pin c6304224 的 pins/agent-system-frontend
未落地：缺少 go.mod'; pin layouts verified across all five commits; local
build-product.sh on the delivered head succeeds.
Impact: task card only.
Refs: PR #682
Why: advancing the RDM pin red-lights test-pg on a real composition problem
that make test cannot see, and the card must say so plainly instead of showing
a green combination run.
Evidence: run 4707 job 7812 — the combination build reports missing go.sum
entries for agent-document-renderer packages. RDM bc8db88 replaces that module
with a local path and therefore carries no go.sum entries for it, while the
Dev-side build redirects the backend replace to modules/backend (f084d10),
which imports those packages directly.
Impact: task card only.
Refs: PR #682
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-svc-superadmin-envfile-surface-conv.md; R0=d9e9c0560a2767539f4415b579adbeff86a22ba6.
Impact: task metadata only; the feature workspace starts at d9e9c0560a.
Refs: .task/fix-svc-superadmin-envfile-surface-conv.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
weichen
agent-exec-transport