feat: rename workflows to agent files

[RomneyDa]

Description

Rename workflows to agent files in CLI code
Breaking changes in config yaml for parsing function/type naming
Also breaking change of flag from --workflow to --agent

---

Summary by cubic

Renamed “workflows” to “agent files” across the CLI and config-yaml. This includes new CLI flags, service/types, and YAML parser names, and is a breaking change for consumers.

• Refactors

  • Replaced WorkflowService with AgentFileService and SERVICE_NAMES.AGENT_FILE.
  • Switched hub package type/processor from “workflow” to “agent-file” and parseAgentFile.
  • Updated ConfigEnhancer, ModelService, ToolPermissionService, and chat flow to use agent file state (prompt, tools, model).
  • config-yaml exports now come from agentFiles.ts (AgentFile, parseAgentFile, parseAgentFileTools, serializeAgentFile).

• Migration

  • CLI: use --agent instead of --workflow.
  • Imports: replace WorkflowFile → AgentFile, parseWorkflowFile/parseWorkflowTools → parseAgentFile/parseAgentFileTools, and import from agentFiles.ts.
  • Hub: use package type “agent-file” for slugs and processors.
  • Services: switch SERVICE_NAMES.WORKFLOW → SERVICE_NAMES.AGENT_FILE and workflow* state fields → agentFile* equivalents (including agentFilePolicyCount).

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ Continue configuration error. Please verify that the assistant exists in Continue Hub.

---

[cubic-dev-ai]

3 issues found across 26 files

Prompt for AI agents (all 3 issues)

Understand the root cause of the following 3 issues and fix them.


<file name="extensions/cli/src/shared-options.ts">

<violation number="1" location="extensions/cli/src/shared-options.ts:114">
The inheritable option key should stay aligned with the &quot;--agent&quot; flag; using &quot;agent-file&quot; prevents subcommands from inheriting the agent slug.</violation>
</file>

<file name="packages/config-yaml/src/markdown/agentFiles.test.ts">

<violation number="1" location="packages/config-yaml/src/markdown/agentFiles.test.ts:73">
The expected error message now asserts &quot;Agent File file...&quot; but parseAgentFile still throws &quot;Agent file must contain YAML frontmatter with a &#39;name&#39; field&quot;. Please update the expectation to match the real error string so the test reflects the implementation.</violation>
</file>

<file name="extensions/cli/src/services/AgentFileService.test.ts">

<violation number="1" location="extensions/cli/src/services/AgentFileService.test.ts:227">
This suite is asserting against the mocked agentFileProcessor defined earlier in the test file, so it never covers the real implementation—regressions in hubLoader.ts would still pass. Consider unmocking or importing the actual agentFileProcessor before running these expectations.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[sestinj]

I see nothing wrong

[sestinj]

🎉 This PR is included in version 1.28.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.25.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