create-byan-agent 2.47.0 → 2.48.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -9,6 +9,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
9
9
 
10
10
  ## [Unreleased]
11
11
 
12
+ ## [2.48.0] - 2026-07-16
13
+
14
+ ### Added - The whole dispatch chain now runs automatically at the entry
15
+
16
+ - On every non-conversational task, BYAN runs the full chain of its own accord —
17
+ the user no longer has to ask for it: (1) match the agent (agent-matcher),
18
+ (2) route the runtime with dispatch-router (Codex for execution/shell/deploy/
19
+ devops/browser ; Claude for architecture/refactor/quality/planning ; verification
20
+ stays Claude ; no Fable ; model+effort by complexity), (3) execute — Codex-lane
21
+ delegates to Codex via codex-bridge (`codex exec` -> diff -> Claude applies, with
22
+ a Claude fallback when Codex is unavailable) ; Claude-lane runs on Claude at the
23
+ chosen model.
24
+ - Reconciled with the double-validation rule: the human stays required only for
25
+ (a) creating a NEW agent when none fits and (b) confirming a destructive action.
26
+ Agent match, runtime routing and execution are automatic. Proportionate — a
27
+ trivial task with an existing agent routes directly, no ceremony.
28
+ - Wiring only: the code (agent-matcher 2.47, dispatch-router + codex-bridge 2.46)
29
+ already existed ; this connects it into the entry flow. Updated the byan-byan
30
+ skill (section 0), `.claude/rules/agent-entry-gate.md`, and `CLAUDE.md`. Honest
31
+ ceiling: the auto-chain is driven by the loaded skill (via `/byan-byan`) plus the
32
+ reactive nets — not a guarantee outside a loaded skill.
33
+ - Skill bundles rebuilt ; jest 2640 + MCP 846 green ; zero emoji ; mirrored to
34
+ install/templates.
35
+
36
+ ## [2.47.1] - 2026-07-16
37
+
38
+ ### Fixed - Doctrine told users to invoke with `@byan`, which does not load the skill
39
+
40
+ - The docs said "tape `@byan` / `@hermes`" to invoke BYAN. In Claude Code, `@` is a
41
+ file mention, not a skill loader — so the byan-byan skill (which holds the agent
42
+ entry gate) was not loaded, and BYAN ran a task inline with no dispatch. Root
43
+ cause of the entry gate appearing "not to work" on a real machine.
44
+ - Corrected the entry guidance in `CLAUDE.md`: invoke BYAN with the **command**
45
+ `/byan-byan` (it loads the skill, the entry gate, and the rail) ; noted explicitly
46
+ that `@byan`/`@hermes` do not load the skill. Mirrored to install/templates.
47
+ - Note: the entry-gate code (2.47.0) is unchanged and correct ; it simply was not
48
+ reached because the skill was not loaded. Open question (does the loaded doctrine
49
+ reliably make BYAN propose an agent, or is a hard pre-write block needed) is to be
50
+ decided by testing `/byan-byan` with the rail actually loaded.
51
+
12
52
  ## [2.47.0] - 2026-07-16
13
53
 
14
54
  ### Added - Mandatory agent entry gate (match-or-create), the base of BYAN
@@ -11,7 +11,7 @@
11
11
  Avant de chercher un agent specifique, demande a Hermes. Il connait tous les agents,
12
12
  workflows et contextes, et te route vers le bon specialiste.
13
13
 
14
- Pour invoquer Hermes, tape: `@hermes` ou demande simplement "quel agent pour [ta tache]?"
14
+ Pour lancer BYAN sur une tache, utilise la **commande** `/byan-byan` : c'est elle qui charge le skill (donc la porte d'entree et le rail de dispatch). Attention — `@byan` / `@hermes` NE chargent PAS le skill : cote Claude Code, `@` est une mention de fichier, pas un lanceur. Une fois dans `/byan-byan`, decris ta tache ou demande "quel agent pour [ta tache] ?".
15
15
 
16
16
  Voir @.claude/rules/hermes-dispatcher.md pour les commandes Hermes.
17
17
 
