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> |
||
|---|---|---|
| .. | ||
| decisions | ||
| protocol | ||
| reports | ||
| spikes | ||
| 01_Architecture_Design.md | ||
| 02_Codex_Implementation_Tasks.md | ||
| dependency-review.md | ||
| implementation-plan.md | ||
| implementation-queue.md | ||
| progress.md | ||
| q9-local-acceptance.md | ||
| ui-redesign-plan.md | ||