docs: accept ADR-0021 — monorepo consolidation decision with ecosystem and extraction analysis

[Copilot]

ADR-0021 was stuck in "Proposed" with a recommendation to split into 3–4 repos, while the actual migration had already gone the opposite direction (all codeflow-* repos imported into this monorepo). This closes the loop by accepting the monorepo decision and answering the open ecosystem questions.

ADR-0021 (docs/adr/0021-repository-structure.md)

Rewritten from "Proposed / split recommended" → Accepted / monorepo confirmed.

• Component coupling table — desktop/ and vscode-extension/ integrate with engine/ via HTTP/WebSocket API only (no direct imports), so independent release cadences are preserved inside the monorepo without extra tooling.

• Why monorepo is correct now — most split repos were already archived; re-splitting recreates maintenance burden with no payoff; path-aware CI (dorny/paths-filter) eliminates the full-build penalty; cross-repo coordination cost is unjustified at current team size.

• Ecosystem fit — no phoenixvc references exist anywhere in the codebase. Documents each component's role for justaghost/* / phoenixvc/* consumers and defines the integration path if a shared org infra repo is ever created.

• Future extraction candidates (with explicit trigger conditions, not speculative):

  Component	Extract when
  website/	Content team needs repo access without engine write access
  orchestration/bootstrap/	A shared justaghost/* or phoenixvc/* infra repo is established

Supporting docs

• docs/adr/README.md — ADR-0021 entry updated to Accepted ⭐; "Future Considerations" section updated.
• MIGRATION_PLAN.md — Phase 1 marked complete (adds items completed since the plan was written); pending work renamed Phase 2; Future Extraction Candidates table added with link back to the ADR.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Discussion: Should codeflow-* repositories be reintegrated into a monorepo? How do they fit into the justaghost ecosystem?</issue_title>
<issue_description>```

Context

This issue aims to initiate a discussion and gather perspectives on two key points:

1. Should the codeflow-* repositories be re-integrated into a monorepo?
2. Exactly how do the codeflow-* repositories fit into the overall `phoenixvc/' and 'justaghost/`` ecosystem?

---

Background

Currently, the following codeflow-* repositories exist under the JustAGhosT organization (archived status noted when relevant):

• codeflow-engine
• codeflow-orchestration (archived)
• codeflow-infrastructure (archived)
• codeflow-desktop (archived)
• codeflow-azure-setup (archived)
• codeflow-website (archived)
• codeflow-vscode-extension (archived)

---

Open Pull Requests

For context, here are open PRs across all codeflow-* repositories as of this writing:

codeflow-engine

• chore(deps): bump the pip group across 1 directory with 11 updates (#20)
• chore(deps): bump the pip group across 1 directory with 2 updates (#12)

codeflow-website

• chore(deps-dev): bump qs from 6.14.0 to 6.14.1 in the npm_and_yarn group across 1 directory (#5)

codeflow-desktop

• chore(deps): Bump react-router from 7.9.6 to 7.12.0 in the npm_and_yarn group across 1 directory (#3)

codeflow-vscode-extension

• Bump the npm_and_yarn group across 1 directory with 4 updates (#1)

---

Discussion Points

• What are the pros and cons of maintaining separate repositories versus adopting a monorepo approach for codeflow-*?
• Are there architectural, operational, deployment, or contribution reasons for or against consolidation?
• How does each codeflow-* repository relate to the broader phoenixvc/*' and 'justaghost/* vision and stack?
• Can (or should) certain repositories remain decoupled or archived going forward?
• What additional tooling, CI/CD, or process changes would be required for a monorepo?
• Are there lessons learned from migration or maintenance history so far?

---

Feedback and perspectives are welcome from all contributors and stakeholders.

<agent_instructions>refer to https://github.com/copilot/c/4b78fa08-2fff-4fb3-9448-ad32345e381a</agent_instructions>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Discussion: Should codeflow-* repositories be reintegrated into a monorepo? How do they fit into the justaghost ecosystem? #21

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.