@@ -23,7 +23,14 @@ PROPOSENT ; l'utilisateur valide (double validation IA + humain), PUIS on lance
23
23
  workflow. Aucun agent adapte -> interview pour cadrer le besoin -> recherche web
24
24
  (competences + bonnes pratiques du metier) -> creation de l'agent sur mesure ->
25
25
  workflow. Le declencheur de l'interview est l'absence d'un agent adapte, pas la
26
- taille de la tache. Detail + enforcement : voir @.claude/rules/agent-entry-gate.md
26
+ taille de la tache.
27
+
28
+ A l'entree, BYAN enchaine AUTOMATIQUEMENT toute la chaine, sans que tu la
29
+ demandes : (1) quel agent, (2) quel moteur — Codex pour execution/shell/deploy/
30
+ devops/navigateur, Claude sinon (via `dispatch-router`), (3) execution, avec
31
+ delegation reelle a Codex sur sa voie. L'humain reste requis seulement pour creer
32
+ un nouvel agent et confirmer une action destructive. Detail + enforcement : voir
33
+ @.claude/rules/agent-entry-gate.md et @docs/intelligent-dispatch.md
27
34
 
28
35
  ## Architecture BYAN
29
36
 
@@ -68,7 +75,7 @@ Doctrine d'equipe complete (template role-in-team, analogie orchestre, principes
68
75
 
69
76
  ## Commandes Utiles
70
77
 
71
- - `@hermes` → Dispatcher universel (recommandations, routage, pipelines)
78
+ - `/byan-byan` → Entree BYAN + dispatcher universel (recommandations, routage, pipelines). Le `@` ne charge pas le skill.
72
79
  - Agent disponibles: voir @.claude/rules/byan-agents.md
73
80
  - Doctrine d'equipe: voir @.claude/rules/team-doctrine.md
74
81
  - Methodologie: voir @.claude/rules/merise-agile.md
@@ -47,6 +47,29 @@ declencher une interview a chaque fois. Agent existant qui colle = on route
47
47
  direct. Besoin flou ou aucun agent adapte = la ou l'interview + creation se
48
48
  declenchent. La ceremonie est proportionnee au manque, pas systematique.
49
49
 
50
+ ## La chaine complete, automatique (agent -> moteur -> execution)
51
+
52
+ Le dispatch d'agent n'est que la premiere marche. A l'entree, sur toute tache,
53
+ BYAN enchaine la chaine ENTIERE de lui-meme, sans que l'utilisateur ait a la
54
+ demander :
55
+
56
+ 1. **Agent** — matcher (ci-dessus). Fit -> cet agent ; no-fit -> interview +
57
+ recherche web + creation. Seul point ou l'humain reste requis : creer un
58
+ nouvel agent.
59
+ 2. **Moteur** — router via `_byan/mcp/byan-mcp-server/lib/dispatch-router.js` :
60
+ Codex pour execution / shell / deploiement / devops / navigateur ; Claude pour
61
+ architecture / refactor / qualite / planif ; la verification reste sur Claude ;
62
+ Fable n'est pas emis ; modele + effort selon la complexite. Decision
63
+ automatique, pas de validation utilisateur.
64
+ 3. **Execution** — Codex-lane : deleguer a Codex via le pont
65
+ (`lib/codex-bridge.js` : `codex exec` -> diff unifie -> Claude applique le
66
+ diff ; repli sur Claude si Codex est indisponible). Claude-lane : executer sur
67
+ Claude au modele choisi. Automatique.
68
+
69
+ Ce qui reste a l'humain : (a) creer un nouvel agent quand aucun ne colle, (b)
70
+ confirmer une action destructive. Le reste — match agent, routage moteur,
71
+ execution — part tout seul. Detail du routage moteur : `docs/intelligent-dispatch.md`.
72
+
50
73
  ## La double validation
51
74
 
52
75
  Le matcher (F1, `_byan/mcp/byan-mcp-server/lib/agent-matcher.js`) est un
@@ -7,19 +7,31 @@ description: BYAN — Builder of YAN. Core meta-agent that owns the Feature Deve
7
7
 
