@desplega.ai/agent-swarm 1.164.1 → 1.166.0

package/dist/{index-c4aqcyz1.js → index-9b65j1m5.js}

@@ -1,18 +1,16 @@
 import {
   getEmbeddingProvider,
   getMemoryStore,
+  init_memory,
   resetEmbeddingProvider
-} from "./cli-v7fqehqd.js";
-import"./cli-agjzafns.js";
-import"./cli-cvk6yzw5.js";
-import"./cli-0wn3ypqv.js";
-import"./cli-v0e7jpr5.js";
+} from "./cli-yshaazs1.js";
+import"./cli-xvdgasgy.js";
 import"./cli-3qhyh31j.js";
-import"./cli-vbr859rz.js";
-import"./cli-n7h1kqpf.js";
+import"./cli-jhm6hzjn.js";
 import"./cli-7mm2r1kp.js";
 import"./cli-g5erf0zt.js";
-import"./cli-yj790e19.js";
+import"./cli-dmtrxqhg.js";
+import"./cli-tadfgd0t.js";
 import"./cli-ywybs5as.js";
 import"./cli-gd4favx9.js";
 import"./cli-agamgm0p.js";
@@ -20,13 +18,15 @@ import"./cli-5c2j5yvx.js";
 import"./cli-1a2j50m0.js";
 import"./cli-f9w1semm.js";
 import"./cli-ej6gbxfb.js";
-import"./cli-g3qgrzck.js";
+import"./cli-zsh093hk.js";
 import"./cli-sd0mxa3c.js";
 import"./cli-w5e1d1vv.js";
-import"./cli-1d3w4xm3.js";
+import"./cli-4r1sjfc4.js";
 import"./cli-zf8jjwex.js";
-import"./cli-qt5wzq6v.js";
+import"./cli-wt7ccy4r.js";
 import"./cli-bc05qbss.js";
+init_memory();
+
 export {
   getEmbeddingProvider,
   getMemoryStore,

package/dist/{index-r46s01nq.js → index-bn6cy8ps.js}

@@ -4,38 +4,34 @@ import {
   runScheduleNow,
   startScheduler,
   stopScheduler
-} from "./cli-a9bw0xxt.js";
-import"./cli-003785v9.js";
-import"./cli-07s39g1n.js";
+} from "./cli-df56tqdw.js";
+import"./cli-xvc3q9br.js";
+import"./cli-mv2520nm.js";
 import"./cli-w0bwte75.js";
 import"./cli-re8z5p8p.js";
-import"./cli-etbrt8x1.js";
-import"./cli-976r1zqx.js";
-import"./cli-wg8yjqtw.js";
-import"./cli-j0tmc908.js";
+import"./cli-0nhdwxd5.js";
+import"./cli-rggdq8wq.js";
+import"./cli-ysnyhws9.js";
+import"./cli-jvj6a0cv.js";
 import"./cli-epan13p1.js";
 import"./cli-f14fvzag.js";
 import"./cli-zt3w1cn1.js";
-import"./cli-1wetf34q.js";
-import"./cli-2c8eky5y.js";
+import"./cli-f2n17zhp.js";
+import"./cli-feh3dkah.js";
 import"./cli-3dpj7atn.js";
 import"./cli-2x0e561b.js";
 import"./cli-pkke6geq.js";
 import"./cli-rb9m6rpe.js";
 import"./cli-mzfth0bp.js";
-import"./cli-0a7r5331.js";
-import"./cli-v7fqehqd.js";
-import"./cli-agjzafns.js";
-import"./cli-93rxw9yd.js";
+import"./cli-j2jbr8af.js";
 import"./cli-fad8m16k.js";
 import"./cli-bsakbbkm.js";
 import"./cli-zxg80zs9.js";
 import"./cli-51tf7ac3.js";
 import"./cli-ydt3zkwv.js";
-import"./cli-4drstbb9.js";
+import"./cli-ecknp7p1.js";
 import"./cli-q51yprfq.js";
 import"./cli-3er6gcsn.js";
-import"./cli-cvk6yzw5.js";
 import"./cli-yatxqynm.js";
 import"./cli-b0f70z24.js";
 import"./cli-nexwh8zg.js";
@@ -44,16 +40,16 @@ import"./cli-1m2e086m.js";
 import"./cli-bzr0ftht.js";
 import"./cli-bd957dgb.js";
 import"./cli-pzxba7gw.js";
-import"./cli-xb7kyanp.js";
-import"./cli-1wd1n2ya.js";
-import"./cli-0wn3ypqv.js";
-import"./cli-v0e7jpr5.js";
+import"./cli-8kgvmkak.js";
+import"./cli-rfphkzh5.js";
+import"./cli-yshaazs1.js";
+import"./cli-xvdgasgy.js";
 import"./cli-3qhyh31j.js";
-import"./cli-vbr859rz.js";
-import"./cli-n7h1kqpf.js";
+import"./cli-jhm6hzjn.js";
 import"./cli-7mm2r1kp.js";
 import"./cli-g5erf0zt.js";
