repo-manager/workplans/RMGR-WP-0018-publisher-registry-image-refresh.md

id	type	title	domain	repo	status	owner	created	updated	state_hub_workstream_id
RMGR-WP-0018	workplan	Deliver publisher registry corrections for renamed repositories	infotech	repo-manager	finished	codex	2026-10-03	2026-10-03	b931dd36-c937-508b-9747-e7d070b0198d

Deliver publisher registry corrections for renamed repositories

Inbox requests 067710ae-825a-4a13-b3f8-60ee3ef60aab and 706d014b-1aee-4a51-988e-8ec6dd4330ce report two identity mismatches in the deployed publisher. Both source corrections already exist, but the runtime still uses the September 1 image. Track source/package completion separately from the consuming wrapper's live acceptance gate.

Verify both canonical registry identities

id: RMGR-WP-0018-T01
status: done
priority: high
state_hub_task_id: "866d79f6-b2f1-5c7a-ba84-98b970b56ed5"

Forgejo reads on October 3 confirm identity-canon redirects to commerce-canon (Forge ID 46), and access-engine resolves with Forge ID 42. State Hub direct identity reads confirm the existing UUIDs match the committed registry. The corrections landed in ca7dcad (September 6) and d66d474 (September 30). Both sources pass the strict publisher observation path with exact commit and classification fingerprints. No UUID reassignment or archived evidence edit.

Package and verify the corrected registry

id: RMGR-WP-0018-T02
status: done
priority: high
state_hub_task_id: "8e09a581-81a8-5e8c-a373-a6ebdddd02cc"

Build the publisher from clean source commit 03869ff304, verify its embedded registry and runtime, and publish an immutable digest for the wrapper. Document the image refresh requirement so a source-only correction is not mistaken for live completion.

Published image: forgejo.coulomb.social/coulomb/repo-manager@sha256:69d00898cfa1ff0a4b7db8cdc86d15f5f4bea4526915019d3ca82b6f5574354c. The container holds 123 entries, observes both renamed sources successfully, and serves /readyz with HTTP 200. Full suite: 196 passed. Evidence: docs/evidence/2026-10-03-publisher-registry-refresh.md.

Track deployment and full publisher acceptance

id: RMGR-WP-0018-T03
status: done
priority: high
state_hub_task_id: "77cf3bbd-5f64-5e05-8b00-6d8bf3862817"

The deployment owner is rapp-core-hub, tracked by RAPPCOREHUB-WP-0003-T05. This repository session packages the correction; it does not authorize a live cluster rollout. After deployment, retain the 123/0 receipt here and in the wrapper before claiming live completion. Candidate connection remains the wrapper's separate acceptance step.

2026-10-03 receipt (CUST-WP-0075): rapp-core-hub pinned and the founder deployed repo-manager@sha256:69d00898…. make verify-publisher in rapp-core-hub: accepted 123/123, errors 0/0, registry 123 ("publisher baseline passed"). The corrected identity-canon and access-engine sources resolve live. Candidate connection stays the wrapper's separate step (RAPPCOREHUB-WP-0003-T05).