Skip to content

BUG_REPORT.md

Latest commit

 

History

History
46 lines (31 loc) · 1.51 KB

BUG_REPORT.md

File metadata and controls

46 lines (31 loc) · 1.51 KB

BUG REPORT guIDE Session Audit

WORKING ORDER: Chronological, 1 through N. No skipping. No scattering. Fix in order, verify in order.

CHECK OFF AS YOU GO!!!!* CRITICAL CHECK OFF AS YOU FUCKING FIX THEM!>

Log file: %APPDATA%\guide-ide\logs\guide-main.log Session started: fresh previous bugs cleared, log wiped Log reviewed by agent: not yet (run a fresh test first)

RULES FOR USING THIS FILE

  1. Every bug gets a number. Numbers are assigned IN ORDER based on severity/discovery.
  2. Agent reads the log FIRST before assigning bugs or discussing anything.
  3. User provides front-end observations (screenshots, behavior descriptions).
  4. Agent provides backend evidence (log lines, function names, exact cause).
  5. No fix is "done" until it is checked off HERE.
  6. No skipping ahead. No fixing #5 before #3.
  7. If a fix is uncertain (not verified), mark as NEEDS VERIFY, not FIXED.
  8. Agent NEVER says "done" without proof. A feature is real and functional, or it is not done.

HOW THIS SESSION WORKS

  1. User rebuilds the app
  2. User runs through GAUNTLET.md test script
  3. User reports front-end observations (what they see, screenshots)
  4. Agent reads the fresh log from %APPDATA%\guide-ide\logs\guide-main.log
  5. Agent populates this file with numbered bugs, evidence, root cause, fix plan
  6. User approves fix plan
  7. Agent implements, checks off, moves to next IN ORDER

BUG LIST

(empty awaiting fresh test session)

FIX LOG

(empty no fixes this session yet)