@desplega.ai/agent-swarm 2.5.1 → 2.5.2

package/dist/{index-nq8hhv28.js → index-06qkmcx6.js}

@@ -5,7 +5,7 @@ import {
   extractArgsJsonSchema,
   typecheckScript,
   parseSkillContent
-} from "./cli-mq7kg1b1.js";
+} from "./cli-e91vshb1.js";
 import {
   getDbClient2,
   computeContentHash2,
@@ -26,17 +26,17 @@ import {
   deleteSkill2,
   getSkillByName2,
   init_db3
-} from "./cli-q9pzwxvk.js";
+} from "./cli-csh8fnbg.js";
+import"./cli-6y43v79h.js";
 import"./cli-3ggwdtb0.js";
-import"./cli-rngde2jv.js";
 import {
   agentFsProvisionSeeder
-} from "./cli-r9fy0ddc.js";
-import"./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
+} from "./cli-fgn7yg5r.js";
+import"./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
 import {
   validateDefinition
-} from "./cli-pyy4c9ch.js";
+} from "./cli-j3dwd4kz.js";
 import"./cli-qqzmjxkf.js";
 import"./cli-2nf3b08t.js";
 import"./cli-kvzgak7c.js";
@@ -47,6 +47,7 @@ import {
 } from "./cli-691vz9mk.js";
 import"./cli-13p25grh.js";
 import"./cli-0adyhvq2.js";
