Why: the pinned RDM artifact is 73 commits behind the mainline, so the daily instance and everything built from the composed product are missing everything merged there since the last follow-up.
Evidence:
sha advances to the current RDM main head, whose own CI (runs 4946 and 4947, push) is green on both jobs — this is not an unvalidated commit.
Both selection constraints still hold, and they were checked before choosing the pair rather than discovered afterwards. The pins layout is unchanged at six, and there is zero schema or migration difference between the old pin and the new one. The second one matters because scripts/svc.sh refuses an incompatible switch before stopping the old service; the first is what the per-pin CI materialization requires.
The delivered lifecycle work is still present in the new pin: managementCeilingDenial and txProjectManaged both resolve in its tree.
The span is genuinely useful this time: prev_sha becomes the previously pinned commit, 73 commits back, so the round-trip identity test covers a real upgrade distance rather than two adjacent merges.
legacy_sha is untouched since it carries the no-identity semantics.
The pin comment states the new span and both constraints instead of the stale numbers it carried before.
Why: the pinned RDM artifact is 73 commits behind the mainline, so the daily instance and everything built from the composed product are missing everything merged there since the last follow-up.
Evidence:
- `sha` advances to the current RDM main head, whose own CI (runs 4946 and 4947, push) is green on both jobs — this is not an unvalidated commit.
- Both selection constraints still hold, and they were checked before choosing the pair rather than discovered afterwards. The pins layout is unchanged at six, and there is **zero** schema or migration difference between the old pin and the new one. The second one matters because `scripts/svc.sh` refuses an incompatible switch before stopping the old service; the first is what the per-pin CI materialization requires.
- The delivered lifecycle work is still present in the new pin: `managementCeilingDenial` and `txProjectManaged` both resolve in its tree.
- The span is genuinely useful this time: `prev_sha` becomes the previously pinned commit, 73 commits back, so the round-trip identity test covers a real upgrade distance rather than two adjacent merges.
- `legacy_sha` is untouched since it carries the no-identity semantics.
- The pin comment states the new span and both constraints instead of the stale numbers it carried before.
Refs: Dev PR #690 (the previous pin follow-up).
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-rdm-pin-advance-latest-2.md; R0=6ced938a126981ee2a4fab671a2da94f49cb56c5.
Impact: task metadata only; the feature workspace starts at 6ced938a12.
Refs: .task/fix-rdm-pin-advance-latest-2.md
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 73 commits behind the mainline, so the daily instance and everything built from the composed product are missing everything merged there since the last follow-up.
Evidence:
shaadvances to the current RDM main head, whose own CI (runs 4946 and 4947, push) is green on both jobs — this is not an unvalidated commit.scripts/svc.shrefuses an incompatible switch before stopping the old service; the first is what the per-pin CI materialization requires.managementCeilingDenialandtxProjectManagedboth resolve in its tree.prev_shabecomes the previously pinned commit, 73 commits back, so the round-trip identity test covers a real upgrade distance rather than two adjacent merges.legacy_shais untouched since it carries the no-identity semantics.Refs: Dev PR #690 (the previous pin follow-up).