An audit of the destroy→hide change across four lenses raised 17
findings; 14 survived adversarial verification. Two of them were
regressions that change introduced, and both had the same shape: code
that only worked because the pet window used to not exist.
show_pet_context_menu picked the pet window and fell back to main.
While the pet rendered inside the app its window had been destroyed at
startup, so the fallback happened to select the visible main window.
Now that the window merely hides, the menu was being anchored to a
hidden HWND, which Win32 cannot bring to the foreground. The
visibility test is explicit now rather than incidental.
DesktopPetView read the connection state in a mount effect and nothing
emitted connection events, so destroy-and-rebuild was what re-read it.
Without a remount the floating pet showed whatever was true at startup
for the rest of the session. reveal_pet_window now emits
pet-window-revealed and the view re-reads on it.
The rest were already there. Every pet setting was decorative: the
preferences were applied and then dropped, so reveal_pet_window had to
invent an answer and hard-coded the first monitor, the safe edge and
always-on-top — reverting the user's choices on every show. The pet view
re-sent a fully hard-coded payload whenever game mode toggled, and the
settings page initialised its controls from literals, so returning to
the page and changing one thing pushed three stale defaults back onto
the window. There is a session-scoped store now, a command to read it,
and both frontends read before they write. Persisting it across restarts
is F-75.
Always-on-top is off by default, which is what the Q6 acceptance
criterion asked for (F-35), and the window no longer takes focus when
shown — it was activating on show and swallowing keystrokes meant for
the main window. focusable is left alone on purpose: clearing it adds
WS_EX_NOACTIVATE, which would re-break the context menu now anchored to
that window. That is F-79.
The pet also painted a solid dark rectangle before its assets arrived.
The transparency rule is gated on a class that an effect inside the
5.2 MB lazy chunk added, so until that chunk ran the app's opaque
background won. This is why the earlier hunt for "the rule that beats
!important" found nothing: the class was not applied yet, so specificity
was never the question. The pet now has its own entry document carrying
the class statically. An inline script would not do — tauri-utils only
nonces script[src^='http'], so it would pass in dev and be blocked by
script-src 'self' in a release build.
Rust tests 92 → 97, frontend 30 → 35. All 11 mutations of the new
assertions were confirmed to fail.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The queue recorded N-11's cause as "the rebuild path never called
show()". That was a real code defect and it is fixed, but it was not
this symptom — the pet still did not appear after it. The live log
showed the rebuild path failing outright before the reveal step, so the
record now states that and names the fix that actually worked. The two
root causes I proposed and retracted are kept as their own row, since
"tried and disproved" is worth more to the next reader than a clean
record.
Also formats the queue with prettier, which reflows three tables. One
hunk of that reflow was reverted by hand: a continuation line began
with "+" meaning "and", and prettier normalised it into a nested list
item, turning half a sentence into a bullet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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>
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.