feat(guanghu-os): add repository bridge lifecycle
This commit is contained in:
parent
9acee850cd
commit
0d1ded1196
9 changed files with 326 additions and 4 deletions
|
|
@ -127,6 +127,15 @@ prove physical boot or bounded wake/reclaim of the real repository bridge, so
|
|||
those predicates and final master control remain `0`. See ADR-0177 and
|
||||
`deployments/JD-FD-PRIMARY/CROSS-ROOT-SUPERVISOR-QEMU-RECEIPT-20260815.hldp`.
|
||||
|
||||
## Bounded repository bridge lifecycle
|
||||
|
||||
`scripts/guanghu-repository-bridge-lifecycle.sh` requires a live root-supervisor
|
||||
state and one allowlisted repository readback request. It wakes a registered
|
||||
backend, verifies the pinned `main`, and reclaims the backend on both success
|
||||
and failure. `scripts/forgejo-repository-shadow-backend.sh` provides a separate
|
||||
loopback-only Forgejo data plane for physical-node isolation tests; it never
|
||||
targets the public repository process. See ADR-0178.
|
||||
|
||||
## Language-primary boot target
|
||||
|
||||
`guanghu-language-primary.target` makes the accepted cognitive-control model
|
||||
|
|
|
|||
Loading…
Reference in a new issue