coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Close live inventory migration and prepare workplan identity repair
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-05 10:17:42 +02:00
parent da42f764c0
commit 3dc005df1c
5 changed files with 157 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

17
workplans/RPF-WP-0028-durable-live-image-inventory.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Make Forgejo image protection survive checkout replacement"
domain: financials
repo: railiance-platform
status: blocked
status: finished
owner: codex
created: "2026-09-05"
updated: "2026-09-05"
@ -14,7 +14,7 @@ state_hub_workstream_id: "622d1208-b085-5ec2-9fb7-5e41f23e1843"
# Make Forgejo image protection survive checkout replacement
Source: State Hub message `868a2326-cdad-4256-be4c-7cd6c8ec4b5b`. Reviewed against current repository state
on 2026-09-05. Repository implementation is complete; live closure remains pending.
on 2026-09-05. Repository implementation and live inventory migration are complete.
## Implement and verify durable publication
@ -36,9 +36,18 @@ alongside a bad one, proving partial coverage cannot authorize deletion.
```task
id: RPF-WP-0028-T02
status: wait
status: done
priority: high
state_hub_task_id: "2d0795ba-ccc0-5ba9-8315-2deb4d0d71a6"
```
Requires the production host inventory, activity-core directory mount/configuration update, and cluster rollout hook adoption. Follow docs/forgejo-package-prune.md. Preserve the restored union and worker refusal on missing/empty inventory; do not manually trigger prune. No production migration or live verification occurred in this session.
Requires the production host inventory, activity-core directory mount/configuration update, and cluster rollout hook adoption. Follow docs/forgejo-package-prune.md. Preserve the restored union and worker refusal on missing/empty inventory; do not manually trigger prune. Completed 2026-09-05: installed the versioned helper outside the checkout,
seeded all 51 restored entries and merged a fresh railiance01 export (86 total),
added the read-only directory mount, rolled out actcore-worker, and synced the
exact definition override. API readback confirms the durable path. The resolver
accepts that path and refuses missing input before subprocess execution; the
command construction check used a mock and did not run prune. A post-rollout
capture succeeded. Activity-core's refresh target delegates to this hook; invoke
it after subsequent cluster rollouts (no new periodic schedule was introduced).
Evidence: `docs/evidence/RPF-WP-0028-live-inventory-2026-09-05.json`.
Source revisions: platform `da42f76`, activity-core `4083f31`.

48
workplans/RPF-WP-0031-workplan-identity-collision.md Normal file
View file

@ -0,0 +1,48 @@
---
id: RPF-WP-0031
type: workplan
title: "Separate duplicated apps-pg and Core Hub workplan identities"
domain: financials
repo: railiance-platform
status: blocked
owner: codex
created: "2026-09-05"
updated: "2026-09-05"
---
# Separate duplicated workplan identities
## Diagnose and prepare the exact repair
```task
id: RPF-WP-0031-T01
status: done
priority: high
```
The supported `rmgr sync --path . --push` path reached the verified primary
railiance01 projection in 5.8 seconds, but refused six duplicate identities.
Both the May apps-pg archive and August Core Hub onboarding use RPF-WP-0021,
the same workplan UUID, and the same first five task UUIDs. No projection rows
were created, changed, or retired by the refused reconciliation.
`docs/evidence/RPF-WP-0021-collision-repair-proposal.json` fixes the proposed
choice: retain the older archive and reidentify the newer onboarding record as
RPF-WP-0030, with six Repo Manager-derived UUIDs and four evidence-reference
updates. Existing source UUIDs have not been changed.
## Apply the identity repair and reconcile
```task
id: RPF-WP-0031-T02
status: wait
priority: high
```
Requires a one-time user exception to AGENTS.md's prohibition on editing managed
UUID fields. The existing Repo Manager migration command considers only live
workplans and unfinished tasks, so it does not repair these finished records.
After approval, apply the exact proposal, preserve the archived identity and
all completion evidence, check uniqueness across root and archived workplans,
commit/push, and run `rmgr sync`. Inspect any retirement refusal before proceeding;
never blanket-acknowledge unrelated retirements.