feat(schedule): send messages later on existing threads - #1253

AssertionError: expected [ { id: 'general', …(9) }, …(45) ] to have a length of 45 but got 46 - Expected + Received - 45 + 46 ❯ tests/builtin-profiles.test.ts:37:35

AssertionError: expected [ 'general', 'explore', …(44) ] to have a length of 45 but got 46 - Expected + Received - 45 + 46 ❯ tests/builtin-profiles.test.ts:32:52

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/top-level-cases/attachment-store-model.cases.ts:414:56

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/top-level-cases/attachment-store-model.cases.ts:162:56

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/top-level-cases/attachment-store-model.cases.ts:128:56

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/top-level-cases/attachment-store-model.cases.ts:86:77

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/agent-loop-transcript.test.ts:544:31

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/agent-loop-transcript.test.ts:462:31

AssertionError: expected 'failed' to be 'completed' // Object.is equality Expected: "completed" Received: "failed" ❯ tests/agent-loop-sandbox.test.ts:26:20

ExtensionToolCatalogDriftError: Extension tool catalog epoch epoch_first no longer matches the active registrations. ❯ ExtensionToolRegistry.assertCatalogCurrent src/adapters/tool/extension-tool-provider.ts:602:42 ❯ Object.shouldAdvertise src/adapters/tool/extension-tool-provider.ts:365:14 ❯ CapabilityRegistry.listTools src/adapters/tool/capability-registry.ts:117:38 ❯ src/adapters/tool/local-tool-host-core.ts:62:84 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { epochId: 'epoch_first', drift: { kind: 'breaking', missing: [ 'extension:com.example.epoch/beta' ], changed: [], added: [] }, code: 'extension_tool_catalog_drift' } This error originated in "src/adapters/tool/extension-tool-provider.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

React Hook useEffect has missing dependencies: 'credentialMutationTimers', 'drainCredentialRef', 'mutationOwner', and 'pendingSharedProviderCredentials'. Either include them or remove the dependency array

React Hook useEffect has missing dependencies: 'catalogMutationTimers', 'credentialMutationTimers', 'drainCatalogRef', 'drainCredentialRef', 'mutationOwner', 'pendingSharedProviderCatalogs', and 'pendingSharedProviderCredentials'. Either include them or remove the dependency array

React Hook useEffect has a missing dependency: 'cursorMetadataRepairAttempts'. Either include it or remove the dependency array

React Hook useEffect has a missing dependency: 'value'. Either include it or remove the dependency array. If 'setDraft' needs the current value of 'value', you can also switch to useReducer instead of useState and read 'value' in the reducer

The 'childRuns' conditional could make the dependencies of useMemo Hook (at line 279) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'childRuns' in its own useMemo() Hook

React Hook useEffect has a missing dependency: 'busy'. Either include it or remove the dependency array

React Hook useLayoutEffect has a missing dependency: 'userTurnKey'. Either include it or remove the dependency array

The ref value 'flushOnUnmountRef.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'flushOnUnmountRef.current' to a variable inside the effect, and use that variable in the cleanup function

The ref value 'statusTimer.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'statusTimer.current' to a variable inside the effect, and use that variable in the cleanup function