Preserve every settlement and ownership gate while exposing fixed reason codes for checkpoint mismatches and prior authority verification. Cover each diagnostic branch without logging evidence values.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Authorize exact user-owned viewer cleanup independently of the current task environment, with route and module regressions.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Integrate the scoped production correction and existing config test from 2700054c6a. Full Claude and Codex execute regressions remain in the stacked acceptance PR.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep controller instruction reads while advertising the registered persistent execution path. Mount approved remote Claude skills into the isolated user configuration so user-only settings can discover them without enabling project settings.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Integrate the production route correction from 5af1eb0762; its full route regression suite remains in the stacked acceptance PR.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Delayed cleanup of an older lease must not replace the latest task authority for computer previews. Keep rejecting a non-live latest owner instead of searching older leases.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Restrict fresh Boat Codex setup to CLI and preserve unsupported existing ACP/default settings as explicit repair choices. Block saving or testing until CLI is selected; keep Claude and other environments unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep the deployed Boat migration and append the unchanged upstream fast-response migration with regenerated Drizzle snapshots. This branch is staging-only; canonical feature history remains unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Keep an exact inode receipt under the existing editor lock before writing temporary content. Recover only that recorded inode on the next operation and preserve replacements and unknown files.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Apply GNU timeout after SSH admission deducts queue time. Verify a delayed remote-shaped Python write is killed independently of local SSH termination.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Propagate the admitted operation deadline through readiness, claims, and SSH commands. Keep only a bounded transport-settlement hold, and expire a short file waiter without cancelling shared SSH initialization.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Show CLI as the visible initial engine for fresh legacy agents on active Boat environments and preserve explicit choices through probe and hire. Permit the runtime engine selector on attached Boat environments while retaining managed host-path restrictions and other environment policy.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
* commit '2c09c8c16da3d605fc043c745535a7e65f961bb9':
perf(chat): wake action queues from commits and deadlines (#15808)
chore(lockfile): refresh pnpm-lock.yaml (#15820)
feat: add company fast-response acknowledgements (#15748)
ci: move the Grok public-install verification off Canary Dry Run (#15213)
Preserve the exact deployed Boat SQL hash under generated migration 0332 so existing staging databases recognize its history. Keep additive schema and shared exports from both branches.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Update Grok, Claude, and Codex wizard probe and hire assertions to preserve the explicitly created account and grant. Subscription-default expectations remain unchanged.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Bind the account returned by credential creation explicitly instead of silently resolving the user’s existing provider default. Preserve that binding on connection-test retries without creating another account or changing defaults.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work.
> - Chat keeps durable rows for provider actions and setup messages.
> - Five action queues still scan the database every second when empty.
> - Empty scans add idle database traffic and prevent cost savings from
sleep.
> - This pull request wakes these queues when their writes commit or
their next deadline arrives.
> - Existing rows retain retry and restart recovery. Empty queues stop
scanning.
## Linked Issues or Issue Description
Refs #15802, #15625, #15750, #15757. Related allocation work: #15153.
**What existing behavior does this improve?**
Idle chat reconciliation for Slack Board messages, Slack slash-command
task starts, Slack setup verification messages, receipt reactions, and
Slack session stops.
**Current behavior**
The app runs these five queue scans through chat maintenance every
second, including when no work exists.
**Proposed behavior**
Each queue has an independent worker on the existing scheduler.
Producers and foreground claim/retry/settlement writes announce work
inside their database transaction. The worker wakes after the outer
transaction settles. Startup restores durable work. Shared dispatch and
deadline predicates select real retries and abandoned claims. Empty
queues disarm.
**Subsystem affected**
Server chat services. No schema or migration changes.
## What Changed
- Register five action workers alongside the three delivery workers from
#15802. Remove their scans from periodic app maintenance.
- Share action eligibility between dispatch and deadline selection. Park
paused Board messages and task starts until endpoint changes. Preserve
uncertain-send quarantine.
- Wake setup verification after account, welcome, registration, or
authenticated callback changes. Exclude prerequisites that need another
event.
- Persist a retry time for failed provider-confirmed task admission. Its
own commit notification cannot cause an immediate retry loop.
- Reuse the existing transaction signals and scheduler registration
code. Provider calls remain outside database transactions.
- Update the instance-sleep inventory and add scheduler and PostgreSQL
regression coverage.
## Verification
- Passed: 37 scheduler, coordinator, and app-wiring tests, including an
idle hour with no further scans or timers.
- Passed: seven focused PostgreSQL chat cases. These cover deadline
eligibility, startup recovery, outer-commit wakes, actual producer
signals, and signed-callback verification without maintenance polling.
- Passed: `pnpm typecheck`.
- Passed: full chat integration suite and related
publication/coordinator tests, **1,278 tests** across six files,
including **1,228 chat integration cases**.
- Passed: `pnpm build`.
- After the review fix, seven focused PostgreSQL integration cases and
the server typecheck passed again. Deadline and dispatch queries now
exclude completed action history.
- Greptile: **5/5** on `35a979fce6bb9ab910fab3373ec8e537fc2d01a9`, with
the prior finding resolved and no new findings.
- Fixed a CI timing failure in the GitHub mention integration test:
asynchronous admission now has an explicit ten-second assertion deadline
instead of the default one second. The failure reproduced locally; all
five mention variants and all 398 cases in the matching CI shard pass
after the fix.
- Hosted CI passed on `35a979fce6bb9ab910fab3373ec8e537fc2d01a9`: **54
successful checks**, two intentionally skipped Storybook checks, no
failures or pending checks.
Provider responses are simulated in the integration suite. PostgreSQL,
transactions, service dispatch, and scheduling are real. No live Slack
workspace was used.
## Risks
- Every producer that changes runnable state must emit a transaction
signal. This change covers the five queues and their foreground
dispatch/retry paths. Direct SQL and independent DB owners still need
explicit integration or startup recovery.
- Missing retry or claim deadlines can strand work. Tests compare the
dispatch and deadline behavior, including paused and uncertain states.
- Other provider maintenance, sockets, and scheduled jobs remain. This
change does not establish full instance sleep.
- No new tables, migrations, or provider credentials are required.
## Model Used
OpenAI Codex (GPT-6), with repository inspection, code execution, and
automated tests.
## Checklist
- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
---------
Co-authored-by: Paperclip <noreply@paperclip.ing>
Dotta