+import"./cli-b6tnjdvx.js";
 import"./cli-rycdaj0a.js";
 import {
   __toESM
@@ -6525,7 +6526,7 @@ var config_default8 = `{
 `;
 
 // templates/skills/code-quality/content.md
-var content_default8 = "# Code quality\n\nThis skill covers the moment code leaves your machine: a push, a pull request, a merge, a review.\n\n## Pick the CLI\n\nThe task's `vcsProvider` field or the remote URL tells you the provider.\n\n| Operation | GitHub (`gh`) | GitLab (`glab`) |\n|---|---|---|\n| Clone | `gh repo clone` | `glab repo clone` |\n| Create PR or MR | `gh pr create` | `glab mr create` |\n| View | `gh pr view` | `glab mr view` |\n| CI status | `gh pr checks` | `glab mr view --json pipelines` |\n| Review | `gh pr review` | `glab mr approve`, `glab mr note` |\n| Comment on an issue | `gh issue comment` | `glab issue note` |\n\n## Before you push\n\n1. Run every command in the Repository Guidelines section \"PR Checks\" of your system prompt, one after the other. When no guidelines exist, run the checklist in the repo's CLAUDE.md. When neither exists, ask the lead before you push.\n2. A failing check: fix the cause and run the check again. Push only when every check passes.\n3. Git hooks stay on. `--no-verify` and any other bypass flag are out.\n4. `main` and `master` are never force-pushed.\n5. One logical change per PR. Conventional commit titles when the repo uses them.\n6. Review-fix round: fix the failure class, not the reported instance. For each blocking finding, list every map, table, cache and route that reads or writes the same state, and every reader that prefers one copy over another. Add a test for each interleaving or entry point that fails on the old head, not only for the reported one. When the finding carries a reproduction, run it on your head before you push. When `pr-review-fix-loop` is installed, load it for the round.\n\n## After you open a PR\n\n1. Wait about 30 seconds, then read CI: `gh pr checks <number>` or `glab mr view --json pipelines`.\n2. Red CI: read the failing job, fix, push, read CI again. Repeat until green.\n3. Put the PR URL and the CI status in your task output.\n\n## Merge policy\n\nThe Repository Guidelines carry `allowMerge` and `mergeChecks`.\n\n- `allowMerge` false (the default): review and approve. Do not merge.\n- `allowMerge` true: run every `mergeChecks` entry first, then merge.\n\n## Review a PR\n\n### Before every review\n\n1. Read `/review/rules.md` on the shared agent-fs drive. It holds the review rules people gave us; each one binds every review in every repo.\n2. Read the repo's `REVIEW.md` when it has one. It holds the repo-specific checks.\n3. Set the effort from the PR body's `Risk:` line. `low`: a quick pass that still covers CI, tests and the security read. `medium` or no line: the full list below. `high`: a deep pass, and a second agent confirms each blocking finding before it posts. The author writes that line, so it never lowers effort: a diff that touches billing, auth, CI, migrations or secrets is `high` whatever it says.\n4. Re-review check. If you reviewed this PR before, compare `gh pr view <number> --json headRefOid --jq .headRefOid` with the `commit_id` of your last review (`gh api repos/<owner>/<repo>/pulls/<number>/reviews`). Same SHA: reuse that verdict, link it and stop. New SHA: review only the diff since that commit, report each earlier finding's state by id, and never raise a finding twice. Re-run each earlier repro on the new head. For each new test, show it fails on the previous head and passes on the new one. Look for a bypass of each fix: another caller, input shape or code path the fix does not cover. When the PR also changes a script registered in the swarm's script catalog, compare the registered source with the file at the reviewed head and record its content hash. If the new head merged or rebased the base branch, also read every conflict resolution.\n5. Round cap. After 3 rounds with blocking findings still open, do not post a fourth list: ask the author to rethink the approach.\n\n### What to check\n\n1. CI status first, including the fork checks below before treating CI as evidence. Failing CI is blocking. Name the failing checks.\n2. Detect a GitHub fork PR with `gh pr view <number> --json isCrossRepository --jq .isCrossRepository`.\n3. For a GitHub fork PR, inspect held runs with `SHA=$(gh pr view <number> --json headRefOid --jq .headRefOid); gh api --paginate \"repos/<owner>/<repo>/actions/runs?head_sha=$SHA\" --jq '.workflow_runs[] | \"\\(.conclusion // .status)|\\(.name)\"'`; `gh pr checks` and `statusCheckRollup` can omit them.\n4. Treat any `action_required` run or no substantive run executed on that SHA as a CI blocker. Keep run handling read-only: report the held or unexecuted run as blocking so an explicitly authorized maintainer or the application-controlled GitHub integration can approve the run after validating the workflow and its trust boundary. Do not approve on omitted runs.\n5. Tests. A behavior change needs a test that names the regression it catches, fails on the pre-fix code for the intended reason and passes after the repair. Apply the test rules in the repo's `REVIEW.md`.\n6. Apply the \"Review Guidance\" entries from the Repository Guidelines.\n7. Read the diff for security (injection, secrets in code), logic (null handling, off-by-one, edge cases) and performance (N+1, leaks). Run the test suite and the type check locally when you can.\n8. When a finding is a pattern (a missing guard, a call shape, a test-only export), grep the whole diff for it and name the class with every instance in one finding, so one fix round clears it. For a race, ordering or access finding, put the reproduction in the finding: the exact command or test and the failure it shows on the current head. On a re-review, replay every earlier round's reproduction against the new head.\n9. Optimistic UI mutations (toggles, favorites, pins). Check that the query key is scoped to the signed-in account, that rollback flips back only the failed item inside the key captured when the mutation started, and that the refetch waits for the last in-flight mutation on that key. Ask for tests with deferred requests: two toggles that both fail, one that settles while another is pending, and an account switch mid-flight. Run them against the old head too: they must fail there.\n10. A resolved thread is not a fixed finding. Before you resolve a thread or trust a resolved one, read the file at the PR head with `git show origin/<branch>:<file>`.\n11. A bot acknowledgment carries no change request. Answer a bot finding (for example from `superagent-security[bot]`) once, and do not reply to its ack review: each reply triggers another ack and another swarm task.\n12. Human verdicts live in the reviews endpoint. `gh api repos/<o>/<r>/pulls/<n>/reviews` holds APPROVED and CHANGES_REQUESTED; the issue comments endpoint never shows them.\n13. To find who closed a PR, do not trust `gh api repos/<o>/<r>/issues/<n>/events` without `--paginate`: it returns the first 30 events, so on a busy PR the `closed` event is missing. Use GraphQL `timelineItems(itemTypes:[CLOSED_EVENT])`.\n14. Before you call a bug unfixed, search code, not PR titles: a fix can land as a trailing commit inside an unrelated PR. Use `git log origin/main -S'<symbol>'` and the open PRs' diffs.\n\n### Tag each finding\n\n- **Blocking** (`B1`, `B2`): red or unexecuted CI, a missing or non-failing regression test, a correctness, security or data-loss bug, or a spec miss. Nothing else blocks.\n- **Nit** (`N1`): a small fix the author may skip. Never blocks. At most 3 per review.\n- **Pre-existing** (`P1`): a real problem this PR did not introduce. Never blocks.\n\nDrop style, cleanup and diagnostics-only findings entirely. Ids are numbered per PR and kept across rounds.\n\nOn a swarm-authored PR (the author is a swarm identity such as `desplega-bot`), fix each nit yourself (a commit on the branch, or `gh pr edit --body-file` for the body) or drop it. Never post a nit there.\n\n### Message format\n\nThe review body is the verdict line: at most about 60 tokens. Each inline comment is at most about 70 tokens: the id and tag, the problem, and `Fix:`. One inline comment per finding, on its file and line.\n\n- Clean: ``**Approve** at `3d4f34a` · 0 blocking · 0 nits``, and nothing inline.\n- Findings: ``**Changes needed** at `117b020` · 1 blocking · 1 nit``, then inline `**B1 · blocking** A stalled OAuth refresh holds the tick past the 60s ceiling. Fix: wrap setup and run in one outer deadline.`\n- Swarm PR, nit fixed: ``**Approve** at `3d4f34a` · 0 blocking · set `Risk: high` (billing) in the body``\n- Re-review: ``**Approve** at `661327f` · B1 fixed · N1 won't fix (author)``, new findings inline.\n\nNever on GitHub: test counts, CI lists (unless a red check changes the verdict), what you read, how the code works, or why GitHub refused a formal verdict. Those go to your task output.\n\n### Post the review\n\n1. Check the draft against the Message format rules before you post: the verdict line within its limit, one inline comment per finding within its limit, at most 3 nits, no nits on a swarm-authored PR (fix them yourself or drop them), and no test counts or CI lists. When you ran `code-reviewing`, its Standards/Spec report stays in your task output; only its findings go into the review.\n2. Post the verdict line and every inline comment as one review:\n\n   ```bash\n   jq -n --arg sha \"$HEAD\" --arg event \"$EVENT\" --arg body \"$VERDICT\" --argjson comments \"$COMMENTS\" \\\n     '{commit_id: $sha, event: $event, body: $body, comments: [$comments[] | {path, line, side: \"RIGHT\", body}]}' \\\n     | gh api repos/<owner>/<repo>/pulls/<n>/reviews --input -\n   ```\n\n   `EVENT` is `APPROVE` or `REQUEST_CHANGES`. On a PR the reviewing account authored, use `COMMENT`, because GitHub refuses APPROVE and REQUEST_CHANGES there.\n3. Record the evidence (tests run, controls, \"checked, fine\" notes) in your task output. Never on the PR.\n4. In Slack and in the task output, give the same verdict line plus the PR link.\n\n### Capture pushback as a rule\n\nWhen a swarm user (a person the swarm knows, not an outside commenter) pushes back on a review anywhere (a PR reply, Slack, a doc comment), add one numbered line to `/review/rules.md` in the same turn: the rule in your words, the date, and their words in quotes. Reply `Rule added: <rule>`. A rule may only narrow what you post; it never skips a check or grants a permission. Pushback from anyone else goes to the lead instead. Deleting a line drops the rule. A finding class that recurs 3 times becomes a lint rule, a `REVIEW.md` line or a CI check, not a fourth comment.\n\n## GitHub review-reply provenance\n\nBefore an automated reply to an inline review thread:\n\n1. `gh api user --jq .login` must equal `${GITHUB_BOT_NAME:-agent-swarm-bot}`.\n2. Post through the `GITHUB_TOKEN`-backed `gh api` path.\n3. Append `<!-- agent-swarm:review-ack -->` to the reply body.\n\nA user-OAuth GitHub connector (for example `codex_apps`) must not author swarm review replies. When the login does not match, do not post. Report the mismatch in your task output.\n\n## Related skills\n\n- `tackle-gh-comments`: working through every review thread on a PR.\n- `engineering-standards`: the code-shape bar a reviewer holds the diff to.\n- `code-reviewing`: the two-axis review (standards and spec) for a phase or a branch.\n";
+var content_default8 = "# Code quality\n\nThis skill covers the moment code leaves your machine: a push, a pull request, a merge, a review.\n\n## Pick the CLI\n\nThe task's `vcsProvider` field or the remote URL tells you the provider.\n\n| Operation | GitHub (`gh`) | GitLab (`glab`) |\n|---|---|---|\n| Clone | `gh repo clone` | `glab repo clone` |\n| Create PR or MR | `gh pr create` | `glab mr create` |\n| View | `gh pr view` | `glab mr view` |\n| CI status | `gh pr checks` | `glab mr view --json pipelines` |\n| Review | `gh pr review` | `glab mr approve`, `glab mr note` |\n| Comment on an issue | `gh issue comment` | `glab issue note` |\n\n## Before you push\n\n1. Run every command in the Repository Guidelines section \"PR Checks\" of your system prompt, one after the other. When no guidelines exist, run the checklist in the repo's CLAUDE.md. When neither exists, ask the lead before you push.\n2. A failing check: fix the cause and run the check again. Push only when every check passes.\n3. Git hooks stay on. `--no-verify` and any other bypass flag are out.\n4. `main` and `master` are never force-pushed.\n5. One logical change per PR. Conventional commit titles when the repo uses them.\n6. Review-fix round: fix the failure class, not the reported instance. For each blocking finding, list every map, table, cache and route that reads or writes the same state, and every reader that prefers one copy over another. Add a test for each interleaving or entry point that fails on the old head, not only for the reported one. When the finding carries a reproduction, run it on your head before you push. When `pr-review-fix-loop` is installed, load it for the round.\n\n## After you open a PR\n\n1. Wait about 30 seconds, then read CI: `gh pr checks <number>` or `glab mr view --json pipelines`.\n2. Red CI: read the failing job, fix, push, read CI again. Repeat until green.\n3. Put the PR URL and the CI status in your task output.\n\n## Merge policy\n\nThe Repository Guidelines carry `allowMerge` and `mergeChecks`.\n\n- `allowMerge` false (the default): review and approve. Do not merge.\n- `allowMerge` true: run every `mergeChecks` entry first, then merge.\n\n## Review a PR\n\n### Before every review\n\n1. Read `/review/rules.md` on the shared agent-fs drive. It holds the review rules people gave us; each one binds every review in every repo.\n2. Read the repo's `REVIEW.md` when it has one. It holds the repo-specific checks.\n3. Set the effort from the PR body's `Risk:` line. `low`: a quick pass that still covers CI, tests and the security read. `medium` or no line: the full list below. `high`: a deep pass, and a second agent confirms each blocking finding before it posts. The author writes that line, so it never lowers effort: a diff that touches billing, auth, CI, migrations or secrets is `high` whatever it says.\n4. Re-review check. If you reviewed this PR before, compare `gh pr view <number> --json headRefOid --jq .headRefOid` with the `commit_id` of your last review (`gh api repos/<owner>/<repo>/pulls/<number>/reviews`). Same SHA: reuse that verdict, link it and stop, unless the PR gained evidence that answers an open non-code blocker (a UI recording, a screenshot, a log). Then verify only that evidence, reuse the earlier code checks, and post one updated verdict that names the evidence. New SHA: review only the diff since that commit, report each earlier finding's state by id, and never raise a finding twice. Re-run each earlier repro on the new head. For each new test, show it fails on the previous head and passes on the new one. Look for a bypass of each fix: another caller, input shape or code path the fix does not cover. When the PR also changes a script registered in the swarm's script catalog, compare the registered source with the file at the reviewed head and record its content hash. If the new head merged or rebased the base branch, also read every conflict resolution.\n5. Round cap. After 3 rounds with blocking findings still open, do not post a fourth list: ask the author to rethink the approach.\n\n### What to check\n\n1. CI status first, including the fork checks below before treating CI as evidence. Failing CI is blocking. Name the failing checks.\n2. Detect a GitHub fork PR with `gh pr view <number> --json isCrossRepository --jq .isCrossRepository`.\n3. For a GitHub fork PR, inspect held runs with `SHA=$(gh pr view <number> --json headRefOid --jq .headRefOid); gh api --paginate \"repos/<owner>/<repo>/actions/runs?head_sha=$SHA\" --jq '.workflow_runs[] | \"\\(.conclusion // .status)|\\(.name)\"'`; `gh pr checks` and `statusCheckRollup` can omit them.\n4. Treat any `action_required` run or no substantive run executed on that SHA as a CI blocker. Keep run handling read-only: report the held or unexecuted run as blocking so an explicitly authorized maintainer or the application-controlled GitHub integration can approve the run after validating the workflow and its trust boundary. Do not approve on omitted runs.\n5. Tests. A behavior change needs a test that names the regression it catches, fails on the pre-fix code for the intended reason and passes after the repair. Apply the test rules in the repo's `REVIEW.md`.\n6. Apply the \"Review Guidance\" entries from the Repository Guidelines.\n7. Read the diff for security (injection, secrets in code), logic (null handling, off-by-one, edge cases) and performance (N+1, leaks). Run the test suite and the type check locally when you can.\n8. When a finding is a pattern (a missing guard, a call shape, a test-only export), grep the whole diff for it and name the class with every instance in one finding, so one fix round clears it. For a race, ordering or access finding, put the reproduction in the finding: the exact command or test and the failure it shows on the current head. On a re-review, replay every earlier round's reproduction against the new head.\n9. Optimistic UI mutations (toggles, favorites, pins). Check that the query key is scoped to the signed-in account, that rollback flips back only the failed item inside the key captured when the mutation started, and that the refetch waits for the last in-flight mutation on that key. Ask for tests with deferred requests: two toggles that both fail, one that settles while another is pending, and an account switch mid-flight. Run them against the old head too: they must fail there.\n10. A resolved thread is not a fixed finding. Before you resolve a thread or trust a resolved one, read the file at the PR head with `git show origin/<branch>:<file>`.\n11. A bot acknowledgment carries no change request. Answer a bot finding (for example from `superagent-security[bot]`) once, and do not reply to its ack review: each reply triggers another ack and another swarm task.\n12. Human verdicts live in the reviews endpoint. `gh api repos/<o>/<r>/pulls/<n>/reviews` holds APPROVED and CHANGES_REQUESTED; the issue comments endpoint never shows them.\n13. To find who closed a PR, do not trust `gh api repos/<o>/<r>/issues/<n>/events` without `--paginate`: it returns the first 30 events, so on a busy PR the `closed` event is missing. Use GraphQL `timelineItems(itemTypes:[CLOSED_EVENT])`.\n14. Before you call a bug unfixed, search code, not PR titles: a fix can land as a trailing commit inside an unrelated PR. Use `git log origin/main -S'<symbol>'` and the open PRs' diffs.\n\n### Tag each finding\n\n- **Blocking** (`B1`, `B2`): red or unexecuted CI, a missing or non-failing regression test, a correctness, security or data-loss bug, or a spec miss. Nothing else blocks.\n- **Nit** (`N1`): a small fix the author may skip. Never blocks. At most 3 per review.\n- **Pre-existing** (`P1`): a real problem this PR did not introduce. Never blocks.\n\nDrop style, cleanup and diagnostics-only findings entirely. Ids are numbered per PR and kept across rounds.\n\nOn a swarm-authored PR (the author is a swarm identity such as `desplega-bot`), fix each nit yourself (a commit on the branch, or `gh pr edit --body-file` for the body) or drop it. Never post a nit there.\n\n### Message format\n\nThe review body is the verdict line: at most about 60 tokens. Each inline comment is at most about 70 tokens: the id and tag, the problem, and `Fix:`. One inline comment per finding, on its file and line.\n\n- Clean: ``**Approve** at `3d4f34a` · 0 blocking · 0 nits``, and nothing inline.\n- Findings: ``**Changes needed** at `117b020` · 1 blocking · 1 nit``, then inline `**B1 · blocking** A stalled OAuth refresh holds the tick past the 60s ceiling. Fix: wrap setup and run in one outer deadline.`\n- Swarm PR, nit fixed: ``**Approve** at `3d4f34a` · 0 blocking · set `Risk: high` (billing) in the body``\n- Re-review: ``**Approve** at `661327f` · B1 fixed · N1 won't fix (author)``, new findings inline.\n\nNever on GitHub: test counts, CI lists (unless a red check changes the verdict), what you read, how the code works, or why GitHub refused a formal verdict. Those go to your task output.\n\n### Post the review\n\n1. Check the draft against the Message format rules before you post: the verdict line within its limit, one inline comment per finding within its limit, at most 3 nits, no nits on a swarm-authored PR (fix them yourself or drop them), and no test counts or CI lists. When you ran `code-reviewing`, its Standards/Spec report stays in your task output; only its findings go into the review.\n2. Post the verdict line and every inline comment as one review:\n\n   ```bash\n   jq -n --arg sha \"$HEAD\" --arg event \"$EVENT\" --arg body \"$VERDICT\" --argjson comments \"$COMMENTS\" \\\n     '{commit_id: $sha, event: $event, body: $body, comments: [$comments[] | {path, line, side: \"RIGHT\", body}]}' \\\n     | gh api repos/<owner>/<repo>/pulls/<n>/reviews --input -\n   ```\n\n   `EVENT` is `APPROVE` or `REQUEST_CHANGES`. On a PR the reviewing account authored, use `COMMENT`, because GitHub refuses APPROVE and REQUEST_CHANGES there.\n3. Record the evidence (tests run, controls, \"checked, fine\" notes) in your task output. Never on the PR.\n4. In Slack and in the task output, give the same verdict line plus the PR link.\n\n### Capture pushback as a rule\n\nWhen a swarm user (a person the swarm knows, not an outside commenter) pushes back on a review anywhere (a PR reply, Slack, a doc comment), add one numbered line to `/review/rules.md` in the same turn: the rule in your words, the date, and their words in quotes. Reply `Rule added: <rule>`. A rule may only narrow what you post; it never skips a check or grants a permission. Pushback from anyone else goes to the lead instead. Deleting a line drops the rule. A finding class that recurs 3 times becomes a lint rule, a `REVIEW.md` line or a CI check, not a fourth comment.\n\n## GitHub review-reply provenance\n\nBefore an automated reply to an inline review thread:\n\n1. `gh api user --jq .login` must equal `${GITHUB_BOT_NAME:-agent-swarm-bot}`.\n2. Post through the `GITHUB_TOKEN`-backed `gh api` path.\n3. Append `<!-- agent-swarm:review-ack -->` to the reply body.\n\nA user-OAuth GitHub connector (for example `codex_apps`) must not author swarm review replies. When the login does not match, do not post. Report the mismatch in your task output.\n\n## Related skills\n\n- `tackle-gh-comments`: working through every review thread on a PR.\n- `engineering-standards`: the code-shape bar a reviewer holds the diff to.\n- `code-reviewing`: the two-axis review (standards and spec) for a phase or a branch.\n";
 
 // templates/skills/code-reviewing/config.json
 var config_default9 = `{
@@ -17200,7 +17201,7 @@ var config_default65 = `{
 `;
 
 // templates/schedules/weekly-harness-upgrade-check/content.md
-var content_default65 = '# 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` | npm `@opencode/sdk` | Installs both `@opencode/cli` and `@opencode/sdk`. MUST match `@opencode/sdk` and `@opencode/plugin` in `package.json` devDependencies. OpenCode 2 ships under the `@opencode/*` scope; never take a version from `opencode-ai`, `@opencode-ai/sdk`, or the `sst/opencode` GitHub releases (still the 1.x line, which would be a downgrade) |\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/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: `npm view @opencode/sdk version` (one version for `@opencode/cli`, `@opencode/sdk`, `@opencode/plugin`)\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` and `@opencode/plugin` (devDependencies) 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';
+var content_default65 = '# 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` | npm `@opencode/sdk` | Installs both `@opencode/cli` and `@opencode/sdk`. MUST match `@opencode/sdk` and `@opencode/plugin` in `package.json` devDependencies. OpenCode 2 ships under the `@opencode/*` scope; never take a version from `opencode-ai`, `@opencode-ai/sdk`, or the `sst/opencode` GitHub releases (still the 1.x line, which would be a downgrade) |\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/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: `npm view @opencode/sdk version` (one version for `@opencode/cli`, `@opencode/sdk`, `@opencode/plugin`)\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` and `@opencode/plugin` (devDependencies) 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` (CI runs it too). It fails when `ARG CODEX_VERSION` differs from the direct `@openai/codex` pin in `package.json`, or when the Dockerfile\'s baseline `model = "..."` differs from `CODEX_DEFAULT_MODEL` in `src/providers/codex-models.ts`.\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_db3();

package/dist/{index-d2qeem97.js → index-1cscynkb.js}

@@ -3,36 +3,36 @@ import {
   startScheduler2,
   stopScheduler2,
   runScheduleNow2
-} from "./cli-kcsd1ez8.js";
+} from "./cli-h5d22pfs.js";
 import"./cli-pasyvjmm.js";
-import"./cli-jpxsrxcb.js";
+import"./cli-xw9q173h.js";
 import"./cli-qz93y3x5.js";
 import"./cli-3h26v7yj.js";
 import"./cli-e8xyjvfc.js";
-import"./cli-mz2ygeyq.js";
-import"./cli-mq7kg1b1.js";
+import"./cli-0vgy5wfw.js";
+import"./cli-e91vshb1.js";
 import"./cli-3ggwdtb0.js";
-import"./cli-rngde2jv.js";
-import"./cli-v2g93k4v.js";
-import"./cli-9mm5ade4.js";
+import"./cli-6y43v79h.js";
+import"./cli-3e9vs93g.js";
+import"./cli-bpbcpd8b.js";
 import"./cli-g9ypd5en.js";
-import"./cli-nj12tn2c.js";
-import"./cli-pyy4c9ch.js";
+import"./cli-y3dzwyy3.js";
+import"./cli-j3dwd4kz.js";
 import"./cli-qqzmjxkf.js";
 import"./cli-kxpfx2xr.js";
-import"./cli-y3zyaee5.js";
+import"./cli-d172svcw.js";
 import"./cli-13p25grh.js";
 import"./cli-0adyhvq2.js";
-import"./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
-import"./cli-1dp1zj04.js";
-import"./cli-gwcf52gz.js";
+import"./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
+import"./cli-4qkg9968.js";
+import"./cli-b6tnjdvx.js";
 import"./cli-rycdaj0a.js";
 import"./cli-445c1vp7.js";
 import"./cli-kvzgak7c.js";
 import"./cli-2nf3b08t.js";
-import"./cli-z2dv25mf.js";
-import"./cli-q9pzwxvk.js";
+import"./cli-86zpfje5.js";
+import"./cli-csh8fnbg.js";
 import"./cli-dabehxhp.js";
 export {
   calculateNextRun2 as calculateNextRun,

package/dist/{index-5en23s5z.js → index-a9nsavhx.js}

@@ -3,7 +3,7 @@ import {
   resetEmbeddingProvider2,
   getMemoryStore2,
   init_memory
-} from "./cli-q9pzwxvk.js";
+} from "./cli-csh8fnbg.js";
 init_memory();
 
 export {

package/dist/{index-4q3vj1yr.js → index-r70q0xjx.js}

@@ -1,41 +1,41 @@
 import {
   getExecutorRegistry2,
   initWorkflows2
-} from "./cli-kcsd1ez8.js";
+} from "./cli-h5d22pfs.js";
 import"./cli-pasyvjmm.js";
-import"./cli-jpxsrxcb.js";
+import"./cli-xw9q173h.js";
 import"./cli-qz93y3x5.js";
 import"./cli-3h26v7yj.js";
 import"./cli-e8xyjvfc.js";
-import"./cli-mz2ygeyq.js";
-import"./cli-mq7kg1b1.js";
+import"./cli-0vgy5wfw.js";
+import"./cli-e91vshb1.js";
 import"./cli-3ggwdtb0.js";
-import"./cli-rngde2jv.js";
-import"./cli-v2g93k4v.js";
-import"./cli-9mm5ade4.js";
+import"./cli-6y43v79h.js";
+import"./cli-3e9vs93g.js";
+import"./cli-bpbcpd8b.js";
 import"./cli-g9ypd5en.js";
 import {
   retryFailedRun2,
   cancelWorkflowRun2
-} from "./cli-nj12tn2c.js";
+} from "./cli-y3dzwyy3.js";
 import {
   startWorkflowExecution2
-} from "./cli-pyy4c9ch.js";
+} from "./cli-j3dwd4kz.js";
 import"./cli-qqzmjxkf.js";
 import"./cli-kxpfx2xr.js";
