Files
PaperClipAI/releases/v2026.916.1.md
T
Devin Foleyandgithub-actions[bot] cf2742ac48 docs(release): canonicalize v2026.916.1 release notes (#13774)
## Thinking Path

> - Stable `2026.916.1` just published from beta `2026.921.0-beta.0`;
its curated notes live at `releases/beta/v2026.921.0-beta.0.md` on
`master`.
> - The release workflow's `canonicalize_stable_notes` job pushed this
branch, which `git mv`s them to the canonical stable path.
> - Merging restores the canonical `releases/` layout, matching every
prior stable.

## Linked Issues or Issue Description

Follow-up to the
[v2026.916.1](https://github.com/paperclipai/paperclip/releases/tag/v2026.916.1)
stable release; notes were curated in
[#13766](https://github.com/paperclipai/paperclip/pull/13766).

## What Changed

- `git mv releases/beta/v2026.921.0-beta.0.md releases/v2026.916.1.md`
(workflow-generated, content unchanged).

## Verification

- Rename only; the GitHub Release body was already published from this
content.

## Risks

None — documentation layout only.

## Model Used

Anthropic Claude Fable 5 (`claude-fable-5`) via Claude Code, with tool
use and code execution.

## 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
- [x] My branch name describes the change and contains no internal
Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass (rename-only; no tests
apply)
- [x] I have added or updated tests where applicable (none apply)
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green (pending on this fresh PR)
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
(pending)
- [x] I will address all Greptile and reviewer comments before
requesting merge

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-09-21 19:52:58 -07:00

15 lines
1.5 KiB
Markdown

# Paperclip v2026.916.1
> Released: 2026-09-21
A patch on top of [2026.916.0](https://github.com/paperclipai/paperclip/releases/tag/v2026.916.0) that fixes sending messages in the task conversation view. It carries one targeted fix (plus its regression tests and a small server error-classification repair that rode along in the same commit); everything else in 2026.916.0 is unchanged.
## Fixes
- **The chat composer's send button no longer starts out disabled on desktop.** The task page disables the composer while it checks whether the task is paused, and in React Query v5 that pending state is true from mount until the first *successful* response — so every desktop task page loaded with the send button disabled, and it stayed disabled for good if the pause-status request stalled. Sends are now allowed while the check is pending: the server remains authoritative and rejects messages to paused tasks with a 409 before saving a comment or waking an agent, and a confirmed pause hold or a failed status check still blocks the composer as before. ([#13562](https://github.com/paperclipai/paperclip/pull/13562))
- **Duplicate document inserts wrapped by the ORM are classified as retryable conflicts again**, instead of surfacing as opaque database errors; unrelated database failures keep their original identity. (Part of [#13562](https://github.com/paperclipai/paperclip/pull/13562))
## Upgrade Guide
- No migrations, no configuration changes, no API changes. Upgrade in place.