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

Abierto
#2,488 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli, devtools

Línea de trabajo

This is an architecture experiment, not a first task. Start by reading ADR-003 (#2486) and the scenarios in #2487, then the existing Copilot projection of .github/agents/squad.agent.md and the .squad/ state paths that squad_state_read and teamRoot resolve. Done means a findings comment on this issue, plus an ADR-003 update if the recommendation changes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

  • A neutral coordinator source in the workspace. Settle open question 2 of ADR-003: inside .squad/, served by squad_state_read and following teamRoot, or outside it.
  • Copilot and Claude projections generated from it. Copilot's file has to carry what today's file does: the version stamp, the team-capabilities block squad cast writes (#1608), and the customization backup (#1052).

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

Lenguaje dominante
TypeScript
Estrellas
3.4k
Forks
516
Merge medio
1 d 15 h
PR fusionados (30 d)
116

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/squad

Todos los issues de github/squad

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.