docs: record native progress browser acceptance

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/plans/2026-10-24-recurring-server-sleep-stack.md

@@ -1722,7 +1722,8 @@ Latest-head remote gates and parent failures remain open.
 
 ## Slice 29: native chat progress implementation
 
-Branch `codex/sleep-29-native-chat-progress`, parent #17606 at `ed76256b97`.
+PR [#17639](https://github.com/paperclipai/paperclip/pull/17639), branch
+`codex/sleep-29-native-chat-progress`, parent #17606 at `ed76256b97`.
 Native event producers and existing eligibility notifications now wake a scoped
 worker. Progress leaves the chat timer; retained history becomes quiet. The
 worker retains only unfinished batches, concrete lock contention and failures.
@@ -1732,7 +1733,7 @@ coverage, cursor precision repair, authorization boundaries and retained failure
 Forty-four focused native-progress cases pass, as do 13 app coordinator cases and
 the server build/typecheck. All 16 browser chat cases pass before the final
 base-publication hook. The hook fixes a reproduced commit-order wake gap; its
-19 worker and 13 coordinator cases pass. Final browser acceptance and
-publication/checks are pending.
+19 worker and 13 coordinator cases pass. A second fresh browser run passes all
+16 cases at `bcf2f38ff5`; final typecheck passes too. Remote checks/review are pending.
 Parent #17606 now has passing checks and Greptile 5/5 on `ed76256b97`; all three
 review threads are resolved. This is not completion of the broader stack.

doc/plans/2026-10-25-native-chat-progress-sleep-audit.md

@@ -1,8 +1,9 @@
 # Native chat progress: sleep migration audit
 
 Parent: #17606 at `ed76256b979541b962fa784016a550c32920d670`.
-Branch: `codex/sleep-29-native-chat-progress`.
-Status: implementation and focused PostgreSQL acceptance complete; remote acceptance pending; browser acceptance passed before the final base-publication hook. This is not a deployed sleep claim.
+Branch: `codex/sleep-29-native-chat-progress`. PR: #17639.
+Status: implementation, focused PostgreSQL acceptance, and browser acceptance
+complete; exact-head remote checks and review pending. This is not a deployed sleep claim.
 
 ## Duty and owner
 
@@ -123,7 +124,10 @@ and an eligible later event. A query-count guard bounds failure of the old code.
   cases pass after the lifecycle producer signals native progress.
 - Browser acceptance: all 16 `agent-chat-projects.spec.ts` cases pass, log
   `/tmp/sleep29-app-e2e.log`, fresh isolated database, port 32659. This run
-  precedes the final base-publication hook; a final run remains pending.
+  precedes the final base-publication hook. `/tmp/sleep29-final-e2e.log` then
+  passes all 16 cases at committed implementation `bcf2f38ff5` with a second
+  fresh isolated database. `/tmp/sleep29-final-typecheck.log` also passes with
+  the final hook. No retries were needed in either browser run.
 
 PostgreSQL is external and isolated because embedded PostgreSQL is unavailable
 on this host. Worker fixtures clean their own companies. The reused chat fixture
@@ -137,8 +141,7 @@ are controlled fixtures, not live Slack/Telegram/Discord accounts.
 Process-local notifications retain the single active writer model. Independent
 SQL writers and other processes need a wake integration. No Cloud sleep gate or
 external alarm coverage changes here. An internal deadline cannot wake stopped
-compute. Browser acceptance, exact-head CI, and review remain required before
-this slice is ready. The whole stack remains unmerged.
+compute. Exact-head CI and review remain required before this slice is ready. The whole stack remains unmerged.
 
 Fetched master is `19ec787e5b` (not replayed into this stack yet). Newly landed
 #17616 expands native-harness backup expiration to continuity/quarantine evidence