Update the investigate skill to reflect that render mode now executes
JavaScript and exposes more debug surface, and harden it for parallel runs:
- Use --dump-computed/--dump-cascade for CSS evidence; capture stderr to
{stem}.console.txt so script errors and console output are recorded.
- Add a JavaScript finding category and guidance: report script errors and
engine gaps that break rendering, distinguish them from genuinely
out-of-scope runtime capabilities.
- Replace the stale "we don't execute JS" rule; note that empty-in-static
content is no longer automatically expected.
- Accurate tall-page guidance, targeted-read + cross-validation, severity
rubric, Suggested-fix field, and a portable mkdir-based lock around the
shared sites.txt registry.
Engine: log_script_error now takes a dump_dir instead of writing to a fixed
/tmp/rust_browser_failed_script_<label>.js path. Render mode dumps failing
scripts into its per-run output dir as failed-script-<label>.js (per-run
isolated, no cross-run collisions); the interactive browser passes None and
relies on the logged snippet. Adds a regression test.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Zachary D. Rowitsch
1f98c7fc76