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: 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: 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: Backend main now contains the fix for the run-status write-ordering
race in Manager.ResolveHITL (PR #237, merge f084d10); the Dev repo's
modules/backend pin still pointed at the pre-fix SHA, which is why the
multi-instance acceptance test was flaky under load.
Evidence:
/tmp/repin-maketest5-20261021.json: make test green with the new pin
/tmp/repin-modules-evidence2-20261021.json: backend update + state recorded
/tmp/multi-instance-with-be-fix-20261021.json: 96-load reproduction passes (17s)
/tmp/be-runhitl-impl-r2-20261021.json: Backend transport (pi, success, 789f67f)
/tmp/be-runhitl-impl-r1-20261021.json: scope-expansion (r2 expansion granted)
/tmp/be-triage-runhitl-20261021.json: triage NEW
/tmp/multi-instance-loaded-20261021.json: red reproduction (same SHA on pre-fix)
/tmp/multi-instance-heavy-20261021.json: red reproduction under 96-load
/tmp/ci-success-testpg.log: healthy CI 22.4s measurement
Impact: a single gitlink bump (241e1b3 -> f084d10). No Dev-side source change.
Behaviour change: U7 TestTwoInstancesOverSharedPG no longer flakes under CI load.
Refs: Backend PR #237; Dev task fix/backend-repin-resolve-hitl
Why: the knip ratchet flagged one new unused export from the U6 unit; the
reconciled tip is the L1 frontend composition pin.
Impact: frontend gitlink pin.
Refs: PR #634.
Why: the app-package main-line test fixtures needed the same narrowed-model
reconciliation as the rest of the composition; the reconciled tip is the
L1 backend composition pin.
Impact: backend gitlink pin.
Refs: PR #634.
Why: the L1 backend pin advances to the reconciled tip (association/
explanation tests reconciled to the narrowed role model, catalog test
brace restored, full filtered suites green).
Impact: backend gitlink pin.
Refs: PR #634.
Why: the L1 backend pin advances to the composition merge (lifecycle
narrowing + member-history fixes merged with Backend main
association/explanation/super-admin, tests reconciled) so composition
checks (check-pins nested pins) arbitrate on the delivered tree.
Impact: backend gitlink pin (integration of delivered transports).
Refs: PR #634.
Why: the U6 frontend unit (project work-state controls, member
suspend/reactivate, template browsing via rdm.docs.templates/instantiate)
was delivered on the Frontend working branch 581b25d; the L1 composes the
frontend pin at the U6 head and records the verification.
Impact: frontend gitlink pin and task card (integration of the delivered
U6 branch into the L1; the pin bump is host integration of an
already-transported delivery).
Refs: PR #634.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=73bc9f208103ec1b9b83775ca65fee12f79ba99e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
weichen
