9 sessions on Make with a coding agent: the agent failed at least once in 9, and 0 finished without a human stepping in.
Takeaway: Next time I'd ask upfront how this OS's other interactive JS apps handle input, since the busy-poll getKeyNonBlock() loop turned out to be the real cause of the exit crash, not the VGA I/O port theory the agent chased first.
Takeaway: Next time I'd specify the memory-arena ownership model (who owns terms from clauses vs.
Takeaway: Next time I'd flag up front that any CLI flags removed during a refactor need a compatibility shim, since removing --recover silently broke one test fixture.
Takeaway: Next time I'd tell it upfront that Stage 3's 'parser/bytecode boundary' can't be a real physical separation in a 63K-line monolith like quickjs-ng, so it skips straight to building the JS_WriteObject/JS_ReadObject wrapper instead of discovering that mid-session.
Takeaway: Next time I'd tell it up front to match the existing input-loop pattern (blocking getChar, like quill and the shell) instead of letting it invent a getKeyNonBlock busy-poll — that's what caused the GPF on quit.
Takeaway: Next time I'd specify the persistent-arena/variable-registry design up front — the query-vs-clause arena confusion cost the most back-and-forth.
Takeaway: Next time I'd specify upfront which CLI flags must stay wired through even if the C API doesn't support them yet, since dropping --recover during the refactor silently broke a fixture test and cost a round of debugging.
Takeaway: Next time I'd ask upfront for an audit of what quickjs-ng already exposes (JSMallocFunctions, JS_WriteObject/JS_ReadObject) before specifying a stage's API, since the agent ended up discovering mid-stage that the 'ideal' architecture didn't match the 63K-line monolith's reality.
Takeaway: Next time I'd ask upfront for the stack-usage rules (no post-init malloc, bounded everything) to be double-checked against test harness patterns, since two of the three real bugs were stack overflows from large structs being copied or placed on the call stack instead of static storage.