[chen21019]

Host metadata plans now support only name and description with native role/Key checks, human approval and one durable claim. Host detail adds bounded, independently authorized container references; Host/Volume Stack resolution follows the native readable Service relation and rejects ambiguous or changed chains. Catalog launch now binds the native Stack ID before CREATE scheduling through lazy lifecycle-handler composition.

Existing Host lifecycle, labels, grants, output filters and deletion rules remain unchanged. Relationship completeness stays unknown, including empty results. The Catalog fix does not retry uncertain mutations or retroactively bind orphan plans.

Validation: focused metadata, native DAO/view and real Spring/ObjectManager integration checks passed. The release gate preserves all 142 required identities and adds 24 exact methods (166 total). C03 re-extraction binds 458 source inputs and retains all 1396 HTTP tuples with no semantic or grant delta. The 89 POMs and three build scripts are version-only updates; the shared source gate also runs four network-free Maven transport controls and four Guava HTTP/checksum controls. Both builders keep the exact Maven 3.9.16 SHA512 pin with official Apache CDN/archive sources, and checksum failure is terminal. Guava retains its original Maven Central URL and SHA256; HTTP errors and mismatched bytes stop before installation. Both builders replace APT/libapt-pkg7.0 with the two exact official USN-8996-1 3.2.1ubuntu0.1 packages before the first APT operation, with four focused metadata/install failure controls. The prior full Maven run passed 434 suites / 3,981 tests / zero failures and errors / one inherited skip, including the original 166-case XML gate; its overall scan failed on the newly disclosed APT HIGH and remains preserved. Native Trivy OpenVEX covers only CVE-2026-109518 and the two exact officially fixed Ubuntu26.04 amd64 PURLs, after validating the native pair and all nineteen official installed ELF hashes on the same image. Original raw findings remain; a verifier rejects any unrelated finding removal, and the original pip implementation and severity policy are unchanged. Seven focused boundary controls passed, including complete package-content/multiplicity comparisons with explicitly recorded Trivy-derived graph ID mappings. The existing original native report pair also passes offline verification; neither report is rewritten. Full Security/JDK25, independent CodeQL and organization CodeQL remain required; no native runtime acceptance or publication is claimed.