WP-0015 follow-up: hub-core publish pass, refresh docs
Some checks failed
ci / validate-registry (push) Has been cancelled

Re-run federation sweep — hub-core now passes Gitea raw URL probe (12/60
blockers remain). Update workplan progress, SCOPE.md, IntentScopeGapAnalysis,
and operator checklist to reflect T02/T03 closure and current compose stats
(20 capabilities, 0 duplicate warnings).
This commit is contained in:
2026-06-16 03:46:01 +02:00
parent d71f394911
commit 14979f0602
4 changed files with 66 additions and 60 deletions

View File

@@ -68,7 +68,7 @@ status: progress
priority: high
state_hub_task_id: "7024ca46-cabd-44a8-8baf-cbc83d99c1fe"
needs_human: true
intervention_note: "13 repos Gitea raw HTTP 404 — operator must fix visibility or create hub-core repo"
intervention_note: "12 repos Gitea raw HTTP 404 — operator must fix visibility (hub-core resolved 2026-06-16)"
```
Close gap priority **25**.
@@ -76,10 +76,13 @@ Close gap priority **25**.
**2026-06-16:** Sweep re-run — all 13 still HTTP 404. No agent-side remediation
possible without Gitea operator action. Bring all roster rows to `publish_check: pass`.
**Blocked slugs (13):** `activity-core`, `hub-core`, `ihp-railiance-probe`,
`inter-hub`, `net-kingdom`, `railiance-apps`, `railiance-cluster`,
`railiance-enablement`, `railiance-infra`, `railiance-platform`,
`tegwick-control`, `whynot-control`, `whynot-design`
**2026-06-16 (follow-up):** `hub-core` resolved — Gitea repo created, push OK,
`publish_check: pass`. **12** slugs remain HTTP 404.
**Blocked slugs (12):** `activity-core`, `ihp-railiance-probe`, `inter-hub`,
`net-kingdom`, `railiance-apps`, `railiance-cluster`, `railiance-enablement`,
`railiance-infra`, `railiance-platform`, `tegwick-control`, `whynot-control`,
`whynot-design`
Per slug:
@@ -89,8 +92,8 @@ Per slug:
4. Update `local-repo-roster.yaml` (`publish_check`, `publish_note`)
5. Re-run roster sweep: all `publish_fail` → 0
**Special:** `hub-core` create `coulomb/hub-core` on Gitea first (push-to-create
disabled).
**Resolved:** `hub-core``coulomb/hub-core` created on Gitea; roster
`publish_check: pass` (2026-06-16 follow-up).
**Done when:** `reuse-surface stats --roster ... --federation-ready` shows
`all_publish_pass: true`.
@@ -177,6 +180,9 @@ Verify federation health after T01 and T02.
push + `--refresh` for remote reuse-surface source. **13** fetch warnings remain
(blocked on T01).
**2026-06-16 (follow-up):** Compose re-run — **0** duplicate-ID warnings,
**12** remote fetch warnings, **20** federated capabilities. `hub-core` fetch OK.
```bash
reuse-surface hub sync --merge
reuse-surface federation compose
@@ -218,11 +224,15 @@ done (operator choice documented in workplan).
```task
id: REUSE-WP-0015-T06
status: todo
status: progress
priority: low
state_hub_task_id: "fd25e504-21b7-4e9f-841c-cfa20318be33"
```
**2026-06-16 (follow-up):** Partial refresh — `SCOPE.md` and
`docs/IntentScopeGapAnalysis.md` updated for T02/T03 closure and 12/60 publish
blockers. Final pass when T01/T04 complete.
On workplan completion:
- Update `SCOPE.md` §What Is Not Possible Yet and §Current State
@@ -253,4 +263,5 @@ On workplan completion:
| Date | Event |
|---|---|
| 2026-06-16 | WP-0015 created from `history/2026-06-16-intent-scope-assessment.md` |
| 2026-06-16 | T02 dedup (3 local entries); T03 report gaps; T05 CI; T01 operator-blocked |
| 2026-06-16 | T02 dedup (3 local entries); T03 report gaps; T05 CI; T01 operator-blocked |
| 2026-06-16 | Follow-up: hub-core publish pass (12 blockers); T06 partial doc refresh |