@desplega.ai/agent-swarm 1.164.1 → 1.166.0

package/templates/skills/linear-interaction/config.json

@@ -5,7 +5,7 @@
   "slug": "linear-interaction",
   "title": "Linear Interaction",
   "description": "Create issues, update status, and post comments in Linear with explicit project placeholders.",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "category": "skills",
   "placeholders": [
     "LINEAR_PROJECT_ID"

package/templates/skills/linear-interaction/content.md

@@ -1,16 +1,5 @@
 # Linear Interaction (Outbound Push)
 
-**Before attempting any API call below, check if the token has been renewed:**
-```bash
-# Use db-query MCP tool
-db-query: SELECT accessToken, expiresAt FROM oauth_tokens WHERE provider = 'linear'
-```
-If `expiresAt` is in the past, do NOT attempt the API calls — just report the needed update in your task output.
-
-To re-authorize, use your swarm API base URL with `/api/trackers/linear/authorize` (potentially needing to remove the app and re-auth). Only mention this if you can confirm the token is expired or not present.
-
----
-
 ## Critical Context
 
 The swarm's Linear integration is **inbound-only**: Linear → swarm. This means:
@@ -26,34 +15,43 @@ The available MCP tracker tools (`tracker-link-task`, `tracker-link-epic`, `trac
 - **Standard PR workflow:** Transition to **In Review** on PR open, **Done** after merge. If the ticket is still "In Progress" 30 min after the PR merges, you're late.
 - **Blocked:** If a ticket is stuck on a dependency, add a comment linking the blocker — don't leave it silent.
 
-## Authentication
+## Authentication: script credential binding
 
-The OAuth token is stored in the swarm database (`oauth_tokens` table, provider = 'linear').
+Use the `swarm-scripts` skill and `script-run` (`args` first, `ctx` second) for every authenticated request. The API server resolves an OAuth authorization, refreshes it when needed, and substitutes `[REDACTED:LINEAR_OAUTH_ACCESS_TOKEN]` in the request header only for the binding's allowed hosts. Never read credential tables, request a raw token from Lead, or copy a token into source, arguments, environment variables, logs, or task output.
 
-**To get the token:**
-```bash
-# Use db-query MCP tool
-db-query: SELECT accessToken FROM oauth_tokens WHERE provider = 'linear'
-```
+Try the conventional binding key `LINEAR_OAUTH_ACCESS_TOKEN` first, using `Authorization: Bearer [REDACTED:LINEAR_OAUTH_ACCESS_TOKEN]` for `api.linear.app`. Do not ask Lead before the first try. `credential-bindings` is lead-only; workers cannot list bindings.
+
+On HTTP 401 with the conventional key, report the missing binding or authorization to Lead as a blocker. The fetch wrapper in `src/scripts-runtime/credential-broker/fetch-patch.ts` drops any header with an unresolved `[REDACTED:` placeholder, so a missing binding sends an unauthenticated request that yields 401, never a credential leak.
+
+Lead uses `credential-bindings` action `list` to check the binding. If missing, Lead registers/authorizes the provider and creates a binding visible to the agent with `configKey: "LINEAR_OAUTH_ACCESS_TOKEN"`, `authKind: "oauth"`, `oauthAuthorizationId`, `allowedHosts: ["api.linear.app"]`, and `headerTemplate: "Authorization: Bearer [REDACTED:LINEAR_OAUTH_ACCESS_TOKEN]"`.
 
-> **Worker agents (non-lead):** If you are a non-lead agent and cannot access the Linear token via `db-query`, message the lead agent in the task and request the token. Do not complete the task without updating Linear.
+An expiring authorization is refreshed server-side; a refresh failure, revoked/missing authorization, or persistent 401 needs Lead/user re-authorization through `credential-bindings` action `oauth-authorize-url`. Do not query expiry/token columns or loop on 401s.
 
-**Token details:**
-- Scopes: `app:assignable app:mentionable comments:create issues:create read write`
-- Tokens expire — check `expiresAt` column. If expired, the user needs to re-authorize via the OAuth flow.
-- API endpoint: `https://api.linear.app/graphql`
+Supported implementation: `src/be/script-credential-broker.ts` loads scoped relational bindings and calls `resolveOAuthBindingToken` from `src/be/oauth-credential-bindings.ts`. The scripts runtime substitutes placeholders at egress for allowed hosts.
 
-## Making API Calls
+## Making API calls
 
-All Linear API calls use GraphQL via POST to `https://api.linear.app/graphql`.
+Allowed host: `api.linear.app`. Send GraphQL queries and mutations with `script-run`; the common operations below supply the `query` and optional `variables`:
 
-```bash
-curl -s -X POST https://api.linear.app/graphql \
-  -H "Content-Type: application/json" \
-  -H "Authorization: Bearer <ACCESS_TOKEN>" \
-  -d '{"query": "<GRAPHQL_QUERY>"}'
+```typescript
+export default async function (args, ctx) {
+  const response = await fetch("https://api.linear.app/graphql", {
+    method: "POST",
+    headers: {
+      "Content-Type": "application/json",
+      Authorization: "Bearer [REDACTED:LINEAR_OAUTH_ACCESS_TOKEN]",
+    },
+    body: JSON.stringify({ query: args.query, variables: args.variables ?? {} }),
+  });
+  if (!response.ok) throw new Error(`Linear HTTP ${response.status}`);
+  const result = await response.json();
+  if (result.errors?.length) throw new Error(JSON.stringify(result.errors));
+  return result.data;
+}
 ```
 
+Return only the issue fields needed for the task; never return request headers or credentials.
+
 ## Agent Interaction API — `action` vs `thought`
 
 Linear's **Agent Interaction API** (different from issue mutations above) supports two activity payload kinds. Use this section whenever emitting `agentActivityCreate` mutations.
@@ -191,30 +189,13 @@ query {
 
 This is the most common scenario — completing a Linear-sourced swarm task and updating the ticket:
 
-```bash
-# 1. Get the token
-TOKEN=$(db-query result from oauth_tokens)
-
-# 2. Get issue details and team states
-curl -s -X POST https://api.linear.app/graphql \
-  -H "Content-Type: application/json" \
-  -H "Authorization: Bearer $TOKEN" \
-  -d '{"query": "{ issue(id: \"DES-12\") { id team { states { nodes { id name type } } } } }"}'
-
-# 3. Find the "Done" state UUID from the response (type: "completed")
-
-# 4. Update the issue
-curl -s -X POST https://api.linear.app/graphql \
-  -H "Content-Type: application/json" \
-  -H "Authorization: Bearer $TOKEN" \
-  -d '{"query": "mutation { issueUpdate(id: \"<ISSUE-UUID>\", input: { stateId: \"<DONE-STATE-UUID>\" }) { success issue { identifier state { name } } } }"}'
-```
+Run the query in operation 1 through the script above to get the issue UUID and team states. Select the state whose `type` is `completed`, then run `issueUpdate` with that state UUID through the same script. Check GraphQL errors and mutation `success` before reporting the ticket updated.
 
 ## Important Notes
 
 - **Always update Linear when completing Linear-sourced tasks.** The user expects the ticket to reflect the swarm's work. Marking only the swarm task as complete is insufficient. Do not complete only the swarm task — failing to update Linear breaks the sync and wastes resources.
 - **Transition timing:** see the "When to Transition" section above. Direct-to-main work transitions on ship, not on merge.
-- **Token expiry:** Check `expiresAt` before making calls. If expired, notify the user — they need to re-authorize.
+- **Authorization failures:** Report refresh failures or persistent 401s to Lead/user for re-authorization; the server handles normal expiry.
 - **Rate limits:** Linear has rate limits. For bulk operations, add small delays between calls.
 - **Issue identifiers vs UUIDs:** The human-readable identifier (e.g., "DES-12") works for queries but the `issueUpdate` mutation requires the actual UUID. Always fetch the UUID first via a query.
 - **Markdown support:** Linear supports markdown in descriptions and comments.
@@ -222,7 +203,7 @@ curl -s -X POST https://api.linear.app/graphql \
 ## Error Handling
 
 Common errors:
-- `401 Unauthorized` → Token expired or invalid, needs re-auth
+- `401 Unauthorized` → Report the missing binding or authorization to Lead as a blocker; Lead checks provisioning or re-authorization
 - `Forbidden` → Token doesn't have required scope
 - `Entity not found` → Wrong issue ID/identifier
 - `"parameter must not be empty"` (or similar on Agent Interaction API) → You sent an `action` activity without a `parameter` — convert to `thought` or fill in a real noun. See "Agent Interaction API — action vs thought" above.

package/templates/skills/pages/content.md

@@ -454,7 +454,9 @@ with a custom `swarm.call` action handler. Action shape:
 `swarm.call` dispatches through the SPA's bearer (for `app_url` loads) or
 the page-session cookie (for direct `api_url` loads). The endpoint must be
 a valid swarm API path. User-token sessions retain user authorization.
-Operator and password sessions retain deployment-level API access.
+Operator-launched sessions retain deployment-level API access. Password
+sessions are guests: they reach only their own page record and KV, so
+`swarm.call` to any other endpoint returns 403.
 
 See the `@json-render/core` docs for the supported node types (`text`,
 `button`, `input`, `card`, etc.).
@@ -462,8 +464,9 @@ See the `@json-render/core` docs for the supported node types (`text`,
 ## Security & Blast Radius
 
 - User-token launches retain the signed viewer identity and its API permissions.
-- Operator and password sessions are guests with deployment-level API access.
-  They do not inherit the page author's agent identity. Review actions before sharing these pages.
+- Operator launches keep deployment-level API access. They do not inherit the page author's agent identity.
+- Password sessions are guests. Through the proxy they reach only `GET pages/<own id>` (without
+  `passwordHash`) and the page's own KV. Every other route returns 403, and every RBAC verb denies a guest.
 - Browser SDK memory operations use the page owner's agent scope through verified page execution context.
   Viewer authentication, permissions, and audit identity remain separate from this resource scope.
 - Treat agent-generated HTML / JSON like trusted code — the agent already
@@ -473,7 +476,8 @@ See the `@json-render/core` docs for the supported node types (`text`,
 - HTML pages render inside a sandboxed iframe with
   `sandbox="allow-scripts allow-forms allow-same-origin"`. This limits
   some attack surface (no top-level navigation, no pointer-lock) but the
-  page still has full access to the SwarmSDK if cookies are present.
+  page still has the SwarmSDK access of its session: full for user and
+  operator sessions, page record and KV only for password guests.
 - All page bodies pass through `scrubSecrets` at the egress boundary
   (`/p/:id`, `/p/:id.json`, listing endpoint) — accidental secrets in
   the body get masked at serve time, not at write time. Don't rely on

package/templates/skills/qa/content.md

@@ -94,7 +94,7 @@ Write all test cases into the QA document's `## Test Cases` section.
 2. `agent-browser snapshot -i` to read the page state and its `@eN` refs
 3. Act on refs (`click @eN`, `fill @eN "text"`, `type`, `press`) and re-snapshot after every navigation or state change; refs are only valid for the snapshot that produced them
 4. `agent-browser screenshot /tmp/<name>.png` for evidence, then `agent-browser close`
-5. To share a screenshot outside the machine, upload it to agent-fs with `agent-fs write <path> --file /tmp/<name>.png -m "<what it shows>"` (binary-safe; `--content` mangles PNGs), then `agent-fs signed-url <path> --json` and embed the URL as `![caption](<url>)`. If agent-fs is not configured, report the local path and say the upload was skipped
+5. To share a screenshot outside the machine, upload it to agent-fs with `agent-fs write <path> --file /tmp/<name>.png -m "<what it shows>"` (binary-safe; `--content` mangles PNGs), keep it there as the original, and embed it in a PR or GitHub comment as a GitHub user attachment (`github-attach` skill): `![caption](https://github.com/user-attachments/assets/<uuid>)`. Use `agent-fs share-create <path>` for Slack or Linear. If agent-fs is not configured, report the local path and say the upload was skipped
 
 **For manual testing**:
 1. Present each test case's steps to the user
@@ -117,7 +117,7 @@ For each test case, record the actual result and pass/fail status.
 ### Step 4: Capture Evidence
 
 Gather evidence for the QA report:
-- **Screenshots**: Via `agent-browser screenshot` (uploaded to agent-fs with a signed URL when they must be shared) or user-provided
+- **Screenshots**: Via `agent-browser screenshot` (kept on agent-fs; GitHub user attachments in a PR, `share-create` links elsewhere) or user-provided
 - **Videos**: Session recording URLs (Loom, etc.)
 - **Logs**: Console output, error messages, relevant log lines
 - **External links**: Sentry issues, CI/CD runs, Grafana dashboards, PR URLs

package/templates/skills/workflow-iterate/content.md

@@ -108,8 +108,8 @@ Use these shapes as a starting point, then confirm them against the current exec
 
 **Before you add the first `system-one-decision` node to a workflow, confirm its key works.** A node with no working key fails its whole run, and a save only warns. Do these in order and stop at the first failure:
 
-1. Pick the provider. `typesafe` (the default) needs the global secret `TYPESAFE_API_KEY`. `openrouter` needs `OPENROUTER_API_KEY`. `laya` needs the global secret `LAYA_API_KEY` and the global config `LAYA_URL`, the base URL of its server. Use the provider the requester named. If they named none, use `typesafe`. If its key is missing but another provider's key exists, ask which to use rather than switching, because the accounts bill separately.
-2. Check the key is set: `get-config` with `key` set to that name and no `includeSecrets`. A masked value (`********`) means a value exists. No entry means it is missing. Never pass `includeSecrets`, and never read the value. For `laya`, check `LAYA_URL` the same way; it is not secret, so its value shows.
+1. Pick the provider. `typesafe` (the default) needs the global secret `TYPESAFE_API_KEY`. `openrouter` needs `OPENROUTER_API_KEY`. `laya` needs the global secret `LAYA_API_KEY` and the global config `LAYA_URL`, the base URL of its server. `openai` needs `OPENAI_DECISIONS_API_KEY` (never `OPENAI_API_KEY`). `cloudflare` needs the global secret `CLOUDFLARE_API_TOKEN` and the global config `CLOUDFLARE_ACCOUNT_ID`. Use the provider the requester named. If they named none, use `typesafe`. If its key is missing but another provider's key exists, ask which to use rather than switching, because the accounts bill separately.
+2. Check the key is set: `get-config` with `key` set to that name and no `includeSecrets`. A masked value (`********`) means a value exists. No entry means it is missing. Never pass `includeSecrets`, and never read the value. For `laya`, check `LAYA_URL` the same way, and for `cloudflare`, `CLOUDFLARE_ACCOUNT_ID`; neither is secret, so the value shows.
 3. Confirm it works with one cheap call. Create a throwaway one-node workflow, trigger it, read the run, then `delete-workflow` it:
 
    ```json
@@ -162,7 +162,7 @@ Afterwards, a `warnings` entry on `create-workflow` or a patch tool means the ke
 }
 ```
 
-- `provider` is `typesafe` (default), `openrouter`, or `laya`, and must be a literal, not a `{{token}}`. `model` is that provider's own id (`jev-1.13.0` on `typesafe`, `typesafe/jev-1.13` on `openrouter`, a checkpoint name such as `multilingual` on `laya`); leave it unset for the provider's default. `laya` has no default and sends no `model`, because it silently ignores one it does not know: leave it unset unless you mean a specific checkpoint. All three take the same request and return the same answers. There is no fallback between them. Never use OpenRouter's `typesafe/jev-router`, which is a chat router that hands the request to another model.
+- `provider` is `typesafe` (default), `openrouter`, `laya`, `openai`, or `cloudflare`, and must be a literal, not a `{{token}}`. `model` is that provider's own id (`jev-1.13.0` on `typesafe`, `typesafe/jev-1.13` on `openrouter`, a checkpoint name such as `multilingual` on `laya`); `gpt-6-luna` on `openai`, `clef` (default) or `clef-flash` on `cloudflare`, which accepts no other id; leave it unset for the provider's default. `laya` has no default and sends no `model`, because it silently ignores one it does not know: leave it unset unless you mean a specific checkpoint. Every provider returns the same output; `openai` gets a translated request, and an OpenAI refusal of any question fails the step. `cloudflare` takes at most 64 questions. There is no fallback between them. Never use OpenRouter's `typesafe/jev-router`, which is a chat router that hands the request to another model.
 - `state` is required: text, a string array, or a JSON object. An exact `{{token}}` keeps the upstream JSON type. Every question in one call shares the state and cannot see the other answers, so a dependent judgment needs its own node.
 - Each question is `noul` (probability that a claim is true; optional `criteria: { true, false }`), `choice` (2 to 255 options; `criteria: { option: description }`), or `score` (2 to 10 ordered levels; `criteria: [level, ...]`).
 - `returns` repeats every question id and its type. A mismatch is rejected when the workflow is saved.
@@ -171,7 +171,7 @@ Afterwards, a `warnings` entry on `create-workflow` or a patch tool means the ke
 - `humanReview: { band: { min, max }, approvers, title?, timeout?, notifications? }` sends an answer to a person when `min <= confidence <= max` (0 to 1, both ends inside). It raises a `human-in-the-loop` approval (same approvers, timeout, notifications, `waiting` run state), so use the same `approvers` shape. `choice` and `score` are tested on their `confidence` (on `laya` that is its `answer_confidence`, the top probability); a `noul` on `max(noul, 1 - noul)`. Any answer in the band makes the run wait. `next` must then be a port map: `approved` (required, every accepted answer), and optionally `rejected` and `timeout`; a string or list `next` is refused. The output stays `{ model, answers, usage }` on every path, plus `review` (`status`, and per question `confidence`, `inBand`, `decidedBy`). A person's answer replaces the model's in `answers`; `probabilities` and `confidence` stay the model's.
 - On `laya`, ask `choice` questions, not `noul`, until a `noul` question is checked against known inputs. On laya-server 0.1.0 a `noul` sentiment question returned close to 0 even for clearly positive text, while the same judgment as a `choice` answered correctly. This is how the model answered, not a node rule. After a run, read `<node-id>.routing.model` to see which laya checkpoint answered. A complete laya workflow (manual trigger with `{"text": "..."}`, one `choice` question, a review band, and a `property-match` branch on `<node-id>.answers.<question>.choice`) is in `docs-site/content/docs/(documentation)/concepts/workflows.mdx`, section "Example: a laya decision end to end".
 - Do not set `retry` or `validation.retry` on a `system-one-decision` node. It retries connection errors, 408, 429, and 5xx itself (`config.maxRetries`, 0 to 3, default 2) inside `config.timeoutMs` (default 30000). A 401, a 422, or an answer that fails validation ends after one attempt.
-- The node reads its provider's key (`TYPESAFE_API_KEY`, `OPENROUTER_API_KEY`, or `LAYA_API_KEY`, and for `laya` the server URL `LAYA_URL`) server-side. The key never appears in the definition, the step output, or an error. A run whose key or `LAYA_URL` is missing fails before any node executes, and a 401 or 403 fails the step as `<KEY> was rejected`. An unresolved `{{token}}` fails the step before any request.
+- The node reads its provider's key (`TYPESAFE_API_KEY`, `OPENROUTER_API_KEY`, `LAYA_API_KEY`, `OPENAI_DECISIONS_API_KEY`, or `CLOUDFLARE_API_TOKEN`, plus `LAYA_URL` for `laya` and `CLOUDFLARE_ACCOUNT_ID` for `cloudflare`) server-side. The key never appears in the definition, the step output, or an error. A run whose key or `LAYA_URL` is missing fails before any node executes, and a 401 or 403 fails the step as `<KEY> was rejected`. An unresolved `{{token}}` fails the step before any request.
 
 ### `swarm-script`
 

package/tsconfig.json

@@ -13,10 +13,10 @@
     "moduleResolution": "bundler",
     "allowImportingTsExtensions": true,
 
-    // Path aliases
-    "baseUrl": ".",
+    // Path aliases. No `baseUrl`: TS 7 (tsgo) removed it, and relative
+    // `paths` resolve against this file in both TS 5 and TS 7.
     "paths": {
-      "@/*": ["src/*"]
+      "@/*": ["./src/*"]
     },
     "verbatimModuleSyntax": true,
     "noEmit": true,

package/dist/boot-scrub-logs-t8xg7wd7.js

@@ -1,99 +0,0 @@
-import {
-  getDbClient,
-  init_db
-} from "./cli-0wn3ypqv.js";
-import"./cli-v0e7jpr5.js";
-import"./cli-3qhyh31j.js";
-import"./cli-vbr859rz.js";
-import"./cli-n7h1kqpf.js";
-import"./cli-7mm2r1kp.js";
-import"./cli-g5erf0zt.js";
-import"./cli-yj790e19.js";
-import"./cli-ywybs5as.js";
-import"./cli-gd4favx9.js";
-import"./cli-agamgm0p.js";
-import"./cli-5c2j5yvx.js";
-import"./cli-1a2j50m0.js";
-import"./cli-f9w1semm.js";
-import"./cli-ej6gbxfb.js";
-import"./cli-g3qgrzck.js";
-import"./cli-sd0mxa3c.js";
-import"./cli-w5e1d1vv.js";
-import"./cli-1d3w4xm3.js";
-import"./cli-zf8jjwex.js";
-import {
-  init_secret_scrubber,
-  scrubSecrets
-} from "./cli-qt5wzq6v.js";
-import"./cli-bc05qbss.js";
-
-// src/be/boot-scrub-logs.ts
-init_secret_scrubber();
-init_db();
-var SCRUB_KEY = "boot-scrub-logs-v2";
-var CURSOR_KEY = "boot-scrub-logs-v2-cursor";
-var BATCH_SIZE = 200;
-var yieldTick = () => new Promise((r) => setTimeout(r, 5));
-async function runBootScrubLogs() {
-  const done = await getDbClient().get("SELECT key FROM seed_state WHERE kind = ? AND key = ?", ["maintenance", SCRUB_KEY]);
-  if (done)
-    return;
-  const savedCursor = (await getDbClient().get("SELECT seededHash FROM seed_state WHERE kind = ? AND key = ?", ["maintenance", CURSOR_KEY]))?.seededHash ?? "";
-  const lastProcessedId = savedCursor || "";
-  const totalRemaining = (await getDbClient().get(`SELECT COUNT(*) as count FROM session_logs
-         WHERE id > ?
-           AND (content LIKE '%lin!_oauth!_%' ESCAPE '!'
-             OR content LIKE '%lin!_api!_%' ESCAPE '!'
-             OR content LIKE '%npm!_%' ESCAPE '!'
-             OR content LIKE '%ATATT%')`, [lastProcessedId]))?.count ?? 0;
-  if (totalRemaining === 0) {
-    await markDone();
-    return;
-  }
-  console.log(`[boot-scrub-logs] starting: ${totalRemaining} candidate rows remaining` + (lastProcessedId ? ` (resuming from cursor ${lastProcessedId.slice(0, 8)}…)` : ""));
-  const saveCursorSql = `INSERT INTO seed_state (kind, key, seededHash, seededAt)
-     VALUES ('maintenance', '${CURSOR_KEY}', ?, datetime('now'))
-     ON CONFLICT (kind, key) DO UPDATE SET seededHash = ?, seededAt = datetime('now')`;
-  let scrubbed = 0;
-  let scanned = 0;
-  let cursor = lastProcessedId;
-  for (;; ) {
-    const rows = await getDbClient().query(`SELECT id, content FROM session_logs
-       WHERE id > ?
-         AND (content LIKE '%lin!_oauth!_%' ESCAPE '!'
-           OR content LIKE '%lin!_api!_%' ESCAPE '!'
-           OR content LIKE '%npm!_%' ESCAPE '!'
-           OR content LIKE '%ATATT%')
-       ORDER BY id ASC
-       LIMIT ${BATCH_SIZE}`, [cursor]);
-    if (rows.length === 0)
-      break;
-    const batchLastId = rows[rows.length - 1].id;
-    await getDbClient().transaction(async (tx) => {
-      for (const row of rows) {
-        const cleaned = scrubSecrets(row.content);
-        if (cleaned !== row.content) {
-          await tx.run("UPDATE session_logs SET content = ? WHERE id = ?", [cleaned, row.id]);
-          scrubbed++;
-        }
-      }
-      await tx.run(saveCursorSql, [batchLastId, batchLastId]);
-    });
-    scanned += rows.length;
-    cursor = batchLastId;
-    await yieldTick();
-  }
-  await markDone();
-  await getDbClient().run("DELETE FROM seed_state WHERE kind = 'maintenance' AND key = ?", [
-    CURSOR_KEY
-  ]);
-  console.log(`[boot-scrub-logs] complete: scanned=${scanned} scrubbed=${scrubbed}`);
-}
-async function markDone() {
-  await getDbClient().run(`INSERT INTO seed_state (kind, key, seededHash, seededAt)
-     VALUES ('maintenance', ?, 'done', datetime('now'))
-     ON CONFLICT (kind, key) DO UPDATE SET seededHash = 'done', seededAt = datetime('now')`, [SCRUB_KEY]);
-}
-export {
-  runBootScrubLogs
-};

package/dist/cli-0a7r5331.js

@@ -1,168 +0,0 @@
-import {
-  cosineSimilarity,
-  deserializeEmbedding,
-  getEmbeddingProvider,
-  init_embedding,
-  serializeEmbedding
-} from "./cli-v7fqehqd.js";
-import {
-  getDbClient,
-  init_db
-} from "./cli-0wn3ypqv.js";
-import {
-  init_secret_scrubber,
-  scrubSecrets
-} from "./cli-qt5wzq6v.js";
-
-// src/be/scripts/embeddings.ts
-init_secret_scrubber();
-init_db();
-init_embedding();
-var providerOverride = null;
-function embeddingProvider() {
-  return providerOverride ?? getEmbeddingProvider();
-}
-function scriptEmbeddingText(script) {
-  return scrubSecrets([script.description, script.intent, script.signatureJson].join(`
-`));
-}
-function rowToScript(row) {
-  return {
-    id: row.id,
-    name: row.name,
-    scope: row.scope,
-    scopeId: row.scopeId ?? null,
-    source: row.source,
-    description: row.description,
-    intent: row.intent,
-    signatureJson: row.signatureJson,
-    argsJsonSchema: row.argsJsonSchema ?? null,
-    contentHash: row.contentHash,
-    version: row.version,
-    isScratch: row.isScratch === 1,
-    typeChecked: row.typeChecked === 1,
-    fsMode: row.fsMode,
-    createdByAgentId: row.createdByAgentId ?? null,
-    createdAt: row.createdAt,
-    updatedAt: row.updatedAt
-  };
-}
-async function embedScript(script) {
-  const text = scriptEmbeddingText(script);
-  const provider = embeddingProvider();
-  const embedding = await provider.embed(text);
-  if (!embedding)
-    return;
-  if (embedding.length !== provider.dimensions) {
-    console.error(`[script-embed] dimension mismatch for "${script.name}": expected=${provider.dimensions} got=${embedding.length}, skipping`);
-    return;
-  }
-  await getDbClient().run(`INSERT INTO script_embeddings (
-      scriptId, embedding, embeddingModel, embeddedText, embeddedAt
-    )
-    VALUES (?, ?, ?, ?, ?)
-    ON CONFLICT(scriptId) DO UPDATE SET
-      embedding = excluded.embedding,
-      embeddingModel = excluded.embeddingModel,
-      embeddedText = excluded.embeddedText,
-      embeddedAt = excluded.embeddedAt`, [script.id, serializeEmbedding(embedding), provider.name, text, new Date().toISOString()]);
-}
-async function candidateRows(scope, scopeId) {
-  const params = [];
-  let where = "s.isScratch = 0";
-  if (scope === "global") {
-    where += " AND s.scope = 'global' AND s.scopeId IS NULL";
-  } else if (scope === "agent") {
-    where += " AND s.scope = 'agent' AND s.scopeId = ?";
-    params.push(scopeId ?? "");
-  } else if (scopeId) {
-    where += " AND ((s.scope = 'agent' AND s.scopeId = ?) OR (s.scope = 'global' AND s.scopeId IS NULL))";
-    params.push(scopeId);
-  } else {
-    where += " AND s.scope = 'global' AND s.scopeId IS NULL";
-  }
-  return getDbClient().query(`SELECT
-      s.*,
-      e.scriptId,
-      e.embedding,
-      e.embeddingModel,
-      e.embeddedText,
-      e.embeddedAt
-    FROM script_embeddings e
-    JOIN scripts s ON s.id = e.scriptId
-    WHERE ${where}`, params);
-}
-async function scriptRows(scope, scopeId) {
-  const params = [];
-  let where = "isScratch = 0";
-  if (scope === "global") {
-    where += " AND scope = 'global' AND scopeId IS NULL";
-  } else if (scope === "agent") {
-    where += " AND scope = 'agent' AND scopeId = ?";
-    params.push(scopeId ?? "");
-  } else if (scopeId) {
-    where += " AND ((scope = 'agent' AND scopeId = ?) OR (scope = 'global' AND scopeId IS NULL))";
-    params.push(scopeId);
-  } else {
-    where += " AND scope = 'global' AND scopeId IS NULL";
-  }
-  return getDbClient().query(`SELECT *, NULL as scriptId, NULL as embedding, NULL as embeddingModel, NULL as embeddedText, NULL as embeddedAt FROM scripts WHERE ${where}`, params);
-}
-function nameMatchBonus(script, query) {
-  const trimmed = query.trim().toLowerCase();
-  if (!trimmed)
-    return 0;
-  return script.name.toLowerCase().includes(trimmed) ? 1 : 0;
-}
-async function lexicalFallback(args) {
-  const query = args.query.trim().toLowerCase();
-  return (await scriptRows(args.scope, args.scopeId)).map(rowToScript).filter((script) => {
-    if (!query)
-      return true;
-    return [script.name, script.description, script.intent].join(`
-`).toLowerCase().includes(query);
-  }).map((script) => {
-    const bonus = nameMatchBonus(script, args.query);
-    return {
-      script,
-      score: bonus || 0.5,
-      semanticScore: 0,
-      nameMatchBonus: bonus
-    };
-  }).sort((a, b) => b.score - a.score).slice(0, args.limit ?? 10);
-}
-async function searchScripts(args) {
-  const provider = embeddingProvider();
-  const queryEmbedding = await provider.embed(args.query);
-  if (!queryEmbedding)
-    return lexicalFallback(args);
-  const candidates = await candidateRows(args.scope, args.scopeId);
-  if (candidates.length === 0)
-    return lexicalFallback(args);
-  const results = [];
-  for (const row of candidates) {
-    const stored = deserializeEmbedding(row.embedding);
-    if (stored.length !== queryEmbedding.length)
-      continue;
-    const script = rowToScript(row);
-    const semanticScore = cosineSimilarity(queryEmbedding, stored);
-    const bonus = nameMatchBonus(script, args.query);
-    results.push({
-      script,
-      score: 0.7 * semanticScore + 0.3 * bonus,
-      semanticScore,
-      nameMatchBonus: bonus
-    });
-  }
-  if (results.length === 0)
-    return lexicalFallback(args);
-  return results.sort((a, b) => b.score - a.score).slice(0, args.limit ?? 10);
-}
-async function reembedAllScripts() {
-  const rows = await getDbClient().query("SELECT *, NULL as scriptId, NULL as embedding, NULL as embeddingModel, NULL as embeddedText, NULL as embeddedAt FROM scripts WHERE isScratch = 0 ORDER BY updatedAt ASC");
-  for (const row of rows) {
-    await embedScript(rowToScript(row));
-  }
-}
-
-export { embeddingProvider, embedScript, searchScripts, reembedAllScripts };