-import"./cli-yj790e19.js";
+import"./cli-dmtrxqhg.js";
+import"./cli-tadfgd0t.js";
 import"./cli-ywybs5as.js";
 import"./cli-gd4favx9.js";
 import"./cli-agamgm0p.js";
@@ -61,13 +57,13 @@ import"./cli-5c2j5yvx.js";
 import"./cli-1a2j50m0.js";
 import"./cli-f9w1semm.js";
 import"./cli-ej6gbxfb.js";
-import"./cli-g3qgrzck.js";
+import"./cli-zsh093hk.js";
 import"./cli-sd0mxa3c.js";
 import"./cli-w5e1d1vv.js";
-import"./cli-1d3w4xm3.js";
-import"./cli-xxz89c2n.js";
+import"./cli-4r1sjfc4.js";
+import"./cli-mb75wpxf.js";
 import"./cli-zf8jjwex.js";
-import"./cli-qt5wzq6v.js";
+import"./cli-wt7ccy4r.js";
 import"./cli-bc05qbss.js";
 export {
   calculateNextRun,

package/dist/{index-38kqdt3e.js → index-dkfxpkmm.js}

@@ -4,39 +4,35 @@ import {
   runRebootSweep,
   startHeartbeat,
   stopHeartbeat
-} from "./cli-691f2rxm.js";
-import"./cli-a9bw0xxt.js";
-import"./cli-003785v9.js";
-import"./cli-07s39g1n.js";
+} from "./cli-66zh26sp.js";
+import"./cli-df56tqdw.js";
+import"./cli-xvc3q9br.js";
+import"./cli-mv2520nm.js";
 import"./cli-w0bwte75.js";
 import"./cli-re8z5p8p.js";
-import"./cli-etbrt8x1.js";
-import"./cli-976r1zqx.js";
-import"./cli-wg8yjqtw.js";
-import"./cli-j0tmc908.js";
+import"./cli-0nhdwxd5.js";
+import"./cli-rggdq8wq.js";
+import"./cli-ysnyhws9.js";
+import"./cli-jvj6a0cv.js";
 import"./cli-epan13p1.js";
 import"./cli-f14fvzag.js";
 import"./cli-zt3w1cn1.js";
-import"./cli-1wetf34q.js";
-import"./cli-2c8eky5y.js";
+import"./cli-f2n17zhp.js";
+import"./cli-feh3dkah.js";
 import"./cli-3dpj7atn.js";
 import"./cli-2x0e561b.js";
 import"./cli-pkke6geq.js";
 import"./cli-rb9m6rpe.js";
 import"./cli-mzfth0bp.js";
-import"./cli-0a7r5331.js";
-import"./cli-v7fqehqd.js";
-import"./cli-agjzafns.js";
-import"./cli-93rxw9yd.js";
+import"./cli-j2jbr8af.js";
 import"./cli-fad8m16k.js";
 import"./cli-bsakbbkm.js";
 import"./cli-zxg80zs9.js";
 import"./cli-51tf7ac3.js";
 import"./cli-ydt3zkwv.js";
-import"./cli-4drstbb9.js";
+import"./cli-ecknp7p1.js";
 import"./cli-q51yprfq.js";
 import"./cli-3er6gcsn.js";
-import"./cli-cvk6yzw5.js";
 import"./cli-yatxqynm.js";
 import"./cli-b0f70z24.js";
 import"./cli-nexwh8zg.js";
@@ -45,16 +41,16 @@ import"./cli-1m2e086m.js";
 import"./cli-bzr0ftht.js";
 import"./cli-bd957dgb.js";
 import"./cli-pzxba7gw.js";
-import"./cli-xb7kyanp.js";
-import"./cli-1wd1n2ya.js";
-import"./cli-0wn3ypqv.js";
-import"./cli-v0e7jpr5.js";
+import"./cli-8kgvmkak.js";
+import"./cli-rfphkzh5.js";
+import"./cli-yshaazs1.js";
+import"./cli-xvdgasgy.js";
 import"./cli-3qhyh31j.js";
-import"./cli-vbr859rz.js";
-import"./cli-n7h1kqpf.js";
+import"./cli-jhm6hzjn.js";
 import"./cli-7mm2r1kp.js";
 import"./cli-g5erf0zt.js";
-import"./cli-yj790e19.js";
+import"./cli-dmtrxqhg.js";
+import"./cli-tadfgd0t.js";
 import"./cli-ywybs5as.js";
 import"./cli-gd4favx9.js";
 import"./cli-agamgm0p.js";
@@ -62,13 +58,13 @@ import"./cli-5c2j5yvx.js";
 import"./cli-1a2j50m0.js";
 import"./cli-f9w1semm.js";
 import"./cli-ej6gbxfb.js";
-import"./cli-g3qgrzck.js";
+import"./cli-zsh093hk.js";
 import"./cli-sd0mxa3c.js";
 import"./cli-w5e1d1vv.js";