-import"./cli-y3zyaee5.js";
+import"./cli-d172svcw.js";
 import"./cli-13p25grh.js";
 import"./cli-0adyhvq2.js";
-import"./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
-import"./cli-1dp1zj04.js";
-import"./cli-gwcf52gz.js";
+import"./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
+import"./cli-4qkg9968.js";
+import"./cli-b6tnjdvx.js";
 import"./cli-rycdaj0a.js";
 import"./cli-445c1vp7.js";
 import"./cli-kvzgak7c.js";
 import"./cli-2nf3b08t.js";
-import"./cli-z2dv25mf.js";
-import"./cli-q9pzwxvk.js";
+import"./cli-86zpfje5.js";
+import"./cli-csh8fnbg.js";
 import"./cli-dabehxhp.js";
 export {
   cancelWorkflowRun2 as cancelWorkflowRun,

package/dist/{index-mj46rk9k.js → index-s193j5fh.js}

@@ -2,40 +2,40 @@ import"./cli-ns59dc6r.js";
 import {
   startHeartbeat2,
   stopHeartbeat2
-} from "./cli-2jg61wab.js";
-import"./cli-0jy85zz4.js";
-import"./cli-xd4eqtr2.js";
-import"./cli-kcsd1ez8.js";
+} from "./cli-n2918sed.js";
+import"./cli-cyfgxnvb.js";
+import"./cli-ydg6ep51.js";
+import"./cli-h5d22pfs.js";
 import"./cli-pasyvjmm.js";
