@synap-core/cli 1.11.0 → 1.12.2

package/dist/lib/exporter-coverage.js

@@ -0,0 +1,97 @@
+/**
+ * What `--from-workspace` / `--from-project` do NOT carry out of a live pod.
+ * ==========================================================================
+ *
+ * `synap market publish --from-workspace <id>` serialises a LIVE workspace
+ * through the pod's `workspaceToPackageDefinition`
+ * (synap-backend/packages/api/src/services/workspace-to-package-definition.ts)
+ * and posts the result. `--from-project` walks the same serialiser for every
+ * workspace a project `uses`, then composes a suite — so the same drop-list
+ * applies to each constituent. That serialiser is a **lossy projection**: it
+ * emits 21 of `packageDefinitionSchema`'s keys and has no projection at all
+ * for the ones below. A workspace carrying them exports WITHOUT them — no
+ * error, no signal.
+ *
+ * Loops stay here deliberately: there is no durable loop row to reverse-
+ * serialise (`createLoopFromDefinition` dissolves into playbooks + triggers).
+ *
+ * `TEMPLATE-DEV-GUIDE.md` used to assert, unqualified, that a
+ * `PackageDefinition` "round-trips". It does not, in this direction, and the
+ * consequence is the shape this repo keeps paying for: an author who built one
+ * of the things below publishes their workspace, ships a thinner-than-expected
+ * package, and gets a success message. Same class as `status ?? "installed"` —
+ * a claim of completeness nobody verified. (Cards authored in Card Studio USED
+ * to be one of these — `workspaceToPackageDefinition` now emits them into
+ * `cells[]`, so that loss is fixed; the list below is what remains.)
+ *
+ * ── WHY THIS LIST IS UNCONDITIONAL, NOT DETECTED ────────────────────────────
+ * The CLI never sees the workspace, only the projection's OUTPUT. "key absent
+ * because the workspace had none" and "key absent because the serialiser cannot
+ * emit it" are indistinguishable from here, and reporting a count would be
+ * inventing a fact. So this warns about the DOOR ("this door does not carry
+ * these"), which is true on every call, rather than about the payload.
+ *
+ * Keeping it honest across the repo boundary is
+ * `test/exporter-coverage-parity.test.ts`, which reads the exporter's own
+ * source and fails if a key listed here has gained an assignment (the list is
+ * stale and over-warns) or if a key it claims to emit has lost one.
+ */
+/**
+ * Keys with real user-authored content behind them that the serialiser drops.
+ *
+ * DELIBERATELY EXCLUDED, and why — these are absent from the export too, but
+ * warning about them would be noise rather than a loss:
+ *   • `icon` / `color` / `domain` / `workspaceType` — a live workspace has no
+ *     field to read them from (the exporter says so at L107-109). Honest
+ *     under-convergence, not a silent drop.
+ *   • `suggestedEntities` / `suggestedRelations` / `phases` / `composesFrom` —
+ *     authoring-time seed hints and composition metadata. A live workspace has
+ *     real entities, not "suggestions"; there is nothing to derive them from.
+ *   • `capability` / `sourcePackage` / `contentHash` — a non-workspace package
+ *     body and publish-time provenance. Not this door's business.
+ */
+export const EXPORTER_UNEMITTED_KEYS = [
+    { key: "commands", loses: "workspace commands" },
+    { key: "relationDefs", loses: "relation definitions" },
+    { key: "loops", loses: "loops" },
+    { key: "widgets", loses: "widget definitions" },
+    { key: "dependencies", loses: "declared package dependencies" },
+    { key: "defaultSources", loses: "declared workspace sources" },
+    { key: "sourceRoles", loses: "source roles" },
+];
+/**
+ * The keys the serialiser DOES emit. Not consumed at runtime — it is the other
+ * half of the parity tripwire's assertion, so that "emits" and "does not emit"
+ * are pinned by the same read of the same source and cannot disagree.
+ */
+export const EXPORTER_EMITTED_KEYS = [
+    "_meta",
+    "workspaceName",
+    "description",
+    "workspaceSubtype",
+    "workspaceVisibility",
+    "workspaceCapabilities",
+    "onboarding",
+    "profileEntityBentoTemplates",
+    "profiles",
+    "bentoLayout",
+    "bentoViewBlocks",
+    "bentoViewName",
+    "views",
+    "entityLinks",
+    "displayTemplates",
+    "automations",
+    "playbooks",
+    "capabilities",
+    "layoutConfig",
+    "actionPlacements",
+    "cells",
+];
+/**
+ * One human line per dropped key, for `--json`'s `warnings[]` and for the
+ * terminal hint list. Deliberately phrased as a property of the DOOR.
+ */
+export function exporterDropWarnings() {
+    return EXPORTER_UNEMITTED_KEYS.map((k) => `${k.key} — ${k.loses} (not exported: no projection)`);
+}
+//# sourceMappingURL=exporter-coverage.js.map

