feat: complete self-hosted catalog and release preparation

[Lucenx9]

Summary

Completes the reviewable Feature 004 catalog-bootstrap and release-preparation slice, covering T139–T160. T161 remains explicitly open: this pull request does not create a tag, production signature, release, published asset, or certification claim.

T139–T148 — catalog bootstrap and optional sources

• Boots exactly ten immutable first-party skills with GitHub disabled.
• Verifies provenance, bundle/resource hashes, catalog integrity, and advisory integrity before readiness.
• Makes initialization atomic, lock-protected, idempotent, interruption-safe, and duplicate-free.
• Keeps optional sources disabled until explicitly selected by an administrator.
• Stores the optional GitHub token through a source-specific credential boundary, separate from Codex and Claude credentials.
• Quarantines malformed, unavailable, revoked, rate-limited, or unverified optional content without affecting first-party readiness.
• Keeps required CI offline and network-denied.

T149–T160 — release preparation and evidence boundaries

• Adds credential, telemetry, log, environment, artifact, and repository containment checks.
• Maps all 28 acceptance scenarios and FR-001 through FR-092 to executable evidence.
• Verifies canonical manifests, reproducible archives, offline TrustedRoot/Cosign bundles, signer quorum transitions, revocation, downgrade rejection, and digest-pinned images.
• Recomputes unchanged Feature 003 package and source integrity.
• Defines a reproducible seven-asset release contract with immutable names and collision refusal.
• Defines the Ubuntu 24.04 and Debian 12/13 × amd64/arm64 × rootful/rootless matrix without claiming unexecuted cells passed.
• Adds a disposable signed-asset quickstart with protected ownership state and exact resource cleanup.
• Documents installation, operations, privacy, credentials, recovery, upgrades, uninstall, purge, troubleshooting, and release evidence.

Docker incident

An earlier validation attempt started the system Docker daemon while restoring its missing bridge. Docker restart policies then restarted a pre-existing Compose project; SkillWire cleanup did not target or restart that project. Because PostgreSQL started and stopped, byte-for-byte non-mutation of its pre-existing persistent volume is not claimed.

The converged validation used a fully isolated daemon, Unix socket, data root, bridge, and address pool. Cleanup was bound to exact recorded ownership and left the system daemon inactive and socket-free.

Validation

Certified local runtime: Node 24.18.0 and pnpm 11.21.0.

• Focused T139–T160: 89 passed, 6 expected environment-gated skips.
• Feature 004 aggregate: 367 passed, 8 expected gated skips.
• Complete bounded offline suite: 865 passed, 9 expected gated skips.
• Network-denied required-CI group: 34 passed.
• Real disposable GNOME Keyring/Secret Service: 4 passed.
• Real disposable PostgreSQL backup/restore: 9 passed.
• PostgreSQL migrations and idempotent reruns: 12 passed.
• Feature 003 activation: 98 passed; activation adapter: 65 passed.
• Exactly ten first-party skills and ten advisory events verified.
• All 28 scenarios and FR-001–FR-092 mappings passed.
• Default, test-overlay, benchmark-overlay, and self-hosted Compose renderings passed.
• Formatting, ESLint, strict typecheck, build, Actionlint, package integrity, catalog/advisory integrity, secret scans, and git diff --check passed.

Explicitly pending T161

T161 remains unchecked because it requires post-merge external evidence:

• the immutable final source commit and tag;
• externally generated canonical manifests and production Cosign signatures;
• seven collision-free published release assets;
• all 12 Ubuntu/Debian × amd64/arm64 × rootful/rootless cells;
• quickstart execution against the published signed assets;
• moderated usability evidence;
• final immutable URLs, job IDs, hashes, cleanup results, and certification record.

Feature 004 is neither released nor fully certified by this pull request.