Batch R3 (F-14 through F-19) is implemented and gate-verified. Record
what changed, the measured test counts, and the two things it did not
cover: auto_connect_configured_slots is still serial, and the
operations switch guard still has no production writer.
Also record that the new tests for F-14, F-15 and F-16 were each run
against a mutation restoring the old behaviour and each fails under it,
so they are known not to be tautological.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Commit 3d1d962 inserted an unreleased heading between the H1 and the
preamble without a blank line, so Markdown absorbed the "all notable
changes" preamble as a lazy continuation of a list item, and it also
prepended a UTF-8 BOM. Commit ceb7512 then inserted the 0.1.0-alpha.2
section directly under the H1, which is why the file began
mid-document, and indented the preamble to cement it inside the
bullet.
Restore the canonical order (title, preamble, single [Unreleased] with
one Added/Changed/Fixed/Security group, then the released section),
strip the BOM, and move the duplicate-optimistic-messages entry from
Changed to Fixed. Entry text is otherwise unchanged; the R1 and R2
Fixed groups were verified to be disjoint before merging. The file now
passes prettier --check.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds the 2026-07-26 full-source audit and the execution-ordered fix queue, and
records what actually happened when R1 and R2 were verified:
- R1 had never been compiled. The gate found a type error introduced by its own
`.nullish()` widening and a lint failure from a non-component export, plus one
acceptance test that was specified but never written.
- R2 landed F-10 through F-13, and an adversarial review of it surfaced three
defects the batch had itself introduced, all fixed in the same batch.
- The review subagents ran against the live working tree and left mutations
behind, including a deliberate duplicate POST inside the stream error path.
That injected code was briefly mistaken for a real HTTP-stack defect. It has
been removed and the process note recorded so review runs are isolated next
time.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add configuration-only auto-connect rules, runtime operations slot lock
while tasks are active, and duplicate server-instance warnings without
silent Profile merge. Surface policy status to the settings UI and cover
the new boundaries with Rust and Vitest checks.