e5f3497337
`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.
Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.
The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
1.4 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| RPF-WP-ADHOC-2026-08-23 | workplan | Repair apps-pg tenancy evidence declaration | financials | railiance-platform | finished | codex | railiance | 2026-08-23 | 2026-08-23 |
RPF-WP-ADHOC-2026-08-23 — apps-pg tenancy evidence declaration
Attach evidence to the current apps-pg posture
id: RPF-WP-ADHOC-2026-08-23-T01
status: done
priority: high
Added the existing authoritative backup/restore artifact to the top-level
evidence map for the current apps-pg R2 and V1 claims. The provider-axis
evidence remains in place because it supports the separate capability offer;
the new entries satisfy the current-posture evidence contract directly.
Verification runs the canonical NetKingdom tenancy-posture validator against this repository's declaration and checks the repository diff.
Stabilize expired-engagement broker readiness tests
id: RPF-WP-ADHOC-2026-08-23-T02
status: done
priority: medium
Full test discovery exposed two WP0025 broker-readiness tests that built a receipt with wall-clock time for a terminal prior-day engagement. Add an optional explicit clock to the receipt builders and pin the unit fixtures to the contract window so the production default stays current UTC while offline tests remain deterministic.
The complete 146-test offline suite now passes on dates after the terminal engagement window.