package/dist/lib/exporter-coverage.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"exporter-coverage.js","sourceRoot":"","sources":["../../src/lib/exporter-coverage.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AAUH;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAA4B;IAC9D,EAAE,GAAG,EAAE,UAAU,EAAE,KAAK,EAAE,oBAAoB,EAAE;IAChD,EAAE,GAAG,EAAE,cAAc,EAAE,KAAK,EAAE,sBAAsB,EAAE;IACtD,EAAE,GAAG,EAAE,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE;IAChC,EAAE,GAAG,EAAE,SAAS,EAAE,KAAK,EAAE,oBAAoB,EAAE;IAC/C,EAAE,GAAG,EAAE,cAAc,EAAE,KAAK,EAAE,+BAA+B,EAAE;IAC/D,EAAE,GAAG,EAAE,gBAAgB,EAAE,KAAK,EAAE,4BAA4B,EAAE;IAC9D,EAAE,GAAG,EAAE,aAAa,EAAE,KAAK,EAAE,cAAc,EAAE;CAC9C,CAAC;AAEF;;;;GAIG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAsB;IACtD,OAAO;IACP,eAAe;IACf,aAAa;IACb,kBAAkB;IAClB,qBAAqB;IACrB,uBAAuB;IACvB,YAAY;IACZ,6BAA6B;IAC7B,UAAU;IACV,aAAa;IACb,iBAAiB;IACjB,eAAe;IACf,OAAO;IACP,aAAa;IACb,kBAAkB;IAClB,aAAa;IACb,WAAW;IACX,cAAc;IACd,cAAc;IACd,kBAAkB;IAClB,OAAO;CACR,CAAC;AAEF;;;GAGG;AACH,MAAM,UAAU,oBAAoB;IAClC,OAAO,uBAAuB,CAAC,GAAG,CAChC,CAAC,CAAC,EAAE,EAAE,CAAC,GAAG,CAAC,CAAC,GAAG,MAAM,CAAC,CAAC,KAAK,gCAAgC,CAC7D,CAAC;AACJ,CAAC"}

package/dist/lib/hub-client.d.ts

@@ -1,4 +1,4 @@
-import { HubRestClient } from "@synap/hub-rest-client";
+import { HubRestClient } from "@synap-core/hub-rest-client";
 /**
  * A failed Hub call, carrying the structured facts callers need to branch on.
  *
@@ -89,12 +89,33 @@ export declare function resolveHubConfig(opts?: {
     podUrl?: string;
     apiKey?: string;
 }): Promise<HubConfig>;
-/** Read the active session ID for this terminal from CWD or env var. */
-export declare function readActiveSessionId(): string | undefined;
-/** Attach a session to this terminal — writes .synap-session in CWD. */
-export declare function writeActiveSessionId(sessionId: string): void;
-/** Detach the active session from this terminal — removes .synap-session. */
-export declare function clearActiveSessionId(): void;
+/**
+ * The focus session every hub call should be tagged with.
+ *
+ * Both lens rungs are pod-qualified: a focus-session id is POD-LOCAL, so a lens
+ * stamped with another pod must not leak into `X-Session-Id`. (Lenses written
+ * before the stamp existed have no `podUrl` and match leniently — see
+ * `lensMatchesPod`.)
+ */
+export declare function resolveActiveSessionId(podUrl?: string): string | undefined;
+/** Where an attach landed — reported so the user knows what owns their scope. */
+export type SessionAttachTarget = "session-lens" | "directory-lens";
+/**
+ * Attach a focus session to this terminal.
+ *
+ * Inside Claude Code the SESSION lens wins — per-tab isolation is the point
+ * (tab A on session X, tab B on session Y, same directory). Outside it there is
+ * no `CLAUDE_CODE_SESSION_ID` to key on, so the DIRECTORY lens is the
+ * legitimate fallback: the same per-working-tree scope the retired
+ * `.synap-session` had. `attach` therefore never silently no-ops.
+ */
+export declare function attachActiveSessionId(sessionId: string): SessionAttachTarget;
+/**
+ * Detach — clear the focus session from BOTH lens rungs, and return whatever
+ * was active. Clearing only the top rung would "detach" into the lower one,
+ * which reads as the command failing.
+ */
+export declare function detachActiveSessionId(podUrl?: string): string | undefined;
 export declare function hubGet(path: string, params: Record<string, string | number | undefined>, cfg: HubConfig): Promise<unknown>;
 export declare function hubPost(path: string, body: unknown, cfg: HubConfig, timeoutMs?: number): Promise<unknown>;
 /**
@@ -118,4 +139,4 @@ export declare function hubDelete(path: string, cfg: HubConfig): Promise<unknown
  * Hub Protocol coverage with a shared client contract — eliminating drift.
  */
 export declare function makeHubClient(cfg: HubConfig): HubRestClient;
-export { HubRestClient } from "@synap/hub-rest-client";
+export { HubRestClient } from "@synap-core/hub-rest-client";