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: 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 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: include the current integration baseline before verification.
Evidence: fetched origin/main=a736d5a420370cff052bd946f6d6397d4c354547.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: an independent review caught that the card asserted the two delivery
branches were red at their tips as a verified conclusion, and that the figures
I quoted matched no natural measurement. Both are session-local observations,
not evidence this repo can reproduce.
Evidence: the card now separates a checkable claim (Dev's gates never exercise
the delivery branches) from a SELF observation with the exact commits and
method, marks it as not admissible as GATE evidence, and voids the imprecise
numbers from commit 537bf66.
Impact: task card only.
Refs: RDM PR #460, Development-Manager PR #32
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: both components have landed, the delivery branch red-at-tip finding and
the six authorization defects it exposed are the substantive result, and the
admit baseline-recognition change is what unblocked the merge at all. None of
that was recorded.
Evidence: Backend 7158bea (Dev pin f084d10 already contains it); RDM bc8db88
via PR #460, five review rounds ending PASS, CI green; Development-Manager
2c2e372 via PR #32.
Impact: task card only.
Refs: Backend PR #234, RDM PR #460, Development-Manager PR #32, Dev PR #634
Why: decision D1 (user ruling A1 on whether the role-cap layer is covered by
R3's carve-out) was written into an RDM test comment as "Decision A1" without
ever being recorded anywhere in the repo, so a later review round found it
cited but unverifiable. D2-D4 are not new choices either: they follow directly
from the plan's U2 archive clause, R6, and the standing platform-cap domain
rule, and now have a written home.
Evidence: RDM review rounds 1-4 in this branch's worktree.
Impact: task card only.
Refs: RDM feature/project-access-lifecycle-u4-work-states-merge
Why: the task card still carried the placeholder goal while the Backend half
of the delivery had already landed, and the verified pre-merge pin state is
the justification for the whole task.
Evidence: Backend main 7158bea contains 284d3ac; Dev pins measured at
dfb31da / 113103f / RDM c6304224.
Impact: task card only.
Refs: Backend PR #234
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-pal-component-delivery-pins.md; R0=a496ea0f0249b2b412354677ef97612ccd692d25.
Impact: task metadata only; the feature workspace starts at a496ea0f02.
Refs: .task/fix-pal-component-delivery-pins.md
weichen
agent-exec-transport