| name | electron-debug |
| description | Use when an Electron failure or confirmed review finding can be reproduced and needs root-cause analysis, a minimal fix, and regression verification. Do not use for speculative cleanup, broad refactoring, initial review, or masking failures by weakening safeguards. |
Electron Debug
Prove the root cause before changing production behavior.
- Read the sidecar handoff when present, review finding, matching track/task,
logs, and
references/debug-playbook.md.
- Reproduce the original symptom and capture environment, process, exact input, and raw error without sensitive payloads.
- Classify main, preload, renderer, utility/worker, native module, packaging, update, CI, or platform integration.
- Trace backward across boundaries; form one falsifiable hypothesis at a time and gather discriminating evidence.
- Write a failing regression test/reproducer, observe the intended failure, then apply the smallest fix.
- Run targeted and broader verification, applicable security checks, and remove temporary instrumentation.
- Reopen or advance the affected lane task and record cause, Red/Green
evidence, residual risk, and review conclusion in its Evidence, Review,
and Result sections.
Never substitute fixed sleeps, swallowed errors, disabled tests, dependency-wide upgrades, or weakened Electron security for a root-cause fix.
