Note the two findings worth carrying forward: a missing capability has
now surfaced as a silent no-op twice, and three profile fields were
collected for a path that never read them.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three fixes with provable root causes, and two defects left open on
purpose. The double reply bubble and the missing plugin images each have
two plausible causes in our own code, and picking one without evidence
would produce a fix that holds until a different conversation path hits
the other. Record both candidate chains, the frame trace added to settle
them, and the fact that the bubbles collapsing at the end is only the
session filter hiding an orphan that is still in state and in SQLite.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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>
The R1 and R2 batches were recorded as gate-verified, but the Tauri
release build and the Playwright suite had never been run against them.
Both were executed here and pass, together with the rest of the stage
gate. Record the measured numbers rather than the previously estimated
ones, and name every step that still needs a live AstrBot container.
F-04 is now verified at the packaging level: the production CSP
containing blob: is present in the release binary. Dev builds do not
inject the CSP, so this was the only automated evidence available for
it; rendering an actual attachment remains a manual step.
Also record two things this run surfaced. Prettier reports 25 files
repo-wide, not the 20 previously written down, and the Playwright 680px
case passes only because that viewport sits exactly on the second CSS
breakpoint, leaving the 681px to 900px icon-only band untested and
without accessible nav labels. The latter is tracked as F-62.
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.