Daily Autohealing Report

[fro-bot]

Update — 2026-09-05

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377 — unchanged set since 08-28). Only #377 (Renovate build(dev): update all non-major dependencies: @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.11, @opencode-ai/plugin 1.18.19→1.18.26, mise pins, jdx/mise-action + bfra-me/.github workflow bumps — all SHA-pinned) fails real CI: Lint, typecheck, build, unit tests FAILURE (run 33952911023 / job 101270884035, 09-05 07:34Z; branch head 276ae628 refreshed overnight, merge ref 14d2c47d). Root cause re-confirmed from the actual failing log for the 13th consecutive day: src/lib/rpc-cleanup.ts(38,23)/(39,23) TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"') — bun-types@1.4.0 declares off(event: "memoryPressure", …) directly on NodeJS.Process, shadowing the generic off overloads inherited from NodeJS.EventEmitter (process.once unaffected). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe upcast — no as any/@ts-expect-error, no imports) + proc.off(...) at both call sites + bun-types rationale comment + comment-accuracy touch-up. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (PR #377's version — installed transiently, typechecked, then package.json/bun.lock restored via git restore + bun install --frozen-lockfile; final diff touches only the 2 fix files). Working-dir delivery mode forbids PR-branch checkout/commit/push, so the fix is staged on main for the caller workflow; once landed, #377's next rebase goes green. Other 5 PRs: real CI SUCCESS (#278's renovate/artifacts FAILURE is Renovate-internal, not a CI check). ⚠ = fix staged, NOT committed — 23-day recurring caller-workflow commit failure. HEAD advanced 45f68e7 → d77dc99 since the 09-04 run via three Renovate bumps only (#384 fro-bot/agent v0.107.2, #385 v0.107.3, #386 v0.108.1); still no fro-bot-originated commit on main. Today is the first schedule run on v0.108.1 — watch whether the staged diff finally lands.
SECURITY	✅	gh api repos/…/dependabot/alerts → 0 alerts (count verified). Code Scanning: not configured (404 "no analysis found", re-verified). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 still accurate vs latest published 1.18.29 (devDep pinned 1.18.19; #377 bumps to 1.18.26) — minimum unchanged, no constraint PR needed. @opencode-ai/sdk (latest 1.18.29) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All 16 uses: refs across .github/workflows/ (6 workflows, recounted today: ci 4, copilot-setup-steps 2, fro-bot 3, update-repo-settings 1, renovate 1, release 5 — incl. fro-bot/agent@504e86ab… v0.108.1 via #386) SHA-pinned at 40-char commits — no unpinned actions. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1 (b0f8bdd); .changeset/ holds only README.md + config.json (no unreleased entries); #135/#335 each carry a changeset (re-verified in their diffs today); #377 touches only devDeps/tooling (package.json/bun.lock/mise.toml/2 workflows/renovate.json5 — no changeset required); #241/#278/#332 are devDeps/tooling (no changeset needed). Major devDeps (scoped list): typescript 7.0.2 = latest; rimraf 6.1.3 = latest; @biomejs/biome 2.5.9 → 2.5.12 (patch; #377 carries 2.5.11); @types/bun 1.3.14 → 1.4.1 (minor; #377 carries 1.4.0 — unblocked by this run's rpc-cleanup.ts fix); @types/node 24.13.3 → 26.4.1 (even LTS major — tracked by duplicate #278/#241, awaiting human pick; working-dir mode forbids PR creation/merge). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335), stale #332 (superseded by today's $schema 2.5.9 fix — rebasing #332 would downgrade the schema to 2.5.8), runtime @opentui/* 0.2.7 vs latest 0.5.10 drift, and @changesets/cli 3.0.2 major (pin 2.31.1, out of autoheal's scoped list).
DEVELOPER EXPERIENCE	✅	On main (HEAD d77dc99, advanced since last run by #384/#385/#386): bun install --frozen-lockfile clean (278 installs / 309 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix; re-verified under both @types/bun 1.3.14 and 1.4.0); bun run lint ✅ 0 issues + 0 info (63 files, after biome.json $schema 2.5.5 → 2.5.9, matching installed CLI 2.5.9; today's baseline re-confirmed the lone schema-mismatch info before the fix); bun run build ✅ exit 0 (dist/ populated); Node ESM export-shape smoke test ✅ (import('./dist/index.js') → only default, typeof === 'function'); bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls across 21 files. CI on main green at d77dc99 (09-05 07:31Z). Working-tree diff minimal (+11/−4, 2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (typed proc const with bun-types rationale comment + 2 process.off→proc.off call sites + comment-accuracy touch-up). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (23 days): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9. v0.107.1 (chore(deps): update fro-bot/agent to v0.107.1 #383), v0.107.2 and v0.107.3 (chore(deps): update fro-bot/agent to v0.107.2 #384/chore(deps): update fro-bot/agent to v0.107.3 #385) did NOT fix the post-run commit step: today's run started with a clean working tree at d77dc99, which still carries the unfixed rpc-cleanup.ts + $schema 2.5.5. Today is the first schedule run on v0.108.1 (chore(deps): update fro-bot/agent to v0.108.1 #386, 504e86ab); if the diff still does not land, fix the fro-bot/agent post-run diff-detect/commit step (or grant autoheal commit scope).
• Resolve the duplicate @types/node 24→26 pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, real CI green, tracks latest 26.4.1) or chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, CI green but stale since 08-11), close the other. Prefer chore(dev): update dependency @types/node to v26 #278 (Renovate-managed).
• Resolve the duplicate @opentui pair: close fix(deps): update dependency @opentui/solid to v0.4.3 #135 (0.4.3, superseded) and rebase fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (0.4.5) onto latest 0.5.10, or close both in favor of the coordinated 0.2.7 → 0.5.10 upgrade (delegated to Copilot below). Verify the overrides dedupe carries forward and bun run test:tui passes. Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime upgrade 0.2.7 → 0.5.10 (pre-1.0, treat as breaking; single PR with a minor changeset per AGENTS.md unstable-series convention). Verify bun run build, bun run typecheck, and bun run test:tui under the new versions; carry the overrides dedupe forward. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335.
• Investigate @changesets/cli 2.31.1 → 3.0.2 major (devDep, release toolchain): confirm compatibility with the version-changesets/publish-changesets scripts and changesets/action@v1.9.0 in release.yaml; open a PR if safe. Out of autoheal's scoped list.
• Once build(dev): update all non-major dependencies #377 lands, bump biome.json $schema to match the then-installed @biomejs/biome (2.5.11, or latest 2.5.12 if Renovate refreshes the PR) — today's working-tree fix pins it to 2.5.9 (current main CLI) and build(dev): update all non-major dependencies #377 does not touch biome.json.

Items Needing Human Attention

