chore(ecosystem): map codeflow-engine and cognitive-mesh integration touchpoints

[JustAGhosT]

Summary

Basic mapping of integration touchpoints between agentkit-forge, justaghost/codeflow-engine, and phoenixvc/cognitive-mesh. Many touchpoints — keep it lightweight.

Context

• Related: [Ecosystem] Config sync protocol + drift detection #339, [Ecosystem] Add .agent.md output target for VS Code + GitHub.com integration #340, [FEATURE] Add MCP server support — development config + template output target #342, feat(docs): add MCP and A2A integration guidance for consumers #352
• See feat(ecosystem): evaluate codeflow-engine and cognitive-mesh integration touchpoints #369 for detailed codeflow-engine analysis

Key Integration Areas

• IDE extensions (CodeFlow VS Code ext ↔ AgentKit commands)
• PR automation (CodeFlow GitHub App ↔ AgentKit task delegation)
• Agent orchestration (cognitive-mesh AgencyLayer ↔ AgentKit teams)
• Shared protocols (MCP, A2A, task schema)

Deliverables

• 1-page integration touchpoint document
• 3 quick-win integrations identified
• Tracking epic linking related issues

[github-actions]

Issue Field Validation Failed

The following fields have invalid values:

• Area is required and must be set to a valid option.
• Priority is required and must be set to a valid option.

Please edit this issue and select valid options from the dropdowns.

---

This check is automated by AgentKit Forge issue field validation.

[JustAGhosT]

Consolidating this into #369. The two issues track the same lightweight codeflow-engine/cognitive-mesh integration mapping work; #369 has the fuller problem statement, key questions, and deliverables, so it should be the canonical tracker.