Align Core Hub build lane with Helixforge
This commit is contained in:
parent
5f1aad927c
commit
cac6302a0a
2 changed files with 148 additions and 1 deletions
|
|
@ -194,7 +194,7 @@ retirement is unblocked.
|
|||
|
||||
```task
|
||||
id: CUST-WP-0052-T05
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "b46e608d-0174-422d-baf4-26b5d027e761"
|
||||
```
|
||||
|
|
@ -213,6 +213,14 @@ Minimum scope:
|
|||
Done when the Core Hub continuation has a concrete build/test/release surface
|
||||
rather than one-off shell recipes.
|
||||
|
||||
Completed 2026-06-27: added `docs/core-hub-helixforge-build-alignment.md`.
|
||||
The note separates HelixForge's capability/workplan role from Railiance Forge's
|
||||
concrete build, registry, runner, and evidence contracts. It maps Core Hub's
|
||||
existing Make targets, staging profile, immutable image-tag expectation,
|
||||
operator CLI, smoke evidence, and future `railiance-apps` promotion path into a
|
||||
repeatable build/test/release lane without blocking API contract work on runner
|
||||
automation.
|
||||
|
||||
## Task: UI Rebuild Criteria
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue