railiance-master/workplans/archived/260818-ADHOC-2026-07-30.md
codex 27a7063a11 fix(workplans): qualify archived ad-hoc identifiers
The live-file pass missed these: archived ad-hocs carry a YYMMDD- filename
prefix, so the ADHOC-* glob did not match them. They still derive from the
forge, so they are live records rather than dead files.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 00:34:04 +02:00

1.1 KiB

id type title domain repo status owner topic_slug created updated
RMASTER-WP-ADHOC-2026-07-30 workplan Ad-hoc Railiance framework maintenance on 2026-07-30 financials railiance-master archived codex railiance 2026-07-30 2026-08-18

Ad-hoc maintenance - 2026-07-30

Restore Forgejo repository descriptions

id: RMASTER-WP-ADHOC-2026-07-30-T01
status: done
priority: medium

Compared both public pages of the retired Gitea coulomb organization with both public pages of Forgejo. Gitea retained nonempty descriptions for 79 migrated repositories; Forgejo had lost or replaced all 79. Restored the normalized Gitea descriptions through the existing activity-core ExternalSecret-backed Forgejo administrative boundary. Repositories created only in Forgejo were initially left untouched; the four that remained blank (fin-hub, forgejo-actions-probe, railiance-bootstrap, and railiance-hosts) then received descriptions derived from their local scope/intent metadata or explicit probe purpose. All 100 Forgejo repositories now have nonempty descriptions. No credential value left the cluster or entered recorded output.