[SaladDay]

Core installation currently carries all three native daemon/Harness installers inside its image and again in its archive. Keep only their matched build/protocol/checksum catalog in the default Core image and control archive. Session bootstrap downloads the current platform from a fixed Release asset; explicit offline archives carry one external copy per platform, served through the same Core endpoint.

Container and native Core retain the same catalog directory. Same-version repair preserves offline content, and adding it refreshes Core's availability state. Runtime/Harness execution and installation grant/claim semantics remain unchanged. Publication and qualification validate the independent native assets before publication.

Validation:

• Catalog tests, including online redirect, verified offline serving and corrupt-local refusal.
• Real two-origin HTTPS POSIX bootstrap test, including checksum rejection and no credentials at the artifact origin; Go race check passed.
• Installer tests cover online installation, offline addition, read-only container mounting, native configuration and repair.
• Thin/offline archive inventory and publication/qualification refusal tests passed.
• OpenAPI regeneration produced no contract changes. Fresh independent blind review passed through efa1f576.
• Native CI passed on Linux, macOS and Windows; API acceptance passed. The Mac host also passed a lightweight real HTTPS redirect/download/checksum fixture smoke.
• Remote make check is finishing; completed unchanged targets are reused after correcting test-host proxy/database setup.

No release tag or existing installation is changed. This PR has not produced a new full release or measured its final compressed size. Windows bootstrap and the native Harness payloads are unchanged; native CI is the cross-platform gate.