@lotics/cli 0.86.1 → 0.87.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.86.1",
+  "version": "0.87.0",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {

package/dist/package_commands.d.ts

@@ -1,221 +0,0 @@
-import { LoticsClient, type ExtractFinding } from "./client.js";
-import { type UpgradeResolutions } from "@lotics/shared/schemas/packages";
-/**
- * Read the local APP project's manifest (`package.json#lotics.app_id` +
- * `lotics.knowledge`) — what `lotics app pull` writes. `lotics app publish` /
- * `release` run from a pulled app project resolve the app id from it, and
- * `publish` forwards the package-managed knowledge declaration to the server
- * (agents reference docs by free text, so the author declares which the package
- * owns). Returns null when the dir has no package.json. `app_id` is null when the
- * manifest is a package/non-app project.
- */
-export declare function readLocalAppManifest(projectDir: string): {
-    app_id: string | null;
-    knowledge: Array<{
-        alias: string;
-        doc_id: string;
-    }>;
-} | null;
-/** Parse repeated `--rename old=new` flags into `{ from, to }[]` (first-publish alias fixes). */
-export declare function parseRenameFlags(renames: string[]): Array<{
-    from: string;
-    to: string;
-}>;
-/**
- * Render a package-extract report grouped by severity (errors, then warnings,
- * then info), one `  [<severity>] <area>: <message>` line each, and classify
- * whether any `error` finding is present. Shared by the release preview display.
- * Pure — the command prints `lines` to stderr and gates on `hasError`.
- */
-export declare function formatExtractReport(report: ExtractFinding[]): {
-    lines: string[];
-    hasError: boolean;
-};
-/**
- * Parse repeated `--resolve <key>=<value>` flags into the ONE namespaced
- * resolutions map every upgrade wire takes. Keys pass through verbatim — a
- * drifted binding entry (`<namespace>.<alias>`), a modified artifact
- * (`<kind>.<alias>`), a bundled/standalone knowledge doc (`knowledge.<alias>`),
- * or a live-role re-point (`roles.<alias>`). A value that is one of the
- * resolution verbs stays a verb; anything else is a `{ bind_to }` id. The
- * server validates value-kind against what each key resolves.
- */
-export declare function parseResolveFlags(resolve: string[]): UpgradeResolutions;
-/**
- * Health check: version pin vs. registry latest + binding drift. Exits
- * non-zero when drift is found so scripts can gate on it.
- */
-export declare function packageDoctor(client: LoticsClient, args: {
-    app_id?: string;
-}): Promise<void>;
-/**
- * Preview-then-apply an app-installation upgrade. Prints the additive plan +
- * informational removals + any bundled-knowledge changes; refuses (exit 1, with
- * the exact --resolve syntax) while any binding drift, modified core artifact, or
- * consent-requiring bundled-knowledge doc lacks a resolution.
- *
- * `--resolve` speaks ONE namespaced grammar, passed to the server verbatim: a
- * drifted binding entry (`<namespace>.<alias>`), a modified artifact
- * (`<kind>.<alias>`), a bundled knowledge doc (`knowledge.<alias>` —
- * apply|keep|archive|recreate|unbind), or a live-role re-point
- * (`roles.<alias>=<grp_id>`). `--bind-to` consents an added-knowledge-doc name
- * collision; `--apply-all` accepts the package's version for every
- * consent-requiring knowledge doc (overwriting local edits).
- */
-export declare function packageUpgrade(client: LoticsClient, args: {
-    app_id: string;
-    version?: number;
-    resolve: string[];
-    bindTo: string[];
-    applyAll: boolean;
-}): Promise<void>;
-/**
- * `lotics package show <package_id>` — registry metadata + version history
- * (trust badge, retirement, per-version channel/yank/changelog). The read
- * surface for "what is this package and what shipped when". Kind-agnostic — a
- * content package shows here the same way.
- */
-export declare function packageShow(client: LoticsClient, args: {
-    package_id: string;
-}): Promise<void>;
-/**
- * CLEAN BREAK for an explicit `pci_` argument on `upgrade` / `uninstall`: the
- * `pci_` resource id is retired from human sight — content installs are addressed
- * by their PACKAGE id. Prints a loud redirect, best-effort resolving the `pci_`
- * back to its package id (via list-content) so the exact command is spelled out.
- * The header prints synchronously first, so the redirect is observable even when
- * the best-effort resolution can't reach the registry.
- */
-export declare function redirectContentPciForm(client: LoticsClient, pci_id: string, verb: "upgrade" | "uninstall"): Promise<never>;
-/**
- * `lotics upgrade <apg_>` — the package-id upgrade path, kind-branched. `kind` is a
- * DERIVED display hint (`contractHasAppSurface`): `'content'` means no app surface.
- *   - a CONTENT package upgrades THIS workspace's standalone content installation
- *     (resolved from the package id — the anchor is unique per workspace, so the
- *     `pci_` never surfaces), through the same content review gate.
- *   - an APP-surface package FLEET-upgrades every installation across the org
- *     (unchanged) — the resolve/bind/apply-all flags don't apply to a fleet run.
- */
-export declare function packageUpgradeByPackageId(client: LoticsClient, args: {
-    package_id: string;
-    version?: number;
-    resolve: string[];
-    bindTo: string[];
-    applyAll: boolean;
-}): Promise<void>;
-/** Parse repeated `--bind-to alias=kdc_id` flags into an alias → doc-id consent map. */
-export declare function parseBindToFlags(bindTo: string[]): Record<string, string>;
-export declare function packageInstall(client: LoticsClient, args: {
-    package_id: string;
-    version?: number;
-    /** Content-kind only: adopt a same-named workspace doc on a knowledge collision. */
-    bind_to?: Record<string, string>;
-    /** App-kind only: per-knob config overrides applied over the contract defaults. */
-    config?: Record<string, string | number | boolean>;
-}): Promise<void>;
-/**
- * `lotics uninstall <app_id|package_id>` — ONE top-level command over both
- * installation kinds, dispatched by the id form (mirrors `lotics upgrade`):
- *   - a package id (`apg_`) → THIS workspace's STANDALONE CONTENT installation
- *     (content installs are addressed by package id, UNIQUE per workspace, so the
- *     `pci_` resource id never surfaces): deletes the row and (unless
- *     `--keep-content`) archives its package-bound docs AND templates, listing each
- *     archived id.
- *   - anything else (an `app_id`) → an APP installation: archives its workflow
- *     artifacts and — with `--archive-tables` — the scaffolded entity tables
- *     (provenance- + reference-gated server-side).
- * A flag used on the wrong path is a loud error, never silently ignored.
- */
-export declare function packageUninstall(client: LoticsClient, args: {
-    id: string;
-    keep_content: boolean;
-    archive_tables: boolean;
-}): Promise<void>;
-/**
- * `lotics package list-content` — list the selected workspace's STANDALONE
- * content installations (an app-bundled corpus rides its app's
- * `binding.knowledge` and shows on the Apps surface instead), each with its
- * registry status. The what-is-installed listing: each row leads with the PACKAGE
- * id — the address for `lotics upgrade <package_id>` / `lotics uninstall
- * <package_id>` (the `pci_` resource id stays hidden).
- */
-export declare function packageListContent(client: LoticsClient): Promise<void>;
-export declare function packageEject(client: LoticsClient, args: {
-    app_id: string;
-}): Promise<void>;
-/** `--config key=value` (install): inferred types, server-validated. */
-export declare function parseInstallConfigFlags(config: string[]): Record<string, string | number | boolean>;
-/**
- * `lotics package config <app_id>` — show the installation's effective config;
- * with `--set key=value` (repeatable) partial-merge edits, each value parsed by
- * the knob's current type. No `--set` prints the values.
- */
-export declare function packageConfig(client: LoticsClient, args: {
-    app_id: string;
-    sets: string[];
-}): Promise<void>;
-/**
- * `lotics app unpublish <app_id|package_id> [--undo]` — take a published package
- * off the shelf (or `--undo` restore it): new installs refuse it and it hides
- * from other orgs, while existing installations keep working and may still
- * upgrade. Given an app id (an installation of the package) it resolves the
- * package from the app; a package id targets it directly. Owner-org admin-only.
- */
-export declare function appUnpublish(client: LoticsClient, args: {
-    id: string;
-    undo: boolean;
-}): Promise<void>;
-/**
- * `lotics app publish [app_id|.] [--rename old=new ...] [-m <changelog>] [--yes]` —
- * FIRST-RELEASE a bespoke app as a package (docs/packages.md § Promotion). Nothing
- * starts as a package. Mirrors `app release`'s preview→apply UX: it first shows the
- * dry-run preview (GET, no writes) — the package name, the auto-minted RENAMABLE
- * aliases (the exact `--rename` keys, so v1's frozen aliases are inspected first,
- * never a blind publish), and the extract findings — then APPLIES only with
- * `--yes` (else exits 1 with the re-run hint). On apply the server extracts the
- * contract, creates the registry package, publishes v1 from the DEPLOYED source +
- * dist, and pins the origin as installation #1. `--rename old=new` fixes an
- * auto-minted alias before v1 freezes it; an `error` finding blocks the apply. An
- * already-linked app releases with `lotics app release` instead. The app id is the
- * positional (`.`/omitted → resolved from the local app project manifest).
- */
-export declare function appPublish(client: LoticsClient, args: {
-    app_id?: string;
-    renames: string[];
-    changelog?: string;
-    yes: boolean;
-    projectDir?: string;
-}): Promise<void>;
-/**
- * `lotics app release [app_id|.] -m <changelog> [--yes]` — snapshot an
- * adopted/installed origin app into its next registry version (docs/packages.md
- * § Promotion). The origin is the permanent working copy; a release binding-aware-
- * extracts it (stable aliases), repackages its DEPLOYED source + dist as the
- * bundle, publishes the next version, and re-pins the origin. Prints the preview
- * first (next version, new + changed aliases, the bundled-knowledge delta,
- * findings); applies only with `--yes`, else exits 1 so a review step can't be
- * skipped. An `error` finding blocks the apply.
- *
- * Run from the pulled app project, the manifest's `lotics.knowledge` (alias →
- * doc_id) is the bundle DECLARATION — it re-declares which docs the package owns
- * (add/drop/re-snapshot). Forwarded only when non-empty; empty (or a bare id from
- * elsewhere) sends nothing, so the current corpus is reconstructed from the pin
- * (never silently dropped).
- */
-export declare function appRelease(client: LoticsClient, args: {
-    app_id?: string;
-    changelog: string;
-    yes: boolean;
-    projectDir?: string;
-}): Promise<void>;
-/**
- * `lotics package yank <package_id> <version> [--undo]` — mark a published
- * version uninstallable (or restore it). New installs/upgrades/adopts refuse a
- * yanked version and "latest" skips it; installations already pinned keep
- * running. Owner-org admin-only.
- */
-export declare function packageYank(client: LoticsClient, args: {
-    package_id: string;
-    version: number;
-    undo: boolean;
-}): Promise<void>;