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

Recover external repository renames through verified Forgejo redirects
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Multi-Context Image / build-and-push (push) Successful in 24s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
tegwick 2026-09-05 18:57:15 +02:00
parent 022cf4b727
commit fe6b8d96c2
4 changed files with 166 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

52
workplans/STATE-WP-0089-rename-redirect-recovery.md Normal file
View file

@ -0,0 +1,52 @@
---
id: STATE-WP-0089
type: workplan
title: "Recover an externally completed Forgejo rename through its old-name redirect"
domain: infotech
repo: state-hub
status: active
owner: codex
created: "2026-09-05"
updated: "2026-09-05"
---
# Recover the canon federation rename journal
CFED-WP-0001-T03 renamed Forgejo repository 46 from identity-canon to
commerce-canon through the approved operator credential lane. Journal
615e7b44-d84e-4feb-92c5-1708feaf1e65 remains preflighted because the Forge adapter
rejects the old coordinate's 307 redirect. New coordinate and exact source head
40d5792fafbb2de778eabb56cfeaf00aecd058e1 are independently verified.
## Handle the redirect without weakening identity checks
```task
id: STATE-WP-0089-T01
status: done
priority: high
```
Report redirects without following them or forwarding credentials. For forward
recovery, inspect the new coordinate directly and verify immutable ID, branch,
head and projection first. Accept the old redirect only if it names that exact
same-instance/owner/new-coordinate API URL. Wrong identity, external redirects,
wrong owner, missing Location and both names occupied remain failures.
Add transport and API regression tests, and run the rename suite.
## Promote the tested fix and resume the existing journal
```task
id: STATE-WP-0089-T02
status: progress
priority: high
```
Commit/push; promote the immutable CI image through the existing Helm release
with reused values and atomic rollback. Preserve API-only signing configuration.
Verify healthy primary/railiance01, then retry forge-renamed and statehub-rebound
on the same journal. Record image/revision and live recovery evidence. The donor
rename, checkout moves and consumer acceptance remain CFED-WP-0001-T03 and
IDENTITY-WP-0004 responsibilities. No direct DB edits or journal replacement.
Validation: rename API, CLI and workplan tests pass (46 tests), including seven
new transport/forward-recovery cases. `git diff --check` passes.