Why: the pinned RDM artifact is 59 commits behind the RDM mainline, so anything merged there since — including the three review observations closed in RDM PR #467 — is not in what the composed product builds or what the daily instance runs.
Evidence:
sha advances to the current RDM main head. That head's own CI (runs 4806 and 4805, push) is green on both jobs, so this is not deploying an unvalidated commit.
The delivered lifecycle work is present in the new pin: managementCeilingDenial and txProjectManaged in the RDM tree, plus AuthorizeProjectManagementCmd which is the creator-side gate the render-profile convergence relies on.
prev_sha becomes the previously pinned commit. This is better than the value it replaces: the old prev_sha sat one merge behind its sha, so the round-trip identity test barely spanned anything. The new pair is 59 commits apart, which is real version distance for that test to cover.
Both selection constraints still hold. The pins layout is unchanged at six, and there is zero schema or migration difference between the two commits — which matters because scripts/svc.sh refuses an incompatible switch before stopping the old service. legacy_sha is untouched since it carries the no-identity semantics.
The pin comment was rewritten to state the new span and the two constraints, rather than the stale numbers it carried before.
make test is green locally; the real combination gates that actually build this pin — test-pg and svc-realcombo — run only in CI.
Refs: RDM PR #467, Dev PR #682 (the pin advance this follows).
Why: the pinned RDM artifact is 59 commits behind the RDM mainline, so anything merged there since — including the three review observations closed in RDM PR #467 — is not in what the composed product builds or what the daily instance runs.
Evidence:
- `sha` advances to the current RDM main head. That head's own CI (runs 4806 and 4805, push) is green on both jobs, so this is not deploying an unvalidated commit.
- The delivered lifecycle work is present in the new pin: `managementCeilingDenial` and `txProjectManaged` in the RDM tree, plus `AuthorizeProjectManagementCmd` which is the creator-side gate the render-profile convergence relies on.
- `prev_sha` becomes the previously pinned commit. This is better than the value it replaces: the old `prev_sha` sat one merge behind its `sha`, so the round-trip identity test barely spanned anything. The new pair is 59 commits apart, which is real version distance for that test to cover.
- Both selection constraints still hold. The pins layout is unchanged at six, and there is zero schema or migration difference between the two commits — which matters because `scripts/svc.sh` refuses an incompatible switch before stopping the old service. `legacy_sha` is untouched since it carries the no-identity semantics.
- The pin comment was rewritten to state the new span and the two constraints, rather than the stale numbers it carried before.
`make test` is green locally; the real combination gates that actually build this pin — `test-pg` and `svc-realcombo` — run only in CI.
Refs: RDM PR #467, Dev PR #682 (the pin advance this follows).
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-rdm-pin-advance-latest.md; R0=1de7c28c2122609dd9b6435881696492bd052a34.
Impact: task metadata only; the feature workspace starts at 1de7c28c21.
Refs: .task/fix-rdm-pin-advance-latest.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=b7636742fc9ea937e6030123afc608fd294861bf.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: the pinned RDM artifact is 59 commits behind the RDM mainline, so anything merged there since — including the three review observations closed in RDM PR #467 — is not in what the composed product builds or what the daily instance runs.
Evidence:
shaadvances to the current RDM main head. That head's own CI (runs 4806 and 4805, push) is green on both jobs, so this is not deploying an unvalidated commit.managementCeilingDenialandtxProjectManagedin the RDM tree, plusAuthorizeProjectManagementCmdwhich is the creator-side gate the render-profile convergence relies on.prev_shabecomes the previously pinned commit. This is better than the value it replaces: the oldprev_shasat one merge behind itssha, so the round-trip identity test barely spanned anything. The new pair is 59 commits apart, which is real version distance for that test to cover.scripts/svc.shrefuses an incompatible switch before stopping the old service.legacy_shais untouched since it carries the no-identity semantics.make testis green locally; the real combination gates that actually build this pin —test-pgandsvc-realcombo— run only in CI.Refs: RDM PR #467, Dev PR #682 (the pin advance this follows).