-import"./cli-jpxsrxcb.js";
+import"./cli-xw9q173h.js";
 import"./cli-qz93y3x5.js";
 import"./cli-3h26v7yj.js";
 import"./cli-e8xyjvfc.js";
-import"./cli-mz2ygeyq.js";
-import"./cli-mq7kg1b1.js";
+import"./cli-0vgy5wfw.js";
+import"./cli-e91vshb1.js";
 import"./cli-3ggwdtb0.js";
-import"./cli-rngde2jv.js";
-import"./cli-v2g93k4v.js";
-import"./cli-9mm5ade4.js";
+import"./cli-6y43v79h.js";
+import"./cli-3e9vs93g.js";
+import"./cli-bpbcpd8b.js";
 import"./cli-g9ypd5en.js";
-import"./cli-nj12tn2c.js";
-import"./cli-pyy4c9ch.js";
+import"./cli-y3dzwyy3.js";
+import"./cli-j3dwd4kz.js";
 import"./cli-qqzmjxkf.js";
 import"./cli-kxpfx2xr.js";
-import"./cli-y3zyaee5.js";
+import"./cli-d172svcw.js";
 import"./cli-13p25grh.js";
 import"./cli-0adyhvq2.js";
-import"./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
-import"./cli-1dp1zj04.js";
-import"./cli-gwcf52gz.js";
+import"./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
+import"./cli-4qkg9968.js";
+import"./cli-b6tnjdvx.js";
 import"./cli-rycdaj0a.js";
 import"./cli-445c1vp7.js";
 import"./cli-kvzgak7c.js";
 import"./cli-2nf3b08t.js";
 import"./cli-b2mz5mjc.js";
