Fix lossless reads, typed conflicts, agent recovery and nightly portability

.agents/pm/chores/pm-dvwm.toon

@@ -6,7 +6,7 @@ status: open
 priority: 3
 tags[5]: "area:docs",code-quality,docstrings,maintainability,token-efficiency
 created_at: "2026-07-19T04:07:16.881Z"
-updated_at: "2026-10-04T04:00:37.844Z"
+updated_at: "2026-10-06T14:21:38.068Z"
 author: maintainer-agent
 estimated_minutes: 240
 acceptance_criteria: "Census script or lint rule flags the known filler templates (Implements X for the public runtime surface of this module; Value that configures or reports X for this contract; Provides CLI runtime support for X; payload exchanged by command, SDK, and package integrations) and the count is ratcheted down, not up; Touched-file burn-down policy documented so gate-mandated docstrings added going forward must carry real information (what the value means, units, invariants) or use @inheritDoc/type-level docs; Static-gate docstring coverage stays at 100 percent throughout - the fix is content quality, never coverage relaxation"
@@ -48,7 +48,7 @@ dependencies[7]:
     author: "harness:codex"
     source_kind: "cli:update:dep"
     author_source: detected
-comments[16]:
+comments[18]:
   - created_at: "2026-09-13T16:15:21.639Z"
     author: "harness:codex"
     text: "Continuation observation: runtime-contracts.ts still contains generic interface/member filler despite coverage gates. The command-discovery tranche improves the modified module and function documentation with concrete visibility and assembly semantics, but does not implement the repository-wide filler census or ratchet owned here. Reuse this canonical owner for that remaining work; no duplicate item created."
@@ -98,6 +98,12 @@ comments[16]:
   - created_at: "2026-10-04T04:00:37.844Z"
     author: "harness:codex"
     text: "Scoped continuation: current evidence-consistency delivery replaces the touched Commander recovery-owner filler comment with concrete runtime and workspace semantics and documents the new bounded recheck helper. The supported AST census now reports 4131 filler entries in 204 of 763 maintained files; its reviewed ceiling decreases from 12 to 11 for commander-usage.ts and no ceiling increases. Broader semantic documentation debt remains open under this existing owner. Presence coverage is a separate metric; no duplicate chore or additional in-progress claim was created."
+  - created_at: "2026-10-06T10:11:01.836Z"
+    author: "harness:codex"
+    text: "Current continuation observation: the supported AST docstring gate passes and reports 4,130 legacy filler entries in 204 of 764 maintained source files. The new existing-item error discriminator, guard, context coordinates and focused SDK documentation use semantic contracts. Broader semantic replacement remains open under this canonical owner; this pass introduces no duplicate chore or additional in-progress claim, and presence coverage is not claimed to certify all documentation quality."
+  - created_at: "2026-10-06T14:21:38.067Z"
+    author: "harness:codex"
+    text: "PR1416 review documentation observation: added semantic contracts to required-create policy, canonical scalar recovery examples, honest empty required collections and non-interactive guidance handling. CodeRabbit now reports its separate diff-callable metric 86.36 percent across 22 functions, while the mandatory repository source/export/member presence and filler-ratchet gates pass unchanged. These are different denominators; neither metric proves universally meaningful documentation. The existing canonical semantic-replacement owner and remaining 4,130 filler entries in 204 of 764 maintained-source files remain open. No filler baseline or documentation threshold was relaxed, and no duplicate chore is created."
 files[10]{path,scope,note}:
   packages/pm-guide-shell/extensions/guide-shell/runtime.ts,project,Semantic contracts for every named callable in the reviewed module
   scripts/release/docstring-quality-baseline.json,project,File-level filler debt cannot grow or retain stale headroom

.agents/pm/chores/pm-pj2isb.toon

@@ -6,7 +6,7 @@ status: open
 priority: 2
 tags[6]: data-quality,governance,metadata,normalization,relevance,tracker-governance
 created_at: "2026-07-26T10:59:12.234Z"
