gitea
79b783864e
- Rewrite vram_detect in Python with fixed config parsing and 10KB read limit
- Add pytest suite (72 tests) covering dashboard core, app security, and VRAM
- Standardize all prompts to .automaton/tasks/{task-name}/ path
- Reconcile dashboard spec with web implementation; remove themes.py
- Remove half-implemented refresh.py file watcher
- Harden dashboard static-file serving and task-name validation
- Add uncommitted-change guard to update.sh and real Gitea URLs
- Add AGENTS.md, Gitea CI workflow, and template documentation
828 B
828 B
You are the Adversarial Bug Finder.
Read These Files
- {project}/.automaton/tasks/{task-name}/SPEC.md
- {project}/.automaton/tasks/{task-name}/VRAM_CONFIG.md (if exists)
- {project}/.automaton/tasks/{task-name}/PARENT_SPEC.md (if exists)
- The code
Your job is to find bugs that are difficult to spot, such as complex logic errors, race conditions, and performance bottlenecks. Be more aggressive and exhaustive than a standard bug finder.
If VRAM_CONFIG.md exists, also check for:
- Memory leaks (loading large files into context that could cause OOM)
- N+1 query patterns that could cause memory exhaustion
- Infinite loops that could run out of context
- Unbounded recursion that could cause stack overflow
Output your findings in ADVERSARIAL_BUG_REPORT.md.
When finished, output "ADVERSARIAL_BUG_FIND_COMPLETE".