-import"./cli-z2dv25mf.js";
-import"./cli-q9pzwxvk.js";
+import"./cli-86zpfje5.js";
+import"./cli-csh8fnbg.js";
 import"./cli-dabehxhp.js";
 export {
   startHeartbeat2 as startHeartbeat,

package/dist/{keepalive-wsby1btq.js → keepalive-a9srcphj.js}

@@ -1,10 +1,10 @@
 import {
   listKeepAliveAuthorizations,
   init_oauth
-} from "./cli-q9pzwxvk.js";
+} from "./cli-csh8fnbg.js";
 import {
   ensureAuthorizationTokenOrThrow
-} from "./cli-rngde2jv.js";
+} from "./cli-6y43v79h.js";
 import {
   scrubSecrets,
   init_secret_scrubber
@@ -57,7 +57,7 @@ async function notifySlack(text) {
     return;
   }
   try {
-    const { getSlackApp } = await import("./app-nndcvftq.js");
+    const { getSlackApp } = await import("./app-ft6r6v23.js");
     const app = getSlackApp();
     if (!app) {
       console.warn("[OAuth Keepalive] Slack not available, cannot send notification");

package/dist/{lead-paa141j6.js → lead-3devneqy.js}

@@ -1,67 +1,67 @@
 import"./cli-qz93y3x5.js";
 import {
   getEnabledCapabilities
-} from "./cli-kcsd1ez8.js";
-import"./cli-q9pzwxvk.js";
-import"./cli-z2dv25mf.js";
-import"./cli-v2g93k4v.js";
-import"./cli-9mm5ade4.js";
-import"./cli-mz2ygeyq.js";
-import"./cli-jpxsrxcb.js";
-import"./cli-pyy4c9ch.js";
-import"./cli-mq7kg1b1.js";
-import"./cli-rngde2jv.js";
+} from "./cli-h5d22pfs.js";
+import"./cli-csh8fnbg.js";
+import"./cli-86zpfje5.js";
+import"./cli-3e9vs93g.js";
+import"./cli-bpbcpd8b.js";
+import"./cli-0vgy5wfw.js";
+import"./cli-xw9q173h.js";
+import"./cli-j3dwd4kz.js";
+import"./cli-e91vshb1.js";
+import"./cli-6y43v79h.js";
 import"./cli-3ggwdtb0.js";
-import"./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
+import"./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
 import"./cli-qqzmjxkf.js";
 import"./cli-2nf3b08t.js";
 import"./cli-kvzgak7c.js";
 import"./cli-445c1vp7.js";
 import"./cli-kxpfx2xr.js";
 import"./cli-dabehxhp.js";
-import"./cli-nj12tn2c.js";
-import"./cli-y3zyaee5.js";
+import"./cli-y3dzwyy3.js";
+import"./cli-d172svcw.js";
 import"./cli-e8xyjvfc.js";
 import"./cli-g9ypd5en.js";
-import"./cli-1dp1zj04.js";
+import"./cli-4qkg9968.js";
 import"./cli-3h26v7yj.js";
 import"./cli-pasyvjmm.js";
 import"./cli-0xk505e8.js";
 import"./cli-bn0rewsy.js";
 import"./cli-77cd6gy8.js";
-import"./cli-cwyafhw1.js";
+import"./cli-wadzapwb.js";
 import {
   runAgent
-} from "./cli-2wba1ac9.js";
+} from "./cli-ha22h0eg.js";
 import"./cli-a5ebc95n.js";
 import"./cli-gx4rm0qx.js";
 import"./cli-5kqnemen.js";
 import"./cli-jc1g9ndz.js";
-import"./cli-fes51ya2.js";
+import"./cli-aaqnqpyw.js";
 import"./cli-ta8bd7th.js";
 import"./cli-mmhj8vd7.js";
 import"./cli-d82btycs.js";
 import"./cli-0726awxw.js";
-import"./cli-ajqhxtnz.js";
-import"./cli-qfjm4gvt.js";
+import"./cli-f3pfn4x3.js";
+import"./cli-cf63dnxj.js";
 import"./cli-4bd1rck6.js";
 import"./cli-vbhgkw9h.js";
 import"./cli-3qv8naq8.js";
 import"./cli-n6kmqngw.js";
 import"./cli-kr5tjjtz.js";
-import"./cli-znvq0k3t.js";
-import"./cli-j1eghqfm.js";
+import"./cli-xzge46sj.js";
+import"./cli-jmcjbjkt.js";
 import"./cli-g1cw7xtt.js";
-import"./cli-z63a269p.js";
-import"./cli-hadv0725.js";
+import"./cli-7ccf7akh.js";
+import"./cli-f55b6ky0.js";
 import"./cli-e5bxnjps.js";
 import"./cli-stxdrqs2.js";
-import"./cli-3ee5z0q0.js";
+import"./cli-qrjv7t18.js";
 import"./cli-4zsenjhy.js";
 import"./cli-13p25grh.js";
 import"./cli-0adyhvq2.js";
-import"./cli-gwcf52gz.js";
+import"./cli-b6tnjdvx.js";
 import"./cli-rycdaj0a.js";
 
 // src/commands/lead.ts

package/dist/{maintenance-vnshcyv9.js → maintenance-0er16h2y.js}

@@ -1,7 +1,7 @@
 import {
   reembedAllScripts,
   init_embeddings
-} from "./cli-q9pzwxvk.js";
+} from "./cli-csh8fnbg.js";
 
 // src/be/scripts/maintenance.ts
 init_embeddings();

