drive-by: rebaseline log snapshot to be more resilient

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Prompt update**
> - Refines `development_workflow` step 3 to require asking the user to
interact after adding `console.log` statements so logs actually execute.
> 
> **Test snapshots**
> - Updates snapshots in `local_agent_basic.spec` and
`local_agent_auto.spec` to reflect the new prompt text.
> - Makes `local_agent_read_logs.spec` more resilient by matching
`/LOGSReading \d+ logs/` instead of a fixed count.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
d8191976a120e32f850e47f7b5be8e843684fd6b. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Improves the local agent’s debugging handoff by updating the system
prompt to ask the user to interact with the app after adding console.log
statements, so logs appear only when code paths execute. Rebaselines e2e
snapshots and makes the log-reading check resilient to varying log
counts.

- **Refactors**
- Clarified debugging step in the system prompt: after adding logs,
request user interaction to trigger execution.
- Updated e2e snapshots; replaced fixed “Reading 1 logs” with a regex to
handle dynamic counts.

<sup>Written for commit d8191976a120e32f850e47f7b5be8e843684fd6b.
Summary will update on new commits.</sup>

<!-- End of auto-generated description by cubic. -->