2fb58fbeee
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 101414@bnt-lap001 Assistant-Session: 60b5a221-d435-42b9-b778-983c90c7eed6
98 lines
3.8 KiB
Markdown
98 lines
3.8 KiB
Markdown
---
|
||
id: RAIL-FAB-WP-0031
|
||
type: workplan
|
||
title: "Follow the flex-auth to access-engine repository rename in Fabric"
|
||
domain: financials
|
||
repo: railiance-fabric
|
||
status: blocked
|
||
flavor: residual
|
||
origin: residual
|
||
origin_ref: FLEX-WP-0020
|
||
owner: codex
|
||
topic_slug: railiance
|
||
created: "2026-09-22"
|
||
updated: "2026-09-30"
|
||
state_hub_workstream_id: "631e2974-55ba-58e3-b8ca-dc6c1c294111"
|
||
---
|
||
|
||
# RAIL-FAB-WP-0031 - flex-auth to access-engine rename (fabric-projection)
|
||
|
||
## Goal
|
||
|
||
FLEX-WP-0020 renames the repository coordinate `flex-auth` to `access-engine`.
|
||
The repository UUID `fda8ad85-a7d7-4055-8f21-902a533e59df` and Forge ID 42
|
||
stay. Runtime names stay `flex-auth` (FLEX-DEC-2026-013), so the
|
||
`flex-auth.*` runtime graph IDs must not change.
|
||
|
||
Origin: handoff request from flex-auth on 2026-09-15 (hub message
|
||
`10d4b1a2-8976-42a5-8d76-6fc1ce54fe87`, surface `fabric-projection`).
|
||
|
||
## T01 - Wait for the rename to land
|
||
|
||
```task
|
||
id: RAIL-FAB-WP-0031-T01
|
||
status: done
|
||
priority: medium
|
||
state_hub_task_id: "ded92fd8-cdd1-56b1-ad83-547b0b619cc8"
|
||
```
|
||
|
||
Start T02 only once flex-auth reports FLEX-WP-0020 as executed: the Forgejo
|
||
repository is `coulomb/access-engine` and the local checkout is
|
||
`~/access-engine`. As of 2026-09-22 neither exists.
|
||
|
||
## T02 - Update repository coordinates
|
||
|
||
```task
|
||
id: RAIL-FAB-WP-0031-T02
|
||
status: done
|
||
priority: medium
|
||
state_hub_task_id: "3c9c7773-f6e4-5473-a6cf-1154e9add1a2"
|
||
```
|
||
|
||
- `registry/local-repos.yaml` and `registry/railiance-repos.yaml`: slug, name,
|
||
path, and `remote_url` move to `access-engine`.
|
||
- Repo-owned `fabric/**` declarations with `repo: flex-auth` move to
|
||
`repo: access-engine`. Keep every `flex-auth.*` node id, service name, and
|
||
file name, because they are runtime names.
|
||
|
||
## T03 - Re-ingest and confirm
|
||
|
||
```task
|
||
id: RAIL-FAB-WP-0031-T03
|
||
status: wait
|
||
needs_human: true
|
||
blocking_reason: "Live re-ingest feeds the running Fabric registry service (production write via `railiance-fabric registry`); operator runs it, then confirms the graph. Local export evidence is recorded below."
|
||
priority: medium
|
||
state_hub_task_id: "74f58428-6ee9-52f6-98b9-4b3d9e524b33"
|
||
```
|
||
|
||
Re-run `scan-manifest` for the renamed entry and re-export the graph. Confirm
|
||
that no `repo:flex-auth` repository node remains, that the `flex-auth.*`
|
||
runtime nodes are unchanged, and that no edge endpoint is left unresolved.
|
||
Then reply to flex-auth with the evidence.
|
||
|
||
## Loose-end review — 2026-09-27
|
||
|
||
T01–T03 remain `wait`; the workplan is now `blocked`. The local checkout remains
|
||
`/home/worsch/flex-auth`; `/home/worsch/access-engine` is absent. The owner's
|
||
FLEX-WP-0020 still records T05 (fresh preflight and exact human approval) and T06
|
||
(Forgejo rename) as `wait`. There is no execution receipt satisfying T01.
|
||
|
||
Resume only after the owner reports the completed rename with unchanged
|
||
repository UUID and Forge ID 42. Then update coordinates and re-ingest under
|
||
T02/T03, preserving all `flex-auth.*` runtime identities. Preemptive manifest
|
||
changes would point to a missing checkout; no declarations or historical
|
||
snapshots were renamed during this review.
|
||
|
||
## Execution — 2026-09-30
|
||
|
||
FLEX-WP-0020 executed (access-engine head b943d9a; Forge ID 42; checkout
|
||
`~/access-engine`). T01 satisfied. T02 done: `registry/local-repos.yaml` and
|
||
`registry/railiance-repos.yaml` now name slug/name/path/remote_url `access-engine`
|
||
(`state_hub_repo_id` unchanged), and 13 `fabric/**` declarations moved from
|
||
`repo: flex-auth` to `repo: access-engine`; every `flex-auth.*` node id, service name
|
||
and file name is unchanged. `railiance-fabric validate .`: 0 errors, 0 warnings;
|
||
`unresolved`: none. Local `export --format json`: no `flex-auth` repository
|
||
reference remains, `flex-auth.*` runtime ids present (69 references). The repo's
|
||
pytest env lacks pytest/`railiance_fabric` on the path (pre-existing), so unit tests
|
||
were not run. T03's live re-ingest is an operator step (see task).
|