@agentvault/claude-bridge 0.7.16 → 0.8.0

package/dist/bridge.d.ts

@@ -167,6 +167,15 @@ export declare function attachLifecycle(channel: LifecycleChannel, opts?: {
     onTerminal?: (reason: string, o: {
         restart: boolean;
     }) => void;
+    /** #913 item 2 — remove this agent's supervised service when its device is
+     *  gone for good. Injected for tests; defaults to the real remover, because
+     *  an opt-in default is a feature nobody gets.
+     *
+     *  Every terminal reason is offered to it and IT decides. Filtering here as
+     *  well would put the same rule in two files, and the two would eventually
+     *  disagree — which is how `session_replaced` (device still alive) would end
+     *  up removing a healthy install. */
+    selfUninstall?: (reason: string, env: NodeJS.ProcessEnv) => boolean;
 }): void;
 /**
  * Slice 2 Plan C (Task 11) — one drain of the local-approval marker dir.

package/dist/config.d.ts

@@ -1,9 +1,51 @@
+/**
+ * Package-manager scratch caches. `service/subcommand.ts` bakes `process.argv[1]`
+ * into the launcher script, so a service installed from one of these points at a
+ * directory the package manager later prunes — it works today and dies weeks later
+ * with nothing naming the cause.
+ *
+ * A DENYLIST, not proof of durability: it covers npm's npx cache, pnpm/yarn `dlx`,
+ * `bunx`, and anything under the OS temp dir. Other ephemeral runners are knowingly
+ * unhandled.
+ *
+ * Ported from the grok fork (#909, #921). This bridge had no such guard at all,
+ * while running the same bake-argv[1]-into-the-launcher install.
+ */
+export declare function isEphemeralEntrypoint(entrypoint: string): boolean;
+/** Throw unless `entrypoint` is durable enough to bake into a supervised service. */
+export declare function assertInstallableEntrypoint(entrypoint: string): void;
+/**
+ * #913 item 3 — the device id inside this data dir's credentials, or null.
+ *
+ * Lives HERE, beside CRED_FILES and BACKUP_FILE, because this module already
+ * owns the knowledge of which files hold credentials. `doctor` reading those
+ * names itself would make a second copy of the list, and the copy that is not
+ * next to the constant is the one that goes stale.
+ *
+ * Checks the same files in the same order as hasPersistedCreds, INCLUDING the
+ * .bak: a device_revoked wipe deletes agentvault.json and leaves the backup, so
+ * the .bak is exactly where the id lives for the machine most likely to be
+ * running doctor.
+ *
+ * Returns null rather than throwing on missing/unreadable/malformed input — a
+ * doctor that dies on one bad file reports nothing about the others.
+ */
+export declare function readPersistedDeviceId(dataDir: string): string | null;
 export declare function hasPersistedCreds(dataDir: string): boolean;
 export declare function slugify(name: string): string;
 export type DataDirSource = "explicit" | "per-agent" | "legacy";
+/** Where the agent name came from.
+ *
+ *  #927's test for a safe default is: can a reader of the output tell the input
+ *  was MISSING? A bare `agentName` cannot answer that — "Claude" reads the same
+ *  whether the customer typed it or the bridge chose it. This field is what
+ *  makes the two distinguishable, so callers can SAY which one happened. */
+export type AgentNameSource = "supplied" | "defaulted";
 export declare function resolveDataDir(env: NodeJS.ProcessEnv): {
     dataDir: string;
     source: DataDirSource;
+    agentName: string;
+    agentNameSource: AgentNameSource;
 };
 export interface BridgeConfig {
     inviteToken: string;
@@ -11,6 +53,8 @@ export interface BridgeConfig {
     dataDirSource: DataDirSource;
     apiUrl: string;
     agentName: string;
+    /** Whether AV_AGENT_NAME was given, or the package default was used (#927). */
+    agentNameSource: AgentNameSource;
     roomFilter?: string;
     model?: string;
     systemPrompt?: string;