@agentvault/muse-bridge 0.1.1 → 0.1.3

package/README.md

@@ -9,9 +9,14 @@ direct messages and rooms.
 
 ## Prerequisite
 
-Install Muse Code and run `muse login` (or set `META_API_KEY`). The bridge
-copies host `~/.config/muse/auth.json` into its fence once, at first run, and
-never overwrites it.
+Install Muse Code and set `META_API_KEY` (it always wins). `muse login` is
+fine on the host, but Muse 1.0.1 stores that login in the macOS Keychain.
+The bridge **does not** copy a keychain-only host `auth.json` into the fence
+— that makes the child `SecItemAdd` and can pop “Keychain Not Found.”
+
+A file `providers.meta.api_key` is harvested once into
+`<dataDir>/meta-api-key.json` (mode `0600`) and forwarded as `META_API_KEY`.
+It is never written to launchd/systemd.
 
 ## First enroll
 

package/dist/fence-auth.d.ts

@@ -1,10 +1,27 @@
-export type SeedResult = "seeded" | "already-present" | "no-host-credential";
+export type SeedResult = "seeded" | "already-present" | "no-host-credential" | "host-credential-keychain-only";
+/** File-backed Meta key in the fence. Undefined for missing, garbage, or keychain-only. */
+export declare function readFenceMetaApiKey(fenceHome: string): string | undefined;
+export type HarvestResult = "harvested" | "already-sidecar" | "none";
+/** Bridge-private key file. Not under fence HOME, so Muse 1.0.1 will not migrate it. */
+export declare function sidecarMetaApiKeyPath(dataDir: string): string;
+export declare function readSidecarMetaApiKey(dataDir: string): string | undefined;
+/**
+ * Muse 1.0.1 SecItemAdd-migrates a fence file api_key even when META_API_KEY is
+ * set (live: file+env hung; env-only rejected the key in 0.3s with no dialog).
+ * Keep the key in dataDir and take it out of the child's XDG auth.json.
+ */
+export declare function harvestFenceApiKeyToSidecar(opts: {
+    dataDir: string;
+    fenceHome: string;
+    log?: (m: string) => void;
+}): HarvestResult;
 /**
  * Copy the host's Muse credential into the agent's fence, ONCE.
  *
  * Copies auth.json alone — never host settings.json, skills, or trust.json.
  * Never overwrite an existing fence credential (a fenced child refreshes its
- * own token in place). Never log file contents.
+ * own token in place), except a keychain-only pointer: that is not a usable
+ * file key and would make the child SecItemAdd. Never log file contents.
  */
 export declare function seedFenceCredential(opts: {
     fenceHome: string;