Naming conventions

[chrisayl]

Just a small point but when dubugging tracing the flow can be annoying:

Perfect! I found the mapping. Looking at lines 38-41 of
  /usr/local/share/npm-global/lib/node_modules/codemachine/config/main.agents.js:

  {
    id: 'task-sanity-check',
    name: 'Task Verification Agent',
    description: 'Verifies generated code against task requirements and acceptance criteria',
    promptPath: path.join(promptsDir, 'codemachine', 'agents', '06-task-validation-agent.md'),
  },

  So there are actually THREE different names for the same agent:

  1. Workflow step ID: task-sanity-check (used in workflow files)
  2. File name: 06-task-validation-agent.md (the actual prompt file)
  3. Display name: "Task Verification Agent" (human-readable name)

  The names are different because:
  - The workflow uses the ID (task-sanity-check) - a more casual/colloquial name
  - The file uses a formal name (task-validation-agent) - more professional naming convention
  - The config maps them together so the workflow can find the right prompt file

[moazbuilds]

Yeah, good point, even the protocol name for each agent (shown in the first line of the prompt) might differ. This happened because the workflow was built in several separate stages, which led to some inconsistent naming. I’ll work on improving this in future versions.