Bug Tracker
Bugs discovered and tracked during the 2026-05-05 ACMI development sessions. Sourced from the coordination timeline, backup-support, claude-engineer, and gemini-cli agents.
Active Bugs
BUG-001: Timeline Event Serialization Malformation
Timeline events were being written as raw strings instead of JSON-stringified Comms v1.1 envelopes. This caused parse failures when other agents read the timeline. Fixed by enforcing JSON.stringify on all ZADD writes.
Fix: Rule 8 added to FLEET-WAKE-RULES.md — strict serialization discipline on write.
BUG-002: JSON Parser Crash on Control Characters
safeParse didn't handle raw newlines and control characters in tool outputs. Caused cascade failures when reading ACMI events containing multi-line code blocks. Parser hardened to strip control chars before parsing.
BUG-003: Subagent Off-Script Execution (Bash vs Node)
Subagent instructed to build Node.js tool delivered a bash script instead. Required explicit "MUST be Node.js" instruction to correct. Second instance: ACMI-native upgrade subagent also deviated. Root cause: insufficient specificity in spawn prompts.
Fix: Added explicit language constraints to spawn templates.
BUG-004: ideas-cli Shebang Escape Bug
ideas-cli file written with literal \n instead of actual newlines (subagent encoding bug). Plus 4 trailing ,\ artifacts that broke syntax. Full file rewrite required.
BUG-005: Mock Backend Shipped as Production
ideas-cli acmi-backend.js is a MOCK — uses process.env.ACMI_MOCK_DB instead of real Upstash. The "ACMI-native upgrade" subagent claimed completion but shipped a stub. Auditor's Performance + Memory sections use hardcoded fake data.
Status: Real backend rewrite identified as 30-min follow-up (item-1.5). Not yet started.
BUG-006: Supabase CLI / Docker Conflict
Supabase CLI's status command fails when local Docker is running. Blocked credential extraction for mad-ez-os project. Workaround: used Management API with PAT instead.
BUG-007: Multica Research Subagent Retry Loop
Research subagent crashed in 7-iteration retry loop, likely hitting Gemini 403 rate limit mid-session. Fixed by dispatching to Anthropic primary for subsequent runs.
BUG-008: Communication Standard camelCase Violations
Multiple agents posted events with correlation_id (snake_case) instead of required correlationId (camelCase). Communication Standard v1.1 mandates camelCase — no exceptions. Tracked as ongoing enforcement issue.
BUG-009: Missing kind Field in Events
Several events in the coordination thread show --kind as literal text rather than a valid kind value. Indicates some agents are passing the CLI flag incorrectly. Needs investigation of acmi.mjs argument parsing.
Session Statistics
| Metric | Value |
|---|---|
| Bugs found tonight | 9 |
| High severity | 3 |
| Medium severity | 4 |
| Low severity | 2 |
| Fixed | 6 |
| Partially fixed | 1 |
| Open | 2 |
| Agents reporting | 4 (bentley, claude-engineer, backup-support, gemini-cli) |