feat: add isolated Linux shadow backend
This commit is contained in:
parent
36996be39a
commit
f5217fef0f
6 changed files with 283 additions and 2 deletions
|
|
@ -78,6 +78,19 @@ at 100% of declared source lines and functions. No production Linux
|
|||
subcontrol backend, independent Guanghu boot supervisor, JD boot change, or
|
||||
physical cutover is implied by that source result.
|
||||
|
||||
`scripts/linux-subcontrol-docker-backend.sh` is the first executable shadow
|
||||
backend for the Linux-hosted transition. It binds the exact JD instance,
|
||||
backend id, immutable Ubuntu image digest, and preserved GRUB rescue slot. A
|
||||
wake starts a networkless, read-only, capability-free container with explicit
|
||||
CPU, memory, and PID limits. Only the registered runtime-identity readback is
|
||||
accepted; reclaim removes the container and verifies `DORMANT`. Environment
|
||||
path overrides are rejected outside the isolated test harness.
|
||||
|
||||
This backend can prove the bounded Linux lifecycle while Ubuntu is still the
|
||||
host. It cannot prove Guanghu-first boot control or the final topology. Those
|
||||
remain `0` until the same lifecycle is owned by an independently booted
|
||||
Guanghu supervisor and has a current JD server receipt.
|
||||
|
||||
## Language-primary boot target
|
||||
|
||||
`guanghu-language-primary.target` makes the accepted cognitive-control model
|
||||
|
|
|
|||
Loading…
Reference in a new issue