@camstack/system 1.2.29 → 1.2.31

package/dist/kernel/addon-installer.d.ts

@@ -22,6 +22,25 @@ import { AddonManifest } from './addon-manifest.js';
  * `addonsDir/<pkg>` → `packages/<pkg>`.
  */
 export type InstallSource = 'npm' | 'local' | 'symlink';
+/** The one bootstrap package the server closure carries itself. */
+export declare const CLOSURE_PROVIDED_PACKAGE = "@camstack/system";
+/**
+ * Should the bootstrap SKIP seeding `packageName` into /data/addons?
+ *
+ * True only for the package the closure provides, and only when it actually
+ * resolves. Both halves are load-bearing:
+ *
+ *  - seeding a copy the closure already provides creates one that WINS over
+ *    the closure and is never refreshed (bootstrap is seed-only, and
+ *    `camstack deploy` of a framework package is rejected on an image hub), so
+ *    the node runs first-boot builtins forever while reporting the new
+ *    version;
+ *  - skipping it when it does NOT resolve is how a fresh deployment was once
+ *    made unbootable ("No addon provides required infrastructure capability
+ *    storage-provider"). That is why the guard is resolvability rather than a
+ *    blanket removal from the bootstrap list.
+ */
+export declare function shouldSkipClosureProvidedSeed(packageName: string, isResolvable: boolean): boolean;
 export interface AddonInstallerConfig {
     /** Directory where addons are stored (e.g., {dataDir}/addons) */
     readonly addonsDir: string;
@@ -31,6 +50,13 @@ export interface AddonInstallerConfig {
     readonly workspacePackagesDir?: string;
     /** Install source mode. Default: auto-detect */
     readonly installSource?: InstallSource;
+    /**
+     * Override for "does the running closure already provide this package?".
+     * Production leaves it unset (real `require.resolve`); a spec sets it to
+     * reach the branch that still seeds `@camstack/system`, which is otherwise
+     * unreachable in a process where that package always resolves.
+     */
+    readonly isPackageResolvable?: (packageName: string) => boolean;
 }
 export type { InstalledPackage };
 /** Outcome of {@link AddonInstaller.sweepBackups}. Absolute paths. */
@@ -46,6 +72,7 @@ export declare class AddonInstaller {
     readonly workspaceDir: string | undefined;
     readonly installSource: InstallSource;
     private readonly logger;
+    private readonly isPackageResolvable?;
     /**
      * Central manifest of installed addons. Tracks version + source +
      * timestamps + last-backup pointer per package, written atomically
@@ -71,6 +98,17 @@ export declare class AddonInstaller {
      * hardcoded lists — see design spec
      * docs/superpowers/specs/2026-05-20-docker-install-from-npm-design.md.
      */
+    /**
+     * Is `packageName` reachable through normal resolution — i.e. does the
+     * running closure already provide it?
+     *
+     * Overridable via `AddonInstallerConfig.isPackageResolvable` so a spec can
+     * exercise BOTH sides. That matters more than it looks: the branch that
+     * still seeds is the one protecting a fresh deployment from an unbootable
+     * node, and it is unreachable in a test process where `@camstack/system`
+     * always resolves.
+     */
+    private isResolvableFromClosure;
     private static deriveBootstrapList;
     /**
      * Bootstrap packages installed on first boot — derived from the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.2.29",
+  "version": "1.2.31",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",