release: 1.37.9

README.md

@@ -16,7 +16,7 @@ See what needs attention, resume the right conversation, and work on a paired PC
 
 </div>
 
-> **Candidate documentation:** this branch contains the unreleased **1.37.9 reliability candidate**, including confirmed session renames and task conflict protection. The [published releases](https://github.com/writingdeveloper/devdeck/releases/latest), not this version number or a green build, determine what users can install. Use matching updated builds on both machines for the new write protocol. See [the candidate review](docs/quality-review-2026-09-08.md) and [session synchronization review](docs/session-sync-review-2026-09-08.md).
+> **1.37.9** adds confirmed session renames and task conflict protection ([release notes](docs/releases/1.37.9.md)). Use 1.37.9 on both machines for the new write protocol. See [the maintenance review](docs/quality-review-2026-09-08.md) and [session synchronization review](docs/session-sync-review-2026-09-08.md).
 
 <div align="center">
 <img src="docs/screenshots/projects.png" width="820" alt="DevDeck project overview with repository and session navigation" />
@@ -83,7 +83,7 @@ Both machines must be reachable, for example on the same LAN, through an existin
 | Application settings | Belong to the PC whose Settings screen you are using. |
 | Terminal screen | The host provides bounded recent output for reconstruction, not an unlimited durable archive. |
 
-**Compatibility:** confirmed titles and task editing need compatible 1.37.9-or-newer builds on both ends. During candidate testing, use the same build, not an earlier candidate with the same version number. The app checks title-version support and refuses unversioned writes rather than silently treating a viewer-only rename as shared success. Titles of disconnected or ended sessions cannot be remotely committed.
+**Compatibility:** confirmed titles and task editing need compatible 1.37.9-or-newer builds on both ends. The app checks title-version support and refuses unversioned writes rather than silently treating a viewer-only rename as shared success. Titles of disconnected or ended sessions cannot be remotely committed.
 
 Reconnecting reads the host's current title; it must not send an old cached title back. Clearing a custom title is an explicit change to the default project name, not an invitation to restore the old name. See [state ownership and consistency](docs/state-consistency.md) for the implementation contract and remaining gaps.
 

docs/README.md

@@ -6,7 +6,7 @@ The README describes the product. This directory separates current operating gui
 | --- | --- |
 | [Quality and release checks](quality.md) | Required commands, isolated QA, release gates, evidence rules |
 | [Privacy and network boundaries](privacy.md) | Local processing, optional AI calls, Link transport, diagnostics |
-| [Maintenance review: 2026-09-08](quality-review-2026-09-08.md) | Changes in the 1.37.9 candidate and verification status |
+| [Maintenance review: 2026-09-08](quality-review-2026-09-08.md) | Changes in 1.37.9 and verification status |
 | [State ownership and consistency](state-consistency.md) | Shared metadata contracts, identity, failure and synchronization rules |
 | [Session synchronization review](session-sync-review-2026-09-08.md) | Reproduced title bug, root fixes and multi-app evidence |
 | [Backlog](backlog.md) | Unfinished work, priority and acceptance criteria |

docs/backlog.md

@@ -1,6 +1,6 @@
 # Prioritized backlog
 
-Updated 2026-09-08. The 1.37.9 maintenance candidate is not a published release. Implementation and evidence: [review](quality-review-2026-09-08.md).
+Updated 2026-09-08. The 1.37.9 maintenance work was released on 2026-10-15. Implementation and evidence: [review](quality-review-2026-09-08.md).
 
 | Priority | Work | Acceptance criteria |
 | --- | --- | --- |
@@ -15,7 +15,7 @@ Updated 2026-09-08. The 1.37.9 maintenance candidate is not a published release.
 | P2 | Note concurrency | Notes remain last-write-wins across devices; add revision checks while preserving drafts |
 | P2 | Focused module extraction | Terminal lifecycle/rendering boundaries protected by regression tests; no rewrite solely for file length |
 
-## Implemented in the candidate
+## Implemented in 1.37.9
 
 Revision-checked task writes, legacy refusal, conflict review with retained attempted change, settings save rollback and inline validation, js-yaml/Vitest advisory fixes, Node24 CI, maintenance regression gates, fail-closed performance preconditions, and current documentation/maintenance configuration. See the candidate review for evidence and limits.
 

docs/quality-review-2026-09-08.md

@@ -1,6 +1,6 @@
 # Maintenance review — 2026-09-08
 
-Status: **1.37.9 candidate, not released**. Baseline: `83b27b3` / 1.37.7. Branch: `fix/reliability-docs-20260908`.
+Status: **released as 1.37.9** on 2026-10-15 ([notes](releases/1.37.9.md)). Baseline: `83b27b3` / 1.37.7. Branch: `fix/reliability-docs-20260908`.
 
 ## Fixed and checked
 
@@ -27,6 +27,7 @@ Performance QA refuses absent/invisible terminals, missing CPU measurements, inc
 | Actual Windows unpacked executable (built as the 1.37.9 candidate, before renumbering) | Maintenance 5/5 and resilience 9/9 passed, normal exit |
 | Current documentation checks | 8 documents, 21 local links and script/CI assertions passed |
 | Initial candidate all-OS CI and packaging | CI `34315556132` and Release dry-run `34315556248` passed at `24e3eb7`; publication skipped (PR, no tag) |
+| Merged with 1.37.8 and the project-list fix (2026-10-15) | 1,321 unit tests passed; all-OS CI and packaging passed on `5b520a7`. The full-tree advisory gate is high and the shipped-dependency gate moderate: electron-builder and Vitest carry moderate advisories with no fixed release |
 | Human visual acceptance, installer wizard, extended real network testing | Not performed by this review |
 
 Evidence locations: `qa/shots/maintenance/`, `qa/shots/resilience/`, and CI artifacts. Full logs stay local/attached, not committed. Tests use disposable profiles and synthetic tasks. Autostart and paid-summary settings are tested only on the failing-save path, before any operating-system/provider side effect; QA does not enable them.

docs/releases/1.37.9.md

@@ -0,0 +1,8 @@
+# DevDeck 1.37.9
+
+- Settings are applied only after they are saved. A failed save restores the previous value and shows an error instead of looking applied. Threshold fields reject values that are not ordered, positive whole days.
+- Task lists are saved with a revision. If another window or PC changed the list first, nothing is overwritten: the current list is shown and your attempted change is kept for review.
+- Session titles renamed from another PC are confirmed by the host before they show as saved. Titles of disconnected or ended sessions are not changed remotely.
+- Opening Projects right after a reboot no longer piles up work. When the screen gave up on a slow project list and asked again, the earlier scan kept running alongside the new one; requests now share the scan in progress. Scans slower than 20 seconds log how long each step took.
+
+Task editing and confirmed titles across PCs need 1.37.9 on both ends. A 1.37.9 host refuses task saves from older viewers with an update message rather than accepting writes it cannot check. Notes remain last-write-wins.

docs/session-sync-review-2026-09-08.md

@@ -1,6 +1,6 @@
 # Session title synchronization: 2026-09-08
 
-Status: implemented in the unreleased 1.37.9 candidate on PR #33. This review extends the [earlier maintenance pass](quality-review-2026-09-08.md); it is not evidence that the installed/public 1.37.7 application has been replaced.
+Status: released in 1.37.9 (PR #33, 2026-10-15). This review extends the [earlier maintenance pass](quality-review-2026-09-08.md).
 
 ## Reproduced defect
 

docs/state-consistency.md

@@ -1,6 +1,6 @@
 # State ownership and consistency
 
-This is the implementation/review contract for the 1.37.9 candidate. It is not a claim that every mutable field has already migrated to one state framework.
+This is the implementation/review contract for 1.37.9. It is not a claim that every mutable field has already migrated to one state framework.
 
 ## Why locally correct code still failed in use