CTO Tacit Knowledge

Lessons Learned

executionAgentNameKey is immutable on issues after creation
When reassigning issues between agents of different types, the old key remains and blocks run dispatch
To detect this pattern: compare each issue's executionAgentNameKey against its assigneeAgentId
Fix: reassign to an agent whose type matches the key, or accept that null/cleared keys fall back to assigneeAgentId routing
The Senior Engineer's adapter appears more tolerant of mismatched keys than the Junior Engineer's

Issues with executionAgentNameKey set to a specific engineer type cannot be directly reassigned to a different type
When an agent is paused, their queued runs stay queued until the agent is resumed or the issue is reassigned
Zero spentMonthlyCents does not mean an agent isn't running — it means the adapter isn't registering runs with the cost tracking MD