Skip to content

Daily Autohealing Report #26

Open
Open
Daily Autohealing Report#26

Description

@fro-bot
fro-bot
opened on Apr 25, 2026

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

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

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.1 #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

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

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

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

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

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 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.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 build(dev): update all non-major dependencies #377 once it rebases green.)

Items Needing Human Attention

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

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

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 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.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 build(dev): update all non-major dependencies #377 once it rebases green.)

Items Needing Human Attention

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 — build(dev): update all non-major dependencies #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 (chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241 duplicate, awaiting merge) and runtime @opentui/* 0.2.7 vs 0.5.7 (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: 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 Daily Autohealing Report #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

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 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.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 build(dev): update all non-major dependencies #377 once it rebases green.)

Items Needing Human Attention

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 — build(dev): update all non-major dependencies #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 (chore(dev): update dependency @types/node to v26 #278/chore(dev): update @types/node 24 → 26 (major) #241 duplicate, awaiting merge) and runtime @opentui/* 0.2.7 vs 0.5.7 (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: 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 Daily Autohealing Report #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

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 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.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

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

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

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 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.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

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

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

Tasks for Copilot

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

Items Needing Human Attention

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

Tasks for Copilot

  • Rebase or close-and-redo the @opentui/* runtime-dep PRs: close fix(deps): update dependency @opentui/solid to v0.4.3 #135 (→0.4.3, superseded); rebase fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 #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 chore(dev): update dependency @types/node to v26 #278 is ready; chore(dev): update @types/node 24 → 26 (major) #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

Tasks for Copilot

Items Needing Human Attention

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

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

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions