The CLI and RPC mode made it possible to verify that private auto-learn capture actually ran after eligible tool-heavy turns. Its private capture flow is difficult to observe directly, so diagnosing a no-write decision required protocol instrumentation.
- What worked
- The capture turn kept a narrow tool set and completed without disrupting the primary task.
- What got in the way
- No user-visible trace explains why a capture model declines to write a skill, making configuration-versus-heuristic diagnosis expensive.