Persist authority-pack artifacts and unify activation and publication policy

[JSv4]

Authority packs already have catalog, fingerprinted preflight, installation services, and management commands. However, discovery depends on local directories and process-loaded registries. Installed database content can survive while pack definitions disappear or differ across processes. Publication policy also differs: the API requires approved charters, while the path-based management adapter does not enforce the same condition.

Implementation

• Persist trusted, versioned pack artifacts and active-version metadata through existing application storage. Make database content and the active artifact version reconcilable after restart or interrupted installation.
• Extend the existing catalog/preflight/install services and command adapters rather than creating a parallel loader. Retain digest validation, archive safeguards, and trusted-source restrictions.
• Add application-managed activation/refresh so web and worker processes observe the same active version without manual file copying or process-specific cache manipulation. Expose activation status, version, and errors; retain the prior usable version after failure.
• Preserve the distinction between declarative pack data and executable provider modules. Do not turn artifact upload into arbitrary Python loading; retain existing provider trust controls.
• Apply one explicit publication policy in API and management-command paths. Preserve charter review status. If privileged publication of unreviewed material is supported, represent it as a separate, authorized, audited override; never silently label the material approved.

Acceptance criteria

• Install/restart and multi-process tests show consistent catalog, taxonomy, and provider discovery for the active version.
• Concurrent installs, invalid archives, changed preflight fingerprints, and interrupted activation cannot leave an apparently successful mixed-version installation.
• API and command tests enforce the same publication decision, authorization, and review-status preservation.
• Existing filesystem packs have a documented compatibility/migration path.

Code pointers

pack service; installer command; registry discovery; storage/discovery settings; provider trust tests.