-import"./cli-1d3w4xm3.js";
-import"./cli-xxz89c2n.js";
+import"./cli-4r1sjfc4.js";
+import"./cli-mb75wpxf.js";
 import"./cli-zf8jjwex.js";
-import"./cli-qt5wzq6v.js";
+import"./cli-wt7ccy4r.js";
 import"./cli-bc05qbss.js";
 export {
   getBootEpochMs,

package/dist/{index-630kj5vd.js → index-f8xnqrye.js}

@@ -3,37 +3,31 @@ import {
 } from "./cli-ep19k3mb.js";
 import {
   agentFsProvisionSeeder
-} from "./cli-v5pr2fgt.js";
+} from "./cli-gt8azyet.js";
 import {
   extractArgsJsonSchema,
   extractScriptSignature,
-  getScript,
   require_dist,
   typecheckScript,
-  upsertScriptByName,
   validateDefinition,
   validateScriptImports
-} from "./cli-j0tmc908.js";
+} from "./cli-jvj6a0cv.js";
 import"./cli-epan13p1.js";
 import"./cli-f14fvzag.js";
 import"./cli-zt3w1cn1.js";
-import"./cli-1wetf34q.js";
-import"./cli-2c8eky5y.js";
+import"./cli-f2n17zhp.js";
+import"./cli-feh3dkah.js";
 import"./cli-3dpj7atn.js";
 import"./cli-2x0e561b.js";
 import"./cli-pkke6geq.js";
 import"./cli-rb9m6rpe.js";
-import"./cli-0a7r5331.js";
-import"./cli-v7fqehqd.js";
-import"./cli-agjzafns.js";
-import"./cli-93rxw9yd.js";
+import"./cli-j2jbr8af.js";
 import"./cli-bsakbbkm.js";
 import"./cli-zxg80zs9.js";
 import"./cli-ydt3zkwv.js";
-import"./cli-4drstbb9.js";
+import"./cli-ecknp7p1.js";
 import"./cli-q51yprfq.js";
 import"./cli-3er6gcsn.js";
-import"./cli-cvk6yzw5.js";
 import"./cli-yatxqynm.js";
 import"./cli-b0f70z24.js";
 import"./cli-nexwh8zg.js";
@@ -50,22 +44,25 @@ import {
   deleteSkillFile,
   getDbClient,
   getScheduledTaskByName,
+  getScript,
   getSkillByName,
   getSkillFiles,
   init_db,
+  init_db1 as init_db2,
   listWorkflows,
   updateScheduledTask,
   updateSkill,
   updateWorkflow,
+  upsertScriptByName,
   upsertSkillFiles
-} from "./cli-0wn3ypqv.js";
-import"./cli-v0e7jpr5.js";
+} from "./cli-yshaazs1.js";
+import"./cli-xvdgasgy.js";
 import"./cli-3qhyh31j.js";
-import"./cli-vbr859rz.js";
-import"./cli-n7h1kqpf.js";
+import"./cli-jhm6hzjn.js";
 import"./cli-7mm2r1kp.js";
 import"./cli-g5erf0zt.js";
-import"./cli-yj790e19.js";
+import"./cli-dmtrxqhg.js";
+import"./cli-tadfgd0t.js";
 import"./cli-ywybs5as.js";
 import"./cli-gd4favx9.js";
 import"./cli-agamgm0p.js";
@@ -73,17 +70,18 @@ import"./cli-5c2j5yvx.js";
 import"./cli-1a2j50m0.js";
 import"./cli-f9w1semm.js";
 import"./cli-ej6gbxfb.js";
-import"./cli-g3qgrzck.js";
+import"./cli-zsh093hk.js";
 import"./cli-sd0mxa3c.js";
 import"./cli-w5e1d1vv.js";
-import"./cli-1d3w4xm3.js";
+import"./cli-4r1sjfc4.js";
 import"./cli-zf8jjwex.js";
-import"./cli-qt5wzq6v.js";
+import"./cli-wt7ccy4r.js";
 import {
   __toESM
 } from "./cli-bc05qbss.js";
 
 // src/be/seed-scripts/index.ts
+init_db2();
 init_db();
 
 // src/be/seed-scripts/catalog/app-sync-run.ts
