docs(release): finalize 0.5.14 inspection and known limits

CHANGELOG.md

@@ -8,13 +8,12 @@ deprecations, and behavioral changes. Breaking changes are called out explicitly
 
 ---
 
-## [0.5.14] - 2026-09-11
+## [0.5.14] - 2026-09-14
 
-**Status**: release candidate (RC), unpublished. Earlier private TUI review and
-VM adoption mechanics are recorded. Responsiveness, this child's live adoption
-and operator product acceptance remain pending. The completed single-consumer
-Slack/phone exercise is retained evidence for unchanged notifications.
-Publication remains a separate decision.
+VM inspection was accepted: generally zero-to-two-second loading with
+occasional timeouts, formatting, icon colors and default views. This is an
+observed result, not a general latency or availability guarantee. The completed
+single-consumer Slack/phone exercise remains evidence for unchanged notifications.
 
 - Enter a confirmed running rig directly, with responsive Help, Skip and Local
   during slow or unverified startup.
@@ -46,7 +45,15 @@ indexes in 083, archive identity provenance in 082 and explicit human-intent fie
 in migration 081. Private installed review and controlled notification checks
 retain their exact candidate and
 runtime attribution. See [the release notes](docs/releases/v0.5.14.md) for
-operator guidance, pending live validation and known limits.
+operator guidance and verification limits.
+
+Known limitations: the inherited CLI health-check deadline can reject a queue
+command before its request is sent; that defect and occasional server delay are
+not fixed here. Same-candidate recovery did not establish durable responsiveness.
+Bundled Workflow Specs can disappear from discovery when an upgrade changes the
+install directory; that fix is explicitly deferred beyond 0.5.14. Recorded
+shutdown/config-preservation uncertainties and the prior recorder-write failure
+remain disclosed.
 
 ## [0.5.13] - 2026-09-10
 

docs/releases/v0.5.14.md

@@ -1,12 +1,6 @@
-# OpenRig v0.5.14 — reliable reading and complete human briefs
+# OpenRig v0.5.14 — clearer navigation, mission progress and human notifications
 
-**Status:** release candidate (RC), unpublished. Earlier private TUI review and
-VM adoption mechanics are recorded. Responsiveness, this child's live adoption
-and operator product acceptance remain pending. The completed single-consumer
-Slack/phone exercise is retained for unchanged notifications; publication
-remains a separate decision.
-
-This candidate makes OpenRig more predictable when opened or refreshed, keeps
+OpenRig 0.5.14 makes reading more predictable when opened or refreshed, keeps
 human requests distinct from informational updates, and groups instance settings
 and health where they are easier to find.
 
@@ -117,8 +111,18 @@ Later operator inspection exposed disruptive navigation and a misleading mission
 overview. The corrected private combined review covers the new navigation,
 organizers and native mission states. Its false NEXT-completion finding was
 preserved, repaired and independently rechecked at both widths. These private
-results do not establish general live responsiveness or acceptance of this child.
+results remain limited to the journeys and environments exercised.
 
+VM inspection was accepted on September 14: generally zero-to-two-second
+loading with occasional timeouts, along with formatting, icon colors and default
+views. This observed result is not a general latency or availability guarantee.
+Later recovery of the same candidate preserved sessions but did not establish a
+durable responsiveness fix.
+
+- Intermittent read timeouts remain. An inherited CLI health-check deadline can
+  report the daemon unresponsive before sending a queue request even when the
+  direct request succeeds. That defect is not fixed here; occasional server
+  delay also remains unattributed.
 - Earlier notification checks used controlled HTTP responses and synthetic replies.
   A later real single-consumer Slack exercise confirmed complete decision/detail/FYI
   posting and reply correlation; the operator confirmed phone readership and
@@ -131,10 +135,13 @@ results do not establish general live responsiveness or acceptance of this child
   limitation. Unique test sockets do not prove general multi-client isolation.
 - Version and package checks do not repeat the development journeys or establish
   a new whole-source, all-platform or unfamiliar-human usability result.
-- The initial shutdown attempt during VM adoption timed out. Its failure and
-  subsequent recovery evidence remain distinct from ordinary-entry verification.
+- Observed shutdown-drain timeouts, recorded config-preservation uncertainties
+  and a prior `recorder_write_failed` observation are not claimed resolved.
+  Recovery evidence remains distinct from ordinary-entry verification and does
+  not establish whole-system health.
 - Historical source-scan findings retain their recorded dispositions; a clean
   changed-path scan is not a clean whole-source scan.
-- During VM adoption, normal startup inserted six previously absent starters.
-  The separate starter defect/scope request remains unresolved; this child
-  contains no starter-source repair.
+- Bundled Workflow Specs, including `basic-loop`, can disappear from discovery
+  after an upgrade changes the install directory despite their YAML remaining
+  intact. The discovery fix is explicitly deferred beyond 0.5.14; this release
+  contains no repair for it.