create-byan-agent 2.25.0 → 2.27.0

package/CHANGELOG.md

@@ -9,6 +9,308 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed - Portable MCP config: the server resolves its own credentials
+
+The byan MCP server now resolves its config (`BYAN_API_URL` / `BYAN_API_TOKEN`
+and the Leantime pair) instead of depending on `.mcp.json` `${...}` expansion,
+which silently passed a literal `"${BYAN_API_URL}"` to the server when the
+launcher could not expand it — breaking every byan_web call (projects/memory/
+strict sync). This makes the MCP portable across zsh/fish/bash x Linux/Windows/
+macOS and covers Claude Code AND Codex with one mechanism.
+
+- `_byan/mcp/byan-mcp-server/lib/resolve-config.js` (new): per-key precedence
+  `process.env -> ~/.byan/credentials.json -> localhost default`. An unexpanded
+  `${...}` env value is treated as ABSENT (so a stale `.mcp.json` no longer
+  poisons the config), and a missing/invalid credentials file degrades to
+  defaults rather than throwing at boot. `server.js` wires it and backfills
+  `process.env` so downstream readers (Leantime) see the resolved values.
+- The yanstaller now writes a global, gitignored, chmod-600
+  `~/.byan/credentials.json` (`byan-platform-config`'s new `credentials.js`,
+  wired into `setupByanWebIntegration`) — one file for all the user's projects,
+  via `os.homedir()` so it is truly cross-OS with no shell-profile editing.
+- `.mcp.json` no longer carries byan config env: the template drops the `env`
+  block and `mergeByanEntry` stops writing `BYAN_API_URL` (and repairs a stale
+  entry by stripping any `BYAN_API_URL`/`BYAN_API_TOKEN` it carried). The token
+  stays out of `.mcp.json` (it lives only in the gitignored credentials file
+  and .env / settings.local.json).
+- Precedence summary for operators: a real `BYAN_API_URL` env var still wins
+  (prod sidecar / Docker / CI unaffected); the global credentials file is the
+  local-dev fallback; `http://localhost:3737` is the last resort.
+- Reviewed by Quinn + `bmad-compliance` (security domain): a TOCTOU on the
+  credentials file (write-then-chmod exposed the token at 0644 for a window)
+  was fixed by creating the file at mode 0600 directly, with a regression test.
+- Tests: `resolve-config` (8) + `credentials` (8, incl. the TOCTOU + overwrite
+  cases) + the realigned `mcp-config` suite; connector suite 635/635 green.
+
+### Added - OAuth 2.1 per-member identity for the Claude Team org connector
+
+The remote connector now carries per-member identity through OAuth 2.1
+(authorization-code + PKCE S256), so a single Claude.ai Team org connector
+authenticates each member as themselves. This is the only per-member path: a
+Claude.ai org connector sends no custom auth header and has no per-member token
+passthrough, so the API-key-paste channel (kept as a fallback) cannot identify
+members on its own.
+
+- Connector (`server-http.js`) becomes an OAuth protected resource (RFC 9728):
+  serves `/.well-known/oauth-protected-resource` (+ the path-suffixed `/mcp`
+  variant) advertising the byan_web authorization server, and validates every
+  caller's Bearer per-request against byan_web `/api/auth/me` (loopback) BEFORE
+  any tool runs — fail-closed on non-2xx, network error, or timeout. An
+  unauthenticated `/mcp` hit returns `401` with
+  `WWW-Authenticate: Bearer resource_metadata=...` to bootstrap the flow.
+  `BYAN_OAUTH_ISSUER` (falls back to `BYAN_API_URL`) and
+  `BYAN_MCP_BEARER_TIMEOUT_MS` configure it.
+- byan_web (separate repo, committed on its own branch) gains the authorization
+  server: `/.well-known/oauth-authorization-server`, `/authorize` (auto-consent
+  from the Authentik SSO session), `/token` (PKCE S256, `application/x-www-form-urlencoded`,
+  short-TTL revocable `byan_` access token), and the single-use `oauth_codes`
+  table. The shared JSON body parser is untouched (Content-Type gating).
+- `docs/oauth-connector.md`: the OAuth runbook — env vars, the proposed Traefik
+  host-split diff (`/authorize` via forwardauth, `/token` + well-known via
+  strip-trust), and the one-member pilot procedure with the five Claude.ai
+  behaviors to live-verify.
+- Reviewed by Quinn (qualitative) and `bmad-compliance` (adversarial, security
+  domain): a loopback `redirect_uri` hardening (reject userinfo/query/fragment)
+  and RFC 6749 §5.1 token-response cache headers were applied and re-verified
+  with no residual bypass.
+- Deferred, documented (not silently cut): Dynamic Client Registration
+  (pre-registered `claude-ai` client id), refresh tokens (~1h re-auth),
+  server-side `connector:read` scope enforcement (carried RBAC gap; TTL +
+  revocation bound the blast radius), and `/token` rate-limiting.
+- Operator-owned to go live: deploy, the Traefik host-split, the Claude.ai org
+  connector registration, and the pilot.
+
+### Added - Remote MCP connector enabling layer (BYAN native to Claude Team)
+
+The MCP server can now serve a remote HTTP transport so BYAN can be added as a
+Claude.ai Team Org Connector (which also syncs down to Claude Code), without
+changing the local stdio path.
+
+- `createByanServer({ token, remoteOnly })` factory extracted from `server.js`;
+  the stdio entrypoint is guarded so importing the module no longer grabs stdio.
+- `server-http.js`: a stateless streamable-HTTP transport on `/mcp` (+ `/health`),
+  built on the bundled SDK transport (no new dependency). Streamable-HTTP carries
+  the SSE streaming leg itself, so no separate legacy `/sse` endpoint is mounted.
+- Per-request identity: the caller's token is read from each request's
+  `Authorization` header and threaded through the byan_web calls (the module-global
+  token becomes the local stdio fallback), so concurrent Team members reach
+  byan_web with their own token instead of a shared one.
+- Remote-safe surface: `remoteOnly` exposes only `REMOTE_SAFE_TOOLS`, a read-only
+  byan_web-backed allowlist; filesystem-local / stateful / write tools stay
+  stdio-only and are refused over the remote transport. `bin/byan-lint-remote-safe.js`
+  (wired into pre-commit) guards the allowlist.
+- Skill bundles: `bin/byan-build-skill-bundles.js` packages each `.claude/skills`
+  SKILL.md as its own `.zip` into `dist/skill-bundles/` (zero-dep stored ZIP) — one
+  archive per skill, shaped as a single top-level folder + SKILL.md, which is what
+  Claude.ai org Skills accepts (a flat SKILL.md or a multi-skill archive is
+  rejected). `skill-bundles-manifest.json` is the tracked drift ledger with a
+  `--check` pre-commit gate.
+- Tests: per-request auth isolation (two tokens reach byan_web with distinct
+  headers), remote-surface filtering, and the skill bundler.
+- Admin runbook: `docs/connector-admin-runbook.md`. The byan_web hosting track it
+  depended on is now built (see the next entry); a true OAuth flow remains deferred.
+  Projects/Artifacts have no external API so byan_web stays the state authority.
+
+### Added - Remote connector hosting layer (byan_web sidecar + per-member enrollment)
+
+The cross-repo byan_web track the enabling layer depended on is now built: the
+connector runs as a hosted sidecar and each Claude Team member enrolls with their
+own byan_web key.
+
+- Sidecar image: `_byan/mcp/byan-mcp-server/Dockerfile` (node:22-slim + tini PID1,
+  `npm ci --omit=dev`, `CMD node server-http.js`, wget-backed HEALTHCHECK on
+  `/health`) plus a `.dockerignore`. byan_web references the image by tag and does
+  not build the connector source (anti-vendoring boundary).
+- Startup guard: `assertNoAmbientToken` fails the connector boot if `BYAN_API_TOKEN`
+  is present, so a sidecar carries per-request identity only (defense-in-depth on
+  top of `resolveCallerToken`, which ignores the env token in remote mode).
+- Per-member enrollment (byan_web repo): `POST /api/connector/link` mints a personal
+  `byan_` key (idempotent per user, raw returned once, sha256-at-rest, 90-day TTL)
+  that the member pastes into the Claude.ai connector config. The minted key is a
+  full-capability byan_web credential whose read-only behaviour is enforced at the
+  MCP transport only, so it must be treated as a secret. byan_web changes:
+  `routes/connector-link.js` + test, the `byan-mcp-connector` compose service, and a
+  `byan-mcp.<domain>` Traefik route reusing `byan-strip-trust` with no SSO forwardauth.
+- Connector smoke test (`/health` 200, import without binding a port), kept on the
+  BYAN side so byan_web CI stays PostgreSQL-free.
+- Runbook expanded: the hosting build, the per-member enrollment flow, the
+  one-member 48h pilot gate, the security invariants, and the operator-only steps
+  (DNS, image build, compose up, Claude.ai registration) that remain manual.
+
+### Added - Leantime opt-in block in the installer (yanstaller)
+
+`npx create-byan-agent` now offers an optional, opt-in Leantime board
+connection (after the byan_web step, Claude Code targets only; defaults to no).
+When accepted it prompts for the backend URL (with the wrong-host warning), the
+`lt_` API key (masked), and an optional user id, then writes the vars to
+`.claude/settings.local.json` + `.env` (both gitignored), adds the
+`${LEANTIME_API_URL}` / `${LEANTIME_API_TOKEN}` references to the `byan` entry in
+`.mcp.json` (references only, the secret stays out of tracked files), and runs a
+reachability probe that flags the wrong-host case (`non_json`) at install time.
+
+The Leantime token is per-instance: each user configures their own instance and
+key, so it is not shared across installs. Mirrors the existing byan_web block and
+reuses the shared `byan-platform-config` secret-writing primitives. New
+`promptForLeantime` / `LEANTIME_ENV_KEYS` (token-prompt), `mergeLeantimeRefs` /
+`ensureLeantimeRefs` (mcp-config), `validateLeantimeReachability` (validate), and
+the `install/lib/byan-leantime-integration.js` wrapper. Scoped to
+create-byan-agent; update-byan-agent parity is a follow-up.
+
+## [2.26.0] - 2026-06-16
+
+### Added - Leantime FD auto-sync hook (FD lifecycle -> board, automatic)
+
+The FD -> Leantime mirror is now AUTOMATIC. A `PostToolUse` hook
+(`.claude/hooks/leantime-fd-sync.js`, registered in `.claude/settings.json`) fires
+after `byan_fd_advance` / `byan_fd_update` and drives the board with no agent
+action: it ensures the project at DISCOVERY, creates one task per backlog feature
+at DISPATCH, and moves tasks through `todo -> doing -> blocked/review -> done` as
+the FD advances. This supersedes the hand-driven section 2.5 fire points (which
+the agent had to run by hand and could skip).
+
+- **Pure core** (`_byan/mcp/byan-mcp-server/lib/leantime-fd-core.js`):
+  `decideActions` maps a phase transition + the sidecar to ordered Leantime
+  intents; unit-tested for every transition. The hook is a thin I/O shell that
+  executes them.
+- **Best-effort + bounded**: the hook exits 0 in every path (a sync issue does
+  not block the turn), no-ops when Leantime is off, self-heals a dropped call on
+  the next phase event (a per-call timeout + a hook wall-clock budget), and logs
+  every attempt to `.byan-leantime/sync.jsonl`.
+- **Idempotence**: a gitignored sidecar (`.byan-leantime/map.json`, keyed by
+  fd_id) is the single id ledger — a REFACTOR loop re-builds without duplicating a
+  project or task. The hook does not write `fd-state.json` (state-coupling).
+- **Human visibility** (`assignUserToProject` + `LEANTIME_ASSIGN_USER_ID`): an
+  API-created project is owned by the API service user and hidden from a person's
+  project selector; the hook relates the configured human so the board shows up.
+  The underlying Leantime RPC reconciles a user's whole project list, so the
+  assign reads the full list first and writes the union (fail-closed if that read
+  is incomplete) to avoid unassigning the user's other projects.
+
+### Added - Leantime project-management integration (one-way FD -> board)
+
+BYAN can now mirror its Feature Development lifecycle onto a self-hosted Leantime
+instance. When `LEANTIME_API_URL` + `LEANTIME_API_TOKEN` are configured, the FD
+phases drive a Leantime project and one task per backlog feature ; when absent,
+the tools report disabled and FD proceeds unchanged. The sync is one direction
+(FD -> Leantime) and best-effort : a down or misconfigured Leantime degrades to
+`{ synced:false, reason }` and does not block a phase transition.
+
+- **Client** (`_byan/mcp/byan-mcp-server/lib/leantime-sync.js`): a JSON-RPC 2.0
+  client for `<base>/api/jsonrpc`, authenticated by the Leantime-native
+  `x-api-key` header (kept distinct from the byan_web `ApiKey/Bearer` scheme).
+  Best-effort and does not throw, with an `AbortController` timeout and a
+  non-JSON-200 guard that rejects an HTML login body (the wrong-host lesson)
+  instead of reading it as an empty board. Business fns: `ensureProject`
+  (idempotent by name), `createTask`, `moveTask`, `assignTask`, `getTask`,
+  `getBoard`, plus `resolveStatusMap` / `resolveClientId` / `resolveEditorId`.
+- **MCP tools** (7): `byan_leantime_ping`, `byan_leantime_project_ensure`,
+  `byan_leantime_task_create`, `byan_leantime_task_move`,
+  `byan_leantime_task_assign`, `byan_leantime_task_get`,
+  `byan_leantime_board_get`. All but `ping` pass through `requireLeantime()`.
+- **FD wiring** (`.claude/skills/byan-byan/SKILL.md` section 2.5): fire points
+  DISCOVERY -> project_ensure, DISPATCH -> task_create per feature, BUILD ->
+  doing, REVIEW/VALIDATE-KO -> blocked, VALIDATE-OK -> review, DOC -> done.
+  Leantime ids persist into fd-state (`project_context.leantime.projectId`,
+  backlog `leantime.taskId`) so a REFACTOR loop reuses tasks instead of
+  duplicating them.
+- **Status mapping**: the canonical FD columns (`todo|doing|blocked|review|done`)
+  resolve to per-project Leantime status ids at call time, with a conservative
+  fallback when the labels cannot be read.
+- **Tests**: `test/leantime-sync.test.js` (14 cases: auth header, non-JSON guard,
+  timeout, idempotence, column resolution) + `test/leantime-tools.test.js`
+  (the 7-tool declaration/handler surface in server.js).
+- **Docs**: `.claude/rules/byan-api.md` section 8 (the `byan_leantime_*` family +
+  the wrong-host lesson).
+- **Pending**: the live wire-format verification (one real POST with a Leantime
+  PAT, to confirm `params:{values:{}}` wrapping against the running instance) is
+  a documented follow-up ; the tested format follows the Leantime master source.
+
+### Removed - GitHub Copilot CLI + VSCode dropped as target platforms (3 -> 2)
+
+BYAN now targets two platforms: Claude Code and Codex. GitHub Copilot CLI and
+the VSCode extension are no longer install targets. This is a breaking change for
+anyone who relied on the Copilot/VSCode output.
+
+- **Install path** (`npx create-byan-agent`): the platform menu, auto-select, and
+  generated stubs cover Claude Code + Codex only. The `byan_copilot_*` MCP tool
+  family and the `marc` Copilot-oriented agent were removed in the core pass
+  (commit `0f06cf8`).
+- **Web UI** (ships on npm via `install/src/webui`): the chat CLI selector, the
+  `cli-detector` definitions, the platform-detection list, and the marketing copy
+  drop Copilot and VSCode; the `copilot-adapter` bridge and its `createBridge`
+  case are gone (`createBridge('copilot')` now rejects with `Unknown CLI adapter`).
+- **Dead code**: both shipped copies of the orphaned `copilot-context` module
+  (`src/byan-v2/context/` and `install/src/byan-v2/context/`) and two stale
+  non-jest harnesses (`test-byan-v2-workflow.js`, `test-workflow-simple.js`) were
+  deleted.
+- **Note**: the `byan-loadbalancer` Copilot *provider* (an LLM backend, not an
+  install target) is unaffected and stays.
+
+### Added - Auto-Benchmark: native sourced decision benchmarks (C1-C5)
+
+When the agent is about to ask you to choose between options, it now benchmarks
+the fork by default: one compact `Option | criteria | Niv` table with a best-first
+recommendation, sourced and confidence-tagged, at the right level of detail — so
+you no longer have to ask each time. Two layers cover this honestly (Claude Code
+exposes no pre-display interception hook today, GH #28273):
+
+- **Proactive doctrine** (the broadly-portable layer). The full doctrine lives in
+  `.claude/rules/benchmark.md`, generated from the single source of truth
+  `_byan/_config/autobench.yaml` by `byan-sync-rules`, and a lean pointer is
+  upserted cross-platform into `.claude/CLAUDE.md`, `AGENTS.md`, and
+  `.github/copilot-instructions.md` (idempotent `BYAN-AUTOBENCH` markers). It
+  covers the TRIGGER 2-gate rule (>= 2 non-substitutable options diverging on
+  >= 1 weighted criterion) + the exemption list (y/n confirms, destructive
+  prompts) + internal/external routing + a verbatim few-shot decision tree, the
+  SCALER 5-level evidence rubric + strict-domain floors + the link-only-if-WebFetch
+  rule, the FORMAT compact table with hard caps (<= 4 options / <= 4 criteria /
+  <= 3 links) + collapse-the-degenerate + `[bench:expand]` opt-in, and the
+  ANTI-BLOAT latency guard + escape-hatch + no-re-benchmark.
+- **Reactive Stop hook** (`.claude/hooks/autobench-stop-guard.js`), the safety
+  net. It **ships DISARMED**: it observes and ledgers every turn but stays inert
+  (does not block) until you opt in — set `enforcement.armed: true` in
+  `_byan/_config/autobench.yaml` and run `byan-sync-rules` (config-only; there is
+  no loose flag file) — so day one is zero noise / zero latency.
+  Detection is **artifact-primary**: a real fork is recognized from an
+  `AskUserQuestion` tool_use in the finished turn, with the choice-language regex
+  as a last-resort fallback. Block-once is content-hashed (no loop); a session
+  escape-hatch (`touch .byan-autobench/off`) plus a cross-session toggle suppress
+  it.
+- **Tooling.** A `byan-benchmark` skill (conductor) and a DATA-only native
+  workflow (`.claude/workflows/byan-benchmark.js`), both registered in the
+  workflow manifest / PORTABLE bucket / INDEX. A BYAN-only opt-in layer enriches
+  the matrix via `byan_fc_check`. Every fire/miss is audited to
+  `_byan-output/benchmark-ledger.jsonl`.
+
+### Added - byan-install-core (F1): headless, deterministic install engine
+
+First feature of the installer refactor (FD lot 1). A new internal workspace
+package `byan-install-core` (`install/packages/install-core/`) that replaces the
+LLM-driven AUTO interview with a deterministic engine. It is the shared core both
+front-ends bind to: the npm CLI wizard (F2, next) and the Electron app (F5).
+
+- **Four-verb lifecycle.** `detect(opts)` builds a serializable MachineProfile
+  (os, arch, node, npm, git, claude, codex) and is spawn-free by default
+  (`probeVersions` is opt-in). `plan(profile, answers)` is pure and turns the
+  non-interactive answers contract into an ordered InstallPlan. `apply(plan, opts)`
+  is the only mutator. `verify(plan|target)` is read-only.
+- **No LLM, no `which`.** Detection uses a pure-Node PATH walk (`lookpath`,
+  honoring Windows PATHEXT); recommendations come from a versioned JSON decision
+  table (`data/recommender.json`), not a model call.
+- **Per-OS env + validate-or-die .mcp.json.** `env-writer` and `mcp-renderer`
+  reuse the existing `byan-platform-config` package (idempotent marker blocks;
+  a config is parsed and validated before any write, so a broken file is not
+  emitted on an invalid input).
+- **Per-user install, no sudo.** `--install-cli claude|codex` installs via
+  `npm -g`; the AUTH step is an explicit handoff (the engine returns the manual
+  command and reports a pending state rather than a fake authenticated success).
+- **ES5 preflight.** `byan-install-core/preflight` is a dependency-free, ES5-only
+  entry a launcher can require on an ancient Node to gate the version before any
+  modern module loads.
+- Tests: 9 suites / 161 tests for the package; full repo suite green
+  (no regression). The CLI wizard, `doctor`, journal/resume and the v2.19
+  `--yes` end-to-end snapshot land in the following features (F2, F3).
+
 ## [2.25.0] - 2026-06-09
 
 ### Added - Advisory auto-feed (BYAN learns from each session, automatically)

package/README.md

@@ -69,7 +69,7 @@ Diversifier les personas elargit la surface de competence collective.
 
 - Node.js >= 12.0.0
 - npm >= 6.0.0
-- Un compte GitHub Copilot, Claude Code ou Codex (selon la plateforme cible)
+- Un compte Claude Code ou Codex (selon la plateforme cible)
 
 ### Installation rapide (recommandée)
 
@@ -89,7 +89,7 @@ L'installeur (Yanstaller) vous guide interactivement à travers le processus :
 ```
 ? Nom du projet : mon-projet
 ? Langue de communication : Francais
-? Plateforme cible : GitHub Copilot CLI
+? Plateforme cible : Claude Code
 ? Activer le fact-check scientifique ? [Y/n]
 ? Activer le système ELO de confiance ? [Y/n]
 ? Optimiser les coûts LLM automatiquement (~54% d'économies) ? [Y/n]
@@ -108,7 +108,6 @@ votre-projet/
     workflows/         # Workflows guidés
     knowledge/         # Base de connaissances sources (axiomes, benchmarks)
     config.yaml        # Configuration principale (langue, utilisateur, chemins)
-  .github/agents/      # Wrappers GitHub Copilot CLI
   .claude/             # Intégration Claude Code (si activée)
   .codex/              # Intégration Codex/OpenCode (si activée)
   bin/byan-v2-cli.js   # CLI BYAN
@@ -164,7 +163,7 @@ const ctx = byan.getClaimContext('security');
 console.log('Scaffold level :', ctx.scaffoldLevel);
 ```
 
-### Activer les agents dans GitHub Copilot CLI
+### Activer les agents dans Claude Code ou Codex
 
 Une fois installé, les agents sont disponibles via `@agent-name` :
 
@@ -183,7 +182,7 @@ Une fois installé, les agents sont disponibles via `@agent-name` :
 
 ## Liste des Agents Disponibles
 
-BYAN contient **27 agents spécialisés** organisés en **5 modules** :
+BYAN contient **26 agents spécialisés** organisés en **5 modules** :
 
 ### Core — Fondation de la Plateforme
 
@@ -203,7 +202,6 @@ BYAN contient **27 agents spécialisés** organisés en **5 modules** :
 | **agent-builder** | Bond | Expert en construction d'agents BMAD-compliant | Construire un agent complexe manuellement |
 | **module-builder** | Morgan | Architecte de modules BYAN complets | Créer un nouveau module métier |
 | **workflow-builder** | Wendy | Designer de workflows guidés | Concevoir un processus multi-étapes |
-| **marc** | Spécialiste | Intégration GitHub Copilot CLI | Déployer des agents sur Copilot |
 | **rachid** | Spécialiste | Déploiement npm/npx | Publier un package BYAN |
 | **carmack** | Optimiseur | Optimisation tokens (-46%) | Réduire le coût d'utilisation des agents |
 | **patnote** | Gestionnaire | Mises à jour BYAN et résolution de conflits | Mettre à jour un projet BYAN existant |
@@ -274,7 +272,7 @@ Un agent est un spécialiste IA avec une identité définie. Il possède :
 - **Rules** : les contraintes absolues qu'il ne peut pas violer (les 71 mantras)
 - **Capabilities** : ce qu'il peut faire, ce qu'il ne fait pas
 
-Les agents sont définis en Markdown avec des sections XML. Ils sont stockés dans `_byan/{module}/agents/` et exposés sur chaque plateforme via un wrapper léger (`.github/agents/`, `.claude/`, `.codex/prompts/`).
+Les agents sont définis en Markdown avec des sections XML. Ils sont stockés dans `_byan/{module}/agents/` et exposés sur chaque plateforme via un wrapper léger (`.claude/`, `.codex/prompts/`).
 
 ### Workflow
 
@@ -432,7 +430,7 @@ Domaines stricts : `security` / `performance` / `compliance` → LEVEL-2 minimum
 
 Mode d'enforcement qui empêche l'agent de livrer moins que demandé (un MVP au
 lieu de l'app prod, un stub au lieu de la feature, un template baclé). Actif sur
-les **3 plateformes** : Claude Code, Codex, GitHub Copilot.
+les **2 plateformes** : Claude Code, Codex.
 
 ```
 1. Lock du scope       byan_strict_lock_scope  (scope verbatim + critères testables)
@@ -442,8 +440,8 @@ les **3 plateformes** : Claude Code, Codex, GitHub Copilot.
 ```
 
 Le commit est **bloqué** par un filet pre-commit tant que la session strict
-engagée n'est pas complétée correctement — y compris pour Codex et Copilot qui
-n'ont pas de hook in-session. Source de vérité unique :
+engagée n'est pas complétée correctement — y compris pour Codex qui
+n'a pas de hook in-session. Source de vérité unique :
 `_byan/_config/strict-mode.yaml`, régénérée via `byan-sync-rules`.
 
 Activation : `byan_fd_start strict:true`, skill `byan-strict`, ou auto-détection
@@ -466,7 +464,7 @@ sur mots-clés (`prod`, `client`, `livrable`, `contrat`, `release`...).
 | `testarch-atdd` | Générer des tests ATDD avant implémentation | tea |
 | `fact-check` | Analyser une assertion ou un document | fact-checker |
 | `elo-workflow` | Consulter et gérer le score de confiance ELO | byan |
-| `byan-sync-rules` | Régénérer les artefacts du mode strict (3 plateformes) | byan |
+| `byan-sync-rules` | Régénérer les artefacts du mode strict (2 plateformes) | byan |
 
 ---
 
@@ -474,7 +472,6 @@ sur mots-clés (`prod`, `client`, `livrable`, `contrat`, `release`...).
 
 | Plateforme | Invocation | Chemin de config |
 |------------|-----------|------------------|
-| GitHub Copilot CLI | `@agent-name` | `.github/agents/*.md` |
 | Claude Code | `@agent-name` | `.claude/rules/*.md` |
 | Codex / OpenCode | `@agent-name` | `.codex/prompts/*.md` |
 | CLI direct | `node bin/byan-v2-cli.js` | `_byan/config.yaml` |