fix(workplans): resolve repository grant id collision
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Container Image / build-and-push (push) Successful in 7s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf
This commit is contained in:
tegwick 2026-09-04 19:30:53 +02:00
parent 4f426c29d4
commit 41a5815d78
3 changed files with 16 additions and 11 deletions

View file

@ -1,5 +1,5 @@
---
id: ACTIVITY-WP-0037
id: ACTIVITY-WP-0038
type: workplan
title: "Carry repository grants and reconcile terminal queue closes"
domain: infotech
@ -37,7 +37,7 @@ queue boundaries. The grant must not be inferred from task prose, labels,
## Review and specify the cross-repository contract
```task
id: ACTIVITY-WP-0037-T01
id: ACTIVITY-WP-0038-T01
status: done
priority: high
```
@ -56,7 +56,7 @@ grant-absent rows remain valid during migration.
## Carry the authoritative repository grant
```task
id: ACTIVITY-WP-0037-T02
id: ACTIVITY-WP-0038-T02
status: done
priority: high
```
@ -80,7 +80,7 @@ policy id `2ed31282d721f4466bc9ea722067d9d0` for the shared fixture.
## Preserve evidence and reconcile terminal closes
```task
id: ACTIVITY-WP-0037-T03
id: ACTIVITY-WP-0038-T03
status: done
priority: high
```
@ -108,7 +108,7 @@ non-terminal.
## Verify and hand off
```task
id: ACTIVITY-WP-0037-T04
id: ACTIVITY-WP-0038-T04
status: wait
priority: high
```
@ -136,6 +136,11 @@ schema and repeat-close contract in message
The first two required `statehub fix-consistency` attempts timed out querying
the local API; retry after this final file update remains the only close gate.
Identity correction 2026-09-04: this unregistered workplan was renumbered from
`ACTIVITY-WP-0037` to `ACTIVITY-WP-0038`. The former ID was already immutably
assigned on 2026-08-26 to archived historical record `WP-0002` / State Hub
UUID `b221e65a-6f97-44b0-8dae-442fffcb7f64`.
The third attempt reached inbox-hygiene collection but remained blocked waiting
for the local State Hub messages endpoint for more than two minutes and was
interrupted. Direct message, decision, progress, and mark-read API writes all