Restore persistent system path composition

This commit is contained in:
ms2k 2026-07-22 03:07:42 +09:00
commit 7aff8e542e

View file

@ -285,13 +285,15 @@ the same component-wise `0700` creation rules.
Configuration resolution also requires a closed sandbox layout. Its
closed protected-destination set contains `/workspace` and every product-owned
sandbox mount destination selected by default bundle construction. Each
persistent or volume destination is compared with every member in both ancestry
directions. The configuration loader does not guess paths for control,
credential, mailbox, proc, sys, dev, runtime, or later product mounts, and a
layout cannot be constructed without `/workspace`. Bundle
construction, rather than trusted-host configuration syntax, owns the remaining
exact destination choices.
sandbox mount destination selected by default bundle construction. Volumes and
protected trees may not overlap in either ancestry direction. Persistent paths
follow the same rule except that a bundle-classified exact transient mount may
replace a child of a persistent parent. The child remains protected and may not
itself contain or be selected as persistent state. The configuration loader does
not guess paths for control, credential, mailbox, proc, sys, dev, runtime, or
later product mounts, and a layout cannot be constructed without `/workspace`.
Bundle construction, rather than trusted-host configuration syntax, owns the
exact destination choices and transient-child classification.
The loader resolves environment references only after structural, path, and
network validation. A missing, non-UTF-8, or NUL-containing host value refuses