• 23-day delivery-pipeline failure (critical): every autoheal run since ~08-13 has staged working-tree fixes that the caller workflow never commits (re-verified today: run-start working tree clean at HEAD d77dc99, which still shows $schema 2.5.5 and the original rpc-cleanup.ts; the v0.107.1→v0.107.3 bumps changed nothing). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence — Renovate refreshed it overnight and it failed identically at 07:34Z today. Today's run is the first on fro-bot/agent v0.108.1; verify post-run whether the staged diff finally lands. Until the caller's diff-detect/commit step is fixed (or autoheal is granted commit scope), autoheal cannot land anything under the working-dir contract.
• Merge/close decisions needed (destructive — left to humans): @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278 vs chore(dev): update @types/node 24 → 26 (major) #241); @opentui/* (fix(deps): update dependency @opentui/solid to v0.4.3 #135 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 vs coordinated 0.5.10 upgrade); stale chore(dev): bump biome config schema to 2.5.8 #332 (superseded by the $schema 2.5.9 fix staged today — rebasing chore(dev): bump biome config schema to 2.5.8 #332 would downgrade the schema to 2.5.8, so close rather than merge).
• @opentui/* runtime drift: 0.2.7 vs latest 0.5.10 (three 0.x minors behind on runtime deps with TUI impact). Pre-1.0 breaking bumps need TUI verification — not routine autoheal work.
• @changesets/cli 3.0.2 major available (pin 2.31.1) — release-toolchain major; needs compatibility review against release.yaml changesets/action@v1.9.0 (delegated to Copilot above).

---

Update — 2026-09-04

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377 — unchanged set since 08-28). Only #377 (Renovate build(dev): update all non-major dependencies: @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.11, @opencode-ai/plugin 1.18.19→1.18.25, mise pins, jdx/mise-action + bfra-me/.github workflow bumps — all SHA-pinned) fails real CI: Lint, typecheck, build, unit tests FAILURE (run 33874187350 / job 101027089846, 09-04 12:43Z) after Renovate's overnight rebase (branch head 14cb268c onto HEAD 45f68e7). Root cause re-confirmed from the actual failing log for the 12th consecutive day: src/lib/rpc-cleanup.ts(38,23)/(39,23) TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"') — bun-types@1.4.0 declares off(event: "memoryPressure", …) directly on NodeJS.Process, shadowing the generic off overloads inherited from NodeJS.EventEmitter (process.once unaffected; @types/node's Process declares on/once but not off). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe upcast — no as any/@ts-expect-error, no imports) + proc.off(...) at both call sites + bun-types rationale comment + comment-accuracy touch-up (process.off→proc.off in the belt-and-suspenders note). Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (PR #377's version — installed transiently via bun add -d, typechecked, then package.json/bun.lock restored via git restore + bun install --frozen-lockfile; final diff touches only the 2 fix files). Working-dir delivery mode forbids PR-branch checkout/commit/push, so the fix is staged on main for the caller workflow; once landed, #377's next rebase goes green. Other 5 PRs: real CI SUCCESS (#278's renovate/artifacts FAILURE is Renovate-internal, not a CI check). ⚠ = fix staged, NOT committed — 22-day recurring caller-workflow commit failure. v0.107.1 (#383) did NOT fix the post-run commit step: yesterday's (09-03) schedule run completed SUCCESS at 45f68e7, yet today's run started with a clean working tree at the same 45f68e7, which still carries the unfixed rpc-cleanup.ts + $schema 2.5.5.
SECURITY	✅	gh api repos/…/dependabot/alerts → 0 alerts. Code Scanning: not configured (404 "no analysis found", re-verified). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 still accurate vs latest published 1.18.28 (devDep pinned 1.18.19; #377 bumps to 1.18.25 and will refresh toward 1.18.28 on its next rebase) — minimum unchanged, no constraint PR needed. @opencode-ai/sdk (latest 1.18.28) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All 17 uses: across .github/workflows/ (6 workflows, incl. fro-bot/agent@e6b620bd… v0.107.1 via #383) SHA-pinned at 40-char commits — no unpinned actions. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries); #135/#335 each carry a changeset (re-verified in their diffs today); #377 touches only package.json/bun.lock/mise.toml/ci.yaml/renovate.yaml (devDeps & tooling — no changeset required). Major devDeps (scoped list): typescript 7.0.2 = latest; rimraf 6.1.3 = latest; @biomejs/biome 2.5.9 → 2.5.12 (patch; #377 carries 2.5.11); @types/bun 1.3.14 → 1.4.1 (minor; #377 carries 1.4.0 — unblocked by this run's rpc-cleanup.ts fix); @types/node 24.13.3 → 26.4.1 (even LTS major — tracked by duplicate #278/#241, awaiting human pick; working-dir mode forbids PR creation/merge). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335), stale #332 (superseded by today's $schema 2.5.9 fix — rebasing #332 would downgrade the schema to 2.5.8), runtime @opentui/* 0.2.7 vs latest 0.5.10 drift, and @changesets/cli 3.0.2 major (pin 2.31.1, out of autoheal's scoped list).
DEVELOPER EXPERIENCE	✅	On main (HEAD 45f68e7, unchanged since 09-03 — no new commits landed): bun install --frozen-lockfile clean (278 installs / 309 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix; re-verified under both @types/bun 1.3.14 and 1.4.0); bun run lint ✅ 0 issues + 0 info (63 files, after biome.json $schema 2.5.5 → 2.5.9, matching installed CLI 2.5.9; today's baseline re-confirmed the lone schema-mismatch info before the fix); bun run build ✅ exit 0 (dist/ populated); Node ESM export-shape smoke test ✅ (import('./dist/index.js') → only default, typeof === 'function'); bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls across 21 files. CI on main green at 45f68e7 (09-03 01:21Z). Working-tree diff minimal (+12/−4, 2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (typed proc const with bun-types rationale comment + 2 process.off→proc.off call sites + comment-accuracy touch-up). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (22 days): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9. v0.107.1 (chore(deps): update fro-bot/agent to v0.107.1 #383) confirmed NOT to fix the post-run commit step: the 09-03 schedule run completed SUCCESS at 45f68e7, yet today's run started with a clean tree at the same 45f68e7 still carrying the unfixed code. Evidence: gh run list --workflow=fro-bot.yaml --event=schedule shows 08-30 at a4de20b, 08-31/09-01/09-02 all at 87e7028, 09-03 and today at 45f68e7 — every headSha is a Renovate/maintainer commit; no fro-bot-originated commit exists on main, and no autoheal PR appears in the open or recently-closed PR lists (all Renovate). Fix the fro-bot/agent post-run diff-detect/commit step (or grant autoheal commit scope).
• Resolve the duplicate @types/node 24→26 pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, real CI green, tracks latest 26.4.1) or chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, CI green but stale since 08-11), close the other. Prefer chore(dev): update dependency @types/node to v26 #278 (Renovate-managed).
• Resolve the duplicate @opentui pair: close fix(deps): update dependency @opentui/solid to v0.4.3 #135 (0.4.3, superseded) and rebase fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (0.4.5) onto latest 0.5.10, or close both in favor of the coordinated 0.2.7 → 0.5.10 upgrade (delegated to Copilot below). Verify the overrides dedupe carries forward and bun run test:tui passes. Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime upgrade 0.2.7 → 0.5.10 (pre-1.0, treat as breaking; single PR with a minor changeset per AGENTS.md unstable-series convention). Verify bun run build, bun run typecheck, and bun run test:tui under the new versions; carry the overrides dedupe forward. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335.
• Investigate @changesets/cli 2.31.1 → 3.0.2 major (devDep, release toolchain): confirm compatibility with the version-changesets/publish-changesets scripts and changesets/action@v1.9.0 in release.yaml; open a PR if safe. Out of autoheal's scoped list.
• Once build(dev): update all non-major dependencies #377 lands, bump biome.json $schema to match the then-installed @biomejs/biome (2.5.11, or latest 2.5.12 if Renovate refreshes the PR) — today's working-tree fix pins it to 2.5.9 (current main CLI) and build(dev): update all non-major dependencies #377 does not touch biome.json.

Items Needing Human Attention

• 22-day delivery-pipeline failure (critical): every autoheal run since ~08-13 has staged working-tree fixes that the caller workflow never commits (re-verified today: run-start working tree clean at HEAD 45f68e7, which still shows $schema 2.5.5 and the original rpc-cleanup.ts; the hoped-for fix in fro-bot/agent v0.107.1 did not change behavior). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence — Renovate rebased it onto 45f68e7 and it failed identically at 12:43Z today. Until the caller's diff-detect/commit step is fixed (or autoheal is granted commit scope), autoheal cannot land anything under the working-dir contract.
• Merge/close decisions needed (destructive — left to humans): @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278 vs chore(dev): update @types/node 24 → 26 (major) #241); @opentui/* (fix(deps): update dependency @opentui/solid to v0.4.3 #135 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 vs coordinated 0.5.10 upgrade); stale chore(dev): bump biome config schema to 2.5.8 #332 (superseded by the $schema 2.5.9 fix staged today — rebasing chore(dev): bump biome config schema to 2.5.8 #332 would downgrade the schema to 2.5.8, so close rather than merge).
• @opentui/* runtime drift: 0.2.7 vs latest 0.5.10 (three 0.x minors behind on runtime deps with TUI impact). Pre-1.0 breaking bumps need TUI verification — not routine autoheal work.
• @changesets/cli 3.0.2 major available (pin 2.31.1) — release-toolchain major; needs compatibility review against release.yaml changesets/action@v1.9.0 (delegated to Copilot above).

---

Update — 2026-09-03

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377 — unchanged set since 08-28). Only #377 (Renovate build(dev): update all non-major dependencies: @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.11, @opencode-ai/plugin 1.18.19→1.18.25 [latest now 1.18.27], mise pins @github/copilot 1.0.80→1.0.82 + opencode-ai 1.18.19→1.18.25, jdx/mise-action v4.2.5→v4.3.0 + bfra-me/.github v4.19.0→v4.24.0 — both SHA-pinned, verified in the PR diff) fails real CI: Lint, typecheck, build, unit tests FAILURE (run 33703359310 / job 100487192979, 09-03 01:22Z). Renovate rebased #377 onto current HEAD 45f68e7 overnight (merge ref 5c2ac59 = 06e71ac into 45f68e7) and it failed identically — confirming main itself still carries the unfixed code. Root cause re-confirmed from the actual failing log for the 11th consecutive day: src/lib/rpc-cleanup.ts(38,23)/(39,23) TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"') — bun-types@1.4.0 declares off(event: "memoryPressure", …) directly on NodeJS.Process, shadowing the generic off overloads inherited from NodeJS.EventEmitter (process.once unaffected; @types/node's Process declares on/once but not off, so there is nothing to merge against). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe upcast — no as any/@ts-expect-error, no imports) + proc.off(...) at both call sites + comment-accuracy touch-up. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently, typechecked, then package.json/bun.lock restored + bun install — final diff touches only the 2 fix files). Working-dir delivery mode forbids PR-branch checkout/commit/push, so the fix is staged on main for the caller workflow; once landed, #377's next rebase goes green. Other 5 PRs: real CI SUCCESS (#278's renovate/artifacts FAILURE is Renovate-internal, not a CI check). ⚠ = fix staged, NOT committed — 21-day recurring caller-workflow commit failure (run-start working tree clean at HEAD 45f68e7, which still carries the unfixed rpc-cleanup.ts + $schema 2.5.5). New today: this is the first schedule run at a HEAD containing fro-bot/agent v0.107.1 (#383, e6b620bd) — if v0.107.1 fixed the post-run diff-detect/commit step, today's staged diff should finally land; verify after this run completes.
SECURITY	✅	gh api repos/…/dependabot/alerts → 0 alerts (count verified). Code Scanning: not configured (404 "no analysis found"). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 still accurate vs latest published 1.18.27 (up from 1.18.26; devDep pinned 1.18.19; #377 bumps to 1.18.25 and will refresh toward 1.18.27 on its next rebase) — minimum unchanged, no constraint PR needed. @opencode-ai/sdk (latest 1.18.27) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All 17 uses: across .github/workflows/ (6 workflows, incl. fro-bot/agent@e6b620bd… # v0.107.1 via #383) SHA-pinned at 40-char commits — no unpinned actions; #377's action bumps (jdx/mise-action@c2a8761… v4.3.0, bfra-me/.github@2f2e9da… v4.24.0) also SHA-pinned, verified in the PR diff. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries); no open PR introduces user-visible changes without a changeset (#377 is devDeps/workflow/mise tooling only — no changeset required; #135/#335 carry changesets). Major devDeps (scoped list): typescript 7.0.2 = latest; rimraf 6.1.3 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377; latest now 2.5.12); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); @types/node 24.13.3 → 26.4.1 (even LTS major — tracked by duplicate #278/#241, awaiting human pick; working-dir mode forbids PR creation/merge). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335), stale #332 (superseded by today's $schema 2.5.9 fix — rebasing #332 would downgrade the schema to 2.5.8), runtime @opentui/* 0.2.7 vs latest 0.5.10 drift, and @changesets/cli 3.0.1 major (pin 2.31.1, out of autoheal's scoped list).
DEVELOPER EXPERIENCE	✅	On main (HEAD 45f68e7, advanced since last run by #383 fro-bot/agent v0.107.1): bun install clean (278 installs / 309 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run lint ✅ 0 issues + 0 info (63 files, after biome.json $schema 2.5.5 → 2.5.9, matching installed CLI 2.5.9; supersedes stale #332 which only bumps to 2.5.8); bun run build ✅ exit 0 (dist/ populated); Node ESM export-shape smoke test ✅ (import('./dist/index.js') → only default, typeof === 'function'); bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls across 21 files. CI on main green at 45f68e7 (today 01:21Z). Working-tree diff minimal (+9/−4, 2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (typed proc const with bun-types rationale comment + 2 process.off→proc.off call sites + comment-accuracy touch-up). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (21 days): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9. Evidence the caller workflow discards the diff daily: gh run list --workflow=fro-bot.yaml --event=schedule shows 08-28 & 08-29 both SUCCESS at fd0ee29, 08-30 at a4de20b, 08-31/09-01/09-02 all at 87e7028, and today's run in progress at 45f68e7 — every headSha is a Renovate/maintainer commit; no fro-bot-originated commit exists on main. Today's run is the first on fro-bot/agent v0.107.1 (chore(deps): update fro-bot/agent to v0.107.1 #383) — check whether the v0.107.1 bump fixed the post-run diff-detect/commit step; if the diff still does not land, fix that step (or grant autoheal commit scope).
• Resolve the duplicate @types/node 24→26 pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, real CI green, tracks latest 26.4.1) or chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, CI green but stale since 08-11), close the other. Prefer chore(dev): update dependency @types/node to v26 #278 (Renovate-managed).
• Resolve the duplicate @opentui pair: close fix(deps): update dependency @opentui/solid to v0.4.3 #135 (0.4.3, superseded) and rebase fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (0.4.5) onto latest 0.5.10, or close both in favor of the coordinated 0.2.7 → 0.5.10 upgrade (delegated to Copilot below). Verify the overrides.@opentui/core dedupe carries forward and bun run test:tui passes. Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime upgrade 0.2.7 → 0.5.10 (pre-1.0, treat as breaking; single PR with a minor changeset per AGENTS.md unstable-series convention). Verify bun run build, bun run typecheck, and bun run test:tui under the new versions; carry the overrides.@opentui/core dedupe forward. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335.
• Investigate @changesets/cli 2.31.1 → 3.0.1 major (devDep, release toolchain): confirm compatibility with the version-changesets/publish-changesets scripts and changesets/action@v1.9.0 in release.yaml; open a PR if safe. Out of autoheal's scoped list.
• Once build(dev): update all non-major dependencies #377 lands, bump biome.json $schema to match the then-installed @biomejs/biome (2.5.11, or latest 2.5.12 if Renovate refreshes the PR) — today's working-tree fix pins it to 2.5.9 (current main CLI) and build(dev): update all non-major dependencies #377 does not touch biome.json.

Items Needing Human Attention

• 21-day delivery-pipeline failure (critical): every autoheal run since ~08-13 has staged working-tree fixes that the caller workflow never commits (re-verified today: run-start working tree clean at HEAD 45f68e7, which still shows $schema 2.5.5 and the original rpc-cleanup.ts). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence — Renovate rebased it onto 45f68e7 overnight and it failed identically at 01:22Z. Possible relief: fro-bot/agent v0.107.1 landed via chore(deps): update fro-bot/agent to v0.107.1 #383 and this is the first schedule run on it; verify post-run whether the staged diff finally lands. Until the caller's diff-detect/commit step is fixed (or autoheal is granted commit scope), autoheal cannot land anything under the working-dir contract.
• Merge/close decisions needed (destructive — left to humans): @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278 vs chore(dev): update @types/node 24 → 26 (major) #241); @opentui/* (fix(deps): update dependency @opentui/solid to v0.4.3 #135 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 vs coordinated 0.5.10 upgrade); stale chore(dev): bump biome config schema to 2.5.8 #332 (superseded by the $schema 2.5.9 fix staged today — rebasing chore(dev): bump biome config schema to 2.5.8 #332 would downgrade the schema to 2.5.8, so close rather than merge).
• @opentui/* runtime drift: 0.2.7 vs latest 0.5.10 (three 0.x minors behind on runtime deps with TUI impact). Pre-1.0 breaking bumps need TUI verification — not routine autoheal work.
• @changesets/cli 3.0.1 major available (pin 2.31.1) — release-toolchain major; needs compatibility review against release.yaml changesets/action@v1.9.0 (delegated to Copilot above).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33777336137 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing (build(dev): update all non-major dependencies #377 only — TS2345 rpc-cleanup.ts:38-39 under @types/bun@1.4.0, re-confirmed from today's failing log run 33703359310 after Renovate's overnight rebase onto 45f68e7; root-cause fix staged on main working tree, verified under both @types/bun 1.3.14 and 1.4.0). Other 5 open PRs CI-green. No PR-branch pushes (working-dir delivery mode).
• SECURITY: 0 open Dependabot alerts (count verified); Code Scanning not configured (404); no security PRs. No action.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.27; @opencode-ai/sdk not a peer; all 17 workflow uses: SHA-pinned (incl. build(dev): update all non-major dependencies #377's action bumps, verified in its diff); no changeset drift (pkg 0.12.1 == tag v0.12.1); scoped devDeps current except @types/node 24→26 (duplicate chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241); runtime @opentui/* 0.2.7 vs 0.5.10 drift; @changesets/cli 3.0.1 major out of scoped list.
• DEVELOPER EXPERIENCE: on main at 45f68e7 — bun install (278/309, no peer warnings) / typecheck / build / Node ESM export-shape smoke test / test:unit (322 pass) all clean; lint 0 issues + 0 info after $schema 2.5.5→2.5.9; CI on main green at HEAD.
• Actions taken: 2 working-tree file changes (src/lib/rpc-cleanup.ts type fix + biome.json schema bump) left for the caller workflow to commit/push; perpetual issue Daily Autohealing Report #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-09-02

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377 — unchanged set since 08-28). Only #377 (Renovate build(dev): update all non-major dependencies: @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.11, @opencode-ai/plugin 1.18.19→1.18.25 [pending 1.18.26], mise pins @github/copilot 1.0.80→1.0.82 + opencode-ai 1.18.19→1.18.25, jdx/mise-action v4.2.5→v4.3.0 + bfra-me/.github v4.19.0→v4.23.0 — both SHA-pinned, verified in the PR diff) fails real CI: Lint, typecheck, build, unit tests FAILURE (run 33578456318 / job 100087438190, 09-02 01:13Z, after Renovate's overnight rebase). Root cause re-confirmed from the actual failing log for the 10th consecutive day: src/lib/rpc-cleanup.ts(38,23)/(39,23) TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"') — bun-types@1.4.0 declares off(event: "memoryPressure", …) directly on NodeJS.Process, shadowing the generic off overloads inherited from NodeJS.EventEmitter (process.once unaffected). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe upcast — no as any/@ts-expect-error) + proc.off(...) at both call sites + comment-accuracy touch-up. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently, typechecked, then package.json/bun.lock restored + bun install --frozen-lockfile — final diff touches only the 2 fix files). Working-dir delivery mode forbids PR-branch checkout/commit/push, so the fix is staged on main for the caller workflow; once landed, #377's next rebase goes green. Other 5 PRs: real CI SUCCESS (#278's renovate/artifacts FAILURE is Renovate-internal, not a CI check). ⚠ = fix staged, NOT committed — 20-day recurring caller-workflow commit failure (run-start working tree clean at HEAD 87e7028, which still carries the unfixed rpc-cleanup.ts + $schema 2.5.5).
SECURITY	✅	gh api repos/…/dependabot/alerts?state=open → 0 alerts. Code Scanning: not configured (404 "no analysis found", re-verified). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 still accurate vs latest published 1.18.26 (today's latest, up from 1.18.25; devDep pinned 1.18.19; #377 bumps to 1.18.25, pending 1.18.26) — minimum unchanged, no constraint PR needed. @opencode-ai/sdk (latest 1.18.26) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All 17 uses: across .github/workflows/ (6 workflows, incl. fro-bot/agent@26fdb0b5… # v0.107.0) SHA-pinned at 40-char commits — no unpinned actions; #377's action bumps (jdx/mise-action@c2a8761… v4.3.0, bfra-me/.github@eb1772e… v4.23.0) also SHA-pinned, verified in the PR diff. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries); no open PR introduces user-visible changes without a changeset (#377 is devDeps/workflow/mise tooling only — no changeset required; #135/#335 carry changesets). Major devDeps (scoped list): typescript 7.0.2 = latest; rimraf 6.1.3 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); @types/node 24.13.3 → 26.4.1 (even LTS major — tracked by duplicate #278/#241, awaiting human pick; working-dir mode forbids PR creation/merge). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335), runtime @opentui/* 0.2.7 vs latest 0.5.10 drift, and @changesets/cli 3.0.1 major (pin 2.31.1, out of autoheal's scoped list).
DEVELOPER EXPERIENCE	✅	On main (HEAD 87e7028, unchanged since last run — no new commits landed): bun install --frozen-lockfile clean (278 installs / 309 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run lint ✅ 0 issues + 0 info (63 files, after biome.json $schema 2.5.5 → 2.5.9, matching installed CLI 2.5.9; supersedes stale #332 which only bumps to 2.5.8); bun run build ✅ exit 0 (dist/ populated); bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls across 21 files. CI on main green at 87e7028/847a284/cdce8bc. Working-tree diff minimal (2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (typed proc const + 2 process.off→proc.off call sites + comment-accuracy touch-up). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (20 days): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9. Evidence the caller workflow discards the diff daily: gh run list --workflow=fro-bot.yaml --event=schedule shows 08-28 & 08-29 both SUCCESS at fd0ee29, 08-30 at a4de20b, 08-31 & 09-01 both at 87e7028, and today's run in progress at 87e7028 — every headSha is a Renovate/maintainer commit; no fro-bot-originated commit exists on main. Fix the fro-bot/agent post-run diff-detect/commit step (or grant autoheal commit scope).
• Resolve the duplicate @types/node 24→26 pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, real CI green, tracks latest 26.4.1) or chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, CI green but stale since 08-11), close the other. Prefer chore(dev): update dependency @types/node to v26 #278 (Renovate-managed).
• Resolve the duplicate @opentui pair: close fix(deps): update dependency @opentui/solid to v0.4.3 #135 (0.4.3, superseded) and rebase fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (0.4.5) onto latest 0.5.10, or close both in favor of the coordinated 0.2.7 → 0.5.10 upgrade (delegated to Copilot below). Verify the overrides.@opentui/core dedupe carries forward and bun run test:tui passes. Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime upgrade 0.2.7 → 0.5.10 (pre-1.0, treat as breaking; single PR with a minor changeset per AGENTS.md unstable-series convention). Verify bun run build, bun run typecheck, and bun run test:tui under the new versions; carry the overrides.@opentui/core dedupe forward. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335.
• Investigate @changesets/cli 2.31.1 → 3.0.1 major (devDep, release toolchain): confirm compatibility with the version-changesets/publish-changesets scripts and changesets/action@v1.9.0 in release.yaml; open a PR if safe. Out of autoheal's scoped list.
• Once build(dev): update all non-major dependencies #377 lands, bump biome.json $schema to match the then-installed @biomejs/biome (2.5.11) — today's working-tree fix pins it to 2.5.9 (current main CLI) and build(dev): update all non-major dependencies #377 does not touch biome.json.

Items Needing Human Attention

• 20-day delivery-pipeline failure (critical): every autoheal run since ~08-13 has staged working-tree fixes that the caller workflow never commits (re-verified today: run-start working tree clean at HEAD 87e7028, which still shows $schema 2.5.5 and the original rpc-cleanup.ts; the 09-01 schedule run also completed SUCCESS at 87e7028 with nothing landed). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence (Renovate rebased it overnight at 01:12Z and it failed identically at 01:13Z). Until the caller's diff-detect/commit step is fixed (or autoheal is granted commit scope), autoheal cannot land anything under the working-dir contract.
• Merge/close decisions needed (destructive — left to humans): @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278 vs chore(dev): update @types/node 24 → 26 (major) #241); @opentui/* (fix(deps): update dependency @opentui/solid to v0.4.3 #135 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 vs coordinated 0.5.10 upgrade); stale chore(dev): bump biome config schema to 2.5.8 #332 (superseded by the $schema 2.5.9 fix staged today — rebasing chore(dev): bump biome config schema to 2.5.8 #332 would downgrade the schema to 2.5.8, so close rather than merge).
• @opentui/* runtime drift: 0.2.7 vs latest 0.5.10 (three 0.x minors behind on runtime deps with TUI impact). Pre-1.0 breaking bumps need TUI verification — not routine autoheal work.
• @changesets/cli 3.0.1 major available (pin 2.31.1) — release-toolchain major; needs compatibility review against release.yaml changesets/action@v1.9.0 (delegated to Copilot above).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33653672081 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing (build(dev): update all non-major dependencies #377 only — TS2345 rpc-cleanup.ts:38-39 under @types/bun@1.4.0, re-confirmed from today's failing log run 33578456318; root-cause fix staged on main working tree, verified under both @types/bun 1.3.14 and 1.4.0). Other 5 open PRs CI-green. No PR-branch pushes (working-dir delivery mode).
• SECURITY: 0 open Dependabot alerts; Code Scanning not configured (404); no security PRs. No action.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.26; @opencode-ai/sdk not a peer; all 17 workflow uses: SHA-pinned (incl. build(dev): update all non-major dependencies #377's action bumps, verified in its diff); no changeset drift (pkg 0.12.1 == tag v0.12.1); scoped devDeps current except @types/node 24→26 (duplicate chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241); runtime @opentui/* 0.2.7 vs 0.5.10 drift; @changesets/cli 3.0.1 major out of scoped list.
• DEVELOPER EXPERIENCE: on main at 87e7028 — bun install (278/309, no peer warnings) / typecheck / build / test:unit (322 pass) all clean; lint 0 issues + 0 info after $schema 2.5.5→2.5.9; CI on main green at HEAD.
• Actions taken: 2 working-tree file changes (src/lib/rpc-cleanup.ts type fix + biome.json schema bump) left for the caller workflow to commit/push; perpetual issue Daily Autohealing Report #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-09-01

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377 — unchanged set since 08-28). Only #377 (Renovate build(dev): update all non-major dependencies: @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.11, @opencode-ai/plugin 1.18.19→1.18.25, mise pins, jdx/mise-action v4.3.0 + bfra-me/.github v4.23.0 — both SHA-pinned) fails real CI: Lint, typecheck, build, unit tests FAILURE (run 33375482979 / job 99435900545, unchanged since its 08-31 rebase). Root cause re-confirmed from the actual failing log for the 9th consecutive day: src/lib/rpc-cleanup.ts(38,23)/(39,23) TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"') — bun-types@1.4.0 declares off(event: "memoryPressure", …) directly on NodeJS.Process, shadowing the generic off overloads inherited from NodeJS.EventEmitter (base declares no own off; process.once(...) is unaffected). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe widening — no as any/@ts-expect-error) + proc.off(...) at both call sites. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently via bun add -d, typechecked, then package.json/bun.lock restored + bun install --frozen-lockfile — final diff touches only the 2 fix files). Working-dir delivery mode forbids PR-branch checkout/commit/push, so the fix is staged on main for the caller workflow; once landed, #377's next rebase goes green. Other 5 PRs: real CI SUCCESS (#278's renovate/artifacts FAILURE is Renovate-internal, not a CI check). Also noted: #377's bun.lock regresses lockfileVersion 2→1 vs post-#382 main — its next Renovate rebase will regenerate it (frozen install still succeeded inside the failing run, so it is not CI-blocking). ⚠ = fix staged, NOT committed — 19-day recurring caller-workflow commit failure (run-start working tree clean; HEAD 87e7028 still carried the unfixed rpc-cleanup.ts + $schema 2.5.5).
SECURITY	✅	gh api repos/…/dependabot/alerts?state=open → 0 alerts. Code Scanning: not configured (404 "no analysis found", re-verified). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 still accurate vs latest published 1.18.25 (devDep pinned 1.18.19; #377 bumps to 1.18.25) — minimum unchanged, no constraint PR needed. @opencode-ai/sdk (latest 1.18.25) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All 17 uses: across .github/workflows/ (6 workflows, incl. fro-bot/agent@26fdb0b5… # v0.107.0 via #381) SHA-pinned at 40-char commits — no unpinned actions. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries); no open PR introduces user-visible changes without a changeset (#377 is devDeps/workflow/mise tooling only — no changeset required; #135/#335 carry changesets). Major devDeps (scoped list): typescript 7.0.2 = latest; rimraf 6.1.3 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); @types/node 24.13.3 → 26.4.0 (even LTS major — tracked by duplicate #278/#241, awaiting human pick; working-dir mode forbids PR creation/merge). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335), runtime @opentui/* 0.2.7 vs latest 0.5.10 drift, and @changesets/cli 3.0.1 major (pin 2.31.1, out of autoheal's scoped list).
DEVELOPER EXPERIENCE	✅	On main (HEAD 87e7028, advanced since last run only by Renovate #380/#381/#382): bun install --frozen-lockfile clean (278 installs / 309 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run lint ✅ 0 issues + 0 info (after biome.json $schema 2.5.5 → 2.5.9, matching installed CLI 2.5.9; supersedes stale #332 which only bumps to 2.5.8); bun run build ✅ exit 0 (dist/ populated); bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. CI on main green at 87e7028/847a284/cdce8bc. Working-tree diff minimal (+7/−3, 2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (typed proc const + comment + 2 process.off→proc.off call sites + comment-accuracy touch-up). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (19 days): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9. Evidence the caller workflow discards the diff daily: gh run list --workflow=fro-bot.yaml --event=schedule shows the 08-28 and 08-29 runs both completed SUCCESS at fd0ee29 (chore(deps): update fro-bot/agent to v0.105.1 #378), 08-30 at a4de20b (chore(deps): update fro-bot/agent to v0.106.1 #379), 08-31 at 87e7028 (chore(deps): maintain lockfiles #382) — every headSha is a Renovate/maintainer commit; no fro-bot-originated commit exists on main. Fix the fro-bot/agent post-run diff-detect/commit step (or grant autoheal commit scope).
• Resolve the duplicate @types/node 24→26 pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, real CI green, tracks latest 26.4.0) or chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, CI green), close the other. Both predate the caret-range guidance; prefer chore(dev): update dependency @types/node to v26 #278 (Renovate-managed).
• Resolve the duplicate @opentui pair: close fix(deps): update dependency @opentui/solid to v0.4.3 #135 (0.4.3, superseded) and rebase fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (0.4.5) onto latest 0.5.10, or close both in favor of the coordinated 0.2.7 → 0.5.10 upgrade (delegated to Copilot below). Verify the overrides.@opentui/core dedupe carries forward and bun run test:tui passes. Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime upgrade 0.2.7 → 0.5.10 (pre-1.0, treat as breaking; single PR with a minor changeset per AGENTS.md unstable-series convention). Verify bun run build, bun run typecheck, and bun run test:tui under the new versions; carry the overrides.@opentui/core dedupe forward. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335.
• Investigate @changesets/cli 2.31.1 → 3.0.1 major (devDep, release toolchain): confirm compatibility with the version-changesets/publish-changesets scripts and changesets/action@v1.9.0 in release.yaml; open a PR if safe. Out of autoheal's scoped list.
• Once build(dev): update all non-major dependencies #377 lands, bump biome.json $schema to match the then-installed @biomejs/biome (2.5.11) — today's working-tree fix pins it to 2.5.9 (current main CLI) and build(dev): update all non-major dependencies #377 does not touch biome.json.

Items Needing Human Attention

• 19-day delivery-pipeline failure (critical): every autoheal run since ~08-13 has staged working-tree fixes that the caller workflow never commits (re-verified today: 08-28/08-29 schedule runs both completed at fd0ee29, 08-30 at a4de20b, 08-31 at 87e7028 — all Renovate/maintainer commits; run-start working tree clean, HEAD still unfixed). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence. Until the caller's diff-detect/commit step is fixed (or autoheal is granted commit scope), autoheal cannot land anything under the working-dir contract.
• Merge/close decisions needed (destructive — left to humans): @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278 vs chore(dev): update @types/node 24 → 26 (major) #241); @opentui/* (fix(deps): update dependency @opentui/solid to v0.4.3 #135 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 vs coordinated 0.5.10 upgrade); stale chore(dev): bump biome config schema to 2.5.8 #332 (superseded by the $schema 2.5.9 fix staged today — rebasing chore(dev): bump biome config schema to 2.5.8 #332 would downgrade the schema to 2.5.8, so close rather than merge).
• @opentui/* runtime drift: 0.2.7 vs latest 0.5.10 (three 0.x minors behind on runtime deps with TUI impact). Pre-1.0 breaking bumps need TUI verification — not routine autoheal work.
• @changesets/cli 3.0.1 major available (pin 2.31.1) — release-toolchain major; needs compatibility review against release.yaml changesets/action@v1.9.0 (delegated to Copilot above).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33532507423 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing (build(dev): update all non-major dependencies #377 only — TS2345 rpc-cleanup.ts:38-39 under @types/bun@1.4.0; root-cause fix staged on main working tree, verified under both @types/bun 1.3.14 and 1.4.0). Other 5 open PRs CI-green. No PR-branch pushes (working-dir delivery mode).
• SECURITY: 0 open Dependabot alerts; Code Scanning not configured (404); no security PRs. No action.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.25; @opencode-ai/sdk not a peer; all 17 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); scoped devDeps current except @types/node 24→26 (duplicate chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241); runtime @opentui/* 0.2.7 vs 0.5.10 drift; @changesets/cli 3.0.1 major out of scoped list.
• DEVELOPER EXPERIENCE: on main at 87e7028 — bun install (278/309, no peer warnings) / typecheck / build / test:unit (322 pass) all clean; lint 0 issues + 0 info after $schema 2.5.5→2.5.9; CI on main green at HEAD.
• Actions taken: 2 working-tree file changes (src/lib/rpc-cleanup.ts type fix + biome.json schema bump) left for the caller workflow to commit/push; perpetual issue Daily Autohealing Report #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-31

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377 — #380 and #381 merged since last run). Only #377 (Renovate build(dev): update all non-major dependencies, rebased fresh today 08:59: now @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.11, @opencode-ai/plugin 1.18.19→1.18.25, mise opencode-ai 1.18.25 / copilot 1.0.81, bfra-me/.github v4.23.0, jdx/mise-action v4.3.0) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 33375482979 / job 99435900545, 2026-08-31T08:59). Root cause re-confirmed for the 8th consecutive day from the actual failing log this run: src/lib/rpc-cleanup.ts(38,23) + (39,23) TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"') under @types/bun@1.4.0 — bun-types@1.4.0 overrides.d.ts declares off(event: "memoryPressure", …) (and removeListener(event: "memoryPressure", …)) directly on NodeJS.Process; because @types/node 24's Process does not declare off/removeListener itself (they are inherited from NodeJS.EventEmitter), the bun-specific declaration hides the generic off<K>(eventName: string | symbol, …) base overload. process.once(...) is unaffected (@types/node declares explicit once overloads on Process; merging concatenates them). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe, no as needed — Process extends EventEmitter) then proc.off('beforeExit'/'SIGTERM', …). Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently via bun add -d, typechecked, then git checkout -- package.json bun.lock + bun install --frozen-lockfile — final diff touches only the 2 fix files). Other 5 PRs: real CI SUCCESS (#278 also carries Renovate-internal renovate/artifacts FAILURE — not a CI check). ⚠ = fix staged on main working tree, NOT committed — see "Items Needing Human Attention" (18-day recurring caller-workflow commit failure; run-start working tree was clean and main HEAD 87e7028 still contained the unfixed rpc-cleanup.ts + $schema 2.5.5, confirming yesterday's staged diff was again discarded).
SECURITY	✅	gh api repos/…/dependabot/alerts (open) → 0 alerts. Code Scanning: not configured (404 "no analysis found", re-verified). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 still accurate vs latest published 1.18.25 (devDep pinned 1.18.19; PR #377 bumps to 1.18.25) — minimum unchanged, no constraint PR needed. @opencode-ai/sdk (latest 1.18.25) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All uses: across .github/workflows/ (17 entries in 6 workflows, incl. fro-bot/agent@26fdb0b5… # v0.107.0 via #381) SHA-pinned at 40-char commits — no unpinned actions. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries). Major devDeps: typescript 7.0.2 = latest; rimraf 6.1.3 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); @types/node 24.13.3 → 26.4.0 (even LTS major — tracked by duplicate #278/#241, awaiting human pick; autoheal cannot create/merge PRs under working-dir delivery mode). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335), runtime @opentui/* 0.2.7 vs latest 0.5.9 drift, and @changesets/cli 3.0.1 major (pin 2.31.1, out of autoheal's scoped list).
DEVELOPER EXPERIENCE	✅	On main (HEAD 87e7028, advanced since last run only by Renovate #380/#381/#382): bun install --frozen-lockfile clean (278 installs / 309 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run lint ✅ 0 issues + 0 info (after biome.json $schema 2.5.5 → 2.5.9 — clears the lone lint info; supersedes stale #332 which only bumps to 2.5.8); bun run build ✅ exit 0; bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. Working-tree diff minimal (+7/−3, 2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (typed proc const + comment + 2 process.off→proc.off call sites). Re-validated together on main and under @types/bun@1.4.0. Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (18-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale chore(dev): bump biome config schema to 2.5.8 #332). The 08-13 → 08-30 runs each staged these (or equivalent) fixes in the working tree, but main (HEAD 87e7028, advanced only by Renovate chore(deps): update fro-bot/agent to v0.106.2 #380/chore(deps): update fro-bot/agent to v0.107.0 #381/chore(deps): maintain lockfiles #382) still shows $schema 2.5.5 and the original rpc-cleanup.ts — re-verified at run start today before re-applying. The autoheal caller is NOT committing the working-tree diff it claims to own. Until it commits, every run re-applies the same fix and build(dev): update all non-major dependencies #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on build(dev): update all non-major dependencies #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. Renovate already rebased build(dev): update all non-major dependencies #377 overnight (08:59 today) and it failed identically — it will keep failing until the fix lands on main. If Renovate won't rebase after the fix lands, close build(dev): update all non-major dependencies #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, MERGEABLE, real CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale, last real CI 2026-08-11). Left to human — autoheal cannot push to PR branches under working-dir delivery mode.
• Resolve duplicate @opentui/solid PR pair (fix(deps): update dependency @opentui/solid to v0.4.3 #135 Renovate 0.4.3 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 fro-bot 0.4.5): both stale and superseded by runtime drift to @opentui/core/@opentui/solid latest 0.5.9 (current pinned 0.2.7). Recommend closing both and letting Renovate open a fresh PR targeting 0.5.9, or updating fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 to 0.5.9. Coordinate with the OpenTUI 0.4→0.5 breaking-change review first.

Tasks for Copilot

• Investigate and fix the fro-bot/agent action's Post Run Fro Bot post-step so it detects working-tree diffs produced by the agent and commits + pushes them to main (or opens a PR) for schedule-triggered runs. Reproduce: trigger the Fro Bot workflow on schedule, have the agent make a trivial working-tree change, observe whether the post-step commits it. Expected: a commit lands on main; actual: no commit, headSha unchanged across consecutive successful runs (08-26 & 08-27 both c6c055d; 08-28 & 08-29 both fd0ee29; 08-30 a4de20b → 08-31 87e7028 moved only via Renovate merges chore(deps): update fro-bot/agent to v0.106.2 #380/chore(deps): update fro-bot/agent to v0.107.0 #381/chore(deps): maintain lockfiles #382). This is the root cause of the 18-day recurring autoheal fix loss and the reason PR build(dev): update all non-major dependencies #377 stays red. Single PR to the fro-bot/agent action repo.
• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.9 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135 and fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.11 (patch, non-major, devDependency, no changeset) and re-sync biome.json $schema (2.5.9 → 2.5.11). (Covered by PR build(dev): update all non-major dependencies #377 once it rebases green.)

Items Needing Human Attention

• CRITICAL (18-day recurring): The autoheal caller workflow (fro-bot/agent post-step) is not committing working-tree diffs to main. Eighteen consecutive days of autoheal fixes (rpc-cleanup.ts type fix + biome.json schema bump) have been staged in the working tree and silently discarded — main HEAD 87e7028 still shows $schema 2.5.5 and the original rpc-cleanup.ts (verified at run start today before re-applying). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence (Renovate rebased it overnight and it failed identically). Requires investigation of the fro-bot/agent action's commit/post-step configuration — outside the autoheal agent's permissions (cannot git commit/git push/gh pr create/switch branches under the working-dir delivery contract).
• Decide which @types/node 24→26 PR to merge: chore(dev): update dependency @types/node to v26 #278 (Renovate, fresh, real CI green) vs chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale since 2026-08-11). Recommend merging chore(dev): update dependency @types/node to v26 #278 and closing chore(dev): update @types/node 24 → 26 (major) #241.
• Decide on the duplicate @opentui/solid PR pair: fix(deps): update dependency @opentui/solid to v0.4.3 #135 (Renovate, 0.4.3) vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (fro-bot, 0.4.5). Both superseded by runtime drift to latest 0.5.9 (current 0.2.7). Recommend closing both and opening a fresh PR targeting 0.5.9 after reviewing the 0.4→0.5 breaking changes.
• Consider closing stale fro-bot branches/PRs (chore(dev): update @types/node 24 → 26 (major) #241, chore(dev): bump biome config schema to 2.5.8 #332, fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335) that are superseded by Renovate equivalents or by this run's working-tree fixes, to reduce dashboard noise.
• @changesets/cli 3.0.1 major available (current pin 2.31.1) — out of autoheal's scoped devDep list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@a45c4d59…).

---

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33412894740 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 6 open; 1 failing real CI — build(dev): update all non-major dependencies #377 Lint, typecheck, build, unit tests FAILURE (run 33375482979, 2026-08-31T08:59; Renovate rebased it overnight to @biomejs/biome 2.5.11 / @opencode-ai/plugin 1.18.25 / copilot 1.0.81 / bfra-me v4.23.0). Root cause re-confirmed from the actual failing log (8th day): bun-types@1.4.0 declares off(event: "memoryPressure", …) on NodeJS.Process; @types/node 24's Process has no own off/removeListener (inherited from NodeJS.EventEmitter), so the bun declaration hides the generic off<K>(string \| symbol, …) → src/lib/rpc-cleanup.ts:38-39 TS2345. Fix staged in working tree on main: const proc: NodeJS.EventEmitter = process; proc.off('beforeExit'/'SIGTERM', …) (type-safe, no as). Verified by actually installing @types/bun@1.4.0 this run: tsc --noEmit clean with the fix; reverted via git checkout -- package.json bun.lock + bun install --frozen-lockfile (final diff = rpc-cleanup.ts + biome.json only). Clean under both @types/bun 1.3.14 (main) and 1.4.0 (build(dev): update all non-major dependencies #377). process.once(...) left unchanged (does not error — explicit once overloads on Process). chore(deps): update fro-bot/agent to v0.106.2 #380/chore(deps): update fro-bot/agent to v0.107.0 #381 merged green since last run; chore(dev): update dependency @types/node to v26 #278's renovate/artifacts FAILURE is Renovate-internal, its real CI is green.
• SECURITY: 0 Dependabot alerts / 0 security-update PRs / 0 advisories; Code Scanning not configured (404, re-verified).
• HEALTH & MAINTENANCE: peer @opencode-ai/plugin >=1.14.41 accurate vs latest 1.18.25; @opencode-ai/sdk not a peer (transitive); all 17 workflow uses: entries across 6 workflows SHA-pinned (incl. fro-bot/agent@26fdb0b5… # v0.107.0); no changeset drift (pkg 0.12.1 == tag v0.12.1, .changeset/ = README.md + config.json only); devDeps current except @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241 duplicate, awaiting merge), @biomejs/biome 2.5.9→2.5.11 patch (build(dev): update all non-major dependencies #377), @changesets/cli 2.31.1→3.0.1 major (human triage), and runtime @opentui/* 0.2.7 vs 0.5.9 (fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 stale).
• DEVELOPER EXPERIENCE: bun install --frozen-lockfile / typecheck / build / test:unit (322 pass / 0 fail) all clean; lint lone info (biome $schema 2.5.5 vs CLI 2.5.9) fixed in working tree (2.5.5 → 2.5.9); re-ran → 0 issues, 0 info.
• Actions taken: applied rpc-cleanup.ts proc: NodeJS.EventEmitter routing + biome.json schema bump in working tree (caller workflow owns commit/push; no git/PR actions per working-dir delivery mode); perpetual issue Daily Autohealing Report #26 updated with today's section. Recurring blocker (18-day): prior runs' working-tree diff never landed on main — caller workflow must commit this run's diff or the fix cycle repeats and build(dev): update all non-major dependencies #377 stays red.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-30

Summary

Category	Status	Actions
ERRORED PRs	⚠️	7 open PRs (#135, #241, #278, #332, #335, #377, #380 — #380 new since last run: Renovate fro-bot/agent 0.106.1, CI green + CLEAN). Only #377 (Renovate build(dev): update all non-major dependencies; bumps @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.10, @opencode-ai/plugin 1.18.19→1.18.23, mise opencode-ai 1.18.19→1.18.23, bfra-me/.github v4.19.0→v4.22.0, jdx/mise-action v4.2.5→v4.3.0) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 33285537818, 2026-08-30T01:23). Root cause re-confirmed for the 7th consecutive day from the actual failing log this run: src/lib/rpc-cleanup.ts(38,23) + (39,23) error TS2345 (Argument of type '"beforeExit"'/'"SIGTERM"' is not assignable to parameter of type '"memoryPressure"') under @types/bun@1.4.0, because bun-types@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …), shadowing the generic off<K>(eventName: string | symbol, …) inherited from EventEmitter. Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe upcast, Process extends EventEmitter) then proc.off('beforeExit'/'SIGTERM', …) — restores the generic off overload from the base interface; no as any/@ts-expect-error. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently via package.json edit + bun install, tsc clean, then git checkout -- package.json bun.lock + bun install --frozen-lockfile — final diff only touches rpc-cleanup.ts + biome.json). bun run lint ✅ 0 issues, bun run build ✅ exit 0, bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls on main. Other 6 PRs: real CI SUCCESS (#278 also carries Renovate-internal renovate/artifacts FAILURE — not a CI check). ⚠ = fix staged on main working tree, NOT committed — see "Items Needing Human Attention" (17-day recurring caller-workflow commit failure).
SECURITY	✅	gh api repos/…/dependabot/alerts (open) → 0 alerts. Code Scanning: not configured (404, re-verified). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 satisfied by latest published 1.18.25 (devDep pinned 1.18.19; PR #377 bumps to 1.18.23; latest 1.18.25 is a patch — Renovate's domain, no constraint change needed). @opencode-ai/sdk (latest 1.18.25) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All uses: across .github/workflows/ (17 entries in 6 workflows, incl. fro-bot/agent@eeb3dbd… # v0.106.0) SHA-pinned at 40-char commits — no unpinned actions. Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries). Major devDeps: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377 bumps to 2.5.10); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → 26.4.0 (even LTS major — tracked by duplicate #278/#241, awaiting human pick). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.9 drift (#335 targets 0.4.5, #135 targets 0.4.3).
DEVELOPER EXPERIENCE	✅	On main (HEAD a4de20b, advanced since last run only by Renovate #379 fro-bot/agent 0.106.0): bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run build ✅ exit 0; bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls; bun run lint ✅ 0 issues (after biome.json $schema 2.5.5 → 2.5.9 fix — clears the lone lint info and supersedes stale #332 which only bumps to 2.5.8). Working-tree diff (minimal, 2 files): biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (+proc: NodeJS.EventEmitter const + explanatory comment + 2 process.off→proc.off call-site updates). Re-validated together (typecheck/lint/build/322 tests green on main) and under @types/bun@1.4.0. Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (17-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts process as NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale chore(dev): bump biome config schema to 2.5.8 #332 which only bumps to 2.5.8). The 08-13 → 08-29 runs each staged these (or equivalent) fixes in the working tree, but main (HEAD a4de20b, advanced only by Renovate chore(deps): update fro-bot/agent to v0.105.1 #378/chore(deps): update fro-bot/agent to v0.106.1 #379) still shows $schema 2.5.5 and the original rpc-cleanup.ts — verified again this run before applying the fix. Schedule-run history: 08-26→08-29 all report conclusion: success while headSha only moved via Renovate merges — the fro-bot/agent Post Run Fro Bot post-step completes SUCCESS yet commits NOTHING. The autoheal caller is NOT committing the working-tree diff it claims to own. Until it commits, every run re-applies the same fix and build(dev): update all non-major dependencies #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on build(dev): update all non-major dependencies #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. If Renovate won't rebase, close build(dev): update all non-major dependencies #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, MERGEABLE, real CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale, last real CI 2026-08-11). Left to human — autoheal cannot push to PR branches under working-dir delivery mode.
• Resolve duplicate @opentui/solid PR pair (fix(deps): update dependency @opentui/solid to v0.4.3 #135 Renovate 0.4.3 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 fro-bot 0.4.5): both stale and superseded by runtime drift to @opentui/core/@opentui/solid latest 0.5.9 (current pinned 0.2.7). Recommend closing both and letting Renovate open a fresh PR targeting 0.5.9, or updating fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 to 0.5.9. Coordinate with the OpenTUI 0.4→0.5 breaking-change review first.

Tasks for Copilot

• Investigate and fix the fro-bot/agent action's Post Run Fro Bot post-step so it detects working-tree diffs produced by the agent and commits + pushes them to main (or opens a PR) for schedule-triggered runs. Reproduce: trigger the Fro Bot workflow on schedule, have the agent make a trivial working-tree change, observe whether the post-step commits it. Expected: a commit lands on main; actual: no commit, headSha unchanged across consecutive successful runs (08-26 & 08-27 both c6c055d; 08-28 & 08-29 both fd0ee29). This is the root cause of the 17-day recurring autoheal fix loss and the reason PR build(dev): update all non-major dependencies #377 stays red. Single PR to the fro-bot/agent action repo.
• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.9 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135 and fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.11 (patch, non-major, devDependency, no changeset). After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.11). (Covered by PR build(dev): update all non-major dependencies #377 once it rebases green.)

Items Needing Human Attention

• CRITICAL (17-day recurring): The autoheal caller workflow (fro-bot/agent post-step) is not committing working-tree diffs to main. Seventeen consecutive days of autoheal fixes (rpc-cleanup.ts type fix + biome.json schema bump) have been staged in the working tree and silently discarded — main HEAD a4de20b still shows $schema 2.5.5 and the original rpc-cleanup.ts (verified before this run's fix). PR build(dev): update all non-major dependencies #377 stays red as a direct consequence. Requires investigation of the fro-bot/agent action's commit/post-step configuration — outside the autoheal agent's permissions (cannot git commit/git push/gh pr create/switch branches under the working-dir delivery contract).
• Decide which @types/node 24→26 PR to merge: chore(dev): update dependency @types/node to v26 #278 (Renovate, fresh, real CI green) vs chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale since 2026-08-11). Recommend merging chore(dev): update dependency @types/node to v26 #278 and closing chore(dev): update @types/node 24 → 26 (major) #241.
• Decide on the duplicate @opentui/solid PR pair: fix(deps): update dependency @opentui/solid to v0.4.3 #135 (Renovate, 0.4.3) vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (fro-bot, 0.4.5). Both superseded by runtime drift to latest 0.5.9 (current 0.2.7). Recommend closing both and opening a fresh PR targeting 0.5.9 after reviewing the 0.4→0.5 breaking changes.
• Consider closing stale fro-bot branches/PRs (chore(dev): update @types/node 24 → 26 (major) #241, chore(dev): bump biome config schema to 2.5.8 #332, fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335) that are superseded by Renovate equivalents or by this run's working-tree fixes, to reduce dashboard noise.
• @changesets/cli 3.0.1 major available (current pin 2.31.1) — out of autoheal's scoped devDep list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@a45c4d59…).

---

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33321747227 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing real CI — build(dev): update all non-major dependencies #377 Lint, typecheck, build, unit tests FAILURE (run 33285537818, 2026-08-30T01:23). Root cause re-confirmed from the actual failing log (7th day): @types/bun@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …) which shadows the generic off<K>(string \| symbol, …) inherited from EventEmitter → src/lib/rpc-cleanup.ts:38-39 TS2345 ('"beforeExit"'/'"SIGTERM"' is not assignable to '"memoryPressure"'). Fix staged in working tree on main: const proc: NodeJS.EventEmitter = process; proc.off('beforeExit'/'SIGTERM', …) (base interface keeps the generic overload; type-safe upcast, no as any). Verified by actually installing @types/bun@1.4.0 this run: tsc --noEmit clean with the fix; reverted via git checkout -- package.json bun.lock + bun install --frozen-lockfile (final diff = rpc-cleanup.ts + biome.json only). Clean under both @types/bun 1.3.14 (main) and 1.4.0 (build(dev): update all non-major dependencies #377). process.once(...) left unchanged (does not error — @types/node declares explicit once overloads for these events). New PR chore(deps): update fro-bot/agent to v0.106.2 #380 (Renovate, fro-bot/agent 0.106.1) green + CLEAN; chore(dev): update dependency @types/node to v26 #278's renovate/artifacts FAILURE is Renovate-internal, its real CI is green.
• SECURITY: 0 Dependabot alerts / 0 security-update PRs / 0 advisories; Code Scanning not configured (404, re-verified).
• HEALTH & MAINTENANCE: peer @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.25; @opencode-ai/sdk not a peer (transitive); all 17 workflow uses: entries across 6 workflows SHA-pinned (incl. fro-bot/agent@eeb3dbd… # v0.106.0); no changeset drift (pkg 0.12.1 == tag v0.12.1, .changeset/ = README.md + config.json only); devDeps current except @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241 duplicate, awaiting merge), @biomejs/biome 2.5.9→2.5.11 patch (build(dev): update all non-major dependencies #377→2.5.10), and runtime @opentui/* 0.2.7 vs 0.5.9 (fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 stale).
• DEVELOPER EXPERIENCE: bun install --frozen-lockfile / typecheck / build / test:unit (322 pass / 0 fail) all clean; lint 1 info (biome $schema 2.5.5 vs CLI 2.5.9) fixed in working tree (2.5.5 → 2.5.9); re-ran → 0 issues.
• Actions taken: applied rpc-cleanup.ts proc: NodeJS.EventEmitter routing + biome.json schema bump in working tree (caller workflow owns commit/push; no git/PR actions per working-dir delivery mode); perpetual issue Daily Autohealing Report #26 updated with today's section. Recurring blocker (17-day): prior runs' working-tree diff never landed on main — caller workflow must commit this run's diff or the fix cycle repeats and build(dev): update all non-major dependencies #377 stays red.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-29

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377). Only #377 (Renovate build(dev): update all non-major dependencies; bumps @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.10, @opencode-ai/plugin 1.18.19→1.18.23, mise opencode-ai 1.18.19→1.18.23, bfra-me/.github v4.19.0→v4.22.0, jdx/mise-action v4.2.5→v4.3.0) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 33170745732, 08-28 12:21). Root cause re-confirmed for the 6th consecutive day: src/lib/rpc-cleanup.ts:38-39 process.off('beforeExit'/'SIGTERM', …) errors TS2345 under @types/bun@1.4.0 because bun-types@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …), shadowing the generic off<K>(eventName: string | symbol, …) inherited from EventEmitter (process.once(...) is unaffected — @types/node declares explicit once overloads on Process). Fix re-applied in working tree on main: const proc: NodeJS.EventEmitter = process (type-safe upcast, Process extends EventEmitter) then proc.off(...) — restores the generic off overload from the base interface; no as any/@ts-expect-error. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently via package.json edit + bun install, tsc clean, then reverted package.json/bun.lock via git restore bun.lock + bun install --frozen-lockfile — no dep mutation in the final diff). bun run lint ✅ 0 issues, bun run build ✅ exit 0, bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls on main. Other 5 PRs: real CI SUCCESS (#278/#241/#135 also carry Renovate-internal renovate/artifacts FAILURE — not a CI check). ⚠ = fix staged on main working tree, NOT committed — see "Items Needing Human Attention" (16-day recurring caller-workflow commit failure).
SECURITY	✅	gh api repos/…/dependabot/alerts (open) → 0 alerts. Code Scanning: not configured (404). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 satisfied by latest published 1.18.25 (devDep pinned 1.18.19; PR #377 bumps to 1.18.23; latest 1.18.25 is a patch — Renovate's domain, no constraint change needed). @opencode-ai/sdk (latest 1.18.25) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All uses: across .github/workflows/ SHA-pinned at 40-char commits (re-verified: actions/cache, actions/checkout, actions/create-github-app-token, actions/setup-node, bfra-me/.github renovate+update-repo-settings, changesets/action, fro-bot/agent, jdx/mise-action, oven-sh/setup-bun). Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries). Major devDeps: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377 bumps to 2.5.10); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → 26.4.0 (even LTS major — tracked by duplicate #278/#241, awaiting human pick). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.9 drift (#335 targets 0.4.5, #135 targets 0.4.3).
DEVELOPER EXPERIENCE	✅	On main (HEAD fd0ee29): bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run build ✅ exit 0; bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls; bun run lint ✅ 0 issues (after biome.json $schema 2.5.5 → 2.5.9 fix — clears the lone lint info and supersedes stale #332 which only bumps to 2.5.8). Working-tree diff: biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (+proc: NodeJS.EventEmitter const + explanatory comment + 2 process.off→proc.off call-site updates). Re-validated together (typecheck/lint/build/322 tests green on main) and under @types/bun@1.4.0. Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (16-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts process as NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale chore(dev): bump biome config schema to 2.5.8 #332 which only bumps to 2.5.8). The 08-13 → 08-28 runs each staged these (or equivalent) fixes in the working tree, but main (HEAD fd0ee29, advanced only by Renovate chore(deps): update fro-bot/agent to v0.105.1 #378) still shows $schema 2.5.5 and the original rpc-cleanup.ts. The autoheal caller (fro-bot/agent post-step) is NOT committing the working-tree diff it claims to own. Until it commits, every run re-applies the same fix and build(dev): update all non-major dependencies #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on build(dev): update all non-major dependencies #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. If Renovate won't rebase, close build(dev): update all non-major dependencies #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, MERGEABLE, CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale, last CI 2026-08-11). Left to human — autoheal cannot push to PR branches under working-dir delivery mode.
• Resolve duplicate @opentui/solid PR pair (fix(deps): update dependency @opentui/solid to v0.4.3 #135 Renovate 0.4.3 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 fro-bot 0.4.5): both stale and superseded by runtime drift to @opentui/core/@opentui/solid latest 0.5.9 (current pinned 0.2.7). Recommend closing both and letting Renovate open a fresh PR targeting 0.5.9, or updating fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 to 0.5.9. Coordinate with the OpenTUI 0.4→0.5 breaking-change review first.

Tasks for Copilot

• Investigate and fix the fro-bot/agent action's Post Run Fro Bot post-step so it detects working-tree diffs produced by the agent and commits + pushes them to main (or opens a PR) for schedule-triggered runs. Reproduce: trigger the Fro Bot workflow on schedule, have the agent make a trivial working-tree change, observe whether the post-step commits it. Expected: a commit lands on main; actual: no commit, headSha unchanged across consecutive successful runs (08-26 & 08-27 both c6c055d). This is the root cause of the 16-day recurring autoheal fix loss and the reason PR build(dev): update all non-major dependencies #377 stays red. Single PR to the fro-bot/agent action repo.
• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.9 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes fix(deps): update dependency @opentui/solid to v0.4.3 #135 and fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.11 (patch, non-major, devDependency, no changeset). After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.11). (Covered by PR build(dev): update all non-major dependencies #377 once it rebases green.)

Items Needing Human Attention

• CRITICAL (16-day recurring): The autoheal caller workflow (fro-bot/agent post-step) is not committing working-tree diffs to main. Sixteen consecutive days of autoheal fixes (rpc-cleanup.ts type fix + biome.json schema bump) have been staged in the working tree and silently discarded — main HEAD fd0ee29 still shows $schema 2.5.5 and the original rpc-cleanup.ts. PR build(dev): update all non-major dependencies #377 stays red as a direct consequence. Requires investigation of the fro-bot/agent action's commit/post-step configuration — outside the autoheal agent's permissions (cannot git commit/git push/gh pr create/switch branches under the working-dir delivery contract).
• Decide which @types/node 24→26 PR to merge: chore(dev): update dependency @types/node to v26 #278 (Renovate, fresh, CI green) vs chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale since 2026-08-11). Recommend merging chore(dev): update dependency @types/node to v26 #278 and closing chore(dev): update @types/node 24 → 26 (major) #241.
• Decide on the duplicate @opentui/solid PR pair: fix(deps): update dependency @opentui/solid to v0.4.3 #135 (Renovate, 0.4.3) vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (fro-bot, 0.4.5). Both superseded by runtime drift to latest 0.5.9 (current 0.2.7). Recommend closing both and opening a fresh PR targeting 0.5.9 after reviewing the 0.4→0.5 breaking changes.
• Consider closing stale fro-bot branches/PRs (chore(dev): update @types/node 24 → 26 (major) #241, chore(dev): bump biome config schema to 2.5.8 #332, fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335) that are superseded by Renovate equivalents or by this run's working-tree fixes, to reduce dashboard noise.
• @changesets/cli 3.0.1 major available (current pin 2.31.1) — out of autoheal's scoped devDep list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@a45c4d59…).

---

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33262281118 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing CI — build(dev): update all non-major dependencies #377 Lint, typecheck, build, unit tests FAILURE (run 33170745732). Root cause (6th-day re-confirm): @types/bun@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …) which shadows the generic off<K>(string \| symbol, …) inherited from EventEmitter → src/lib/rpc-cleanup.ts:38-39 TS2345. Fix staged in working tree on main: const proc: NodeJS.EventEmitter = process; proc.off('beforeExit'/'SIGTERM', …) (base interface keeps the generic overload; type-safe upcast, no as any). Verified by actually installing @types/bun@1.4.0 this run: tsc --noEmit clean with the fix; reverted package.json/bun.lock via git restore bun.lock + bun install --frozen-lockfile (no dep mutation in final diff). Clean under both @types/bun 1.3.14 (main) and 1.4.0 (build(dev): update all non-major dependencies #377). process.once(...) left unchanged (does not error — @types/node declares explicit once overloads for these events).
• SECURITY: 0 Dependabot alerts / 0 security-update PRs / 0 advisories; Code Scanning not configured.
• HEALTH & MAINTENANCE: peer @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.25; @opencode-ai/sdk not a peer (transitive); all workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); devDeps current except @types/node 24→26 (chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241 duplicate, awaiting merge), @biomejs/biome 2.5.9→2.5.11 patch (build(dev): update all non-major dependencies #377→2.5.10), and runtime @opentui/* 0.2.7 vs 0.5.9 (fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 stale).
• DEVELOPER EXPERIENCE: bun install / typecheck / build / test:unit (322 pass) all clean; lint 1 info (biome $schema 2.5.5 vs CLI 2.5.9) fixed in working tree (2.5.5 → 2.5.9); re-ran → 0 infos.
• Actions taken: applied rpc-cleanup.ts proc: NodeJS.EventEmitter routing + biome.json schema bump in working tree (caller workflow owns commit/push; no git/PR actions per working-dir delivery mode); perpetual issue Daily Autohealing Report #26 updated with today's section. Recurring blocker (16-day): prior runs' working-tree diff never landed on main — caller workflow must commit this run's diff or the fix cycle repeats and build(dev): update all non-major dependencies #377 stays red.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-28

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377). Only #377 (Renovate build(dev): update all non-major dependencies; bumps @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.10, @opencode-ai/plugin 1.18.19→1.18.22, mise opencode-ai 1.18.19→1.18.22) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 33170745732). Root cause re-confirmed: src/lib/rpc-cleanup.ts:38-39 process.off('beforeExit' / 'SIGTERM', …) errors TS2345 under @types/bun@1.4.0 because bun-types@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …), shadowing the generic off<K>(eventName: string | symbol, …) inherited from EventEmitter (process.once(...) is unaffected — @types/node declares explicit once overloads on Process). Fix re-applied in working tree on main: route off through const proc: NodeJS.EventEmitter = process (the base interface retains the generic off overload, unaffected by the bun augmentation); no as any/@ts-expect-error. Verified tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently via package.json edit + bun install, error reproduced verbatim, fix applied, confirmed clean, then git restore package.json bun.lock + bun install to restore — no package.json/bun.lock mutation in the final diff). bun run lint ✅ 0 issues, bun run build ✅ exit 0, bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls on main. Other 5 PRs: real CI SUCCESS (#278/#241/#135 also carry Renovate-internal renovate/artifacts FAILURE — not a CI check). ⚠ = fix staged on main working tree, NOT committed — see "Items Needing Human Attention" (recurring 15-day caller-workflow commit failure).
SECURITY	✅	gh api repos/…/dependabot/alerts (open) → 0 alerts. Code Scanning: not configured (404). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 satisfied by latest published 1.18.25 (devDep pinned 1.18.19; PR #377 bumps to 1.18.22; latest 1.18.25 is a patch — Renovate's domain, no constraint change needed). @opencode-ai/sdk (latest 1.18.25) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All uses: across .github/workflows/ SHA-pinned at 40-char commits (re-verified: actions/cache, actions/checkout, actions/create-github-app-token, actions/setup-node, bfra-me/.github renovate+update-repo-settings, changesets/action, fro-bot/agent, jdx/mise-action, oven-sh/setup-bun). Clean changeset hygiene: pkg 0.12.1, .changeset/ holds only README.md + config.json (no unreleased entries). Major devDeps: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → 2.5.11 (patch, #377 bumps to 2.5.10); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → 26.4.0 (even LTS major — tracked by duplicate #278/#241, awaiting human pick). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.8 drift (#335 targets 0.4.5, #135 targets 0.4.3).
DEVELOPER EXPERIENCE	✅	On main (HEAD fd0ee29): bun install clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean (after rpc-cleanup.ts fix); bun run build ✅ exit 0; bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls; bun run lint ✅ 0 issues (after biome.json $schema 2.5.5 → 2.5.9 fix — clears the lone lint info and supersedes stale #332 which only bumps to 2.5.8). Working-tree diff: biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (proc: NodeJS.EventEmitter const + 2 process.off→proc.off call-site updates + explanatory comment). Re-validated together (typecheck/lint/build/322 tests green on main) and under @types/bun@1.4.0. Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (15-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts process as NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale chore(dev): bump biome config schema to 2.5.8 #332 which only bumps to 2.5.8). The 08-13 → 08-27 runs each staged these (or equivalent) fixes in the working tree, but main (HEAD fd0ee29, advanced only by Renovate chore(deps): update fro-bot/agent to v0.105.1 #378) still shows $schema 2.5.5 and the original rpc-cleanup.ts. Verified via gh run list --workflow=fro-bot.yaml --event=schedule: the 08-26 and 08-27 schedule runs both report conclusion: success with identical headSha c6c055d — i.e. the fro-bot/agent action's Post Run Fro Bot step completes SUCCESS yet commits NOTHING. The autoheal caller is NOT committing the working-tree diff it claims to own. Investigate the fro-bot/agent action's post-step commit logic (diff-detect → commit → push) for schedule-triggered runs; until it commits, every run re-applies the same fix and build(dev): update all non-major dependencies #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on build(dev): update all non-major dependencies #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. If Renovate won't rebase, close build(dev): update all non-major dependencies #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge chore(dev): update dependency @types/node to v26 #278 (Renovate, 26.x, MERGEABLE, CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale, last CI 2026-08-11). Left to human — autoheal cannot push to PR branches under working-dir delivery mode.
• Resolve duplicate @opentui/solid PR pair (fix(deps): update dependency @opentui/solid to v0.4.3 #135 Renovate 0.4.3 vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 fro-bot 0.4.5): both are stale and both are superseded by runtime drift to @opentui/core/@opentui/solid latest 0.5.8 (current pinned 0.2.7). Recommend closing both and letting Renovate open a fresh PR targeting 0.5.8, or updating fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 to 0.5.8. Coordinate with the OpenTUI 0.4→0.5 breaking-change review first.

Tasks for Copilot

• Investigate and fix the fro-bot/agent action's Post Run Fro Bot post-step so it detects working-tree diffs produced by the agent and commits + pushes them to main (or opens a PR) for schedule-triggered runs. Reproduce: trigger the Fro Bot workflow on schedule, have the agent make a trivial working-tree change, observe whether the post-step commits it. Expected: a commit lands on main; actual: no commit, headSha unchanged across consecutive successful runs. This is the root cause of the 15-day recurring autoheal fix loss and the reason PR build(dev): update all non-major dependencies #377 stays red. Single PR to the fro-bot/agent action repo.

Items Needing Human Attention

• CRITICAL (15-day recurring): The autoheal caller workflow (fro-bot/agent post-step) is not committing working-tree diffs to main. Fifteen consecutive days of autoheal fixes (rpc-cleanup.ts type fix + biome.json schema bump) have been staged in the working tree and silently discarded — confirmed by unchanged headSha across the 08-26 & 08-27 schedule runs. PR build(dev): update all non-major dependencies #377 stays red as a direct consequence. Requires investigation of the fro-bot/agent action's commit/post-step configuration — outside the autoheal agent's permissions (cannot git commit/git push/gh pr create/switch branches under the working-dir delivery contract).
• Decide which @types/node 24→26 PR to merge: chore(dev): update dependency @types/node to v26 #278 (Renovate, fresh, CI green) vs chore(dev): update @types/node 24 → 26 (major) #241 (fro-bot, stale since 2026-08-11). Recommend merging chore(dev): update dependency @types/node to v26 #278 and closing chore(dev): update @types/node 24 → 26 (major) #241.
• Decide on the duplicate @opentui/solid PR pair: fix(deps): update dependency @opentui/solid to v0.4.3 #135 (Renovate, 0.4.3) vs fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (fro-bot, 0.4.5). Both superseded by runtime drift to latest 0.5.8 (current 0.2.7). Recommend closing both and opening a fresh PR targeting 0.5.8 after reviewing the 0.4→0.5 breaking changes.
• Consider closing stale fro-bot branches/PRs (chore(dev): update @types/node 24 → 26 (major) #241, chore(dev): bump biome config schema to 2.5.8 #332, fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335) that are superseded by Renovate equivalents or by this run's working-tree fixes, to reduce dashboard noise.

---

Update — 2026-08-27

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377). Only #377 (Renovate build(dev): update all non-major dependencies; bumps @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.10, @opencode-ai/plugin 1.18.19→1.18.22, mise opencode-ai 1.18.19→1.18.22) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 33091769781). Root cause re-confirmed and reproduced locally by actually installing @types/bun@1.4.0 (not a simulated copy): bun-types@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …) (lines 110-117), which shadows the generic off<K>(eventName: string | symbol, …) inherited from EventEmitter → src/lib/rpc-cleanup.ts:38-39 process.off('beforeExit' / 'SIGTERM', …) errors TS2345. process.once(...) does not error — @types/node declares explicit once(event: "beforeExit"/"SIGTERM", …) overloads on Process that merge cleanly with the bun augmentation; only off/removeListener are shadowed (they're inherited, not re-declared, so the bun overload replaces them). Fixed in working tree on main via a minimal change: const proc = process as NodeJS.EventEmitter then proc.off(...) — the base EventEmitter interface retains the generic off<K> overload, unaffected by bun's NodeJS.Process augmentation. No as any/@ts-ignore, no new interface. Verified: tsc --noEmit clean under both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (installed transiently via package.json edit + bun install, error reproduced verbatim, fix applied, confirmed clean, then git restore package.json bun.lock + bun install to restore — no package.json/bun.lock mutation in the final diff). bun run lint ✅, bun run build ✅ exit 0, bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls on main. Other 5 PRs: real CI SUCCESS (#278/#241/#135 also carry Renovate-internal renovate/artifacts FAILURE — not a CI check). ⚠ = fix staged on main working tree, not pushed to #377's branch (working-dir delivery mode forbids PR-branch checkout/commit/push).
SECURITY	✅	gh api repos/…/dependabot/alerts (open) → 0 alerts. Code Scanning: not configured (404). No security-labeled PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 satisfied by latest published 1.18.23 (devDep pinned 1.18.19; PR #377 bumps to 1.18.22; latest 1.18.23 is a patch — Renovate's domain, no constraint change needed). @opencode-ai/sdk (latest 1.18.23) intentionally NOT a peer (transitive via @opencode-ai/plugin; never imported in src/). All uses: across .github/workflows/ SHA-pinned at 40-char commits (actions/cache, actions/checkout, actions/create-github-app-token, actions/setup-node, bfra-me/.github renovate+update-repo-settings, changesets/action, fro-bot/agent, jdx/mise-action, oven-sh/setup-bun). Clean changeset hygiene: pkg 0.12.1, .changeset/ holds only README.md + config.json (no unreleased entries); user-visible PRs #335 and #135 each carry a changeset. Major devDeps: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → 2.5.10 (patch, #377); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → 26.4.0 (even LTS major — tracked by duplicate #278/#241, awaiting human pick). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.8 drift (#335 targets 0.4.5).
DEVELOPER EXPERIENCE	✅	On main (HEAD c6c055d, unchanged since last run): bun install clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0; bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls; bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.9) — fixed in working tree by bumping $schema to 2.5.9; re-ran bun run lint → 0 infos. Also applied the src/lib/rpc-cleanup.ts proc: NodeJS.EventEmitter routing fix; both changes re-validated together (typecheck/lint/build/322 tests green on main) and under @types/bun@1.4.0. Working-tree diff: biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (+proc const + 2 process.off→proc.off call-site updates). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (14-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts process as NodeJS.EventEmitter routing for process.off (unblocks PR build(dev): update all non-major dependencies #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale #332 which only bumps to 2.5.8). The 08-13 → 08-26 runs each staged these (or equivalent) fixes in the working tree, but main (HEAD c6c055d) still shows $schema 2.5.5 and the original rpc-cleanup.ts — the autoheal caller workflow is NOT committing the working-tree diff it claims to own. Investigate the caller workflow's diff-detect/commit step; until it commits, every run re-applies the same fix and #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. If Renovate won't rebase, close #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge #278 (Renovate, 26.x, MERGEABLE, CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close #241 (fro-bot, stale, last CI 2026-08-11). Left to human — autohealing won't choose between duplicate major bumps.
• Resolve duplicate @opentui runtime upgrade pair: #335 (0.4.5, has changeset) vs #135 (0.4.3, older). Recommend closing #135 in favor of #335 (satisfies @opencode-ai/plugin peer @opentui/* >=0.4.5), or close both in favor of the coordinated 0.2.7 → 0.5.8 major upgrade (delegated to Copilot below). Left to human.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.8 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes #135 and #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.10 (patch, non-major, devDependency, no changeset). After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.10). (Covered by PR #377 once it rebases green.)

Items Needing Human Attention

• ⚠ Autoheal working-tree diff not persisting to main (14-day recurring): the 08-13 → 08-26 runs each applied biome.json $schema 2.5.5 → 2.5.9 (and 08-24+ added an rpc-cleanup.ts cast) in the working tree, but main HEAD c6c055d still shows $schema 2.5.5 and the original rpc-cleanup.ts — the caller workflow that owns diff-detect/commit is silently dropping the diff. Re-applied this run (cleaner, minimal proc as NodeJS.EventEmitter routing, verified against a real @types/bun@1.4.0 install). Verify the autoheal caller workflow actually commits the working-tree diff before this run ends, or the lint info and #377's typecheck failure persist indefinitely.
• PR #377 typecheck failure root-caused + fixed on main (re-confirmed, real @types/bun@1.4.0 install): @types/bun@1.4.0 adds off(event: "memoryPressure", …) overloads to NodeJS.Process that shadow the generic off<K>(string \| symbol, …) → src/lib/rpc-cleanup.ts:38-39 TS2345. proc as NodeJS.EventEmitter routing fix staged in working tree; verified clean under both @types/bun 1.3.14 and 1.4.0. Land on main, then rebase #377 to unblock automerge.
• @types/node duplicate PR pair — #278 (Renovate, 26.x, MERGEABLE, CI green; latest published 26.4.0) vs #241 (fro-bot, stale). Merge #278 (tick its rebase/retry checkbox to clear the renovate/artifacts FAILURE first) and close #241.
• @opentui/* runtime major drift — pinned at 0.2.7 while latest is 0.5.8 (6-minor gap, pre-1.0 breaking). Open PRs #135 (0.4.3) and #335 (0.4.5) both target intermediate 0.4.x and are stale. #335 at least satisfies the @opencode-ai/plugin peer @opentui/* >=0.4.5. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.8 Copilot task above.
• @changesets/cli 3.x major available (current pin 2.31.1, latest 3.0.1) — out of autoheal's scoped devDep list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@a45c4d59…).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 33109024074 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing CI — #377 Lint, typecheck, build, unit tests FAILURE (run 33091769781). Root cause: @types/bun@1.4.0 overrides.d.ts augments NodeJS.Process with off(event: "memoryPressure", …) which shadows the generic off<K>(string \| symbol, …) inherited from EventEmitter → src/lib/rpc-cleanup.ts:38-39 TS2345. Fix staged in working tree on main: const proc = process as NodeJS.EventEmitter; proc.off('beforeExit'/'SIGTERM', …) (base interface keeps the generic overload). Verified by actually installing @types/bun@1.4.0: reproduced the TS2345 error verbatim, applied fix, confirmed tsc clean, then reverted package.json/bun.lock via git restore + bun install (no dep mutation in final diff). Clean under both @types/bun 1.3.14 (main) and 1.4.0 (#377). process.once(...) left unchanged (does not error — @types/node declares explicit once overloads for these events).
• SECURITY: 0 Dependabot alerts / 0 security-update PRs / 0 advisories; Code Scanning not configured.
• HEALTH & MAINTENANCE: peer @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.23; @opencode-ai/sdk not a peer (transitive); all workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1; user-visible PRs #335/#135 carry changesets); devDeps current except @types/node 24→26 (#278/#241 duplicate, awaiting merge) and runtime @opentui/* 0.2.7 vs 0.5.8 (#135/#335 stale).
• DEVELOPER EXPERIENCE: bun install / typecheck / build / test:unit (322 pass) all clean; lint 1 info (biome $schema 2.5.5 vs CLI 2.5.9) fixed in working tree (2.5.5 → 2.5.9); re-ran → 0 infos.
• Actions taken: applied rpc-cleanup.ts proc as NodeJS.EventEmitter routing + biome.json schema bump in working tree (caller workflow owns commit/push; no git/PR actions per working-dir delivery mode); perpetual issue #26 updated with today's section. Recurring blocker (14-day): prior runs' working-tree diff never landed on main — caller workflow must commit this run's diff or the fix cycle repeats.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-26

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377). Only #377 (Renovate build(dev): update all non-major dependencies; bumps @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.10, @opencode-ai/plugin 1.18.19→1.18.21, @types/bun→1.4.0) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 32949359511). Root cause re-confirmed and faithfully reproduced locally: bun-types@1.4.0 overrides.d.ts adds off(event: "memoryPressure", …) (and removeListener/once/on/…) overloads to NodeJS.Process; under TS overload resolution these shadow the generic off<K>(event: string | symbol, …) inherited from EventEmitter so process.off('beforeExit' / 'SIGTERM', …) errors TS2345 at src/lib/rpc-cleanup.ts:38-39. (process.once(...) does not error — only off/removeListener do — verified empirically.) Fixed in working tree on main via a minimal change: route the two process.off(...) removal calls through const emitter: NodeJS.EventEmitter = process (the base EventEmitter interface retains the generic off<K> overload, unaffected by bun's NodeJS.Process augmentation; no as any/@ts-ignore, no new interface). Verified: tsc --noEmit clean under both @types/bun@1.3.14 (current main) and a faithful local reproduction of @types/bun@1.4.0 (copied the exact memoryPressure overload block from the 1.4.0 overrides.d.ts fetched via CDN into the installed node_modules/bun-types/overrides.d.ts, reproduced the TS2345 error verbatim, applied the fix, confirmed clean, then restored node_modules — no package.json/bun.lock mutation). bun run lint ✅, bun run build ✅ exit 0, bun test tests/ ✅ 322 pass / 0 fail / 1279 expect() calls on main. Other 5 PRs: real CI SUCCESS (#278/#241/#135 also carry Renovate-internal renovate/artifacts FAILURE — not a CI check). ⚠ = fix staged on main working tree, not pushed to #377's branch (working-dir delivery mode forbids PR-branch checkout/commit/push).
SECURITY	✅	gh api repos/…/dependabot/alerts (open) → 0 alerts. Code Scanning: not configured (404). Repo security advisories: 0. No security-update PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 satisfied by latest published 1.18.21 (PR #377 CI installed it successfully; prior runs noted latest 1.18.23 — a patch, Renovate's domain, no constraint change needed; devDep pinned 1.18.19). @opencode-ai/sdk intentionally NOT a peer (never imported in src/, per design notes). All 10 uses: across .github/workflows/ SHA-pinned at 40-char commits (actions/cache, actions/checkout, actions/create-github-app-token, actions/setup-node, bfra-me/.github renovate+update-repo-settings, changesets/action, fro-bot/agent, jdx/mise-action, oven-sh/setup-bun). Clean changeset hygiene: pkg 0.12.1 == latest tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries). Major devDeps: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → 2.5.10 (patch, #377); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → 26.x (even LTS major — tracked by #278 Renovate MERGEABLE+green CI / #241 fro-bot stale). No new major-bump PR needed from autoheal.
DEVELOPER EXPERIENCE	✅	On main (HEAD c6c055d, unchanged since last run): bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0; bun test tests/ ✅ 322 pass / 0 fail / 1279 expect() calls; bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.9) — fixed in working tree by bumping $schema to 2.5.9; re-ran bun run lint → 0 infos. Also applied the src/lib/rpc-cleanup.ts emitter routing fix; both changes re-validated together (typecheck/lint/build/322 tests green on main) and under the reproduced @types/bun@1.4.0. Working-tree diff: biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (+emitter const + comment, 2 process.off→emitter.off call-site updates, 1 comment-word update). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (13-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts emitter: NodeJS.EventEmitter routing for process.off (unblocks PR #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale #332 which only bumps to 2.5.8). The 08-13 → 08-25 runs each staged these (or equivalent) fixes in the working tree, but main (HEAD c6c055d) still shows $schema 2.5.5 and the original rpc-cleanup.ts — the autoheal caller workflow is NOT committing the working-tree diff it claims to own. Investigate the caller workflow's diff-detect/commit step; until it commits, every run re-applies the same fix and #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. If Renovate won't rebase, close #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge #278 (Renovate, 26.x, MERGEABLE, CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close #241 (fro-bot, stale, last CI 2026-08-11). Left to human — autohealing won't choose between duplicate major bumps.
• Resolve duplicate @opentui runtime upgrade pair: #335 (0.4.5, has changeset + overrides.@opentui/core dedupe) vs #135 (0.4.3, older). Both target 0.4.x while latest is 0.5.7. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.7 major upgrade (delegated to Copilot below). Left to human.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.7 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes #135 and #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.10 (patch, non-major, devDependency, no changeset). After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.10). (Covered by PR #377 once it rebases green.)

Items Needing Human Attention

• ⚠ Autoheal working-tree diff not persisting to main (13-day recurring): the 08-13 → 08-25 runs each applied biome.json $schema 2.5.5 → 2.5.9 (and 08-24/08-25 added an rpc-cleanup.ts cast) in the working tree, but main HEAD c6c055d still shows $schema 2.5.5 and the original rpc-cleanup.ts — the caller workflow that owns diff-detect/commit is silently dropping the diff. Re-applied this run (cleaner, more minimal emitter routing). Verify the autoheal caller workflow actually commits the working-tree diff before this run ends, or the lint info and #377's typecheck failure persist indefinitely.
• PR #377 typecheck failure root-caused + fixed on main (re-confirmed, faithfully reproduced): @types/bun@1.4.0 adds off(event: "memoryPressure", …) overloads to NodeJS.Process that shadow the generic off<K>(string \| symbol, …) → src/lib/rpc-cleanup.ts:38-39 TS2345. emitter: NodeJS.EventEmitter routing fix staged in working tree; verified clean under both @types/bun 1.3.14 and reproduced 1.4.0. Land on main, then rebase #377 to unblock automerge.
• @types/node duplicate PR pair — #278 (Renovate, 26.x, MERGEABLE, CI green; latest published 26.3.0) vs #241 (fro-bot, stale). Merge #278 (tick its rebase/retry checkbox to clear the renovate/artifacts FAILURE first) and close #241.
• @opentui/* runtime major drift — pinned at 0.2.7 while latest is 0.5.7 (5-minor gap, pre-1.0 breaking). Open PRs #135 (0.4.3) and #335 (0.4.5) both target intermediate 0.4.x and are stale. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.7 Copilot task above.
• @changesets/cli 3.x major available (current pin 2.31.1) — out of autoheal's scoped devDep list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@a45c4d59…).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32988639996 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing CI — #377 Lint, typecheck, build, unit tests FAILURE (run 32949359511). Root cause: @types/bun@1.4.0 overrides.d.ts adds off(event: "memoryPressure", …) overloads to NodeJS.Process that shadow the generic off<K>(string \| symbol, …) → src/lib/rpc-cleanup.ts:38-39 TS2345. Fix staged in working tree on main: route the two process.off(...) calls through const emitter: NodeJS.EventEmitter = process (base interface keeps the generic overload). Verified clean under both @types/bun 1.3.14 (main) and a faithful local reproduction of 1.4.0 (exact memoryPressure block copied from the 1.4.0 overrides.d.ts into node_modules, error reproduced verbatim then resolved, node_modules restored — no package.json/bun.lock mutation). process.once(...) left unchanged (does not error under 1.4.0).
• SECURITY: 0 Dependabot alerts / 0 security-update PRs / 0 advisories; Code Scanning not configured.
• HEALTH & MAINTENANCE: peer @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.21; @opencode-ai/sdk not a peer; all 10 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); devDeps current except @types/node 24→26 (#278/#241 duplicate, awaiting merge) and runtime @opentui/* 0.2.7 vs 0.5.7 (#135/#335 stale).
• DEVELOPER EXPERIENCE: bun install / typecheck / build / test:unit (322 pass) all clean; lint 1 info (biome $schema 2.5.5 vs CLI 2.5.9) fixed in working tree (2.5.5 → 2.5.9); re-ran → 0 infos.
• Actions taken: re-applied rpc-cleanup.ts emitter routing + biome.json schema bump in working tree (caller workflow owns commit/push; no git/PR actions per working-dir delivery mode); perpetual issue #26 updated with today's section. Recurring blocker: prior runs' working-tree diff never landed on main — caller workflow must commit this run's diff or the fix cycle repeats.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-25

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377). Only #377 (Renovate build(dev): update all non-major dependencies; bumps @types/bun 1.3.14→1.4.0, @biomejs/biome 2.5.9→2.5.10, @opencode-ai/plugin 1.18.19→1.18.21) has a failing real CI check: Lint, typecheck, build, unit tests FAILURE (run 32848132674). Root cause identical to 08-24: @types/bun@1.4.0 narrows NodeJS.Process.off/removeListener to the Bun-only "memoryPressure" event → src/lib/rpc-cleanup.ts:38-39 process.off('beforeExit' / 'SIGTERM', …) errors TS2345. Fixed again in working tree on main via a minimal ProcessEventEmitter cast interface routing process.once/process.off through the standard `string
SECURITY	✅	Dependabot open alerts: 0. Code Scanning: not configured (404 — no analysis found). Repo security advisories: 0. No security-update PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 satisfied by latest published 1.18.23 (devDep pinned 1.18.19; PR #377 bumps to 1.18.21; latest 1.18.23 is a patch — Renovate's domain, no constraint change needed). @opencode-ai/sdk (latest 1.18.23) intentionally NOT a peer (never imported in src/, per design notes). All 10 uses: across .github/workflows/ SHA-pinned at 40-char commits (actions/cache, actions/checkout, actions/create-github-app-token, actions/setup-node, bfra-me/.github renovate+update-repo-settings, changesets/action, fro-bot/agent, jdx/mise-action, oven-sh/setup-bun). Clean changeset hygiene: pkg 0.12.1, .changeset/ holds only README.md + config.json (no unreleased entries). Major devDeps: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → 2.5.10 (patch, #377); @types/bun 1.3.14 → 1.4.0 (minor, #377 — unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → 26.3.0 (even LTS major — tracked by #278 Renovate MERGEABLE+green CI / #241 fro-bot stale-UNKNOWN). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PR pairs needing human pick (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.7 drift.
DEVELOPER EXPERIENCE	✅	On main (HEAD c6c055d, unchanged since last run): bun install clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0; bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls; bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.9) — fixed in working tree by bumping $schema to 2.5.9; re-ran bun run lint → 0 infos. Also applied the src/lib/rpc-cleanup.ts ProcessEventEmitter cast; both changes re-validated together (typecheck/lint/build/322 tests green on main) and under @types/bun@1.4.0. Working-tree diff: biome.json (1 line, $schema) + src/lib/rpc-cleanup.ts (+ProcessEventEmitter interface + emitter cast on 4 call sites). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• CRITICAL / RECURRING (12-day): Land this run's working-tree diff on main: (1) src/lib/rpc-cleanup.ts ProcessEventEmitter cast (unblocks PR #377's @types/bun@1.4.0 bump); (2) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale #332 which only bumps to 2.5.8). The 08-13 → 08-24 runs each staged these exact fixes in the working tree, but main (HEAD c6c055d) still shows $schema 2.5.5 and the original rpc-cleanup.ts — the autoheal caller workflow is NOT committing the working-tree diff it claims to own. Investigate the caller workflow's diff-detect/commit step; until it commits, every run re-applies the same fix and #377 stays red.
• Once the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI green → automerge. If Renovate won't rebase, close #377 and let it recreate (immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge #278 (Renovate, 26.x, MERGEABLE, CI green; tick rebase/retry to clear renovate/artifacts FAILURE before merging) and close #241 (fro-bot, stale UNKNOWN, last CI 2026-08-11). Left to human — autohealing won't choose between duplicate major bumps.
• Resolve duplicate @opentui runtime upgrade pair: #335 (0.4.5, has changeset + overrides.@opentui/core dedupe) vs #135 (0.4.3, older). Both target 0.4.x while latest is 0.5.7. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.7 major upgrade (delegated to Copilot below). Left to human.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.7 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes #135 and #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.10 (patch, non-major, devDependency, no changeset). After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.10). (Covered by PR #377 once it rebases green.)

Items Needing Human Attention

• ⚠ Autoheal working-tree diff not persisting to main (12-day recurring): the 08-13 → 08-24 runs each applied biome.json $schema 2.5.5 → 2.5.9 (and 08-24 added the rpc-cleanup.ts cast) in the working tree, but main HEAD c6c055d still shows $schema 2.5.5 and the original rpc-cleanup.ts — the caller workflow that owns diff-detect/commit is silently dropping the diff. Re-applied this run. Verify the autoheal caller workflow actually commits the working-tree diff before this run ends, or the lint info and #377's typecheck failure persist indefinitely.
• PR #377 typecheck failure root-caused + fixed on main (re-confirmed): @types/bun@1.4.0 narrows process.off/removeListener to "memoryPressure" only → src/lib/rpc-cleanup.ts:38-39 TS2345. ProcessEventEmitter cast fix staged in working tree; verified clean under both @types/bun 1.3.14 and 1.4.0. Land on main, then rebase #377 to unblock automerge.
• @types/node duplicate PR pair — #278 (Renovate, 26.x, MERGEABLE, CI green; latest published 26.3.0) vs #241 (fro-bot, stale, UNKNOWN). Merge #278 (tick its rebase/retry checkbox to clear the renovate/artifacts FAILURE first) and close #241.
• @opentui/* runtime major drift — pinned at 0.2.7 while latest is 0.5.7 (5-minor gap, pre-1.0 breaking). Open PRs #135 (0.4.3) and #335 (0.4.5) both target intermediate 0.4.x and are stale. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.7 Copilot task above.
• @changesets/cli 3.x major available (current pin 2.31.1) — out of autoheal's scoped devDep list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@a45c4d59…).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32870655989 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing CI — #377 Lint, typecheck, build, unit tests FAILURE (run 32848132674). Root cause: @types/bun@1.4.0 narrows process.off to "memoryPressure" → src/lib/rpc-cleanup.ts:38-39 TS2345. Fix (ProcessEventEmitter cast) staged in working tree on main; verified clean under both @types/bun 1.3.14 and 1.4.0.
• SECURITY: 0 Dependabot alerts / 0 security-update PRs / 0 advisories; Code Scanning not configured.
• HEALTH & MAINTENANCE: peer @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.23; @opencode-ai/sdk not a peer; all 10 workflow uses: SHA-pinned; no changeset drift; devDeps current except @types/node 24→26 (#278/#241 duplicate, awaiting merge) and runtime @opentui/* 0.2.7 vs 0.5.7 (#135/#335 stale).
• DEVELOPER EXPERIENCE: bun install / typecheck / build / test:unit (322 pass) all clean; lint 1 info (biome $schema 2.5.5 vs CLI 2.5.9) fixed in working tree (2.5.5 → 2.5.9); re-ran → 0 infos.
• Actions taken: re-applied rpc-cleanup.ts cast + biome.json schema bump in working tree (caller workflow owns commit/push; no git/PR actions per working-dir delivery mode); perpetual issue #26 updated with today's section. Recurring blocker: prior runs' working-tree diff never landed on main — caller workflow must commit this run's diff or the fix cycle repeats.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-24

Summary

Category	Status	Actions
ERRORED PRs	⚠️	6 open PRs (#135, #241, #278, #332, #335, #377). #377 (Renovate build(dev): update all non-major dependencies, @types/bun 1.3.14→1.4.0 + @opencode-ai/plugin 1.18.19→1.18.20 + bfra-me/.github v4.20.0) has a FAILING Lint, typecheck, build, unit tests CI run (run 32708286790). Root cause: @types/bun 1.4.0 (bun-types/overrides.d.ts) narrows NodeJS.Process.off/removeListener to the Bun-specific "memoryPressure" event only; @types/node doesn't re-declare off on Process, so process.off('beforeExit', …) in src/lib/rpc-cleanup.ts:38-39 errors TS2345. Fixed in working tree on main: added a minimal ProcessEventEmitter cast interface routing process.once/process.off through the standard `string
SECURITY	✅	GET /repos/…/dependabot/alerts?state=open → empty (0 open). Code Scanning API 404 (not configured). No security-update PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest published 1.18.22 (devDep 1.18.19 — PR #377 bumps to 1.18.20; latest 1.18.22 non-major, left to Renovate). @opencode-ai/sdk (latest 1.18.22) intentionally NOT a peer (never imported in src/). All 16 uses: across .github/workflows/ SHA-pinned at 40-char commits (re-verified ci/fro-bot/copilot-setup-steps/release/renovate/update-repo-settings). Clean changeset hygiene: pkg 0.12.1, .changeset/ holds only README.md + config.json (no unreleased entries); runtime-dep PRs #135 and #335 both carry changesets. Major devDep landscape: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → latest 2.5.10 (patch, non-major — Renovate); @types/bun 1.3.14 → latest 1.4.0 (MINOR, non-major — in #377, now unblocked by this run's rpc-cleanup.ts fix); rimraf 6.1.3 = latest; @types/node 24.13.3 → latest 26.2.0 (even LTS major — already tracked by #278 Renovate MERGEABLE+green CI and #241 fro-bot stale/UNKNOWN). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PRs needing human pick (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.7 (PRs #135/#335 target intermediate 0.4.x).
DEVELOPER EXPERIENCE	✅	On main (HEAD c6c055d, new since last run via #376 fro-bot/agent v0.105.0): bun install clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0; bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.9) — fixed in working tree by bumping $schema to 2.5.9 (matches installed CLI); re-ran bun run lint → 0 infos. Also applied the src/lib/rpc-cleanup.ts type-compat fix above; both changes re-validated together (typecheck/lint/build/322 tests green). Working-tree diff: biome.json (1 line) + src/lib/rpc-cleanup.ts (ProcessEventEmitter cast). Caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• Land this run's working-tree diff on main: (1) biome.json $schema 2.5.5 → 2.5.9 (clears the lone lint info; supersedes stale #332 which only bumps to 2.5.8); (2) src/lib/rpc-cleanup.ts ProcessEventEmitter cast (unblocks PR #377's @types/bun@1.4.0 bump). Confirm the caller workflow commits both — prior runs (08-13→08-23) repeatedly applied the biome.json schema bump in the working tree but main still shows 2.5.5, so verify the pipeline picks up this run's diff.
• After the rpc-cleanup.ts fix lands on main, tick the rebase/retry checkbox on #377 (Renovate all-minor-patch) so Renovate rebases onto the fixed main → CI should go green → automerge. If Renovate doesn't rebase promptly, close #377 and let Renovate recreate it (it's an immortal Renovate PR).
• Resolve duplicate @types/node major PR pair: merge #278 (Renovate, 26.2.0, MERGEABLE, CI green; carries cosmetic renovate/artifacts FAILURE — tick rebase/retry to clear before merging) and close #241 (fro-bot, stale UNKNOWN, last CI 2026-08-11). Left to human — autohealing won't choose between duplicate major bumps.
• Resolve duplicate @opentui runtime upgrade pair: #335 (0.4.5, has changeset + overrides.@opentui/core dedupe) vs #135 (0.4.3, older). Both target 0.4.x while latest is 0.5.7. Recommend closing both in favor of a coordinated 0.2.7 → 0.5.7 major upgrade (delegated to Copilot). Left to human.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.7 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes #135 and #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.10 (patch, non-major) — keeps the linter current; devDependency, no changeset. After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.10).

Items Needing Human Attention

• biome.json schema fix not persisting: the 2026-08-13 through 2026-08-23 runs each bumped $schema in the working tree, but main still shows 2.5.5 (verified again this run at HEAD c6c055d). Re-applied this run (2.5.5 → 2.5.9 to match installed @biomejs/biome@2.5.9). Verify the caller workflow commits the working-tree diff so the lint info stays cleared; then close #332 (it targets stale 2.5.8).
• PR #377 typecheck failure root-caused and fixed on main: @types/bun@1.4.0 narrows process.off/removeListener to "memoryPressure" only → src/lib/rpc-cleanup.ts TS2345. Fix (ProcessEventEmitter cast) staged in working tree. Once it lands on main, rebase #377 to unblock automerge.
• @types/node duplicate PR pair — #278 (Renovate, 26.2.0, MERGEABLE, CI green) vs #241 (fro-bot, stale, UNKNOWN). Merge #278 (tick its rebase/retry checkbox to clear the renovate/artifacts FAILURE first) and close #241.
• @opentui/* runtime major drift — pinned at 0.2.7 while latest is 0.5.7 (5-minor gap, pre-1.0 breaking). Open PRs #135 (0.4.3) and #335 (0.4.5) both target intermediate 0.4.x and are stale. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.7 Copilot task above.
• @changesets/cli 3.x major available (current pin 2.31.1) — out of the autoheal scoped list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@v1.9.0).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32749396676 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 1 failing CI — #377 Lint, typecheck, build, unit tests FAILURE (run 32708286790). Root cause: @types/bun@1.4.0 narrows NodeJS.Process.off/removeListener to "memoryPressure" only → src/lib/rpc-cleanup.ts:38-39 TS2345 ('"beforeExit"'/'"SIGTERM"' not assignable to '"memoryPressure"'). Fix staged in working tree on main: ProcessEventEmitter cast interface restores the standard string | symbol event signature for process.once/process.off. Verified green against both @types/bun@1.3.14 (current main) and @types/bun@1.4.0 (PR #377). Working-dir mode forbids PR-branch push; fix lands on main, unblocking #377 on next Renovate rebase. Other 5 open PRs (#135/#241/#278/#332/#335): real CI SUCCESS.
• SECURITY: 0 open Dependabot alerts; 0 security-update PRs; Code Scanning 404. No action.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.22; @opencode-ai/sdk not a peer / not imported; all 16 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1, no unreleased entries; #135/#335 carry changesets); devDeps current except @types/node 24→26 LTS-even (PRs #278 mergeable + stale dupe #241) and @biomejs/biome 2.5.9→2.5.10 patch (Renovate); @types/bun 1.3.14→1.4.0 minor now unblocked by this run's rpc-cleanup.ts fix (carried by #377); runtime @opentui/* 0.2.7 vs latest 0.5.7 (stale PRs #135/#335 target 0.4.x).
• DEVELOPER EXPERIENCE: on main at c6c055d (new since last run via #376) — bun install/typecheck/build/test:unit (322 pass) all clean; lint 1 info (biome schema 2.5.5 vs CLI 2.5.9) → fixed in working tree (biome.json $schema → 2.5.9); re-verified lint → 0 infos. Both working-tree changes (biome.json + rpc-cleanup.ts) re-validated together: typecheck/lint/build/322 tests green.
• Actions taken: 2 working-tree file changes left for the caller workflow to commit/push to main — biome.json (schema bump 2.5.5 → 2.5.9) and src/lib/rpc-cleanup.ts (ProcessEventEmitter cast for @types/bun@1.4.0 compat, unblocks PR #377). Perpetual issue #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-23

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). Polled statusCheckRollup on each — every Lint, typecheck, build, unit tests CI run is SUCCESS (Fro Bot SKIPPED). #278 (Renovate @types/node → 26.2.0) re-ran today 2026-08-23: CI SUCCESS, MERGEABLE, but mergeStateStatus: UNSTABLE from the Renovate-internal renovate/artifacts FAILURE status (lockfile-artifact indicator, not a CI check). No failing CI → no PR-branch fixes required. Working-dir delivery mode forbids branch checkout/commit/push, so no PR-branch edits pushed.
SECURITY	✅	GET /repos/…/dependabot/alerts?state=open → [] (0 open). Code Scanning API 404 (not configured). No security-update PRs open. No unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest published 1.18.21 (devDep 1.18.19 — 2 patches behind, non-major, left to Renovate). @opencode-ai/sdk (latest 1.18.21) intentionally NOT a peer (dropped in a prior release; not imported in src/). All 16 uses: across .github/workflows/ SHA-pinned at 40-char commits (re-verified ci/fro-bot/copilot-setup-steps/release/renovate/update-repo-settings). Clean changeset hygiene: pkg 0.12.1 == latest tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries). Major devDep landscape: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → latest 2.5.10 (patch, non-major — Renovate); @types/bun 1.3.14 → latest 1.4.0 (MINOR, non-major — Renovate); rimraf 6.1.3 = latest; @types/node 24.13.3 → latest 26.2.0 (even LTS major — already tracked by #278 Renovate MERGEABLE+green CI and #241 fro-bot stale/UNKNOWN). No new major-bump PR needed from autoheal. ⚠ = stale duplicate PRs needing human pick (#241↔#278, #135↔#335) and runtime @opentui/* 0.2.7 vs latest 0.5.7 (PRs #135/#335 target intermediate 0.4.x).
DEVELOPER EXPERIENCE	✅	On main (HEAD 3cd1b14, new since last run via #375 "update all non-major dependencies to v1.18.19"): bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0; bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.9) — fixed in working tree by bumping $schema to 2.5.9 (matches installed CLI); re-ran bun run lint → 0 infos. This same class of fix has been re-applied by multiple prior runs (2026-08-13→2026-08-22) without landing on main — see Items Needing Human Attention.

Tasks for Fro Bot

• Land the biome.json $schema 2.5.5 → 2.5.9 fix on main (carried in this run's working-tree diff). Multiple prior runs' identical schema bumps did not persist on main (schema reverts to 2.5.5). Confirm the caller workflow commits the working-tree diff this time, then close #332 as superseded (it targets the now-stale 2.5.8).
• Resolve duplicate @types/node major PR pair: merge #278 (Renovate, 26.2.0, MERGEABLE, CI green; carries cosmetic renovate/artifacts FAILURE — tick rebase/retry to clear before merging) and close #241 (fro-bot, stale UNKNOWN, last CI 2026-08-11). Left to human — autohealing won't choose between duplicate major bumps.
• Resolve duplicate @opentui runtime upgrade pair: #335 (0.4.5, has changeset + overrides.@opentui/core dedupe) vs #135 (0.4.3, older). Both target 0.4.x while latest is 0.5.7. Recommend closing both in favor of a coordinated 0.2.7 → 0.5.7 major upgrade (delegated to Copilot). Left to human.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.7 (pre-1.0, treat as breaking). Verify bun run build, bun run typecheck, bun run test:unit, and bun run test:tui (TUI tests under src/tui/__tests__) all pass under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry forward the overrides.@opentui/core pin to dedupe branded renderable types; evaluate relaxing to a caret range once both deps align on the same minor. Supersedes #135 and #335 (coordinate with maintainer on closing them).
• Optional housekeeping: bump @biomejs/biome 2.5.9 → 2.5.10 (patch, non-major) — keeps the linter current; devDependency, no changeset. After bumping, run biome migrate --write to sync the $schema URL (2.5.9 → 2.5.10).

Items Needing Human Attention

• biome.json schema fix not persisting: the 2026-08-13 through 2026-08-22 runs each bumped $schema in the working tree, but main still shows 2.5.5 (verified again this run at HEAD 3cd1b14). Re-applied this run (2.5.5 → 2.5.9 to match installed @biomejs/biome@2.5.9). Verify the caller workflow commits the working-tree diff so the lint info stays cleared; then close #332 (it targets stale 2.5.8).
• @types/node duplicate PR pair — #278 (Renovate, 26.2.0, MERGEABLE, CI green) vs #241 (fro-bot, stale, UNKNOWN). Merge #278 (tick its rebase/retry checkbox to clear the renovate/artifacts FAILURE first) and close #241.
• @opentui/* runtime major drift — pinned at 0.2.7 while latest is 0.5.7 (5-minor gap, pre-1.0 breaking). Open PRs #135 (0.4.3) and #335 (0.4.5) both target intermediate 0.4.x and are stale. Recommend closing both in favor of the coordinated 0.2.7 → 0.5.7 Copilot task above.
• @changesets/cli 3.x major available (current pin 2.31.1) — out of the autoheal scoped list; flagged for human triage (release toolchain compatibility vs release.yaml changesets/action@v1.9.0).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32650599275 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing CI (5 open #135/#241/#278/#332/#335; every Lint, typecheck, build, unit tests CI SUCCESS; #278 renovate/artifacts FAILURE is Renovate-internal, not CI). No PR-branch fixes pushed (working-dir delivery mode).
• SECURITY: 0 open Dependabot alerts ([]); 0 security-update PRs; Code Scanning 404. No action.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.21; @opencode-ai/sdk not a peer / not imported; all 16 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); devDeps current except @types/node 24→26 LTS-even (PRs #278 mergeable + stale dupe #241) and @biomejs/biome 2.5.9→2.5.10 patch (Renovate); runtime @opentui/* 0.2.7 vs latest 0.5.7 (stale PRs #135/#335 target 0.4.x).
• DEVELOPER EXPERIENCE: on main at 3cd1b14 (new since last run via #375) — bun install/typecheck/build/test:unit (322 pass) all clean; lint 1 info (biome schema 2.5.5 vs CLI 2.5.9) → fixed in working tree (biome.json $schema → 2.5.9); re-verified lint → 0 infos.
• Actions taken: 1 working-tree file change (biome.json schema bump 2.5.5 → 2.5.9) left for the caller workflow to commit/push; perpetual issue #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-22

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). The real CI check Lint, typecheck, build, unit tests is SUCCESS on all 5. The only non-green status is #278's Renovate-internal renovate/artifacts FAILURE (Renovate's install-tool bun failed in its own env → bun.lock not regenerated; not a CI check). Working-dir delivery mode forbids PR-branch checkout/commit/push, so no PR-branch fixes were pushed — and none were required since real CI is green everywhere.
SECURITY	✅	dependabot/alerts → 0 open. No vulnerable-dep PRs, no unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest published 1.18.21 (devDep pinned 1.18.18, 3 patches behind — non-major, left to Renovate). @opencode-ai/sdk intentionally not a peer: never imported in src/ (only @opencode-ai/plugin). All 16 uses: across .github/workflows/ SHA-pinned (re-verified ci/fro-bot/copilot-setup-steps/release/renovate/update-repo-settings). Clean changeset hygiene: .changeset/ on main holds only README.md + config.json; pkg 0.12.1, no unreleased entries. devDep majors: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 → latest 2.5.10 (patch, non-major); @types/bun 1.3.14 → latest 1.4.0 (minor, non-major); rimraf 6.1.3 = latest; @types/node 24.13.3 → latest 26.2.0 (even LTS major — already tracked by #278 MERGEABLE+green-CI and #241 stale). No new major-bump PR needed.
DEVELOPER EXPERIENCE	✅	Applied one safe fix to the working tree: biome.json $schema 2.5.5 → 2.5.9 (matches installed CLI 2.5.9, clears the lone lint info). Re-verified on main after edit: bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck clean; bun run build clean; bun run lint clean (0 info, was 1); bun run test:unit → 322 pass / 0 fail. Diff = biome.json 1 line. Per working-dir delivery mode the caller workflow owns commit/push; no git/PR actions taken here.

Tasks for Fro Bot

• Close PR #332 (chore/dev): bump biome config schema to 2.5.8) — superseded; main now carries $schema 2.5.9. Rebasing #332 would downgrade the schema, so close rather than merge.
• Resolve the duplicate @types/node 24→26 pair: merge #241 (fro-bot, clean lockfile, CI-green at 26.x latest) and let Renovate auto-close #278 (MERGEABLE but UNSTABLE via renovate/artifacts FAILURE). Do not merge #278 as-is.
• Resolve the duplicate @opentui pair: #135 (Renovate, @opentui/solid → 0.4.3) and #335 (fro-bot, @opentui/core+@opentui/solid → 0.4.5) are both stale vs latest 0.5.6. Recommend rebasing #335 to 0.5.6 (core+solid together) and closing #135.

Tasks for Copilot

• (none this run — no errored CI, no security advisories, no type/build breaks.)

Items Needing Human Attention

• Stale/duplicate dependency PRs (#241 ↔ #278, #135 ↔ #335) and superseded #332 need a maintainer pick. There are no CI errors anywhere — every real check is green. The only repo-level change this run is the biome.json $schema bump staged in the working tree for the caller workflow to commit to main.

---

Update — 2026-08-21

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). gh pr checks on each: every Lint, typecheck, build, unit tests CI run is SUCCESS. Sole non-green is #278's Renovate-internal renovate/artifacts FAILURE (lockfile-artifact status, not a real CI check; self-heals on rebase/next Renovate run). Working-dir delivery mode forbids branch checkout/commit/push, so no PR-branch fixes pushed — none were required since real CI is green on all PRs.
SECURITY	✅	dependabot/alerts → 0 open. No vulnerable-dep PRs, no unaddressed critical/high advisories. No action.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.21 (devDep 1.18.18 — patch behind, non-major, left to Renovate). @opencode-ai/sdk (latest 1.18.21) intentionally NOT a peer (dropped in a prior release, CHANGELOG-documented; never imported in src/). All uses: across .github/workflows/ SHA-pinned (re-verified ci/fro-bot/copilot-setup-steps/release/renovate/update-repo-settings). Clean changeset hygiene: .changeset/ on main holds only README.md + config.json; pkg 0.12.1, no unreleased entries. Major devDep landscape: typescript 7.0.2 = latest; @biomejs/biome 2.5.9 = latest; @types/bun 1.3.14 → latest 1.4.0 (MINOR, non-major — left to Renovate); rimraf 6.1.3 = latest; @types/node 24.13.3 → latest 26.2.0 (even LTS — already tracked by #278 Renovate MERGEABLE+green CI and #241 fro-bot stale/UNKNOWN). No new major-bump PR needed. ⚠ = stale duplicate PRs needing human pick (#241↔#278, #135↔#335).
DEVELOPER EXPERIENCE	✅	On main (HEAD 542feab): bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck clean; bun run build clean; bun run test:unit → 322 pass / 0 fail. bun run lint surfaced 1 info: biome.json $schema pinned to 2.5.5 while CLI is 2.5.9 (prior 08-19 working-tree fix to 2.5.8 never landed on main). Fixed in working tree by bumping biome.json $schema 2.5.5 → 2.5.9 (config-only; supersedes stale #332 which only bumps to 2.5.8). Post-fix bun run lint fully clean (0 info). Working-tree diff: biome.json only (1 line). Caller workflow owns commit/PR.

Tasks for Fro Bot

• Merge Renovate PR #278 (@types/node 24→26, even/LTS, MERGEABLE, all real CI green) and close stale duplicate #241. The lone failing renovate/artifacts check is a Renovate self-check that self-heals on rebase/next run.
• Close stale Renovate PR #332 (biome.json schema→2.5.8) — superseded by today's working-tree fix bumping the schema directly to 2.5.9 on main.
• Investigate why the 08-19 working-tree fix (biome.json 2.5.5→2.5.8) never committed to main — the caller workflow may not be committing autoheal working-tree changes. Confirm the delivery pipeline is picking up today's biome.json change.

Tasks for Copilot

• Rebase or close-and-redo the @opentui/* runtime-dep PRs: close #135 (→0.4.3, superseded); rebase #335 (→0.4.5) and reconsider against now-latest @opentui/core/@opentui/solid 0.5.6 (0.x minor = effectively major for pre-1.0 deps). Verify bun run test:tui and bun run build still pass under the bumped version. Single PR.
• Docs cleanup (non-blocking): AGENTS.md, .github/copilot-instructions.md, and the fro-bot.yaml review prompt still reference @opencode-ai/sdk as a peer dependency, but it was intentionally dropped from peerDependencies (CHANGELOG-documented). Remove the stale references. Single PR.

Items Needing Human Attention

• @types/node major bump (24→26) is blocked only on a manual merge decision (automerge disabled). PR #278 is ready; #241 is a stale duplicate.
• @opentui/core/@opentui/solid runtime deps are two minors behind (0.2.7 → latest 0.5.6). 0.x runtime dep change with potential TUI impact — needs a decision on chasing latest vs. pinning to a tested range.
• The autoheal delivery pipeline may not be committing working-tree fixes to main (the 08-19 biome.json fix did not land). If today's biome.json change also fails to commit, the working-dir delivery contract needs operator review.

---

Update — 2026-08-20

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). Polled statusCheckRollup on each: every Lint, typecheck, build, unit tests CI run is SUCCESS (Fro Bot SKIPPED). No failing CI checks to fix. #278 (Renovate @types/node v26) retains mergeStateStatus: UNSTABLE from the Renovate-internal renovate/artifacts FAILURE (lockfile-artifact status, not a CI check; self-heals on next Renovate run). Working-dir delivery mode forbids branch checkout/commit/push this run, so no PR code fixes pushed — and none were required.
SECURITY	✅	dependabot/alerts → [] (0 open). security-advisories → 0. Code Scanning endpoint 404 (not configured for the bot token). No vulnerable-dep PRs. No new advisories. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest published 1.18.19 (devDep pinned 1.18.18 — patch behind, non-major, left to Renovate). @opencode-ai/sdk (latest 1.18.19) is not a peer dep and not imported in src/ (grep-verified). All uses: entries across .github/workflows/ SHA-pinned (re-verified ci/fro-bot/release/renovate/copilot-setup-steps/update-repo-settings; no @v/@main/@latest). Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ on main holds only README.md + config.json; user-visible PRs #135 and #335 each carry a .changeset/*.md. Major devDep landscape: typescript 7.0.2 = latest; @biomejs/biome 2.5.8 → latest 2.5.9 (patch, non-major — left to Renovate); @types/bun 1.3.14 = latest; rimraf 6.1.3 = latest; @types/node 24.13.3 → latest 26.2.0 (even LTS — tracked by #278 Renovate MERGEABLE and #241 fro-bot BEHIND/MERGEABLE). No new major-bump PR needed.
DEVELOPER EXPERIENCE	✅	On main (HEAD ff7b6f5): bun install --frozen-lockfile clean (280 installs / 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0; bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.8) — fixed in working tree by bumping $schema to 2.5.8; re-ran bun run lint → 0 infos. The 2026-08-19 run applied this same fix but it did not land on main (schema was 2.5.5 again at HEAD), so re-applied this run.

Tasks for Fro Bot

• Land the biome.json $schema 2.5.5 → 2.5.8 fix on main (carried in this run's working-tree diff; also in PR #332). The 2026-08-19 run's identical fix did not persist — confirm the caller workflow commits the working-tree diff this time, then close #332 as superseded.
• Resolve duplicate @types/node major PR pair: merge #278 (Renovate, 26.x, current 26.2.0, MERGEABLE) and close #241 (fro-bot, BEHIND/MERGEABLE). Left to human — autohealing won't choose between duplicate major bumps. Both use exact pins; the autoheal caret-range guidance was not retrofitted to existing PRs.
• Resolve duplicate @opentui runtime upgrade pair: merge #335 (0.4.5, has changeset + overrides.@opentui/core dedupe, BEHIND/MERGEABLE) and close #135 (0.4.3, BEHIND/MERGEABLE). Left to human.

Tasks for Copilot

• Once #335 (or #135) lands, evaluate relaxing overrides.@opentui/core to a caret range now that both runtime deps align on the same minor — avoids brittleness on the next @opentui/solid bump.
• Optional: bump @biomejs/biome 2.5.8 → 2.5.9 (patch, non-major) and re-run biome migrate --write to sync $schema (2.5.8 → 2.5.9). DevDep, no changeset.

Items Needing Human Attention

• biome.json schema fix not persisting: the 2026-08-19 run's $schema 2.5.5→2.5.8 fix did not land on main (working tree showed 2.5.5 again). Re-applied this run. Verify the caller workflow commits the working-tree diff so the lint info stays cleared; then close #332.
• @types/node duplicate PR pair — #278 (Renovate, 26.x) vs #241 (fro-bot, 26.0.0); both CI-green + MERGEABLE. Merge #278 and close #241.
• @opentui/solid duplicate PR pair — #335 (0.4.5) vs #135 (0.4.3); both BEHIND + MERGEABLE. #335 includes overrides.@opentui/core dedupe + changeset. Prefer #335 (newer); close #135.
• #332 (biome schema 2.5.5 → 2.5.8) — superseded by this run's working-tree fix; close once main carries the schema bump.

---

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32392771025 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing CI (5 open #135/#241/#278/#332/#335, all CI-green + MERGEABLE). #278 carries Renovate-internal renovate/artifacts FAILURE status (not a CI check).
• SECURITY: 0 open Dependabot alerts ([]); 0 security-advisories; Code Scanning API 404 to bot token. No security PRs.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.19; @opencode-ai/sdk not a peer / not imported (grep-verified); all workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); devDeps current except @types/node 24→26 LTS-even (PRs #241/#278 mergeable) and @biomejs/biome 2.5.8→2.5.9 patch (non-major, left to Renovate).
• DEVELOPER EXPERIENCE: bun install --frozen-lockfile / typecheck / build all clean; lint had 1 info (biome schema 2.5.5 vs 2.5.8) → fixed in working tree (biome.json $schema → 2.5.8); re-verified lint → 0 infos. The 2026-08-19 run's identical fix did not persist on main; re-applied.
• Actions taken: 1 working-tree file change (biome.json schema bump 2.5.5 → 2.5.8) left for the caller workflow to commit/push; perpetual issue #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).
• Note: trimmed the oldest update section (2026-08-08) from the issue body to stay under GitHub's 65,536-char limit. Full history remains in prior session transcripts.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-19

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). Polled statusCheckRollup on each: every Lint, typecheck, build, unit tests CI run is SUCCESS (Fro Bot SKIPPED). No failing CI checks to fix. #278 (chore(dev): update dependency @types/node to v26, Renovate) retains mergeStateStatus: UNSTABLE from the Renovate-internal renovate/artifacts FAILURE status (lockfile-artifact status, not a CI check; self-heals on next Renovate run). No PR code fixes required.
SECURITY	✅	dependabot/alerts returns [] (0 open alerts). security-advisories returns 0. vulnerability-alerts endpoint 404 (Code Scanning / vuln alerts disabled for the bot token). No vulnerable-dep PRs. No new advisories. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 still valid vs latest published 1.18.18 (devDep pinned 1.18.18). @opencode-ai/sdk (1.18.18) is not a peer dep / not imported. All 16 uses: entries across .github/workflows/ are SHA-pinned (re-verified in ci.yaml, copilot-setup-steps.yaml, fro-bot.yaml, release.yaml, renovate.yaml, update-repo-settings.yaml; no @v/@main/@latest refs). Clean changeset hygiene: pkg 0.12.1 == tag v0.12.1; .changeset/ on main holds only README.md + config.json. Major devDep landscape: typescript 7.0.2 = latest; @biomejs/biome 2.5.8 → latest 2.5.9 (patch, non-major — left to Renovate); @types/bun 1.3.14 = latest; rimraf 6.1.3 = latest; @changesets/cli 2.31.1 = latest; @types/node 24.13.3 → latest 26.2.0 (even LTS — tracked by #241 26.0.0 MERGEABLE and #278 26.x MERGEABLE). No new major-bump PR needed.
DEVELOPER EXPERIENCE	✅	On main: bun install clean (280 installs / 311 packages, no peer warnings), bun run typecheck ✅ clean, bun run build ✅ exits 0 (dist populated). bun run lint had 1 info (biome.json $schema 2.5.5 vs installed @biomejs/biome@2.5.8) — fixed in working tree by bumping $schema to 2.5.8 (matches installed CLI); re-ran bun run lint → 0 infos. This same fix is also carried by open PR #332 (BEHIND); landing it on main de-duplicates #332.

Tasks for Fro Bot

• Resolve the duplicate @types/node major PR pair: #278 (Renovate, 26.x, MERGEABLE) vs #241 (fro-bot, 26.0.0, MERGEABLE). Recommend merging #278 (Renovate-managed, current latest 26.2.0) and closing #241 to de-duplicate. Left to human — autohealing won't choose between duplicate major bumps.
• Resolve the duplicate @opentui/solid runtime upgrade pair: #335 (bump @opentui/core + @opentui/solid to 0.4.5, BEHIND, MERGEABLE) vs #135 (@opentui/solid → 0.4.3 + @opentui/core override, BEHIND, MERGEABLE). Recommend merging #335 (newer 0.4.5) and closing #135 — but first verify #335 carries the same overrides.@opentui/core dedupe fix from #135 (b40d1e1) so the nested-install typecheck break doesn't regress. Left to human.
• After the biome.json schema fix lands on main (via this run's working-tree diff), close #332 as superseded.

Tasks for Copilot

• Once #335 (or #135) lands, evaluate whether the overrides.@opentui/core pin can be relaxed to a caret range now that both runtime deps live at the same version — avoids brittleness on the next @opentui/solid bump.
• Optional housekeeping: bump @biomejs/biome 2.5.8 → 2.5.9 (patch, non-major) — keeps the linter current; devDependency, no changeset. After bumping, re-run biome migrate --write to sync the $schema URL.

Items Needing Human Attention

• @types/node duplicate PR pair — #278 (Renovate, 26.x) vs #241 (fro-bot, 26.0.0); both MERGEABLE and CI-green. Merge #278 and close #241.
• @opentui/solid duplicate PR pair — #335 (0.4.5) vs #135 (0.4.3); both BEHIND + MERGEABLE. Verify #335 includes the overrides.@opentui/core dedupe (without it, bun run typecheck breaks with duplicate branded renderable types — see 2026-07-13 fix b40d1e1). Prefer #335 (newer) once verified; close #135.
• #332 (biome schema 2.5.5 → 2.5.8) — superseded by this run's working-tree fix to main; can be closed once main carries the schema bump.

---

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32276321561 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing (5 open #135/#241/#278/#332/#335, all CI-green + MERGEABLE). #278 carries Renovate-internal renovate/artifacts FAILURE status (not a CI check).
• SECURITY: 0 open Dependabot alerts ([]); 0 security-advisories; vuln-alerts API 404 to bot token. No security PRs.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.18; @opencode-ai/sdk not a peer / not imported; all 16 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); devDeps current except @types/node 24→26 LTS-even (PRs #241/#278 mergeable) and @biomejs/biome 2.5.8→2.5.9 patch (non-major, left to Renovate).
• DEVELOPER EXPERIENCE: bun install / typecheck / build all clean; lint had 1 info (biome schema 2.5.5 vs 2.5.8) → fixed in working tree (biome.json $schema → 2.5.8); re-verified lint → 0 infos.
• Actions taken: 1 working-tree file change (biome.json schema bump 2.5.5 → 2.5.8) left for the caller workflow to commit/push; perpetual issue #26 updated with today's section. No branches/commits/PRs created directly (working-dir delivery mode).
• Note: issue body was over the 65,536-char GitHub limit (257,612 chars); trimmed oldest update sections (pre-2026-08-08) to fit. Full history remains in prior session transcripts.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-18

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). Polled statusCheckRollup on each — every Lint, typecheck, build, unit tests CI run is SUCCESS (Fro Bot SKIPPED). No failing CI checks. PR #278 carries the Renovate-internal renovate/artifacts FAILURE status (artifact-sync indicator, not a CI test failure; duplicate of fro-bot #241). No type/lint/build fixes required; no code commits pushed. Note: PRs #276 (actions/cache v6) and #277 (actions/checkout v7) are no longer open — merged since the 2026-08-17 run; ci.yaml now pins actions/checkout@…# v7.0.1 and actions/cache@…# v6.1.0.
SECURITY	✅	GET /repos/…/dependabot/alerts?state=open → [] (0 open advisories). Code Scanning endpoint returns 404 (not configured). No security-update PRs open. No critical/high advisories unaddressed. No new security PR opened.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest published 1.18.18 (devDep pinned 1.18.18 — fully current). @opencode-ai/sdk (latest 1.18.18) is not a peer dep and not imported in src/ — nothing to verify. All 6 uses: entries across .github/workflows/ SHA-pinned at 40-char commits with version comments (ci, release, fro-bot, copilot-setup-steps, renovate, update-repo-settings). No changeset drift: package.json 0.12.1 == latest tag v0.12.1; .changeset/ holds only README.md + config.json. Major devDep bumps from the explicit autoheal list: typescript 7.0.2 (current), @biomejs/biome 2.5.8 (latest 2.5.9 — patch, non-major, Renovate-managed), @types/bun 1.3.14 (current), rimraf 6.1.3 (current); only @types/node 24.13.3 → 26.2.0 (even/LTS major) is outstanding — tracked by PR #278 (Renovate, 26.2.0, UNSTABLE due to renovate/artifacts FAILURE) and stale duplicate #241 (fro-bot, 26.2.0, BEHIND). No new PR opened (existing PRs cover it; working-dir delivery mode forbids branch/PR creation this run). Runtime deps @opentui/core/@opentui/solid pinned at 0.2.7 while latest is 0.5.4 — flagged below; intermediate PRs #135 (0.4.3) and #335 (0.4.5) also fall short of latest. @changesets/cli 2.31.1 → 3.0.0 major available (not in explicit list, previously flagged).
DEVELOPER EXPERIENCE	⚠️ → ✅ (pending #332 merge)	On main (at ae35d47): bun install --frozen-lockfile clean (280 installs across 311 packages, no peer warnings); bun run typecheck ✅ clean; bun run build ✅ exit 0 (dist/ populated: index.js, index.d.ts, tui/, runtime/, tools/, discovery/, lib/); bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. bun run lint reports 1 info — biome.json $schema is 2.5.5 while installed CLI is 2.5.8 — the exact mismatch PR #332 (chore/dev-biome-schema-2.5.6, body: schema 2.5.5 → 2.5.8) fixes; awaiting merge. No logic-level lint failures, no new type errors, no build breaks since last run.

Tasks for Fro Bot

• Merge PR #332 (chore/dev-biome-schema-2.5.6 → biome.json $schema 2.5.5 → 2.5.8) — single-line config bump, CI green; resolves the bun run lint schema-mismatch info on main. Branch is BEHIND; rebase onto main at ae35d47 before merging (or merge via merge queue).
• Pick one @types/node 24→26 PR and close the other: PR #278 (Renovate, 26.2.0, current @opencode-ai/plugin pin 1.18.18) is the merge candidate; PR #241 (fro-bot, 26.2.0, stale 1.18.15 plugin pin) is the duplicate. PR #278 carries a renovate/artifacts FAILURE status — tick its rebase/retry checkbox to clear before merging. (Closing a PR is destructive — flagged for human confirmation.)
• Triage stale runtime-dep PRs #135 (@opentui/solid → 0.4.3) and #335 (fro-bot, 0.4.5): both target pre-0.5.x lines while latest published is 0.5.4. Recommend closing both and opening a single coordinated 0.2.7 → 0.5.4 major upgrade with a changeset (delegated to Copilot below). Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Coordinated @opentui/core + @opentui/solid runtime major upgrade 0.2.7 → 0.5.4 (pre-1.0, treat as breaking). Verify TUI rendering and bun run test:tui under the new versions; open a single PR with a minor changeset (per AGENTS.md, 0.x series → minor for breaking runtime changes). Carry the overrides.@opentui/core pin forward and evaluate relaxing to a caret range once both deps align on the same minor. Coordinate with maintainer on PRs #135/#335 status before opening. This supersedes the intermediate PRs.
• Investigate @changesets/cli 2.31.1 → 3.0.0 major bump (devDep). Not in the autoheal explicit list, but a major bump on the release toolchain. Confirm breaking changes against version-changesets / publish-changesets scripts and the changesets/action@v1.9.0 workflow; open a PR if safe.

Items Needing Human Attention

• Biome schema lint info on main: bun run lint reports 2.5.5 schema vs 2.5.8 CLI. Fixed by PR #332 (CI green); merge to clear.
• Duplicate @types/node 24→26 PRs: #278 (Renovate, current plugin pin) vs #241 (fro-bot, stale plugin pin). Recommend merging #278 and closing #241.
• @opentui/* major drift: pinned at 0.2.7 while latest is 0.5.4 — three-major-version gap on runtime dependencies. Not addressed by routine autohealing (pre-1.0 breaking bumps need TUI verification). Intermediate PRs #135 (0.4.3) and #335 (0.4.5) are open but also stale relative to 0.5.4.
• @changesets/cli 3.0.0 is available (current pin 2.31.1). Major bump on the release toolchain; needs compatibility review against release.yaml changesets/action@v1.9.0.

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32160699642 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing (5 open #135/#241/#278/#332/#335; every Lint, typecheck, build, unit tests CI SUCCESS; #278 renovate/artifacts FAILURE is Renovate-internal, not CI). No code fixes required. PRs #276/#277 merged since last run.
• SECURITY: 0 Dependabot alerts (/dependabot/alerts?state=open → []); 0 security-update PRs; Code Scanning 404 (disabled).
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.18 (devDep current); @opencode-ai/sdk not a peer dep / not imported; all 6 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); major devDep bumps from explicit list all current except @types/node 24→26 (PRs #278 + stale dupe #241); @biomejs/biome 2.5.8→2.5.9 patch available (Renovate-managed); runtime @opentui/* 0.2.7 vs latest 0.5.4 (PRs #135/#335 target intermediate 0.4.x); @changesets/cli 2.31.1→3.0.0 major available (not in explicit list, flagged).
• DEVELOPER EXPERIENCE: on main at ae35d47 — bun install/typecheck/build/test:unit (322 pass / 0 fail / 1279 expect() calls) all clean; lint 1 info (biome schema 2.5.5 vs CLI 2.5.8, fixed by PR #332, awaiting merge).
• Actions taken: none required — repo healthy. working-dir delivery mode forbids branch/commit/push/PR creation this run; all pending fixes already covered by open CI-green PRs awaiting human merge. Updated perpetual issue #26 only.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-17

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335) — unchanged from 2026-08-16. Polled statusCheckRollup for each: every Lint, typecheck, build, unit tests CI run is SUCCESS; copilot-setup-steps SUCCESS where present; Renovate SUCCESS; Fro Bot SKIPPED. Only non-green status is renovate/artifacts FAILURE on #278 (Renovate-internal artifact status, not a CI check; CI itself SUCCESS, bun.lock in sync). No failing CI → no PR code fixes required or possible.
SECURITY	✅	gh api repos/.../dependabot/alerts (open) returns 0 alerts. No critical/high advisories. No open security-update PRs. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 accurate (latest published 1.18.18; devDep pinned 1.18.18). @opencode-ai/sdk not declared in package.json — nothing to verify. All 10 uses: entries across 6 .github/workflows/*.yaml SHA-pinned to 40-char commits (no unpinned actions). Changeset hygiene clean: package.json (0.12.1) == latest tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries, no drift). Scoped devDep majors: typescript 7.0.2 (latest), @biomejs/biome 2.5.8 (latest), @types/bun 1.3.14 (latest), rimraf 6.1.3 (latest); only @types/node 24.13.3 → 26.2.0 (even/LTS) outstanding, covered by #241 (fro-bot, 26.2.0, MERGEABLE, CI green, "Closes #278") + #278 (Renovate, 26.2.0, MERGEABLE, renovate/artifacts FAILURE). Runtime deps @opentui/core/@opentui/solid pinned 0.2.7; latest 0.5.3; PRs #335 (0.4.5, fro-bot, has changeset, MERGEABLE, CI green) + #135 (0.4.3, Renovate, has changeset, MERGEABLE, CI green). No new PR needed. Observed (out of scope): @changesets/cli 2.31.1 → 3.0.0 major available but not in the task's scoped devDep list.
DEVELOPER EXPERIENCE	✅	On main: bun install clean (280 installs / 311 packages, no peer warnings), bun run typecheck ✅ clean, bun run build ✅ exit 0, bun run test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. bun run lint had 1 info (biome.json $schema 2.5.5 vs CLI 2.5.8) — fixed in working tree this run: bumped schema to 2.5.8 (1-line change, matches open PR #332); bun run lint now ✅ clean (0 infos). Staged for the caller workflow to commit to main.

Tasks for Fro Bot

• Resolve the duplicate @types/node major PR pair: merge #241 (fro-bot, 26.2.0, MERGEABLE, CI green, "Closes #278") and close #278 (Renovate, renovate/artifacts FAILURE). Left to human — autohealing won't close PRs.
• Resolve the duplicate @opentui runtime-dep PR pair: merge #335 (0.4.5, newer, has changeset, MERGEABLE, CI green) and close #135 (0.4.3, older, superseded). Left to human.
• After the biome.json schema bump lands on main (this run's working-tree fix), close #332 as superseded.

Tasks for Copilot

• Once #335 lands, evaluate whether the overrides.@opentui/core 0.4.5 pin can be relaxed to a caret range now that both runtime deps live at the same version — avoids brittleness on the next @opentui/solid bump.
• Evaluate the @opentui/core/@opentui/solid 0.4.5 → 0.5.3 follow-up upgrade (runtime deps; pre-1.0, treat as breaking) once #335 settles — open a single PR with a changeset.

Items Needing Human Attention

• @types/node duplicate PR pair — #241 (fro-bot, 26.2.0, MERGEABLE, CI green) vs #278 (Renovate, 26.2.0, renovate/artifacts FAILURE). Merge #241 and close #278.
• @opentui duplicate PR pair — #335 (0.4.5, MERGEABLE, CI green, has changeset) vs #135 (0.4.3, MERGEABLE, CI green, has changeset). Merge #335 (newer) and close #135 (superseded).
• biome.json schema — this run applied the 2.5.5 → 2.5.8 fix to the working tree (caller will commit to main); #332 can be closed once it lands.

---

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 32045630625 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing among 5 open PRs (#135/#241/#278/#332/#335); all Lint, typecheck, build, unit tests CI SUCCESS/SKIPPED. #278 renovate/artifacts internal FAILURE (not a CI check). No PR code fixes pushed.
• SECURITY: 0 open Dependabot alerts; 0 security-update PRs.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.18; all 10 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); scoped devDeps current except @types/node 24→26 (covered by #241/#278). @changesets/cli 3.0.0 major observed but out of scoped list.
• DEVELOPER EXPERIENCE: bun install/typecheck/build/test:unit (322 pass) all clean; lint had 1 info (biome schema 2.5.5 vs 2.5.8) → fixed in working tree (schema bumped to 2.5.8); lint now clean.
• Actions taken: 1 working-tree file change (biome.json schema 2.5.5 → 2.5.8) staged for caller to commit to main; no branches/commits/PRs created by this action (working-dir delivery mode); perpetual issue #26 updated with today's section.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-16

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335) — same set as yesterday. Polled statusCheckRollup for each: every Lint, typecheck, build, unit tests CI run is SUCCESS; copilot-setup-steps SUCCESS where present; Renovate SUCCESS; Fro Bot SKIPPED. The only non-green status is renovate/artifacts FAILURE on PR #278 — a Renovate-internal artifact-update status (empty target URL, platform-managed), not a CI build failure (CI is SUCCESS, bun.lock in sync). No PR has a failing CI check, so no code fixes were required or possible this run.
SECURITY	✅	gh api repos/.../dependabot/alerts (open) returns 0 alerts. gh api .../security-advisories returns []. No critical/high advisories. No open security-update PRs. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 still accurate (latest published 1.18.18; devDep pinned 1.18.18). @opencode-ai/sdk is not a declared peer/dev/dependency in package.json — nothing to verify. All uses: entries across the 6 .github/workflows/*.yaml files are pinned to full 40-char commit SHAs (no unpinned actions found). Changeset hygiene clean: package.json (0.12.1) matches latest tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries; no drift). Scoped devDep major-bump check: typescript 7.0.2 (current=latest), @biomejs/biome 2.5.8 (current=latest), @types/bun 1.3.14 (current=latest), rimraf 6.1.3 (current=latest); only @types/node 24.13.3 → 26.2.0 (even/LTS major) is outstanding and already covered by open PRs #278 (Renovate, 26.2.0, mergeable, CI green) + #241 (fro-bot, 26.0.0, BEHIND main) — no new PR needed. Runtime deps @opentui/core/@opentui/solid pinned at 0.2.7; latest published is 0.5.3; PRs #335 (0.4.5, fro-bot, has changeset) and #135 (0.4.3, Renovate, has changeset) both still lag 0.5.3. (Out-of-scope note: @changesets/cli 2.31.1 → 3.0.0 major is available but not in the autoheal scoped list.)
DEVELOPER EXPERIENCE	✅	On main: bun install --frozen-lockfile clean (280 installs / 311 packages, no peer-dep warnings); bun run typecheck ✅; bun run build ✅ (exit 0, dist/ populated); bun run lint exit 0 with 1 info — biome.json $schema is 2.5.5 while installed @biomejs/biome is 2.5.8. This info is already resolved by open PR #332 (yesterday's run rebased it onto main, retargeted the bump to 2.5.8; CI green; MERGEABLE/CLEAN; net diff is a single one-line $schema URL change). No logic-level lint failures, no new type errors, no build breaks since last run. No new code committed this run — green.

Tasks for Fro Bot

• Re-verified all open PR CI states — no errored PRs to fix this run.
• (carried over) No new fro-bot branch work required beyond the pending human-merge items below.

Tasks for Copilot

• (carried over) Open a single coordinated PR upgrading @opentui/core and @opentui/solid from 0.2.7 → 0.5.3 (major), with a .changeset/*.md entry and the overrides.@opentui/core pin retained to avoid duplicate type identities. Supersedes #135 and #335. Verify bun run typecheck, bun run build, bun run test:unit, bun run test:tui all pass before requesting review.

Items Needing Human Attention

• Merge PR #332 (biome config schema 2.5.5 → 2.5.8) — ready (MERGEABLE/CLEAN, CI green). Clears the lingering biome.json lint info on main.
• @types/node 24 → 26 (even/LTS major): merge PR #278 (Renovate, 26.2.0, CI green, mergeable, bun.lock in sync) and close duplicate PR #241 (fro-bot, 26.0.0, BEHIND main). The renovate/artifacts FAILURE on #278 is Renovate-internal; tick its rebase/retry checkbox or let Renovate's next run refresh it before merging.
• @opentui runtime upgrade decision: latest published is 0.5.3; open PRs #335 (0.4.5) and #135 (0.4.3) both lag. Either (a) merge #335 now to reach 0.4.5 and defer 0.5.x, or (b) close #135 and #335 in favor of the coordinated 0.2.7 → 0.5.3 Copilot task above. Closing is destructive — flagged for human confirmation.
• (Out of scope) @changesets/cli 2.31.1 → 3.0.0 major bump available; not in the autoheal scoped list. Flag for human triage if desired.
• Issue body trimmed to the 35 most recent daily sections to stay under GitHub's 262,144-char issue-body limit. The perpetual issue had accumulated 54 sections (257,984 chars); this run's prepend would have exceeded the limit. Older daily entries were dropped; a rolling ~35-section (~2-month) window is retained going forward. (No action needed; noted for transparency.)

---

Update — 2026-08-15

Summary

Category	Status	Actions
ERRORED PRs	✅	5 open PRs (#135, #241, #278, #332, #335). Polled gh pr checks + statusCheckRollup for each — every Lint, typecheck, build, unit tests CI run is SUCCESS; copilot-setup-steps SUCCESS; Renovate SUCCESS; Fro Bot SKIPPED. The only non-green status is renovate/artifacts FAILURE on PR #278 — a Renovate-internal artifact-update status (empty link, platform-managed), not a CI build failure (CI is SUCCESS, lockfile is in sync). PR #277 (cited yesterday) no longer appears in the open list — merged via ed69f11 chore(deps): update actions/checkout action to v7 (#277). No code fixes required-or-possible on any PR this run; the renovate/artifacts status will refresh on Renovate's next scheduled run or when its rebase/retry checkbox is ticked.
SECURITY	✅	gh api repos/.../dependabot/alerts?state=open returns 0 alerts. Code Scanning endpoint 404 (disabled for this repo). No critical/high advisories. No open security-update PRs. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 still accurate (latest published 1.18.18; devDep pinned 1.18.16). @opencode-ai/sdk is not a peer dep, not in package.json, and not imported in src//tests//scripts/ — only transitive via @opencode-ai/plugin. All uses: entries across the 6 .github/workflows/*.yaml files are pinned to full 40-char commit SHAs. No changeset drift: package.json (0.12.1) matches the latest tag v0.12.1; .changeset/ contains only README.md + config.json (no unreleased entries). Major devDep bumps from the autoheal list: typescript 7.0.2 (current=latest), @biomejs/biome 2.5.8 (current=latest, bumped on main via #359), @types/bun 1.3.14 (current=latest), rimraf 6.1.3 (current=latest); only @types/node 24.13.3 → 26.2.0 (even/LTS major) is outstanding — PR #278 (Renovate, 26.2.0, mergeable, CI green, lockfile in sync) is the merge candidate; PR #241 (fro-bot, 26.2.0, stale 1.18.15 plugin pin, BEHIND main) is the duplicate. Runtime deps @opentui/core/@opentui/solid pinned at 0.2.7 while latest published is 0.5.3; PR #335 (0.4.5, fro-bot, has changeset) and PR #135 (0.4.3, Renovate, has changeset) both target pre-0.5.x lines and lag latest.
DEVELOPER EXPERIENCE	⚠️ → ✅	On main: bun install --frozen-lockfile clean (280 installs across 311 packages, no peer-dependency warnings); bun run typecheck ✅; bun run build ✅; bun run test:unit ✅ (322 pass / 0 fail / 1279 expect() calls); bun run lint exit 0 with 1 info — biome.json $schema is 2.5.5 while installed @biomejs/biome is 2.5.8 (bumped via #359 after PR #332 was opened targeting 2.5.7). Action taken: updated PR #332 to bump $schema to 2.5.8 (see Tasks for Fro Bot). No logic-level lint failures, no new type errors, no build breaks since last run.

Tasks for Fro Bot

• Updated PR #332 to bump biome.json $schema 2.5.5 → 2.5.8 (rather than the stale 2.5.7 the branch previously targeted). Merged origin/main into chore/dev-biome-schema-2.5.6 (no conflicts; brought the branch up to date — mergeStateStatus now CLEAN rather than BEHIND), then committed chore(dev): bump biome config schema to 2.5.8 on top. Updated the PR title from ... to 2.5.7 to ... to 2.5.8 and refreshed the PR body. Verified locally on the branch: bun install --frozen-lockfile ✅, bun run lint ✅ (no infos now — schema info cleared), bun run typecheck ✅, bun run build ✅, bun run test:unit ✅ (322 pass / 0 fail). CI re-ran on the pushed branch: Lint, typecheck, build, unit tests PASS (48s), Renovate / Renovate PASS, copilot-setup-steps PASS, Fro Bot SKIPPED. PR #332 is MERGEABLE/CLEAN and ready for review/merge. Net diff against main: a single one-line $schema URL change (2.5.5 → 2.5.8).
• Merge PR #332 (biome schema 2.5.8) once approved — clears the lingering biome.json lint info on main.
• Merge PR #278 (Renovate @types/node → 26.2.0, even/LTS major) and close duplicate PR #241 (fro-bot, stale 1.18.15 plugin pin, BEHIND main). PR #278 is mergeable, CI green, lockfile in sync. The stale renovate/artifacts FAILURE is Renovate-internal (not a CI failure); tick its rebase/retry checkbox or let Renovate's next scheduled run refresh it before merging.
• Triage runtime-dep PRs #135 (@opentui/solid → 0.4.3, Renovate) and #335 (@opentui/core+@opentui/solid → 0.4.5, fro-bot): both lag latest published 0.5.3. Recommend closing both in favor of a single coordinated 0.2.7 → 0.5.3 major upgrade (delegated to Copilot below). Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Open a coordinated PR bumping runtime deps @opentui/core and @opentui/solid from 0.2.7 → 0.5.3 (latest) with a minor changeset (unstable 0.x series). 0.2.7 → 0.5.x is a multi-major jump with likely breaking TUI API changes — must verify bun run build, bun run typecheck, and bun run test:tui (TUI tests under src/tui/__tests__) all pass before requesting review. Carry forward the overrides.@opentui/core entry from PR #335 to deduplicate branded renderable types (TextRenderable, BoxRenderable, KeyEvent, …) — @opentui/solid@0.4.x+ bundles its own @opentui/core, which otherwise breaks bun run typecheck. Landing this supersedes PRs #135 and #335 (close them after — flagged for human confirmation).

Items Needing Human Attention

• Closing PR #241 (fro-bot's duplicate @types/node 24 → 26 bump) — destructive close (Renovate's PR #278 is the canonical one).
• Closing PRs #135 and #335 in favor of the coordinated @opentui 0.2.7 → 0.5.3 PR (queued for Copilot) — destructive closes.
• Merge decision for PR #278 — Renovate's renovate/artifacts FAILURE is cosmetic (Renovate-internal, empty target URL); the CI suite is green and the lockfile is in sync. Tick the rebase/retry checkbox (or wait for Renovate's next run) to refresh that status before merging.
• Merge decision for PR #332 (biome schema 2.5.8) — clears the biome.json schema-info lint info on main; branch is CLEAN and MERGEABLE, CI green.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

---

Update — 2026-08-14

Summary

Category	Status	Actions
ERRORED PRs	✅	6 open PRs (#135, #241, #277, #278, #332, #335). Polled gh pr checks for each: every Lint, typecheck, build, unit tests CI run is SUCCESS; copilot-setup-steps SUCCESS; Fro Bot SKIPPED; Renovate SUCCESS. The only non-green status is renovate/artifacts FAILURE on PR #278 — a Renovate-internal artifact-update check (empty link, platform-managed), not a CI build failure. Checked out renovate/node-26.x and re-ran the full gate locally: bun install --frozen-lockfile ✅ (lockfile in sync with @types/node@26.2.0), bun run typecheck ✅, bun run lint ✅ (exit 0), bun run build ✅, bun test tests/*.test.ts ✅ 322 pass / 0 fail / 1279 expect() calls. No code fixes required or possible — the renovate/artifacts status will be refreshed by Renovate on its next scheduled run (optionally via its rebase/retry checkbox).
SECURITY	✅	dependabot/alerts?state=open returns 0 alerts. No critical/high advisories and no open security-update PRs. No action.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 still accurate (latest published 1.18.18; devDep pinned 1.18.16). Confirmed @opencode-ai/sdk is not a peer dep and is not referenced anywhere in src/, tests/, or scripts/. All 16 uses: entries across the 6 .github/workflows/*.yaml files are pinned to full 40-char commit SHAs. No changeset drift: package.json (0.12.1) == latest tag v0.12.1; .changeset/ holds only README.md + config.json (no unreleased entries). Major devDep bumps from the autoheal list: typescript 7.0.2 (current=latest), @biomejs/biome 2.5.8 (current=latest, bumped on main via #359), @types/bun 1.3.14 (current=latest), rimraf 6.1.3 (current=latest); only @types/node 24.13.3 → 26.2.0 (even/LTS major) is outstanding — PR #278 (Renovate, 26.2.0, mergeable, CI green, lockfile in sync) is the merge candidate; PR #241 (fro-bot, 26.2.0, stale 1.18.15 plugin pin) is the duplicate. Runtime deps @opentui/core/@opentui/solid pinned at 0.2.7 while latest is 0.5.3; intermediate PRs #135 (0.4.3) and #335 (0.4.5) both target pre-0.5.x lines and lag latest.
DEVELOPER EXPERIENCE	⚠️ → ✅	On main: bun install clean (280 installs across 311 packages, no peer-dependency warnings); bun run typecheck ✅; bun run build ✅; bun run lint exit 0 with 1 info — biome.json $schema is 2.5.5 while installed @biomejs/biome is 2.5.8 (bumped on main via #359 after PR #332 was opened targeting 2.5.7). PR #332 (2.5.7) would therefore still leave an info vs 2.5.8 once merged — flagged below. No logic-level lint failures, no new type errors, no build breaks since last run.

Tasks for Fro Bot

• Merge PR #278 (Renovate @types/node → 26.2.0, even/LTS major): mergeable, CI green, lockfile in sync, all 322 unit tests pass locally. It carries a stale renovate/artifacts FAILURE (Renovate-internal, not a CI failure) — tick its rebase/retry checkbox or let Renovate's next scheduled run refresh it before merging, then close duplicate PR #241.
• Update PR #332 to bump biome.json $schema to 2.5.8 (not 2.5.7) so it matches the installed @biomejs/biome 2.5.8 that landed on main via #359; merging at 2.5.7 would still leave the lint info. Renaming the PR/branch (currently ...2.5.6 / ...2.5.7) is cosmetic but recommended.
• Triage runtime-dep PRs #135 (@opentui/solid → 0.4.3) and #335 (@opentui/core + @opentui/solid → 0.4.5): both target pre-0.5.x lines while latest published is 0.5.3. Recommend closing both (#135 is superseded; #335 also lags) in favor of a single coordinated 0.2.7 → 0.5.3 major upgrade with a changeset (delegated to Copilot below). Closing is destructive — flagged for human confirmation.

Tasks for Copilot

• Open a coordinated PR bumping runtime deps @opentui/core and @opentui/solid from 0.2.7 → 0.5.3 (latest) with a minor changeset (unstable 0.x). 0.2.7 → 0.5.x is a multi-major jump with likely breaking TUI API changes — must verify bun run build, bun run typecheck, and bun run test:tui (TUI tests under src/tui/__tests__) all pass before requesting review. Landing this supersedes PRs #135 and #335 (close them after — flagged for human confirmation).

Items Needing Human Attention

• Duplicate/competing PRs need a merge/close decision (closing is mildly destructive): @types/node (PR #278 merge candidate vs duplicate #241) and @opentui/solid (PR #135 vs #335 vs a fresh 0.5.3 PR).
• biome.json schema freshness: PR #332 targets 2.5.7 but installed @biomejs/biome is now 2.5.8 — decide whether to update #332 to 2.5.8 (recommended) or merge 2.5.7 then bump again.

---

[fro-bot]

Run Summary — 2026-06-22 daily autohealing

Branch/PR mode: opened PR #241 and closed stale PR #127; updated the perpetual issue (#26) body with today's dated section.

Category	Status	Outcome
ERRORED PRs	✅	All open PRs passing CI. Closed stale #127.
SECURITY	✅	No Dependabot alerts; alerts API unavailable (404).
HEALTH & MAINTENANCE	⚠️	Opened PR #241 (@types/node 24→26, LTS-even). All Actions SHA-pinned. peer dep >=1.14.41 valid vs latest @opencode-ai/plugin@1.17.9.
DEVELOPER EXPERIENCE	✅	bun install, typecheck, lint, build, test:unit (321 pass) all green on main.

• Opened: #241 — chore(dev): update @types/node 24 → 26 (major)
• Closed: chore(dev): update @types/node 24 → 25 (major) #127 (superseded by chore(dev): update @types/node 24 → 26 (major) #241; targeted odd/non-LTS 25, conflicting).
• See "Items Needing Human Attention" in the perpetual issue for the remaining stale PRs (fix(deps): update dependency @opentui/core to v0.2.7 #130, fix(deps): update dependency @opentui/solid to v0.4.3 #135, fix(lint): update biome schema to match CLI version 2.4.16 #169) and the minor dev-dep bump.

[fro-bot]

Update — 2026-06-23

Summary

Category	Status	Actions
ERRORED PRs	✅	4 open PRs (#241, #169, #135, #134) — all CI passing; no fixes needed.
SECURITY	✅	No Dependabot alerts. No open vulnerability PRs.
HEALTH & MAINTENANCE	⚠️	Peer dep >=1.14.41 still valid vs @opencode-ai/plugin@1.17.9 (latest). Dev dep @opencode-ai/plugin at 1.17.8 (latest 1.17.9 — minor gap, devDep). @types/node 24.13.2 → latest 26.0.0 (PR #241 addresses, LTS-even major). @biomejs/biome 2.5.0 → latest 2.5.1 (patch only). typescript 6.0.3, @types/bun 1.3.14, rimraf 6.1.3 all current. @opentui/core/@opentui/solid at 0.2.6; latest 0.4.1 (significant gap; PRs #130/#135 stale). All Actions SHA-pinned. No unreleased changeset entries.
DEVELOPER EXPERIENCE	✅	bun install, bun run typecheck, bun run lint (63 files), bun run build, bun run test:unit (321 pass / 0 fail) all clean on main.

Tasks for Fro Bot

• No automated fixes required this run. Confirmed main is green across all checks; no errored PRs to repair.

Tasks for Copilot

• No tasks queued.

Items Needing Human Attention

• PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26, LTS-even major) — MERGEABLE, CI passing; awaiting review/merge.
• PR fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134 (CI @types/node LTS-even constraint on the autoheal prompt) — awaiting review/merge.
• PR fix(deps): update dependency @opentui/core to v0.2.7 #130 (@opentui/core → 0.2.7) — superseded; latest is 0.4.1. Recommend closing.
• PR fix(deps): update dependency @opentui/solid to v0.4.3 #135 (@opentui/solid → 0.2.8 with @opentui/core co-bump) — stale; latest is 0.4.1. Recommend closing and letting Renovate re-issue against the latest line.
• PR fix(lint): update biome schema to match CLI version 2.4.16 #169 (biome schema 2.4.15→2.4.16) — superseded by merged fix(lint): migrate biome config to v2.5.0 schema and replace deprecated recommended field #223 (schema 2.5.0 + preset migration). Recommend closing.
• Dev dep @opencode-ai/plugin 1.17.8 could be bumped to 1.17.9 (minor; devDep, not user-visible).
• Runtime deps @opentui/core/@opentui/solid lag at 0.2.6 vs latest 0.4.1 — consider a coordinated upgrade PR (major-version delta; not covered by today's autoheal scope).

---

[fro-bot]

Run Summary — 2026-06-25 (schedule #28186260081)

Daily autohealing run for opencode-copilot-delegate. No fixes required this run; repository is fully green.

Category	Status	Result
ERRORED PRs	✅	5 open PRs (#130, #134, #135, #169, #241) — all CI passing. No fixes needed.
SECURITY	✅	No open Dependabot alerts; no security-update PRs open.
HEALTH & MAINTENANCE	⚠️	Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.17.11. devDep at 1.17.9 (latest 1.17.11 — minor, optional). All GitHub Actions SHA-pinned. No unreleased changesets (package 0.12.0). @types/node 24→26 tracked by PR #241.
DEVELOPER EXPERIENCE	✅	bun install, bun run typecheck, bun run lint (63 files), bun run build, bun run test:unit (321 pass / 0 fail) all clean on main.

Actions Taken

• Updated perpetual issue Daily Autohealing Report #26 with the 2026-06-25 dated section (prepended to top, history preserved).

Items Needing Human Attention

• PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26, LTS-even) — awaiting review/merge.
• PR fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134 (CI @types/node LTS-even constraint) — awaiting review/merge.
• PR fix(deps): update dependency @opentui/core to v0.2.7 #130 / fix(deps): update dependency @opentui/solid to v0.4.3 #135 (stale @opentui 0.2.x bumps; latest is 0.4.1) — recommend closing; let Renovate re-issue.
• PR fix(lint): update biome schema to match CLI version 2.4.16 #169 (biome schema 2.4.15→2.4.16) — superseded by merged fix(lint): migrate biome config to v2.5.0 schema and replace deprecated recommended field #223; recommend closing.
• Optional: devDep @opencode-ai/plugin 1.17.9 → 1.17.11.

[fro-bot]

Run Summary — 2026-06-26

Schedule: schedule-e217cf83-28252043877 · Run ID: 28252043877 · Branch: refs/heads/main

Per-Category Outcomes

Category	Status	Actions
ERRORED PRs	✅	6 open PRs (#130, #134, #135, #169, #241, #250) — all CI passing. No fixes required.
SECURITY	✅	No Dependabot alerts accessible (alerts API HTTP 404). No security-update PRs open.
HEALTH & MAINTENANCE	⚠️	peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.17.11. dev dep at 1.17.9 (latest 1.17.11, minor gap). All GitHub Actions SHA-pinned. No unreleased changesets. @types/node 24→26 still tracked by PR #241. Other devDeps current.
DEVELOPER EXPERIENCE	⚠️ → fix queued	bun install / typecheck / build / test:unit (321 pass) clean on main. lint produced 1 info (biome schema 2.5.0 vs CLI 2.5.1) → opened PR #250 (CI passing).

Work Performed This Run

• Opened PR chore(lint): update biome schema to 2.5.1 to match CLI #250 (fix/biome-schema-2.5.1): migrated biome.json $schema 2.5.0 → 2.5.1 to match installed @biomejs/biome@2.5.1. Verified lint/typecheck/build/test:unit pass on the branch. Push to main was declined by branch protection, so the fix is routed via PR (CI: ✅ Lint, typecheck, build, unit tests pass, Renovate pass, Fro Bot skipped).

Items Needing Human Attention

• PR chore(lint): update biome schema to 2.5.1 to match CLI #250 (biome schema 2.5.0→2.5.1) — awaiting review/merge.
• PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26, LTS-even major) — awaiting review/merge.
• PR fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134 (CI @types/node LTS-even constraint on the autoheal prompt) — awaiting review/merge.
• PR fix(deps): update dependency @opentui/core to v0.2.7 #130 (@opentui/core → 0.2.7) — superseded; latest is 0.4.1. Recommend closing; let Renovate re-issue.
• PR fix(deps): update dependency @opentui/solid to v0.4.3 #135 (@opentui/solid → 0.2.8) — stale; latest is 0.4.1. Recommend closing; let Renovate re-issue.
• PR fix(lint): update biome schema to match CLI version 2.4.16 #169 (biome schema 2.4.15→2.4.16) — superseded by merged fix(lint): migrate biome config to v2.5.0 schema and replace deprecated recommended field #223. Recommend closing.
• Optional: bump devDep @opencode-ai/plugin 1.17.9 → 1.17.11 (minor, devDep — not user-visible).

Detailed dated update has been prepended to the body of this perpetual issue (#26).

---

🤖 Posted by Fro Bot Agent (scheduled autoheal run 28252043877)

[fro-bot]

Run Summary — 2026-06-27

Delivery mode: branch-pr (no branch/PR actions taken; no fixes required this run).

Categories

Category	Status	Notes
ERRORED PRs	✅	6 open PRs (#130, #134, #135, #169, #241, #250) — all CI passing. All mergeable=true (behind, no conflicts). No fixes required.
SECURITY	✅	Dependabot alerts API returns HTTP 404 to the bot; no security-update PRs open.
HEALTH & MAINTENANCE	⚠️	peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.17.11. All GitHub Actions SHA-pinned. No unreleased changesets. @types/node major bump tracked by PR #241 (mergeable). Latest @opentui/core/@opentui/solid 0.4.2 vs current 0.2.6 (PRs #130/#135 stale). devDep @opencode-ai/plugin 1.17.9 → 1.17.11 optional minor.
DEVELOPER EXPERIENCE	⚠️	On main: bun install, typecheck, build, test:unit (321 pass / 0 fail) all clean. lint produces 1 info (biome schema 2.5.0 vs CLI 2.5.1) → PR #250 (mergeable, awaiting merge).

Actions Taken

• Reviewed all 6 open PRs — all green and mergeable; no errored CI to fix.
• Verified bun install / typecheck / lint / build / test:unit on main.
• Verified all .github/workflows/*.yaml uses: are SHA-pinned.
• Verified .changeset/ has no unreleased entries (only README.md + config.json).
• Checked latest published versions: @opencode-ai/plugin 1.17.11, @opencode-ai/sdk 1.17.11, @types/node 26.0.1, @biomejs/biome 2.5.1, typescript 6.0.3, @types/bun 1.3.14, rimraf 6.1.3, @opentui/core/solid 0.4.2.
• Prepended a dated Update section to the top of this issue body (2026-06-27).

No-Op Rationale

No automated fixes were possible this run because:

• Branch protection blocks direct pushes to main; the lone remaining lint info (biome schema) is already routed via PR chore(lint): update biome schema to 2.5.1 to match CLI #250, which is green and mergeable.
• No failing CI on any open PR to repair.
• No critical/high Dependabot advisories accessible; no security PR to file.
• Other devDeps current; @types/node major bump pending merge of chore(dev): update @types/node 24 → 26 (major) #241.

Items Needing Human Attention

• Merge PR chore(lint): update biome schema to 2.5.1 to match CLI #250 (biome schema 2.5.0→2.5.1).
• Merge PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26, LTS-even).
• Merge PR fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134 (autoheal prompt LTS-even constraint).
• Close stale PRs fix(deps): update dependency @opentui/core to v0.2.7 #130, fix(deps): update dependency @opentui/solid to v0.4.3 #135 (superseded; latest @opentui/* is 0.4.2) and fix(lint): update biome schema to match CLI version 2.4.16 #169 (superseded by merged fix(lint): migrate biome config to v2.5.0 schema and replace deprecated recommended field #223).
• Optional: bump devDep @opencode-ai/plugin 1.17.9 → 1.17.11.

[fro-bot]

Daily Autohealing Run — 2026-06-28 (Run #28328673910)

All categories green; no fixes pushed this run. Full details prepended to this issue's body above.

Run Summary

Category	Status	Actions
ERRORED PRs	✅	6 open PRs (#130, #134, #135, #169, #241, #250) — all CI passing; all mergeable (behind only). No fixes required.
SECURITY	✅	Dependabot alerts API returns HTTP 404 to the bot (alerts not exposed). No security-update PRs open. No open advisories.
HEALTH & MAINTENANCE	✅	peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.17.11. devDep @opencode-ai/plugin now at 1.17.11 (latest). All GitHub Actions SHA-pinned. No unreleased changeset entries (package 0.12.0). @types/node 24→26 still via PR #241 (mergeable). Other devDeps current.
DEVELOPER EXPERIENCE	⚠️	bun install, bun run typecheck, bun run build, bun run test:unit (321 pass / 0 fail) all clean. bun run lint produces 1 info (biome.json schema 2.5.0 vs CLI 2.5.1) → addressed by PR #250 (mergeable, awaiting merge).

Tasks for Fro Bot

• No automated fixes required this run.

Tasks for Copilot

• No tasks queued.

Items Needing Human Attention

• Merge PR chore(lint): update biome schema to 2.5.1 to match CLI #250 (biome schema 2.5.0→2.5.1) — clears the lingering lint info on main.
• Merge PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26, LTS-even major).
• Merge PR fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134 (CI @types/node LTS-even constraint on the autoheal prompt).
• Close PR fix(deps): update dependency @opentui/core to v0.2.7 #130 (@opentui/core → 0.2.7) and PR fix(deps): update dependency @opentui/solid to v0.4.3 #135 (@opentui/solid → 0.2.8) — superseded; latest is 0.4.2. Let Renovate re-issue.
• Close PR fix(lint): update biome schema to match CLI version 2.4.16 #169 (biome schema 2.4.15→2.4.16) — superseded by merged fix(lint): migrate biome config to v2.5.0 schema and replace deprecated recommended field #223.

[fro-bot]

Run Summary — 2026-06-29

Delivery mode: branch-pr (no branch/PR actions taken; no fixes required this run).

Categories

Category	Status	Notes
ERRORED PRs	✅	6 open PRs (#130, #134, #135, #169, #241, #250) — all CI passing. No fixes required.
SECURITY	✅	Dependabot alerts API returns HTTP 404 to the bot; no security-update PRs; no open advisories.
HEALTH & MAINTENANCE	✅	peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.17.11 (devDep fully current). All GitHub Actions SHA-pinned. No unreleased changesets. @types/node 24→26 tracked by PR #241. Other devDeps current.
DEVELOPER EXPERIENCE	⚠️	main green: install/typecheck/build/test:unit (321 pass) clean. lint → 1 info (biome.json schema 2.5.0 vs CLI 2.5.1), still addressed by green PR #250 awaiting merge.

Actions Taken

• Updated this perpetual issue (Daily Autohealing Report #26) with the 2026-06-29 dated section prepended to the body.
• No new commits/PRs: all open PRs are green and no new failures, security advisories, or major-bump devDeps warrant a fresh PR.

Items Needing Human Attention

• Merge: PR chore(lint): update biome schema to 2.5.1 to match CLI #250 (biome schema 2.5.0→2.5.1), PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26), PR fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134 (CI @types/node LTS-even constraint) — all green, awaiting review/merge.
• Close (superseded): PR fix(lint): update biome schema to match CLI version 2.4.16 #169 (superseded by merged fix(lint): migrate biome config to v2.5.0 schema and replace deprecated recommended field #223), PR fix(deps): update dependency @opentui/core to v0.2.7 #130 & fix(deps): update dependency @opentui/solid to v0.4.3 #135 (latest @opentui/* is 0.4.2; let Renovate re-issue against the latest line).

[fro-bot]

Run Summary — 2026-07-08 (Daily Autohealing)

Category	Status	Notes
ERRORED PRs	✅	All 8 open PRs pass local bun install/typecheck/lint/test:unit. Only non-green check is renovate/artifacts on #278 (Renovate-internal, not a CI failure).
SECURITY	✅	0 open Dependabot alerts; no critical/high advisories; no security PRs needed.
HEALTH & MAINTENANCE	✅	Peer deps valid; all 16 uses: SHA-pinned; changeset hygiene clean. Opened PR #280 bumping typescript 6.0.3 → 7.0.2 (full green: typecheck/lint/build/test:unit + CI).
DEVELOPER EXPERIENCE	✅	main is green across install/typecheck/lint/build/test:unit.

Delivery (branch-pr mode):

• Created & pushed branch fro-bot/typescript-7 → PR chore(dev): bump typescript to 7.0.2 #280 (chore(dev): bump typescript to 7.0.2). CI: Lint, typecheck, build, unit tests SUCCESS.
• Perpetual issue Daily Autohealing Report #26 body prepended with today's update section.

Tasks raised:

• Fro Bot: close stale dupe PR chore(dev): update @types/node 24 → 26 (major) #241 (superseded by Renovate chore(dev): update dependency @types/node to v26 #278); re-trigger chore(dev): update dependency @types/node to v26 #278 to clear renovate/artifacts.
• Copilot: review/merge chore(dev): bump typescript to 7.0.2 #280.

Human attention:

• Fork PR fix(runtime): skip stale pid registration #279 has no repo CI; locally green — needs maintainer trigger/merge.
• typescript 7.0.2 published today; consider brief soak before merging chore(dev): bump typescript to 7.0.2 #280.

[fro-bot]

Run Summary — 2026-07-10 (Daily Autohealing)

Category	Status	Notes
ERRORED PRs	✅	No PR code fixes required. Verified external contributor PR #279 locally (no hosted CI authorized) — all green (322 pass / 0 fail incl. new regression test); posted verification comment. renovate/artifacts FAILURE on #278 is Renovate-internal and self-heals on next Renovate run.
SECURITY	✅	0 open Dependabot alerts; no vulnerable dep PRs needing fixes.
HEALTH & MAINTENANCE	✅	Peer dep @opencode-ai/plugin >=1.14.41 accurate (latest 1.17.18). Dev-dep majors already knocked out (#280 typescript 6→7 green; #241 @types/node 24→26 green). Found @biomejs/biome drifted behind (2.5.2→2.5.3 patch) and opened PR #281. All 16 uses: SHA-pinned. No unreleased changesets on main.
DEVELOPER EXPERIENCE	✅	main green across install/typecheck/lint/build/test:unit (321 pass / 0 fail); no peer warnings.

Delivery (branch-pr mode):

• Created & pushed branch chore/dev-deps-biome-2.5.3 → PR chore(dev): bump @biomejs/biome to 2.5.3 #281 (chore(dev): bump @biomejs/biome to 2.5.3). CI: Lint, typecheck, build, unit tests SUCCESS + Renovate SUCCESS. Bumps the devDependency and syncs biome.json $schema to 2.5.3 (mirrors chore(ci): bump biome schema version to 2.5.2 #270 pattern). No changeset (devDependency-only).
• Verified external contributor PR fix(runtime): skip stale pid registration #279 (fix(runtime): skip stale pid registration) — checked out branch, ran full local CI matrix, posted a verification comment on the PR (not an approval).
• Perpetual issue Daily Autohealing Report #26 body prepended with today's dated ## Update — 2026-07-10 section.

Tasks raised:

• Fro Bot: close duplicate @types/node PR chore(dev): update dependency @types/node to v26 #278 (superseded by chore(dev): update @types/node 24 → 26 (major) #241, same 24→26 major bump with full verification in its body); rebase stale Renovate runtime-dep PRs fix(deps): update dependency @opentui/solid to v0.4.3 #135/fix(deps): update dependency @opentui/core to v0.2.7 #130 (both BEHIND/MERGEABLE) via their rebase/retry checkboxes.
• Copilot: evaluate @opentui/solid + @opentui/core 0.2.6 → 0.4.3 major upgrade (runtime deps; pre-1.0 → treat as breaking) and open a single changeset-bearing PR; review/merge chore(dev): bump @biomejs/biome to 2.5.3 #281.

Human attention:

• First-time contributor PR fix(runtime): skip stale pid registration #279 is sound and locally verified but hosted CI is not authorized to run — a maintainer must approve workflows, then review/merge. Bot verification comment is not an approval.
• @types/node major duplication: recommend merging chore(dev): update @types/node 24 → 26 (major) #241 and closing chore(dev): update dependency @types/node to v26 #278 as duplicate (optionally refresh chore(dev): update @types/node 24 → 26 (major) #241 to 26.1.1 first).
• @opentui/* two-major-version drift on runtime deps (0.2.6 pinned vs 0.4.3 latest) — out of scope for routine autohealing; flagged as Copilot task.

[fro-bot]

Run Summary — 2026-07-28 daily autohealing

Branch/PR mode: rebased/force-pushed PR #302 (fix/biome-schema-2.5.4) onto origin/main (linearized merge commits, 609904d → 51491f2); branch already targets schema 2.5.5. Updated the perpetual issue (#26) body with today's dated section.

Category	Status	Outcome
ERRORED PRs	✅	No open PR has failing Lint, typecheck, build, unit tests CI. Rebased #302 (was BEHIND) → now CLEAN+MERGEABLE; local lint/typecheck/build clean. #278's renovate/artifacts FAILURE is Renovate-internal, non-gating.
SECURITY	✅	dependabot/alerts?state=open returns [] — no advisories, no vulnerable-dep PRs.
HEALTH & MAINTENANCE	✅	peerDep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.8 (devDep 1.18.5, Renovate-managed). All workflow uses: SHA-pinned. Changeset hygiene clean (0.12.1 == tag v0.12.1; no unreleased entries). @types/node 24→26 covered by #278/#241; no new PR.
DEVELOPER EXPERIENCE	✅	bun install clean, typecheck ✅, build ✅ (dist/ populated), test:unit ✅ 322 pass / 0 fail / 1279 expect() calls. lint on main still emits 1 schema info — clears once #302 merges.

• Updated: Issue #26 — Daily Autohealing Report (new ## Update — 2026-07-28 section prepended).
• Force-pushed: PR #302 — chore(dev): bump biome config schema (rebased onto latest main; branch targets $schema: 2.5.5).
• Awaiting human merge: chore(deps): update actions/cache action to v6 #276 (actions/cache v6), chore(deps): update actions/checkout action to v7 #277 (actions/checkout v7), chore(dev): bump biome config schema to 2.5.4 #302 (biome schema 2.5.5), plus chore(dev): update dependency @types/node to v26 #278 vs chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 26 dedup) and fix(deps): update dependency @opentui/solid to v0.4.3 #135 triage. See "Items Needing Human Attention" in the perpetual issue.

[fro-bot]

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 31199777339 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: ✅ 0 failing CI. 7 open PRs (fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335, chore(dev): bump biome config schema to 2.5.8 #332, chore(dev): update dependency @types/node to v26 #278, chore(deps): update actions/checkout action to v7 #277, chore(deps): update actions/cache action to v6 #276, chore(dev): update @types/node 24 → 26 (major) #241, fix(deps): update dependency @opentui/solid to v0.4.3 #135). All Lint, typecheck, build, unit tests SUCCESS (Fro Bot check SKIPPED). PR chore(dev): update dependency @types/node to v26 #278 has a Renovate-managed renovate/artifacts FAILURE status (manual-edit conflict vs chore(dev): update @types/node 24 → 26 (major) #241), not a CI code failure; mergeable but UNSTABLE. No PRs required type/lint/build fixes this run.
• SECURITY: ✅ vulnerabilityAlerts(states:[OPEN]) count 0. No security-update PRs; no critical/high advisories unaddressed.
• HEALTH & MAINTENANCE: ✅ peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.15; @opencode-ai/sdk not a peer / not imported. All 17 workflow uses: SHA-pinned. No changeset drift (pkg 0.12.1 == tag v0.12.1). devDeps current except @types/node 24.13.3→26.1.2 (LTS-even, in flight via parallel PRs chore(dev): update @types/node 24 → 26 (major) #241 / chore(dev): update dependency @types/node to v26 #278). Runtime @opentui/* at 0.2.7; PR fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 bumps to 0.4.5 (current 0.4.x line); latest 0.5.1 now published → future follow-up. All other devDeps current (typescript 7.0.2, @biomejs/biome 2.5.7, @types/bun 1.3.14, rimraf 6.1.3).
• DEVELOPER EXPERIENCE: ⚠️ → ✅ bun install / typecheck / build / test:unit (322 pass / 0 fail) clean on main. bun run lint had 1 info (biome.json schema 2.5.5 vs CLI 2.5.7) — cleared by updating PR chore(dev): bump biome config schema to 2.5.8 #332 (rebased + re-targeted 2.5.5→2.5.7; CI green). Once chore(dev): bump biome config schema to 2.5.8 #332 lands, main lint will be clean.

Actions taken this run:

• PR chore(dev): bump biome config schema to 2.5.8 #332 (chore/dev-biome-schema-2.5.6 → re-titled chore(dev): bump biome config schema to 2.5.7): rebased against latest main, amended the schema bump 2.5.5→2.5.6 to 2.5.5→2.5.7 to match @biomejs/biome@2.5.7 (CLI advanced past the original PR target). Updated PR title + body. Force-pushed. CI green.
• PR fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (chore/opentui-0.4.5): rebased onto latest main to clear BEHIND. Re-verified locally (install/typecheck/build/test:unit all clean). Force-pushed. CI green.
• Perpetual issue Daily Autohealing Report #26 body updated with today's (2026-08-07) section prepended to the top.

No new PRs opened this run — no qualifying untracked major devDep bump or security advisory.Repo is healthy; all pending work is covered by existing green PRs awaiting human review/merge.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

[fro-bot]

Autoheal run complete for marcusrbrown/opencode-copilot-delegate (Run ID 31267199534). Full dated report prepended to this issue body above.

What was done this run

• PR chore(dev): bump biome config schema to 2.5.8 #332 (biome schema 2.5.5→2.5.7): rebased onto latest main (had drifted BEHIND); force-pushed. Branch bun run lint is now fully clean (no schema info).
• PR chore(dev): update @types/node 24 → 26 (major) #241 (@types/node 24→26): had accumulated 3 merge commits and drifted BEHIND. Rewrote to a single clean commit on top of main, advancing the pin to the latest @types/node@26.2.0 (even/LTS per .github/renovate.json5). Verified typecheck/lint/build/test:unit green. Force-pushed; supersedes Renovate duplicate chore(dev): update dependency @types/node to v26 #278.
• PR fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 (@opentui/core+@opentui/solid 0.2.7→0.4.5 with overrides + patch changeset): rebased onto latest main (had drifted BEHIND). Re-verified typecheck/lint/build/test:unit green. Force-pushed.

All three branches verified locally: bun install clean, bun run typecheck exit 0, bun run build exit 0, bun run test:unit 322 pass / 0 fail.

State of main

bun install, bun run typecheck, bun run build, and bun run test:unit (322 pass) are all clean. bun run lint reports 1 info (biome.json schema 2.5.5 vs CLI 2.5.7) — cleared once PR #332 merges.

No new PRs opened

No failing CI to triage. No open security advisories (vulnerabilityAlerts(states:[OPEN]) count 0). Peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.15. All workflow uses: SHA-pinned. No changeset drift (pkg 0.12.1 == tag v0.12.1). Only devDep major bump pending (@types/node 24→26) is now on a clean PR #241. Runtime @opentui/* latest is 0.5.1 (PR #335 targets the 0.4.x line) — future work, not in scope.

Items needing human attention

Merge #332, #335, #241. Close duplicate Renovate PRs #278 (in favor of #241) and #135 (in favor of #335). Review/merge Renovate PRs #277 (actions/checkout v7), #276 (actions/cache v6).

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 31267199534 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing CI (7 open; chore(dev): update dependency @types/node to v26 #278's only failure is Renovate-internal artifacts status, a duplicate of chore(dev): update @types/node 24 → 26 (major) #241).
• SECURITY: 0 vulnerability alerts; 0 security PRs.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.15; @opencode-ai/sdk not a peer / not imported; all workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1 == tag v0.12.1); devDeps current except @types/node 24→26 (now PR chore(dev): update @types/node 24 → 26 (major) #241, clean, latest 26.2.0); runtime @opentui/* 0.2.7 vs 0.5.1 (PR fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 targets 0.4.5).
• DEVELOPER EXPERIENCE: bun install / typecheck / build / test:unit (322 pass) clean on main; lint had 1 info (schema 2.5.5 vs CLI 2.5.7) — cleared by PR chore(dev): bump biome config schema to 2.5.8 #332 (rebased today, branch lint fully clean).
• Actions taken: rebased PR chore(dev): bump biome config schema to 2.5.8 #332 (still addresses schema 2.5.5→2.5.7); rewrote PR chore(dev): update @types/node 24 → 26 (major) #241 to a single clean commit bumping @types/node to the latest 26.2.0 (was BEHIND with 3 merge commits); rebased PR fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 onto latest main. All three force-pushed and verified locally (typecheck/lint/build/test:unit green). No new PRs opened this run (no qualifying untracked major devDep bump / security advisory). Perpetual issue Daily Autohealing Report #26 updated.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

[fro-bot]

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 31515039369 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

• ERRORED PRs: 0 failing (6 open fix(deps): update dependency @opentui/solid to v0.4.3 #135/chore(dev): update @types/node 24 → 26 (major) #241/chore(deps): update actions/checkout action to v7 #277/chore(dev): update dependency @types/node to v26 #278/chore(dev): bump biome config schema to 2.5.8 #332/fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335; all CI Lint, typecheck, build, unit tests SUCCESS pre-rebase). Action: rebased 4 BEHIND branches (fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335, chore(dev): bump biome config schema to 2.5.8 #332, chore(dev): update @types/node 24 → 26 (major) #241, fix(deps): update dependency @opentui/solid to v0.4.3 #135) onto main via gh pr update-branch. No code fixes required.
• SECURITY: 0 Dependabot alerts (API 404 to bot); 0 security-update PRs; 0 new PRs.
• HEALTH & MAINTENANCE: peer dep @opencode-ai/plugin >=1.14.41 valid vs latest 1.18.16; @opencode-ai/sdk not a dep / not imported; all 16 workflow uses: SHA-pinned; no changeset drift (pkg 0.12.1); devDeps current except @types/node 24→26 even/LTS major (duplicate PRs chore(dev): update @types/node 24 → 26 (major) #241 + chore(dev): update dependency @types/node to v26 #278); biome patch gap 2.5.7→2.5.8 (non-major, out of scope); runtime @opentui/* 0.2.7 vs 0.4.x (PRs fix(deps): update dependency @opentui/solid to v0.4.3 #135, fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 — runtime, out of devDep scope).
• DEVELOPER EXPERIENCE: bun install / typecheck / build clean; lint 1 info (biome schema 2.5.5 vs CLI 2.5.7 — covered by PR chore(dev): bump biome config schema to 2.5.8 #332, rebased this run).
• Actions taken: rebased PRs fix(deps): update dependency @opentui/solid to v0.4.3 #135, chore(dev): update @types/node 24 → 26 (major) #241, chore(dev): bump biome config schema to 2.5.8 #332, fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #335 onto main (clearing BEHIND); no new commits, no new PRs opened. Repo healthy.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal. Perpetual issue body updated with the 2026-08-11 section above.