Skip to content

Spike: host-neutral canonical coordinator (ADR-003 option B), opt-in experiment #2488

Backlog

Description

@bradygaster

Part of epic #2438 (Phase 7). This is option B of ADR-003 (#2486) as a bounded experiment, not a shipping commitment (team summary on #2469). Option C (#2487) is the 2.0 path and goes ahead independently. This spike doesn't block it, and it doesn't ship.

Question to answer

Would a host-neutral canonical coordinator in the workspace, with Copilot's .github/agents/squad.agent.md generated from it like every other host's projection, measurably improve correctness or maintainability enough to justify migrating existing repositories? A cleaner directory layout alone doesn't count.

Rules for the spike

  • Only disposable workspaces that explicitly opt in, for example behind an experimental flag or an environment switch that squad init never sets by default.
  • No default installer migration, and no migration of live teams' repositories.
  • A fixed budget, agreed before starting: suggested 3 days. When it runs out, report what was learned, even if the prototype is incomplete.
  • The branch is not merged to dev as shipping behavior. Findings come back as a comment here, and as an ADR-003 update if they change the recommendation.

What to build

What to test

Reuse the behavioral scenarios from #2487, then add:

  • fresh workspaces, and customized legacy workspaces (an edited squad.agent.md)
  • monorepos (the Copilot file at the git root, .squad/ in a subfolder), and remote teamRoot
  • repeatable upgrades: running squad upgrade twice gives no diff
  • customizations preserved, with clear precedence between user edits, project policy and defaults
  • rollback restores the original bytes (harness-adapters §13)
  • no Copilot regression: the snapshot guard, and a Copilot run of the same scenarios

Report back with

  • Did the scenario results improve over C? Count the defects B avoids that C doesn't.
  • Maintainability: how much code and how many tests the single source removes or adds, compared with C.
  • Migration risk: what breaks for customized, monorepo and remote workspaces, and how it's detected and recovered.
  • A recommendation: ship B later, revise it, or drop it.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions