@vibesdotdev/plugins 0.0.0-stage → 1.0.0-rc.0

package/dist/cli/update.cli-command.impl.consumer.d.ts

@@ -0,0 +1,178 @@
+import type { CommandExecutionStartInfo } from '@vibesdotdev/cli/schemas/surface';
+import type { CLICommandAssetDescriptor } from '@vibesdotdev/cli/schemas/types';
+import { type RuntimeRef } from '@vibesdotdev/kernel';
+import { PluginsCLICommand, type PluginsCLIContext } from './context.ts';
+import type { ScopeReport, UpdateFailure } from './schemas/update.ts';
+export type { ScopeReport, UpdateFailure } from './schemas/update.ts';
+/**
+ * The published release base: the `assets` origin the production
+ * `config/environment` declares, under {@link RELEASE_DOWNLOADS_PATH}.
+ * Releases are published only to production, whatever environment this host
+ * calls (the desktop release reads its origin by the same rule), so this
+ * reads the production declaration rather than the active one; `--mirror`
+ * retargets. A runtime that declares no production `assets` origin refuses
+ * `release-origin-undeclared`.
+ */
+export declare function publishedReleaseBase(runtime: Pick<RuntimeRef, 'query' | 'hasKind'>): Promise<string>;
+/** `latest.json` under a release base (the declared `--mirror`, else the published base), trailing slashes trimmed. */
+export declare function latestManifestUrl(base: string): string;
+/**
+ * Which scope reports make `vibes update` FAIL.
+ *
+ * A command that reports `NOT VERIFIED` and exits 0 is the absence-looks-like-
+ * success defect: the shipped draft did exactly that, so a scope whose
+ * verification boot could not compose, and a `$VIBES_HOME` the command refused
+ * to touch at all, both read as "updated" to CI, to a script, and to the WU-07
+ * harness. Pure and exported so the rule is testable without booting a child.
+ *
+ * Not a failure: a benign skip (`no workspace plugin list to update`, a home
+ * delegated to a host workspace) — nothing was asked for and nothing broke.
+ *
+ * `--dry-run` suppresses only the VERIFICATION half: nothing was installed, so
+ * nothing was booted, so an unverified scope is not a defect. A REFUSAL is not
+ * suppressed — a foreign or fossil `$VIBES_HOME`, or a link glob whose parent
+ * is gone, is a fact about the scope as it stands, not about the install that
+ * did not run, and `vibes update --dry-run` in CI has to be able to see it.
+ */
+/** A surface omission is verified because the kernel refused to import the declared export. */
+export declare function isUnverifiedPluginRow(row: {
+    plugin: string;
+    status: string;
+    reason?: string;
+}): boolean;
+export declare function collectUpdateFailures(reports: ReadonlyArray<Pick<ScopeReport, 'scope' | 'root' | 'verified' | 'verifyDetail' | 'skipped' | 'failed'>>, options: {
+    dryRun: boolean;
+}): UpdateFailure[];
+/**
+ * `vibes update` — seed, install, verify, roll (plan §5).
+ *
+ * ### Ordering: self FIRST, then the graph, then ONE roll
+ *
+ * `--self` runs before any scope work and the census roll runs exactly once at
+ * the end. Rolling before the binary is replaced re-stales every body just
+ * rolled — the executable freshness nerve fires on the new inode — so the
+ * draft's "roll, then swap" order produced two rolls and a `pm status` Build
+ * column reading STALE immediately after a successful update.
+ *
+ * ### What triggers the roll: THREE reasons, one nerve each
+ *
+ * 1. the module graph moved (a scope's `bun.lock` digest changed);
+ * 2. `--self` installed a new release over this executable;
+ * 3. a body in the census is **already** executing a replaced file.
+ *
+ * The third one is not redundant. A local `bun run build:install` swaps
+ * `~/.local/bin/vibes` by atomic rename: no lock moves and `--self` downloaded
+ * nothing, so on reasons 1–2 alone `vibes update` reported "nothing changed, so
+ * no body was rolled" in the same minute `vibes pm status` reported "⚠ PM
+ * daemon (pid …) runs a replaced vibes executable". Two surfaces, one fact,
+ * and the surface that could FIX it held the weaker predicate. The census now
+ * consumes the same executable nerve `pm status` and PM's
+ * `ExecutableFreshnessReconciler` consume (`markReplacedExecutables`), so a
+ * body running a replaced executable is rolled and the receipt says why.
+ *
+ * ### Per scope
+ *
+ * preflight (schema, glob parents, foreign-owner refusal, `workspace:*`
+ * declarations) → `bun install` → a SCOPED `bun update <enabled registry
+ * packages> @vibesdotdev/plugins`, never a fleet-wide `bun update` at a
+ * 232-member root → verification by spawning the SHIPPING path
+ * (`vibes plugins list --json --scope <kind>` with `VIBES_HOST_ROOT` bound to
+ * the scope root), where every row must read `loaded`.
+ *
+ * The verification deliberately re-enters the real executable rather than
+ * inspecting the manifest we just wrote. A manifest is a claim; a boot is a
+ * measurement, and it is the only thing that proves the scope this command
+ * just changed can still compose.
+ *
+ * ### Exit code
+ *
+ * A scope that did not verify, and a scope the command REFUSED to touch, both
+ * make `vibes update` exit non-zero — after the full report (including the
+ * `--json` envelope) has been printed. The draft printed `NOT VERIFIED` and
+ * exited 0, so a refused `$VIBES_HOME` and a scope that cannot compose read as
+ * success to CI, to a script and to the WU-07 harness. Benign skips (a
+ * workspace with no plugin list, a home delegated to a host workspace) are not
+ * failures. `--dry-run` never fails a VERIFICATION — it installs nothing, so
+ * it boots nothing — but a REFUSED scope still exits non-zero under it: the
+ * refusal describes the scope as it stands, not the install that did not run.
+ * The rule lives in `collectUpdateFailures`.
+ *
+ * ### Foreign / fossil manifests
+ *
+ * A `$VIBES_HOME/package.json` whose name is not `vibes-global` is somebody
+ * else's file (or the 24-April fossil). We refuse it by name and print
+ * `vibes update --repair --global`; `--repair` then backs it up as
+ * `*.fossil-<stamp>` and prints kept|dropped. Nothing is merged silently and
+ * nothing is deleted without a backup line.
+ */
+export default class UpdateCLICommand extends PluginsCLICommand {
+    constructor(descriptor: CLICommandAssetDescriptor, context: PluginsCLIContext);
+    execute(args: CommandExecutionStartInfo['args'], options: CommandExecutionStartInfo['options']): Promise<void>;
+    /** Replace the running executable from the declared `--mirror`, else the published release base. */
+    private updateSelf;
+    /** Version of the running host: the host's own version fact, the one `--version` reports. */
+    private hostVersion;
+    private updateScope;
+    /** Seed an absent home, repair a fossil one, or refuse a foreign one by name. */
+    private prepareGlobal;
+    /**
+     * The specifiers a scope has ENABLED, read through the SAME resolution the
+     * bootstrap loader composes from.
+     *
+     * The workspace half used to call `resolveWorkspaceListTarget`, the WRITER's
+     * target resolver, which reports an empty list for a `vibes.config.ts`
+     * because it refuses to rewrite a module. `update --workspace` therefore saw
+     * nothing to update for plan §3's PRIMARY workspace surface — the file
+     * requirement #1 tells users to write — and skipped the scope with
+     * `no workspace plugin list to update`. It now reads Runtime's
+     * `readWorkspacePluginSurfaces` (`@vibesdotdev/kernel/bootstrap`, the
+     * owner of workspace composition formats) over the handed runtime's
+     * selected `runtime/loader`, the same reader the workspace composition and
+     * `plugins list` read: `vibes.config.{ts,js,json}#plugins` primary,
+     * `package.json#vibes.plugins` fallback.
+     *
+     * A SHADOWED fallback list is deliberately not included. `bun update` here
+     * targets the packages this scope composes; a specifier the effective surface
+     * overrides is not composed, and installing it would make `vibes update`
+     * disagree with the boot it uses to verify itself.
+     */
+    private selectionsFor;
+    /**
+     * The scope's install inputs. An unreadable or malformed manifest is the
+     * typed `plugin-scope-manifest-unreadable` refusal, carried into the report
+     * as a refused scope (SPEC: a refused scope exits non-zero) and kept whole
+     * as the command's cause; every other failure propagates.
+     */
+    private readDeclarations;
+    /**
+     * On-disk rules that decide whether bun may run at all.
+     *
+     * `benign` separates "there is nothing here to do" (a delegated home owns
+     * no packages — the update belongs to the host workspace) from "the request
+     * could not be carried out" (a link glob whose parent directory is gone).
+     * Only the second kind fails the command; conflating them would make
+     * `vibes update --global` on a delegated machine exit non-zero forever.
+     */
+    private preflight;
+    /**
+     * Boot the SHIPPING path against the scope root and require every row to be
+     * composed. A manifest that parses is not a scope that composes.
+     *
+     * Two details that are easy to get wrong and were measured, not guessed:
+     *
+     * - The child's cwd is the scope root only for the WORKSPACE scope. Setting
+     *   it to `$VIBES_HOME` for the global scope made bootstrap read
+     *   `$VIBES_HOME/package.json#vibes.plugins` as the *workspace* fallback
+     *   list (there is no config there, so the cwd IS the workspace root), so
+     *   the workspace batch claimed every global specifier and the global batch
+     *   reported `deduped` for all of them.
+     * - `deduped` is therefore accepted alongside `loaded`: it means the very
+     *   same specifier was already selected by an earlier scope in that process,
+     *   so the plugin IS composed. `missing` and `failed` are the real failures,
+     *   and `shadowed` is reported as a warning detail because another plugin
+     *   owns the id.
+     */
+    private verifyScope;
+    private emit;
+}
+//# sourceMappingURL=update.cli-command.impl.consumer.d.ts.map

