diff --git a/devlog/_plan/260815_old_draft_triage/020_execution.md b/devlog/_plan/260815_old_draft_triage/020_execution.md
index 4248e60116..18683b41fa 100644
--- a/devlog/_plan/260815_old_draft_triage/020_execution.md
+++ b/devlog/_plan/260815_old_draft_triage/020_execution.md
@@ -52,5 +52,9 @@ Repairs:
  
 ## Execution log
  
+- wp2 (light six): #1744 merged (dev 656376fc6); source PRs #1664 #1669 #1660 #1652 #1165 #1644 closed with attribution comments. 8 KEEP-DRAFT comments posted. lidge @ b05c4942: 12259 pass / 0 fail.
+- wp2b (heavy four): repair workers rebuilt all four; repair reviewer 3 rounds (native fidelity FAIL -> reworked and sentinel-probed; pacing runtime+reconciliation fixed; exact-model Chat auth added; runTurn pacing-rejection containment fixed; flight-authority defect a65bfc0df caught by suite and root-caused). Four-way integration with 5 composition requirements verified. Landed via #1752 (dev 9ed2e8459): #1521 #1584 #1569 #1655 closed with attribution comments. lidge @ a65bfc0df: 12336 pass / 11 skip / 0 fail, all gates OK.
+- Collision note: a parallel maintainer session absorbed the devlog docs (#1745), fixed mcode client-inventory fallout (#1749), and integrated the same repair branches on its own (unpushed) int/260815-heavy; my reviewed int/260815-heavy-final landed first via #1752.
+ 
 (pending)
  
diff --git a/devlog/_plan/260815_old_draft_triage/030_release_readiness.md b/devlog/_plan/260815_old_draft_triage/030_release_readiness.md
index 489d660854..7bad0091fa 100644
--- a/devlog/_plan/260815_old_draft_triage/030_release_readiness.md
+++ b/devlog/_plan/260815_old_draft_triage/030_release_readiness.md
@@ -1,3 +1,38 @@
-# 030 - Release-readiness record (wp5)
+# 030 - Release-readiness record (wp3)
+ 
+Snapshot: 2026-08-15, dev tip b5bf24fe7 (subject to fleet movement).
+ 
+## Audit findings (readiness auditor, GO-WITH-FIXES, 2 blockers)
+ 
+1. Exact-tip CI evidence kept resetting as dev moved; the only real failure in
+   the window was 656376fc6 (4 stale GUI client-inventory assertions, fallout
+   from the #1744 MiniMax landing) - repaired by #1749, green at 31872155114.
+2. scripts/release.ts SemVer guard fail-open (unresolved #1753 finding):
+   compareReleaseVersions produced NaN on build-metadata cores
+   (2.19.3+build.1), passing any candidate. Fixed in #1757 (strict SemVer
+   parse, build metadata ignored for precedence, fail-closed throw; 3
+   regression tests; release-helper suite 13/13). NOTE: release automation
+   change - flagged for the explicit security review MAINTAINERS.md requires.
+ 
+## Verified green
+ 
+- OIDC release pipeline: last release run 31855514468 on main 161c09f60
+  published v2.19.0 with signed provenance; npm latest = 2.19.0. Healthy.
+- audit:high (root+gui): no vulnerabilities (also re-run in the lidge gate).
+- Dependency/workflow hygiene: #1738 cleaned orphaned workflow identities.
+- lidge full gates @ 9ed2e8459 (post-#1752 tree): 12347 tests, 0 fail.
+- lidge full gates @ b5bf24fe7 (final tip incl. #1757): (pending at write time;
+  see final report).
+ 
+## Version-line state (for the release decision - NOT executed)
+ 
+- dev package.json 2.18.0; v2.18.2/v2.19.0 are main-only release commits.
+- Next sensible feature release: 2.20.0 (2.19.1 also legal; 2.19.0 collides).
+- No release/publish/tag/main-promotion was performed in this loop.
+ 
+## Remaining before a release cut
+ 
+- Exact-tip Cross-platform CI green on the chosen release candidate SHA.
+- Service lifecycle runs on the version-bump commit (helper waits for it).
+- Maintainer security approval for the final scripts/release.ts state (#1757).
  
-(pending)