@@ -5721,7 +5719,7 @@ import { join } from "node:path";
 // templates/skills/agent-browser/config.json
 var config_default = `{
   "category": "skills",
-  "description": "Drive a real browser with the agent-browser CLI (headless Chromium over CDP). Use for any browser task: verifying a UI change, taking a screenshot, walking a web page, filling a form, extracting page text, reproducing a frontend bug, or attaching UI evidence to a PR, issue, Linear comment, or Slack thread. Starts with a \`command -v agent-browser\` check and falls back to manual QA on the slim worker image. Screenshots are shared through agent-fs signed URLs. This is the only browser automation tool; do not use qa-use.",
+  "description": "Drive a real browser with the agent-browser CLI (headless Chromium over CDP). Use for any browser task: verifying a UI change, taking a screenshot, walking a web page, filling a form, extracting page text, reproducing a frontend bug, or attaching UI evidence to a PR, issue, Linear comment, or Slack thread. Starts with a \`command -v agent-browser\` check and falls back to manual QA on the slim worker image. Screenshots are kept on agent-fs and embedded in GitHub as user attachments. This is the only browser automation tool; do not use qa-use.",
   "displayName": "Agent Browser",
   "kind": "skill",
   "name": "agent-browser",
@@ -5736,7 +5734,7 @@ var config_default = `{
 `;
 
 // templates/skills/agent-browser/content.md
-var content_default = '# agent-browser\n\n`agent-browser` (vercel-labs) is the swarm\'s browser-automation CLI. It drives a headless Chromium over CDP and returns accessibility-tree snapshots with compact `@eN` refs. Use it for any browser task: verify a UI change, take a screenshot, walk a page, fill a form, extract page text, reproduce a frontend bug, or attach UI evidence to a PR, issue, Linear comment, or Slack thread.\n\nDo not use `qa-use`. It is not installed in the worker image any more.\n\n## Step 0: check that the CLI is present\n\nThe full worker image (`agent-swarm-worker:latest`) ships `agent-browser` and a headless Chromium. The slim image (`:slim`) has neither. The first command of any browser work is:\n\n```bash\ncommand -v agent-browser\n```\n\nIf it prints nothing, you are on the slim image. Say so in your progress report ("agent-browser is not available on this worker image") and fall back to manual QA: write the exact steps a human should run and mark the browser test cases as **Blocked**, not failed. Do not install a browser or the CLI yourself.\n\n## Step 1: load the version-matched guide\n\nThe CLI bundles its own usage guide. Load it once per task before the first browser command. Do not guess flags from memory.\n\n```bash\nagent-browser skills get core          # overview + common patterns\nagent-browser skills get core --full   # adds the full command reference\nagent-browser skills list              # specialized guides (dogfood, electron, slack, ...)\n```\n\n## Step 2: the core loop\n\n```bash\nagent-browser open <url>\nagent-browser snapshot -i              # accessibility tree, interactive elements only, @eN refs\nagent-browser click @e12               # act on refs from the snapshot\nagent-browser fill @e7 "text"\nagent-browser screenshot /tmp/<name>.png\nagent-browser close\n```\n\n- Re-run `snapshot` after every navigation or state change. Refs are only valid for the snapshot that produced them.\n- Run one browser session at a time. Call `store-progress` between page batches so the heartbeat watchdog sees you.\n- The browser is headless. Local servers inside the worker container are reachable at `http://localhost:<port>`.\n- The image launches Chromium with `--no-sandbox,--disable-dev-shm-usage` through `AGENT_BROWSER_ARGS`. If you pass your own `--args`, include `--no-sandbox` again or Chrome will not start.\n\n## Recording\n\nDefault: record with `--cursor`, drive every supported pointer action (`click`, `mouse move`, `drag`) with `--human`, and ship the **1.5x video**. Keep the 1x original only if a reviewer asks for it. Human pointer movement follows an eased curve; use `--seed <n>` on `mouse move` to make the take reproducible instead of using a bare move.\n\nOpen the page first, then record the interaction:\n\n```bash\nagent-browser record start ./in.mp4 --cursor\nagent-browser snapshot -i\nagent-browser mouse move 600 400 --human --seed 42 --duration 1400\nagent-browser click @e3 --human          # use a ref from the current snapshot\n# Perform the remaining QA steps; use --human for drag actions too.\nagent-browser record stop\nffmpeg -y -i in.mp4 -filter:v "setpts=PTS/1.5,fps=30" -an \\\n  -c:v libx264 -preset veryfast -crf 23 -pix_fmt yuv420p out-1.5x.mp4\n```\n\nSpeed-up is a post-process step: `record start` has no speed or human flag. Keep `fps=30` to preserve a steady 30 fps output rather than uneven frame drops at an inferred rate. `-an` disables audio because agent-browser recordings carry no audio track. The worker ships only `ffmpeg`, not `ffprobe`; inspect duration with `ffmpeg -i out-1.5x.mp4 2>&1 | grep Duration`.\n\nAdd `--contact-sheet` to the start command for a timestamped PNG summary of visual changes. Recording needs `ffmpeg` on PATH; check `agent-browser doctor` before starting. Stop the recording before closing the browser so the video is saved. Upload the 1.5x file through the same agent-fs QA path as screenshots below, and link it in the PR body.\n\n## Step 3: share the screenshot through agent-fs\n\nScreenshots on the worker disk disappear with the task. Upload them to agent-fs under the qa path convention. Use `share-create` when a person needs to open the file, and `signed-url` for raw embeds such as an image in GitHub PR markdown. `--file` is binary-safe. `--content` is text-only and mangles PNGs.\n\n```bash\nagent-fs write thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png \\\n  --file /tmp/<name>.png -m "<what it shows>"\nagent-fs stat thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png --json        # confirm size > 0\nagent-fs share-create thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png --json\nagent-fs signed-url thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png --json  # raw URL for embeds; 24h default, --expires-in up to 7d\n```\n\n- Embed the signed URL as `![caption](<url>)` in the PR body, review comment, Linear comment, or Slack message.\n- In `store-progress`, list the upload in the `attachments` field with `kind: "agent-fs"` and the path, and paste the `share-create` link for people who need to open the file.\n- If `agent-fs auth whoami` fails, report the local path, say the upload was skipped, and continue.\n\nThe `artifacts` skill holds the full agent-fs recipe and the naming conventions.\n\n## Gotchas\n\n- `wait <selector>` waits for a VISIBLE match. When the first match is hidden it times out (about 25 s) even though the element exists. Wait on rendered text instead: `wait --text "<rendered text>"`.\n- Never run `pkill -f <pattern>` inside a Bash call: the pattern also matches the calling shell\'s command line and kills it. Record the PID when you start a background server (`echo $!`) and `kill <pid>`.\n';
+var content_default = '# agent-browser\n\n`agent-browser` (vercel-labs) is the swarm\'s browser-automation CLI. It drives a headless Chromium over CDP and returns accessibility-tree snapshots with compact `@eN` refs. Use it for any browser task: verify a UI change, take a screenshot, walk a page, fill a form, extract page text, reproduce a frontend bug, or attach UI evidence to a PR, issue, Linear comment, or Slack thread.\n\nDo not use `qa-use`. It is not installed in the worker image any more.\n\n## Step 0: check that the CLI is present\n\nThe full worker image (`agent-swarm-worker:latest`) ships `agent-browser` and a headless Chromium. The slim image (`:slim`) has neither. The first command of any browser work is:\n\n```bash\ncommand -v agent-browser\n```\n\nIf it prints nothing, you are on the slim image. Say so in your progress report ("agent-browser is not available on this worker image") and fall back to manual QA: write the exact steps a human should run and mark the browser test cases as **Blocked**, not failed. Do not install a browser or the CLI yourself.\n\n## Step 1: load the version-matched guide\n\nThe CLI bundles its own usage guide. Load it once per task before the first browser command. Do not guess flags from memory.\n\n```bash\nagent-browser skills get core          # overview + common patterns\nagent-browser skills get core --full   # adds the full command reference\nagent-browser skills list              # specialized guides (dogfood, electron, slack, ...)\n```\n\n## Step 2: the core loop\n\n```bash\nagent-browser open <url>\nagent-browser snapshot -i              # accessibility tree, interactive elements only, @eN refs\nagent-browser click @e12               # act on refs from the snapshot\nagent-browser fill @e7 "text"\nagent-browser screenshot /tmp/<name>.png\nagent-browser close\n```\n\n- Re-run `snapshot` after every navigation or state change. Refs are only valid for the snapshot that produced them.\n- Run one browser session at a time. Call `store-progress` between page batches so the heartbeat watchdog sees you.\n- The browser is headless. Local servers inside the worker container are reachable at `http://localhost:<port>`.\n- The image launches Chromium with `--no-sandbox,--disable-dev-shm-usage` through `AGENT_BROWSER_ARGS`. If you pass your own `--args`, include `--no-sandbox` again or Chrome will not start.\n\n## Recording\n\nDefault: record with `--cursor`, drive every supported pointer action (`click`, `mouse move`, `drag`) with `--human`, and ship the **1.5x video**. Keep the 1x original only if a reviewer asks for it. Human pointer movement follows an eased curve; use `--seed <n>` on `mouse move` to make the take reproducible instead of using a bare move.\n\nOpen the page first, then record the interaction:\n\n```bash\nagent-browser record start ./in.mp4 --cursor\nagent-browser snapshot -i\nagent-browser mouse move 600 400 --human --seed 42 --duration 1400\nagent-browser click @e3 --human          # use a ref from the current snapshot\n# Perform the remaining QA steps; use --human for drag actions too.\nagent-browser record stop\nffmpeg -y -i in.mp4 -filter:v "setpts=PTS/1.5,fps=30" -an \\\n  -c:v libx264 -preset veryfast -crf 23 -pix_fmt yuv420p out-1.5x.mp4\n```\n\nSpeed-up is a post-process step: `record start` has no speed or human flag. Keep `fps=30` to preserve a steady 30 fps output rather than uneven frame drops at an inferred rate. `-an` disables audio because agent-browser recordings carry no audio track. The worker ships only `ffmpeg`, not `ffprobe`; inspect duration with `ffmpeg -i out-1.5x.mp4 2>&1 | grep Duration`.\n\nAdd `--contact-sheet` to the start command for a timestamped PNG summary of visual changes. Recording needs `ffmpeg` on PATH; check `agent-browser doctor` before starting. Stop the recording before closing the browser so the video is saved. Keep the 1.5x file on the same agent-fs QA path as screenshots below. In a PR, upload it as a GitHub user attachment and put the URL on its own line, so GitHub plays it inline.\n\n## Step 3: share the screenshot through agent-fs\n\nScreenshots on the worker disk disappear with the task. Upload them to agent-fs under the qa path convention: that copy is the durable original. Use `share-create` when a person needs to open the file. `--file` is binary-safe. `--content` is text-only and mangles PNGs.\n\n```bash\nagent-fs write thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png \\\n  --file /tmp/<name>.png -m "<what it shows>"\nagent-fs stat thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png --json        # confirm size > 0\nagent-fs share-create thoughts/<agent-id>/qa/<topic>-screenshots/<name>.png --json\n```\n\n- **GitHub PR body or comment**: upload the PNG, GIF or mp4 as a GitHub user attachment with the `github-attach` skill and embed `![caption](https://github.com/user-attachments/assets/<uuid>)`. Attachments never expire and mp4s play inline. A UI PR puts a before (main) and after pair in the `## Before / after` table. Fallback for images only, when the GitHub token is an App token (`ghu_`/`ghs_`): `agent-fs signed-url <path> --inline --json` (expires in 7 days). Never a presigned URL for an mp4 or a doc: it downloads.\n- **Linear comment or Slack message**: paste the `share-create` link.\n- In `store-progress`, list the upload in the `attachments` field with `kind: "agent-fs"` and the path, and paste the `share-create` link for people who need to open the file.\n- If `agent-fs auth whoami` fails, report the local path, say the upload was skipped, and continue.\n\nThe `artifacts` skill holds the full agent-fs recipe and the naming conventions.\n\n## Gotchas\n\n- `wait <selector>` waits for a VISIBLE match. When the first match is hidden it times out (about 25 s) even though the element exists. Wait on rendered text instead: `wait --text "<rendered text>"`.\n- Never run `pkill -f <pattern>` inside a Bash call: the pattern also matches the calling shell\'s command line and kills it. Record the PID when you start a background server (`echo $!`) and `kill <pid>`.\n';
 
 // templates/skills/apps/config.json
 var config_default2 = `{
@@ -5877,12 +5875,19 @@ agent-fs stat thoughts/<agent-id>/qa/<topic>-screenshots/login.png --json | jq '
 \`\`\`
 
 Capture with \`agent-browser screenshot <path>\` when it is installed, otherwise
-Playwright, ffmpeg, or a system screenshot tool. For an image that must render
-inside a PR body or a Slack message without a login, use a presigned URL
-instead of the viewer link:
+Playwright, ffmpeg, or a system screenshot tool. The agent-fs copy is the
+durable original. Where each kind of content goes:
+
+| Content | Use | Why |
+|---|---|---|
+| Image or GIF in GitHub | GitHub user attachment (\`github-attach\` skill) | Permanent, renders inline, short URL |
+| Video (mp4) in GitHub | GitHub user attachment, else an \`agent-fs share-create\` link | GitHub plays it inline. A presigned link downloads it |
+| Doc (plan, research, report) | \`agent-fs share-create <path> --expires-in 604800\` | Preview page, no download |
+| Durable pointer | \`live.agent-fs.dev\` path, in a PR only under \`## Swarm provenance\` | Share links die after 7 days, this one does not (needs login) |
+| Presigned \`signed-url\` | Image fallback only, with \`--inline\` | Downloads and expires after 7 days. Never for docs or mp4s |
 
 \`\`\`bash
-agent-fs signed-url thoughts/<agent-id>/qa/<topic>-screenshots/login.png --json   # 24h default, --expires-in up to 7d
+agent-fs signed-url thoughts/<agent-id>/qa/<topic>-screenshots/login.png --inline --json   # fallback only; 24h default, --expires-in up to 7d
 \`\`\`
 
 ## Naming conventions
@@ -5898,9 +5903,12 @@ misc/<agent-id>/<task-id>-<description>.ext
 
 ## Attaching artifacts
 
-- **PR body** — embed \`![caption](<resolved-share-url>)\` after resolving and
-  printing the concrete URL as shown above.
-- **Slack** — link the agent-fs URL (team members only, the live viewer needs a login). Use a signed URL (\`agent-fs signed-url\`, up to 7 days) for anyone else.
+- **PR body** — embed images and mp4s as GitHub user attachments
+  (\`![caption](https://github.com/user-attachments/assets/<uuid>)\`), and link docs
+  with \`share-create\`. Never embed a \`share-create\` link as an image: it is an
+  HTML preview page. Swarm task links and durable agent-fs paths go only under
+  \`## Swarm provenance\`.
+- **Slack** — link the agent-fs URL (team members only, the live viewer needs a login). Use a \`share-create\` link (up to 7 days) for anyone else.
 - **\`store-progress\`** — use the \`attachments\` field with \`kind: "agent-fs"\` and the path.
 - **Linear comments** — paste the live URL in the comment body.
 
@@ -9129,7 +9137,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.).
@@ -9137,8 +9147,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
@@ -9148,7 +9159,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
@@ -9702,7 +9714,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
@@ -9725,7 +9737,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
@@ -11975,8 +11987,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
@@ -12029,7 +12041,7 @@ Afterwards, a \`warnings\` entry on \`create-workflow\` or a patch tool means th
 }
 \`\`\`
 
-- \`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.
@@ -12038,7 +12050,7 @@ Afterwards, a \`warnings\` entry on \`create-workflow\` or a patch tool means th
 - \`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\`
 
@@ -12278,7 +12290,7 @@ For complete command documentation with all flags and options, see [COMMANDS.md]
 `;
 
 // src/be/seed-skills/index.ts
-init_db();
+init_db2();
 // src/be/seed-skills/bundled-files.generated.json
 var bundled_files_generated_default = {
   artifacts: [
@@ -15081,7 +15093,7 @@ var skillsSeeder = {
 };
 
 // src/be/seed/state-db.ts
-init_db();
+init_db2();
 async function getSeedState(kind, key) {
   return getDbClient().get("SELECT kind, key, seededHash, seededAt FROM seed_state WHERE kind = ? AND key = ?", [kind, key]);
 }
@@ -16476,7 +16488,7 @@ var config_default63 = `{
 var content_default63 = '# Weekly Harness Upgrade Check\n\nThis is a topology-preserving, anonymized port of the live Sunday schedule. It keeps its bundle, deduplication, baseline, partial-fallback, and CI acceptance behavior.\n\n```json\n{"cron":"0 16 * * 0","timezone":"UTC","agentRole":"lead","enabled":true}\n```\n\n**Weekly Harness Upgrade — self-hosted repository Dockerfile.worker**\n\nRepo: `{{REPO_URL}}` (working dir: `/workspace/repo`)\nFile: `Dockerfile.worker`\n\nThe worker image pins these harnesses via `ARG`. Each week, check upstream for new versions and open ONE PR bundling ALL outdated harness bumps together ({{PR_REVIEWER}}\'s preference — bump ALL in one PR per run, do NOT stagger one-per-run).\n\n| ARG | Source | Sync requirement |\n|---|---|---|\n| `CLAUDE_CODE_VERSION` | npm `@anthropic-ai/claude-code` | none |\n| `PI_CODING_AGENT_VERSION` | npm `@earendil-works/pi-coding-agent` | MUST match `@earendil-works/pi-agent-core`, `@earendil-works/pi-ai`, and `@earendil-works/pi-coding-agent` in `package.json` (family-pin, all same version) — bump all together |\n| `CODEX_VERSION` | npm `@openai/codex` | MUST match direct `@openai/codex` in `package.json` (enforced by `scripts/check-codex-default-model.sh`) |\n| `OPENCODE_VERSION` | https://opencode.ai (latest release) | MUST match `OPENCODE_SDK_VERSION` |\n| `OPENCODE_SDK_VERSION` | npm `@opencode-ai/sdk` | MUST match `OPENCODE_VERSION` — bump both together |\n\n## Steps\n\n1. `cd /workspace/repo && git fetch origin && git checkout main && git pull --ff-only`\n2. Read current pinned versions from `Dockerfile.worker` (the `ARG` lines) and from `package.json` (for the pi family + `@openai/codex` + `@opencode-ai/sdk`).\n3. For each harness, fetch the latest version:\n   - npm claude-code: `npm view @anthropic-ai/claude-code version`\n   - npm pi: `npm view @earendil-works/pi-coding-agent version` (use the SAME version for `@earendil-works/pi-agent-core` and `@earendil-works/pi-ai` — they\'re a family pin)\n   - npm codex: `npm view @openai/codex version`\n   - npm opencode-sdk: `npm view @opencode-ai/sdk version`\n   - opencode: `curl -fsSL https://api.github.com/repos/sst/opencode/releases/latest | jq -r .tag_name`\n4. Check for an existing open bundled PR — `gh pr list --search "harness upgrade in:title" --state open --repo {{REPO_URL}}`. Look at the branch prefix `harness-upgrade/`. If one is already open AND was created within the last 48h (sibling schedule may have just opened it), skip and complete with `"Skipped: sibling harness upgrade PR already open"` + the existing PR URL.\n5. Collect ALL outdated harnesses. If none are outdated, complete with output `"All harnesses up to date as of YYYY-MM-DD"` (no PR).\n6. Branch: `harness-upgrade/weekly-YYYY-MM-DD` (e.g. `harness-upgrade/weekly-2026-06-03`).\n7. Edit `Dockerfile.worker` — bump every outdated ARG. Also update `package.json`:\n   - Codex: bump direct `@openai/codex` to match `CODEX_VERSION`.\n   - Pi family: bump `@earendil-works/pi-agent-core`, `@earendil-works/pi-ai`, and `@earendil-works/pi-coding-agent` to the same new version as `PI_CODING_AGENT_VERSION`.\n   - Opencode: bump `OPENCODE_SDK_VERSION` and `@opencode-ai/sdk` to match `OPENCODE_VERSION`.\n   Then re-run `bun install` so `bun.lock` updates.\n8. Local verification (all must pass before pushing):\n   ```bash\n   bun install --frozen-lockfile\n   bun run lint\n   bun run tsc:check\n   bun test\n   bash scripts/check-db-boundary.sh\n   ```\n   For Codex bumps: also run `bash scripts/check-codex-default-model.sh`.\n   Note: do NOT run `docker build -f Dockerfile.worker .` locally — the runner lacks docker. CI\'s `docker-worker-build` job is the acceptance gate.\n9. If any local check fails, apply the **partial-bundle fallback** before giving up — one harness must never block the others:\n   **BASELINE FIRST — do this before ANY isolation work.** A red gate does NOT mean the bumps broke anything. Re-run the EXACT failing command on a pristine `origin/main` worktree with zero bumps applied (`git worktree add /tmp/hb-baseline origin/main && cd /tmp/hb-baseline && bun install --frozen-lockfile`) and compare. If the SAME checks fail with the SAME assertions and the same pass/skip/fail totals, the failure is **PRE-EXISTING and unrelated to the bumps** ⇒ it does NOT block this PR, and you must NOT attempt isolation for it. Proceed to step 10, open the PR, and add a `## Pre-existing failures (also fail on origin/main)` section quoting the verbatim error plus both totals (baseline vs branch) so the reviewer can see they match. Only a failure that is RED on your branch and GREEN on baseline was caused by a bump — apply a–d below to that failure ONLY. A gate that is red on origin/main is never a reason to skip the weekly bump.\n   a. Isolate which harness\'s bump caused it. The error usually names the package; if not, revert bumps one at a time until the step-8 gate passes.\n   b. Revert ONLY that harness — its `Dockerfile.worker` ARG **and** its `package.json` pins (respect the family/sync requirements in the table above) — then re-run `bun install` and the FULL step-8 gate.\n   c. Gate green ⇒ open the PR with the remaining harnesses and add a `## Held back` section naming the excluded harness, current → attempted version, and the VERBATIM error. Name it in your `store-progress` output too.\n   d. Gate still red with that harness reverted, OR the failure cannot be isolated to one harness ⇒ do NOT open a PR; report via `store-progress` with `failureReason`.\n   Migrating an upstream API break (a removed option, a renamed export, a moved type) is still OUT OF SCOPE for this routine — hold that harness back per (c) rather than changing code here.\n10. Push the branch and open a PR:\n    - Title: `chore(docker): bump harnesses (weekly YYYY-MM-DD)` — or list the bumps, e.g. `chore(docker): bump claude-code, pi, opencode (weekly YYYY-MM-DD)`.\n    - Body: include a table of current → new versions for every harness bumped, link to each upstream changelog (e.g. https://github.com/anthropics/claude-code/releases/tag/v<X.Y.Z>), and the local verification output (or "all green").\n    - Add `{{PR_REVIEWER}}` as a reviewer.\n    - DO NOT merge — {{PR_REVIEWER}} reviews and merges.\n11. Verify CI on the PR — wait for the merge-gate workflow to start, confirm at least the `docker-worker-build` job is queued/passing. If CI fails, comment on the PR with the failure log and leave the branch for human review.\n\n## Constraints\n\n- **ONE bundled PR per run.** Bump every outdated harness in the same PR — do not stagger one-per-run. The ONLY permitted exclusion is a harness held back by the step-9 partial-bundle fallback, which must be declared in the PR body.\n- **No `--no-verify`, no force pushes.**\n- If a harness has a major-version bump (e.g. 2.x → 3.x), still bundle it but flag clearly in the PR description that this is a major bump and may need extra review.\n- Pi family-pin: all three pi packages MUST be the same version. If they drift in the lockfile, fix the drift in the same PR.\n\n## Sibling-schedule coordination\nThis schedule has a sibling — `weekly-harness-upgrade-check-wed` (Wednesday 05:00 BCN). If a sibling-opened PR is OPEN and `< 48h` old, step 4 skips. This is the dedup gate. Don\'t change branch-naming heuristics in a way that breaks the dedup.\n\n## Output\n\n`store-progress` with `status: "completed"` and `output` containing:\n- The PR URL (if one was opened) + the table of harnesses bumped, OR\n- "No-op: all harnesses up to date as of YYYY-MM-DD" with the version table, OR\n- "Skipped: sibling harness upgrade PR already open" with the existing PR URL.\n';
 
 // src/be/seed/schedules-seeder.ts
-init_db();
+init_db2();
 
 // src/be/seed/automation-toggle.ts
 var SEED_AUTOMATIONS_ENABLED_ENV = "SEED_AUTOMATIONS_ENABLED";
@@ -16922,7 +16934,7 @@ The \`maxIterations\` parameter is declarative: the reviewer signals PASS when d
 `;
 
 // src/be/seed/workflows-seeder.ts
-init_db();
+init_db2();
 var asText2 = (value) => value;
 var BUILT_IN_WORKFLOW_SOURCES = [
   { config: asText2(config_default64), content: asText2(content_default64) },