package/dist/cli/update.cli-command.impl.consumer.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"update.cli-command.impl.consumer.d.ts","sourceRoot":"","sources":["../../src/cli/update.cli-command.impl.consumer.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,kCAAkC,CAAC;AAClF,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,gCAAgC,CAAC;AAKhF,OAAO,EAWN,KAAK,UAAU,EACf,MAAM,qBAAqB,CAAC;AAM7B,OAAO,EAAE,iBAAiB,EAAE,KAAK,iBAAiB,EAAE,MAAM,cAAc,CAAC;AAoBzE,OAAO,KAAK,EAGX,WAAW,EAGX,aAAa,EAEb,MAAM,qBAAqB,CAAC;AAE7B,YAAY,EAAE,WAAW,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AA0BtE;;;;;;;;GAQG;AACH,wBAAsB,oBAAoB,CAAC,OAAO,EAAE,IAAI,CAAC,UAAU,EAAE,OAAO,GAAG,SAAS,CAAC,GAAG,OAAO,CAAC,MAAM,CAAC,CAU1G;AAED,uHAAuH;AACvH,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAEtD;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,+FAA+F;AAC/F,wBAAgB,qBAAqB,CAAC,GAAG,EAAE;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC;IAAC,MAAM,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAIvG;AAED,wBAAgB,qBAAqB,CACpC,OAAO,EAAE,aAAa,CACrB,IAAI,CAAC,WAAW,EAAE,OAAO,GAAG,MAAM,GAAG,UAAU,GAAG,cAAc,GAAG,SAAS,GAAG,QAAQ,CAAC,CACxF,EACD,OAAO,EAAE;IAAE,MAAM,EAAE,OAAO,CAAA;CAAE,GAC1B,aAAa,EAAE,CA0BjB;AA6CD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6DG;AACH,MAAM,CAAC,OAAO,OAAO,gBAAiB,SAAQ,iBAAiB;gBAClD,UAAU,EAAE,yBAAyB,EAAE,OAAO,EAAE,iBAAiB;IAIvE,OAAO,CAAC,IAAI,EAAE,yBAAyB,CAAC,MAAM,CAAC,EAAE,OAAO,EAAE,yBAAyB,CAAC,SAAS,CAAC,GAAG,OAAO,CAAC,IAAI,CAAC;IAwEpH,oGAAoG;YACtF,UAAU;IAuCxB,6FAA6F;IAC7F,OAAO,CAAC,WAAW;YAML,WAAW;IA4HzB,iFAAiF;YACnE,aAAa;IAuC3B;;;;;;;;;;;;;;;;;;;;OAoBG;YACW,aAAa;IAuB3B;;;;;OAKG;YACW,gBAAgB;IAU9B;;;;;;;;OAQG;IACH,OAAO,CAAC,SAAS;IAsBjB;;;;;;;;;;;;;;;;;OAiBG;YACW,WAAW;IAsDzB,OAAO,CAAC,IAAI;CAyEZ"}