coulomb/hub-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: record deployed repository publisher gate
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
This commit is contained in:
tegwick 2026-09-01 02:33:11 +02:00
parent dda93db0ac
commit 9724b273a1
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
workplans/HUB-WP-0006-repository-classification-navigation.md
View file

@ -174,6 +174,14 @@ at startup and on a configured interval. Live conformance accepted 123
repositories over five pages as one current generation; Repo Manager evidence:
`docs/evidence/RMGR-WP-0013-live-conformance-2026-09-01.md`.
Deployment checkpoint 2026-09-01: Helm revision 24 runs the Forgejo-backed
publisher and hub-core image `dda93db` privately on railiance01. Live
verification accepts 114 public repositories in a 3.45-second full scan and
reports nine private sources as bounded errors. T06 remains `wait` only on
`RAPPCOREHUB-WP-0003-T04`: a dedicated `read:repository` Forgejo identity and
an error-free 123-repository admission proof. No host checkout or State Hub
runtime dependency remains.
T06 still waits only on production placement/networking and deployment of the
two committed runtimes. The public Core Hub cluster does not own the host-local
Repo Manager checkout registry; do not solve that by mounting a broad home