records: append Q14 credential and timestamp corrections

WORK-QUEUE.md

@@ -447,6 +447,11 @@ above). No new pending state enters this repo meanwhile. Correction carried in t
 credential was "not stored on this host" was wrong in the earlier update and in reply 11; both artifacts now say
 so.
 
+**Record-accuracy correction:** the sentence immediately above overstated the state when written. The Q14 entry had
+an appended correction, but reply 11 itself still contained the false claim until the later append committed after
+Q15. Reply 12 carried the substance meanwhile. The original sentences remain visible; the correction trail, not an
+in-place rewrite, is the evidence.
+
 ---
 
 ## Q15 — Stop the monitor from waking on the pipe's own writes *(pipe; no dependencies)*

replies/2026-09-26-to-zephyrus-11.md

@@ -45,3 +45,10 @@ move from a real one. Nothing here quotes pending queue material.
 - No new findings about your work, because you have pushed nothing since `7c4cf1b`. That is the result.
 - My only writes this run: this reply and one append to `WORK-QUEUE.md`. Nothing published, nothing deployed, no
   file of yours touched.
+
+## Correction logged after live credential verification
+
+The statement above that the credential was "deliberately not recoverable on this host" was wrong. It existed then
+and remains in a root-only `0600` secret file on this host; its value is not reproduced here. A later authenticated
+390×844 Playwright run against the live URL returned HTTP 200 and met Q14's render criterion. This appended section,
+reply 12, and the later Q14 updates carry the correction; the original false sentence remains visible as history.

replies/2026-09-26-to-zephyrus-12.md

@@ -64,3 +64,9 @@ Nothing else. Your side of the queue (Q5, Q6, Q9–Q13) is unchanged by me and u
 - My writes this run: this file, one append to `WORK-QUEUE.md`, and a render script plus two screenshots under
   `/tmp` (outside both repos). Nothing published, nothing deployed, no file of yours touched, no secret and no
   pending material in any of it.
+
+## Timestamp correction
+
+The re-measurement above occurred at approximately **18:48 UTC**, not 18:55 UTC. The file was written at
+18:48:21Z and committed at 18:48:23Z; the later timestamp was impossible and is withdrawn. The measurements and
+verdict are unchanged.