tegwick
54271a2261
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
64 lines
2.7 KiB
Markdown
64 lines
2.7 KiB
Markdown
# RMGR-WP-0013 live publisher conformance — 2026-09-01
|
|
|
|
## Scope
|
|
|
|
This evidence covers the Repo Manager classification publisher and hub-core's
|
|
frozen `helixforge.repository-classification-projection` 1.0.0 consumer. It is
|
|
a live source/conformance proof from the workstation checkout fleet, not a
|
|
production deployment claim.
|
|
|
|
## Registrar bootstrap
|
|
|
|
- State Hub source: `primary` / `railiance01`
|
|
- Discovery root: `/home/worsch` (operator-local, not published)
|
|
- Registered classified repositories: **123**
|
|
- Locally classified but unregistered checkouts: **2**
|
|
(`snuggles-inventor`, `wise-validator`), reported as warnings and omitted
|
|
- Stable IDs: existing State Hub registrar UUIDs; none invented
|
|
- Bulk `/repos/` was not used because it timed out after 180 seconds
|
|
- Successful bounded import: four workers, 15-second request timeout, two
|
|
transient retries
|
|
|
|
The generated private registry was written only to `/tmp` and was not committed.
|
|
It contained host paths for local observation; those paths did not enter the
|
|
published projection.
|
|
|
|
## End-to-end transfer
|
|
|
|
The publisher served the live registry with a page size of 25. Hub-core fetched
|
|
five HMAC-bound pages through its new HTTP `port.repo` client and accepted the
|
|
complete transfer atomically.
|
|
|
|
```json
|
|
{
|
|
"status": "accepted",
|
|
"snapshot_id": "c22faf46794ee9288102d6f0f98b04372ebfaa2c41017edf11c6101f157ec654",
|
|
"repository_count": 123,
|
|
"projection_status": "current",
|
|
"content_hash": "a3a1d584c8245b6c339bd672551d0960bf2b0b133e259bec7e884fe302cfe14c",
|
|
"source_revision": "b28a45e7c9592f6aecdc4537b463333545ba6f1c68746d6a5e904cff4d654008"
|
|
}
|
|
```
|
|
|
|
Repo Manager read classification from each repository's authoritative file and
|
|
published only contract fields. Hub-core derived its own navigation generation;
|
|
no database or private persistence model was shared.
|
|
|
|
## Verification
|
|
|
|
- Repo Manager: **156 passed**; Ruff clean
|
|
- Hub-core: **107 passed**
|
|
- Focused publisher tests cover duplicate identities, deterministic UUID order,
|
|
Git/source provenance, multi-page transfer, cursor tampering, invalid source
|
|
diagnostics, bearer authentication, readiness, and primary registrar import
|
|
- Hub-core focused tests cover cursor/token HTTP transport plus all frozen
|
|
repository-navigation contract and ingestion behaviors
|
|
|
|
## Remaining production gate
|
|
|
|
The code and cross-repository transport are ready. Production still needs an
|
|
explicit placement/network decision because hub-core runs in the public Core
|
|
Hub cluster while the authoritative checkout registry is host-local to the
|
|
Repo Manager worker. No broad host-path mount or implicit State Hub dependency
|
|
was introduced to hide that boundary. `RMGR-WP-0013-T05` remains waiting for
|
|
that deployment handoff; `HUB-WP-0006-T06` must not switch traffic before it.
|