[raylei50653]

Summary

Phase C PR-C3 (scope §6): the PR-C1/C2 shipping tree becomes a package that installs atomically from a clean system. Contract, results and limits: docs/reference/native_runtime_resolved_config.md §19.

• Release = 3 files: <name>.tar.gz, <name>.install.sh, <name>.sha256 (package digest over both). <name> = saccade-0.1.0-linux-x86_64-cu13.0-trt10.16-sm120-glibc2.39.

• shipping/package/install.sh (POSIX sh, Ubuntu 24.04 base tools only):

  1. Checks the digest.
  2. Extracts into private staging next to TARGET.
  3. Checks every file against MANIFEST.json: exact set, regular files, size, sha256, mode.
  4. Runs one mv -n -T, which is renameat2(RENAME_NOREPLACE).

  Any failure or signal removes the staging directory and never creates TARGET. --verify PREFIX re-checks an installed tree. No hook options or environment variables.

• MANIFEST.json: every key except files is derived from the repository at the source commit:

  • pins, versions, SM / glibc
  • attestation / lineage / model-root references
  • the runtime-identity coordinate

  The builder refuses files that are not the pins, a dirty tree, or a stale identity.

• Checks:

  • check_shipping_package.py tarball: 7 checks.
  • check_shipping_package.py install-trace: from strace -yy, the target is touched only by that one rename.
  • check_shipping_bundle.py static --manifest: checks an installed tree.

• Nothing in stage computation, entrypoint pin, operator library, the 27 vendor objects, launcher, auditor or install rules changes.

Design decisions open to owner review (§19.1):

• The installer is outside the tarball.
• The digest is not a signature (P3 records this; signing is PR-C4).
• The runtime identity is republished before the formal run, because the MANIFEST records the coordinate. That republish is the stacked PR on chore/465-prc3-republish.

Formal run: 9217ed92 → PASS

results/465_prc3_package/full_9217ed92/ (not versioned), evaluation.json 6f8e1210….

Gate	Result
1–2	build/install exit 0; static 12/12
3 package	tree_clean, identity_current; tarball 7/7; two builds byte-identical (tarball 21c9ac08…, 2.22 GiB); MANIFEST matches the tree
4 install in clean container (dash)	exit 0; install-trace 5/5: the target is touched by one renameat2(…, RENAME_NOREPLACE) only, 274 other mutations all in staging, staging removed; static --manifest 13/13; --verify 0; installed tree matches the cmake tree
5 installed tree, clean container	EXACT: detector 5316/5316, MOT 7/7, graph 7/7; identical to the PR-C2 A4 run
6 G2-2/G2-4	runtime 3/3; EXACT, 7/7 identical

Installer negative controls P1–P15 all gave their required result:

• Corrupt tarball; one file changed; extra file; missing file.

• Target exists (dir, empty dir, file, symlink); full disk; SIGTERM during extraction and during verification; prefix with :; digest missing or ambiguous; renamed package.

  In every one of these, TARGET is never created (or is left unchanged when it already existed) and no staging directory is left.

• SIGKILL leaves the staging directory (a named limit); the next install reports it and succeeds.

• A plain tar -xzf fails install-trace.

One evaluator fix is recorded in §19.5: P10a's staging count used a recursive listing. The contract is unchanged.

Not done

• No distribution: Phase C scope §4 licensing is still unconfirmed.
• No minisign signature (PR-C4).
• No other GPU, host or filesystem.

Merge order

Review and merge the stacked republish PR into this branch first. That merge is required: test_runtime_identity_staleness fails without it.

scripts/pre_push.sh passed on the combined head.

🤖 Generated with Claude Code