Start REUSE-WP-0017-T05: Forgejo hub URL fixes and compose refresh.
Some checks failed
ci / validate-registry (push) Has been cancelled

Migrate eight stale Gitea hub registrations to Forgejo raw URLs,
recompose production and local federated indexes to 61 capabilities,
and add the T05 human-review checkpoint document.
This commit is contained in:
2026-07-07 14:43:02 +02:00
parent c97834447d
commit 89ca9b3891
4 changed files with 266 additions and 26 deletions

View File

@@ -0,0 +1,67 @@
# REUSE-WP-0017-T05 review checkpoint
Started 2026-07-07. Extends `history/2026-07-06-t04-review-summary.md`.
## Mechanical status (before human sign-off)
| Check | Status |
| --- | --- |
| Roster coverage | 62/62 (`has` or `none`) |
| Publish pass | 62/62 |
| Sibling unpushed registry commits | 0 (spot-check); `railiance-apps` has 1 unrelated unpushed commit |
| Production federated compose | **61 capabilities** / 61 enabled sources (2026-07-07, after Forgejo URL fixes) |
| `core-hub` hub registered | yes (Forgejo URL) |
| `inter-hub` hub disabled | yes |
| Stale Gitea hub URLs (Forgejo origin) | **8 repos fixed** on hub + production compose refreshed |
### Eight repos needing hub URL migration
These publish capability indexes on **Forgejo** but the hub still points at
**Gitea** raw URLs (empty/scaffold indexes):
- `hub-core`
- `issue-core`
- `key-cape`
- `railiance-apps`
- `railiance-cluster`
- `railiance-enablement`
- `railiance-infra`
- `railiance-platform`
Target URL pattern:
`https://forgejo.coulomb.social/coulomb/<slug>/raw/branch/main/registry/indexes/capabilities.yaml`
Broader Gitea→Forgejo migration for the remaining ~53 registrations is
**REUSE-WP-0019-T01**; these eight are the ones blocking federated compose
from picking up T04 drafts today.
## Human review queue (from T04 — still applies)
Review before calling T05 done:
1. **`the-custodian`** — NDA boundary; entry scoped to `runtime/` + `tools/` only.
2. **`vergabe-teilnahme`** — unfilled SCOPE.md; honestly low vector.
3. **`markitect-main`** — superseded-legacy framing.
4. **`issue-core`** — migrated pre-existing manifest; confirm nothing lost.
5. **`inter-hub`** — now `deprecated` / retired; hub disabled 2026-07-07.
6. **`core-hub`** — Gen-3 successor; self-authored entry, not T04 draft.
7. Stale repo-seed READMEs (`open-reuse`, `vantage-point`) — separate cleanup.
## Per-entry review commands
```bash
cd ~/<repo-slug>
git log -1 --stat -- registry/
cat registry/capabilities/*.md # or registry/NO_CAPABILITIES.md
reuse-surface validate --root .
```
## T05 exit criteria
- [ ] Human sign-off on flagged entries (or documented edits)
- [x] Hub URLs corrected for Forgejo-migrated repos with T04 content
- [x] Production `POST /v1/federated/compose`**61** capabilities
- [x] `hub sync` + local `federation compose --refresh` in reuse-surface
- [x] `reuse-surface catalog` + `graph` regenerated
- [ ] Task → `done`; T07 closeout can follow