docs(release): align 2026.1006.0-beta.0 stable notes header with v2026.1012.0 (#16000)

<!-- Write all pull request text in Simplified Technical English
(ASD-STE100). -->

## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - The release pipeline promotes a soaked beta to stable. The stable
job publishes `releases/beta/v<beta-version>.md` from `master` as the
GitHub Release body, pinned at dispatch time.
> - Beta `2026.1006.0-beta.0` (source
`22a3ea3414e9039a538fbb0374b3cfa7fc4371eb`, 130 commits after
v2026.1005.0) has soaked for more than three days. The stable version
for 2026-10-12 is `v2026.1012.0`.
> - The curated notes from #15388 were written at beta time. They guess
`v2026.1009.0` and `2026-10-09`, which did not ship.
> - A pre-dispatch audit confirmed the commit count, the PR cross-check,
the migration range, the environment defaults, and the Contributors
handles. Only the header, the date, the intro version, and the
contributor count are stale.
> - This pull request corrects those four lines before the stable
dispatch, so the public release page shows the version that ships.
> - The benefit is that the GitHub Release body and the canonical notes
file agree with the npm version and the git tag.

## Linked Issues or Issue Description

**Issue type**

Docs: release notes.

**Where is the issue?**

`releases/beta/v2026.1006.0-beta.0.md` on `master`.

**What's wrong?**

The notes carry a guessed stable version and date from beta time:

- The H1 reads `# Paperclip v2026.1009.0` and the next line reads `>
Released: 2026-10-09`. No `v2026.1009.0` stable shipped. The stable that
promotes this beta on 2026-10-12 resolves to `v2026.1012.0`.
- The intro paragraph names `v2026.1009.0` for the same reason.
- The Contributors line says 8 contributors. `git shortlog -sn
v2026.1005.0..22a3ea3414e9039a538fbb0374b3cfa7fc4371eb` lists 10
authors. Excluding `github-actions[bot]` gives 9 (this count includes
`dependabot[bot]`, as the v2026.916.0 notes did).

Paperclip Cloud changes in the range (#15314, #15340) stay out of these
notes. The notes do not cite them today, and this change does not add
them.

**Suggested fix**

Change the version in the H1 and the intro paragraph to `v2026.1012.0`,
change the Released line to `2026-10-12`, and change the contributor
count to 9. Change nothing else.

## What Changed

- Line 1: `# Paperclip v2026.1009.0` → `# Paperclip v2026.1012.0`.
- Line 3: `> Released: 2026-10-09` → `> Released: 2026-10-12`.
- Line 5: the intro paragraph now starts `Paperclip v2026.1012.0 carries
130 commits`.
- Contributors: `from 8 contributors` → `from 9 contributors`.
- No other lines changed. The 130-commit count, the cited PR numbers,
the `0294`–`0305` migration range, the environment defaults, and the
external handles were already correct.

## Verification

- Docs only. `scripts/release.sh stable --print-version --date
2026-10-12` on `master` prints `2026.1012.0`, which matches the new
header.
- `git rev-list --count
v2026.1005.0..22a3ea3414e9039a538fbb0374b3cfa7fc4371eb` is 130, which
matches the notes.
- All 89 PR numbers cited in the notes are in that range. The 40 uncited
in-range PRs are 23 Dependabot bumps, one lockfile refresh, six
test-only changes, five release-notes and contributor-docs changes, one
CODEOWNERS change, two evals changes, one release-smoke test change, and
two Paperclip Cloud changes (#15314, #15340).
- Migrations `0294`–`0305` match `packages/db/src/migrations` in the
range. `0298` is the only migration that updates existing rows.
- Defaults were read at the beta source: `--listen-port` defaults to
43127 in `paperclip-runnerd.rs`; silent-run thresholds are 5 and 15
minutes in the sandbox runtime; remote Codex accepts `0.149.0` up to but
excluding `0.161.0` in `codex-runtime-compatibility.ts`; pins are Codex
`0.160.0`, Claude Agent SDK `0.3.286`, OpenCode `1.18.34`; Sonnet 5.5
needs Claude Code `2.1.284` or later.
- `git shortlog -sn` over the range gives 9 contributors excluding
`github-actions[bot]`. The external handles are `@baozdemir`,
`@valentinpalkovic`, and `@abderbejaoui`, which the notes already list.
- `git diff --stat` shows one file, 4 insertions, 4 deletions.

## Risks

Low. Documentation only. This must merge before the stable dispatch,
because the stable job pins the `master` revision of this file at
dispatch time.

## Model Used

Anthropic Claude Fable 5.1 (`claude-fable-5-1`) 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 (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 (docs 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 (running)
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
(running)
- [x] I will address all Greptile and reviewer comments before
requesting merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

releases/beta/v2026.1006.0-beta.0.md

@@ -1,8 +1,8 @@
-# Paperclip v2026.1009.0
+# Paperclip v2026.1012.0
 
-> Released: 2026-10-09
+> Released: 2026-10-12
 
-Paperclip v2026.1009.0 carries 130 commits, promoted from `2026.1006.0-beta.0`. The headline is that outside assistants can now join your team: Claude Code, Codex, OpenCode, and any MCP client can connect to Paperclip as a signed-in person, review work, and delegate tasks, all behind an experimental setting. Around that: Chat leads the navigation with each agent's tasks and artifacts beside the conversation, the Connections catalog pulls in accounts you already linked in Composio and Arcade, connections carry usage instructions that reach your agents automatically, Claude Sonnet 5.5 and GPT-6.1 Sol arrive with refreshed harnesses, and agents can safely update company skills. Underneath, Codex runs survive server restarts and model-capacity errors, workspace restore locks move to crash-safe SQLite file locks, and default agent instructions shrink to a fraction of their former size.
+Paperclip v2026.1012.0 carries 130 commits, promoted from `2026.1006.0-beta.0`. The headline is that outside assistants can now join your team: Claude Code, Codex, OpenCode, and any MCP client can connect to Paperclip as a signed-in person, review work, and delegate tasks, all behind an experimental setting. Around that: Chat leads the navigation with each agent's tasks and artifacts beside the conversation, the Connections catalog pulls in accounts you already linked in Composio and Arcade, connections carry usage instructions that reach your agents automatically, Claude Sonnet 5.5 and GPT-6.1 Sol arrive with refreshed harnesses, and agents can safely update company skills. Underneath, Codex runs survive server restarts and model-capacity errors, workspace restore locks move to crash-safe SQLite file locks, and default agent instructions shrink to a fraction of their former size.
 
 ## Breaking Changes
 
@@ -46,6 +46,6 @@ Paperclip v2026.1009.0 carries 130 commits, promoted from `2026.1006.0-beta.0`.
 
 ## Contributors
 
-This release has 130 commits from 8 contributors. Thank you to everyone who contributed to this release!
+This release has 130 commits from 9 contributors. Thank you to everyone who contributed to this release!
 
 @baozdemir, @valentinpalkovic, @abderbejaoui