-updated_at: "2026-10-02T18:38:05.708Z"
+updated_at: "2026-10-06T11:54:16.103Z"
 author: "harness:claude-code"
 estimated_minutes: 420
 acceptance_criteria: "Every field dominated by a repeated literal is classified: the value is either replaced with a recoverable fact, cleared so the field is honestly empty, or retained with a recorded rationale that says explicitly it is an archival marker rather than an observation; Clearing and reclassification are ordinary history-recorded mutations, so the original values stay recoverable and the change is explainable; A validation surface reports fields whose values are dominated by a single literal beyond a declared threshold, so this condition is detectable in future rather than discovered by census; Completeness reporting distinguishes a field that is populated from a field that is populated with distinct meaningful values; The relevance engine's signal set is checked against the result, so no scoring signal depends on a field the pass emptied or reclassified; The pass runs under the release-attribution protocol so it produces no unintended changelog movement"
@@ -31,7 +31,8 @@ dependencies[10]{id,kind,created_at}:
   pm-pww8ax,related,"2026-07-26T10:59:12.234Z"
   pm-w7ccmv,verifies,"2026-07-26T10:59:12.234Z"
   pm-wenq,related,"2026-07-26T10:59:12.234Z"
-comments[2]{created_at,author,text}:
+comments[3]{created_at,author,text}:
   "2026-07-29T04:34:56.161Z","harness:claude-code","Measured 2026-07-29: the placeholder block has a lifecycle consequence that was not previously recorded. Sixteen closed items carry no close_reason and validate warns on all of them, and every one of those sixteen carries the placeholder resolution sentence Resolution normalized from closed status because the field was missing or low-signal, plus the matching actual_result placeholder. Two further items in the same warning set - pm-7vm9 and pm-qa2h - carry real recorded resolutions describing what actually shipped, and their close_reason was backfilled honestly from that record today, dropping the count from 18 to 16. The split is exact: where a real resolution exists the missing close_reason is recoverable from the tracker itself, and where the placeholder sentence sits there the record contains nothing to recover from. The normalization sweep that wrote those sentences therefore did more than add noise to relevance scoring - it consumed the only field that could have told a later reader whether the closure evidence was ever captured, and it did so in a way that is indistinguishable from a genuine one-line resolution to every consumer except a literal string match. Any future normalization must write a value that is machine-distinguishable from an authored one."
   "2026-10-02T18:38:05.708Z","harness:codex","Current evidence 2026-10-02: validate --check-resolution --check-history-drift reads all 2863 records with zero missing/unreadable streams, hash/chain/version/workspace-state mismatches or drift. It checks 2551 closed items and warns on 170 missing structured resolution fields. This extends the existing historical evidence-quality census; the two current delivery closures contain explicit resolution, expected and actual values. No placeholder backfill or guessed historical claim was written. This owner remains open and unclaimed for evidence-derived cleanup, and passing integrity is not represented as complete historical resolution metadata."
+  "2026-10-06T11:54:16.103Z","harness:codex","Current evidence 2026-10-06: full validation reads 2898 records with zero history drift, storage duplicates, unreadable streams, hash/chain/version mismatches or workspace-state drift. It checks 2583 closed items and still warns on the same 170 historical missing structured resolution fields. The three new delivery closures have explicit resolution, expected and actual values in their immutable close events. This updates the existing census; no placeholder backfill, duplicate cleanup item or guessed historical observation is introduced. Integrity admission passes separately from this outstanding metadata-quality warning."
 body: ""

.agents/pm/extensions/.managed-extensions.json

@@ -1,12 +1,12 @@
 {
   "version": 1,
-  "updated_at": "2026-10-06T06:59:48.643Z",
+  "updated_at": "2026-10-06T14:22:04.346Z",
   "entries": [
     {
       "name": "pm-changelog",
       "directory": "pm-changelog",
       "scope": "project",
-      "manifest_version": "2026.10.4",
+      "manifest_version": "2026.10.5",
       "manifest_entry": "./dist/extension.js",
       "capabilities": [
         "commands",
@@ -68,13 +68,13 @@
         "preflight_ownership": []
       },
       "installed_at": "2026-05-23T20:26:03.509Z",
-      "updated_at": "2026-10-04T14:09:26.630Z",
+      "updated_at": "2026-10-06T11:50:52.104Z",
       "source": {
         "kind": "npm",
         "input": "npm:pm-changelog",
         "location": "package",
         "package": "pm-changelog",
-        "version": "2026.10.4"
+        "version": "2026.10.5"
       }
     }
   ]