@synap-core/cli 1.11.0 → 1.13.0

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.
  *
@@ -60,23 +60,44 @@ export declare class HubNetworkError extends Error {
     });
 }
 /**
- * Append a one-line "need help?" footer with a clickable Discord invite. Prints
- * to stderr (same stream as the error it follows, so `2>/dev/null` hides both)
- * and only once per process. The invite is an OSC-8 hyperlink on an interactive
- * terminal, a plain URL when the stream is redirected/piped.
+ * Where to send users who hit a wall. The support door is the ONE customer
+ * support entry point shared by every Synap surface (`from=cli` tells support
+ * which surface the person came from); Discord stays as the community option.
  */
-export declare function discordHelpLine(): void;
+export declare const SUPPORT_URL = "https://synap.live/support?from=cli";
+/**
+ * Append a one-line "need help?" footer naming the support door (open a ticket)
+ * and the Discord invite. Prints to stderr (same stream as the error it
+ * follows, so `2>/dev/null` hides both) and only once per process. Each URL is
+ * an OSC-8 hyperlink on an interactive terminal, a plain URL when the stream is
+ * redirected/piped.
+ */
+export declare function helpFooterLine(): void;
 /**
  * Print a failed Hub call: its humanized message plus a hint for the classes
  * where the cause is not obvious from the message alone. Lives here rather than
  * in utils/logger so the logger stays domain-agnostic and the taxonomy and its
- * presentation sit in one file. Always closes with the one-time Discord footer.
+ * presentation sit in one file. Always closes with the one-time help footer.
  */
 export declare function renderHubError(err: unknown): void;
 export interface HubConfig {
     podUrl: string;
     apiKey: string;
+    /**
+     * The ACTING identity sent to the pod (body/query/path `userId`). Only an
+     * explicit caller id (SYNAP_USER_ID) or the sentinel "cli"; read it through
+     * `resolveUserId`, which asks the pod (/users/me) for "cli". Never seed it
+     * with a recorded agent id: the pod acts an agent key as the human it is
+     * linked to and 403s the agent's own id ("userId does not match the
+     * authenticated identity", 2026-10-23). The agent's id is `agentUserId`.
+     */
     userId: string;
+    /**
+     * The agent principal recorded with this key, when one was — WHO the key
+     * is, not who the pod acts as. For recognising the agent's own posts
+     * (`resolveAgentUserId`), never sent as the acting user.
+     */
+    agentUserId?: string;
     /** Active workspace — from `synap use`, pod default, or env var. Undefined if none configured. */
     workspaceId?: string;
     /** Active project — from `synap project use`, pod default, or env var. Peer of workspaceId; independent. */
@@ -89,13 +110,34 @@ 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;
-export declare function hubGet(path: string, params: Record<string, string | number | undefined>, cfg: HubConfig): Promise<unknown>;
+/**
+ * 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, timeoutMs?: number): Promise<unknown>;
 export declare function hubPost(path: string, body: unknown, cfg: HubConfig, timeoutMs?: number): Promise<unknown>;
 /**
  * Multipart POST for Hub doors that accept file uploads (e.g. source-file).
@@ -118,4 +160,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";