提交图

5 提交

作者 SHA1 备注 提交日期
bc0948731c fix(astrbot): make the frame trace reachable by its documented filter
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
The event set an explicit target of astrbot::frame while the enabled!
guard used the default module-path target. A filter naming either one
therefore failed: naming the crate did not reach the event, and naming
the target left the guard returning false. Either way the trace emitted
nothing, which would have looked like the application producing no logs
at all and wasted a reproduction cycle.

Give the guard the same target, hoist it into a constant, and add a test
that drives the exact RUST_LOG value printed in the acceptance
instructions. The test was checked against the broken guard and fails
with empty output. A second test asserts the trace stays silent at the
default level, and both assert no payload text or attachment URL reaches
the log.

Document the capture procedure in the acceptance checklist.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:06:03 +08:00
178fba70ea docs(progress): record the R3 batch and its gate results
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
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>
2026-07-27 00:31:18 +08:00
1a18a8ac85 docs(acceptance): record r1/r2 gate closure and pending hardware steps
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
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>
2026-07-27 00:06:17 +08:00
f61f44021b chore(roadmap): sync roadmap status and acceptance gate 2026-07-22 03:09:35 +08:00
ceb7512bf2 feat(desktop): complete Q9 chat and stability increment
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
2026-07-21 14:43:14 +08:00