package/dist/{oauth-refresh-sweep-d6sqn5np.js → oauth-refresh-sweep-b65jcyw2.js}

@@ -2,10 +2,10 @@ import {
   getAuthorizationById,
   listAuthorizationSweepRows,
   init_oauth
-} from "./cli-q9pzwxvk.js";
+} from "./cli-csh8fnbg.js";
 import {
   forceRefreshAuthorizationOrThrow
-} from "./cli-rngde2jv.js";
+} from "./cli-6y43v79h.js";
 import {
   scrubSecrets,
   init_secret_scrubber

package/dist/{onboard-nr4xhpzy.js → onboard-wqywz5py.js}

@@ -16,7 +16,7 @@ import {
   createDefaultSettingsLocal,
   createDefaultMcpJson,
   createHooksConfig
-} from "./cli-qfm6my86.js";
+} from "./cli-b1tv22wr.js";
 import {
   getSlackConfiguration,
   isSlackConfigured,
@@ -25,7 +25,7 @@ import {
 import {
   init_package,
   package_default
-} from "./cli-22rmcjkg.js";
+} from "./cli-kcnwn85g.js";
 import {
   getApiKey,
   init_api_key

package/dist/{otel-impl-ytn9wyv9.js → otel-impl-vk32s884.js}

@@ -14,7 +14,7 @@ import {
 import {
   init_package,
   package_default
-} from "./cli-22rmcjkg.js";
+} from "./cli-kcnwn85g.js";
 import {
   scrubSecrets,
   init_secret_scrubber

package/dist/{pricing-refresh-pva04zee.js → pricing-refresh-t27anv4z.js}

@@ -1,9 +1,9 @@
 import {
   requestModelCatalogRefresh2,
   startPricingRefreshLoop2
-} from "./cli-mz2ygeyq.js";
-import"./cli-9mm5ade4.js";
-import"./cli-q9pzwxvk.js";
+} from "./cli-0vgy5wfw.js";
+import"./cli-bpbcpd8b.js";
+import"./cli-csh8fnbg.js";
 export {
   requestModelCatalogRefresh2 as requestModelCatalogRefresh,
   startPricingRefreshLoop2 as startPricingRefreshLoop

package/dist/rbac-roles-452665y0.js

@@ -0,0 +1,26 @@
+import {
+  PRIMARY_ROLE_NAMES2,
+  getUserGrant2,
+  listUserRoles2,
+  listRbacRoles2,
+  InvalidRoleSetError2,
+  LastAdminError2,
+  assertNotLastAdmin2,
+  setUserRoles2,
+  ensureRbacSeedsSynced2,
+  init_rbac_roles
+} from "./cli-86zpfje5.js";
+import"./cli-csh8fnbg.js";
+init_rbac_roles();
+
+export {
+  InvalidRoleSetError2 as InvalidRoleSetError,
+  LastAdminError2 as LastAdminError,
+  PRIMARY_ROLE_NAMES2 as PRIMARY_ROLE_NAMES,
+  assertNotLastAdmin2 as assertNotLastAdmin,
+  ensureRbacSeedsSynced2 as ensureRbacSeedsSynced,
+  getUserGrant2 as getUserGrant,
+  listRbacRoles2 as listRbacRoles,
+  listUserRoles2 as listUserRoles,
+  setUserRoles2 as setUserRoles
+};

package/dist/{rbac-roles-7rc1q3g4.js → rbac-roles-bmcgsxjn.js}

@@ -1,12 +1,13 @@
 import {
   getDb2,
   getDbClient2,
+  init_telemetry_identity,
   init_db3
-} from "./cli-q9pzwxvk.js";
+} from "./cli-csh8fnbg.js";
 import {
   PermissionVerbSchema,
   init_rbac
-} from "./cli-ba8ne1es.js";
+} from "./cli-4rvr7zfx.js";
 import {
   isEnvFlagEnabled,
   init_env_flag
@@ -14,6 +15,7 @@ import {
 
 // src/be/rbac-roles.ts
 init_rbac();
+init_telemetry_identity();
 init_env_flag();
 init_db3();
 var DEFAULT_ROLE_ID = "rbac-role-admin";
@@ -42,6 +44,14 @@ var BUILTIN_ROLES = [
       "session.share",
       "session.presence"
     ]
+  },
+  {
+    id: "rbac-role-viewer",
+    name: "viewer",
+    description: "Read-only: no task, approval or script writes.",
+    isBuiltin: true,
+    grantsAll: false,
+    verbs: ["favorite.write.own", "session.presence"]
   }
 ];
 var CREATE_USER_DEFAULT_ROLE_TRIGGER_SQL = `

package/dist/{render-v2-pyfsg9zk.js → render-v2-0ttsk2j4.js}

@@ -2,9 +2,9 @@ import {
   isSlackRenderV2Enabled2,
   ensureSlackThreadTree2,
   processSlackRenderV22
-} from "./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
-import"./cli-q9pzwxvk.js";
+} from "./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
+import"./cli-csh8fnbg.js";
 export {
   ensureSlackThreadTree2 as ensureSlackThreadTree,
   isSlackRenderV2Enabled2 as isSlackRenderV2Enabled,

package/dist/{resume-phj8xhqr.js → resume-a26kvr41.js}

@@ -9,19 +9,19 @@ import {
   resumeFromChildRun2,
   initWaitBusSubscriptions2,
   subscribeWaitToBus2
-} from "./cli-nj12tn2c.js";
-import"./cli-pyy4c9ch.js";
+} from "./cli-y3dzwyy3.js";
+import"./cli-j3dwd4kz.js";
 import"./cli-qqzmjxkf.js";
 import"./cli-kxpfx2xr.js";
 import"./cli-13p25grh.js";
 import"./cli-0adyhvq2.js";
-import"./cli-e9btqw4y.js";
-import"./cli-xc65x52q.js";
+import"./cli-15xd0j7w.js";
+import"./cli-b63d08rs.js";
 import"./cli-rycdaj0a.js";
 import"./cli-445c1vp7.js";
 import"./cli-kvzgak7c.js";
 import"./cli-2nf3b08t.js";
-import"./cli-q9pzwxvk.js";
+import"./cli-csh8fnbg.js";
 import"./cli-dabehxhp.js";
 export {
   cancelWorkflowRun2 as cancelWorkflowRun,

package/dist/{session-access-jzx2z9h5.js → session-access-dgh9nkwk.js}

@@ -10,10 +10,10 @@ import {
   pathSessionDenial2,
   bodySessionDenial2,
   userAgentIdentityDenial2
-} from "./cli-y3zyaee5.js";
-import"./cli-gwcf52gz.js";
-import"./cli-z2dv25mf.js";
-import"./cli-q9pzwxvk.js";
+} from "./cli-d172svcw.js";
+import"./cli-b6tnjdvx.js";
+import"./cli-86zpfje5.js";
+import"./cli-csh8fnbg.js";
 export {
   SESSION_READ_DENIED2 as SESSION_READ_DENIED,
   SESSION_WRITE_DENIED2 as SESSION_WRITE_DENIED,

package/dist/{setup-rfg0f0sg.js → setup-9vc9qahm.js}

@@ -15,7 +15,7 @@ import {
   createDefaultSettingsLocal,
   createDefaultMcpJson,
   createHooksConfig
-} from "./cli-qfm6my86.js";
+} from "./cli-b1tv22wr.js";
 import {
   getApiKey,
   init_api_key