8
8
  You are BYAN when this skill is active. You own the eight-phase Feature Development workflow and you enforce it mechanically. Every new feature the user asks for goes through all phases in order. No skipping. No implicit transitions. The cycle includes a REFACTOR loop back to BUILD when VALIDATE fails.
9
9
 
10
- ## 0. Entry gate — agent dispatch first (match-or-create)
11
-
12
- Before doing any non-conversational task, run the mandatory agent entry gate:
13
- BYAN + Hermes evaluate which specialist agent fits the need (the matcher in
14
- `_byan/mcp/byan-mcp-server/lib/agent-matcher.js` pre-ranks the roster), and you
15
- PROPOSE it to the user, who validates (double validation IA + human). A suited
16
- agent -> launch its workflow (+ runtime dispatch). No suited agent -> propose an
17
- interview to frame the need, do web research on the trade's competencies + best
18
- practices, create the tailored agent, then launch the workflow. The interview is
19
- triggered by the ABSENCE of a suited agent, not by task size — a fit routes
20
- directly, no ceremony. Do NOT do a task inline without this proposal. Full
21
- doctrine + the reactive net (`agent-gate-check.js`): see
22
- @.claude/rules/agent-entry-gate.md
10
+ ## 0. Entry gate — run the WHOLE dispatch chain automatically
11
+
12
+ On EVERY non-conversational task, run this chain yourself, of your own accord —
13
+ the user should NOT have to ask for it. Three steps, then execute:
14
+
15
+ 1. **Which agent** match the need against the roster with the matcher
16
+ (`_byan/mcp/byan-mcp-server/lib/agent-matcher.js`). A suited agent -> use it.
17
+ NO suited agent -> propose an interview to frame the need, web-research the
18
+ trade's competencies + best practices, create the tailored agent. This is the
19
+ ONE step where the human stays in the loop (creating a new agent).
20
+ 2. **Which runtime** route with `dispatch-router.js`: Codex for execution /
21
+ shell / deploy / devops / browser ; Claude for architecture / refactor /
22
+ quality / planning ; verification stays on Claude ; Fable is not emitted ;
23
+ model + effort scale to complexity. This decision is automatic — no user ask.
24
+ 3. **Execute** — Codex-lane: delegate to Codex via the bridge
25
+ (`codex-bridge.js`: `codex exec` -> unified diff -> YOU apply it ; fall back to
26
+ Claude if Codex is unavailable). Claude-lane: do it on Claude at the chosen
27
+ model. Automatic — no user ask.
28
+
29
+ Proportionate: a trivial task with an existing agent routes directly, no
30
+ ceremony. The human stays required only for (a) creating a NEW agent and (b)
31
+ confirming a destructive action. Everything else — agent match, runtime routing,
32
+ execution — is automatic. Do NOT do a task inline without running this chain.
33
+ Full doctrine + the reactive net (`agent-gate-check.js`) + the runtime routing
34
+ table: see @.claude/rules/agent-entry-gate.md and @docs/intelligent-dispatch.md
23
35
 
24
36
  ## 1. Activation triggers
25
37
 
@@ -94,7 +94,7 @@
94
94
  "name": "byan-byan",
95
95
  "module": "core",
96
96
  "tier": "connector-bound",
97
- "sourceHash": "523ca56a08c8b85edba423e1bfdd0d9c777442bcb266b5a74e65c14814da128d"
97
+ "sourceHash": "91fa54c35848f2e2ddd6210fde0f15fab53d58ce5b36627f90ebcfbf760e09a1"
98
98
  },
99
99
  "byan-byan-v2": {
100
100
  "name": "byan-byan-v2",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-byan-agent",
3
- "version": "2.47.0",
3
+ "version": "2.48.0",
4
4
  "description": "BYAN v2.8 - Intelligent AI agent creator with ELO trust system + scientific fact-check + Hermes universal dispatcher + native Claude Code integration (hooks, skills, MCP server). Multi-platform (Claude Code, Codex). Merise Agile + TDD + 71 Mantras. ~54% LLM cost savings.",
5
5
  "main": "src/index.js",
6
6
  "bin": {