AGENTS.md:
- Rule 2 strengthened: U-Boot é compromisso firme com lista de tasks
- New Rule 10: GDB/GDB stub obrigatório em todos os testes (QEMU + HW)
- Architecture Reality Check: added ESP32+U-Boot entry
- Verification Workflow: completo com comandos GDB para cada target
docs/esp32-mcuboot-uboot-strategy.md:
- Chain B (U-Boot) agora é MANDATÓRIA para todos os targets
- Chain A é stepping stone de desenvolvimento apenas
- Chain C (bootstub) será eliminada
- Open decisions marcadas como resolvidas
- Tabela de viabilidade: Xtensa passou de 🔴 risky para 🟡 commitment
All uncommitted work from ESP32 GDB stub development session.
Includes:
- GDB stub (uos_gdbstub.c/.h/_entry.S)
- Startup vector table rewrite
- ESP32 HAL integration files
- Boot chain design docs
- AGENTS.md absolute rules (commit before refactor, no unauthorized changes)
- All prior deepseek session work
This commit prevents further data loss. No claims of correctness.
Major rewrite of TESTING_GUIDELINES.md based on audit of actual codebase:
Key corrections:
- uos-target.py is a target-definition validator, NOT a test orchestrator
- No in-kernel test harness exists (only inline smoke tests)
- No CI boot testing (only build verification)
- No kernel code coverage (only tool-level coverage)
- uos-cover tools ARE operational with 11 test files
New content:
- Current state vs planned state clearly separated
- Host-side testing (pytest) documented with examples
- Firmware testing with uos-check.sh documented
- Code coverage workflow with uos-cover tools
- Test environment requirements
- Risk-based test prioritization (P0-P3)
- Test categories (smoke, functional, regression, performance, stress, security)
- 5-phase roadmap: CI boot tests → test harness → coverage in CI → MC/DC → perf
- Appendices with file locations, CI status, common commands
Document now accurately reflects what exists and provides actionable guidance.
