@sylad/cadence 1.7.0 → 1.9.0

package/templates/inventaire.json

@@ -0,0 +1,96 @@
+{
+  "version": 1,
+  "genre": "inventaire",
+  "document": { "slug": "exemple", "sha256": "0000000000000000000000000000000000000000000000000000000000000000" },
+  "pages": 5,
+  "roles": {
+    "titre": "titre d'un document, d'une page ou d'une section",
+    "titre-panneau": "titre d'un panneau ou d'une fenêtre d'interface",
+    "paragraphe": "phrase ou bloc de texte courant",
+    "legende": "texte qui désigne une figure, un tableau ou une échelle de couleurs (« Figure 1 — … »)",
+    "etiquette-figure": "mot ou valeur écrit dans une figure (flèche, axe, courbe, seuil)",
+    "exigence": "énoncé d'une exigence dans une liste d'exigences",
+    "ligne": "ligne d'un relevé ou d'un formulaire, sans autre fonction",
+    "message_erreur": "message qui signale une erreur ou un refus à l'utilisateur",
+    "unite": "unité accolée à une valeur (kt, hPa, m)",
+    "info_bulle": "texte court qui apparaît au survol ou au focus d'un élément",
+    "bouton": "contrôle sur lequel on agit (composant), ou son libellé (texte)",
+    "champ": "zone où l'on saisit une valeur (composant), ou son libellé (texte)",
+    "case_a_cocher": "contrôle à deux états, coché ou non, indépendant des autres",
+    "selecteur": "contrôle qui fait choisir une valeur dans une liste fermée (liste déroulante, boutons radio)",
+    "onglet": "entrée d'une barre qui bascule entre des vues de même niveau",
+    "menu": "liste d'actions ou de destinations qui s'ouvre depuis un contrôle",
+    "liste": "suite d'éléments de même nature affichés les uns sous les autres",
+    "panneau": "zone d'interface qui regroupe des contrôles (composant)",
+    "carte": "zone d'affichage cartographique ou graphique (composant)",
+    "icone": "pictogramme sans texte qui représente une action ou un objet",
+    "badge": "pastille ou marque qui qualifie un élément (statut, compteur)"
+  },
+  "elements": [
+    {
+      "type": "ecran", "id": "exemple#ecran-1", "confiance": "mesure",
+      "source": { "page": 1, "zone": { "x": 0, "y": 0, "l": 1700, "h": 2200 } },
+      "largeur_reference": 1440,
+      "zones": [{ "nom": "entete", "x": 0, "y": 0, "l": 1440, "h": 96, "pct": { "x": 0, "y": 0, "l": 100, "h": 8 } }]
+    },
+    {
+      "type": "composant", "id": "exemple#composant-1", "confiance": "mesure",
+      "source": { "page": 1, "zone": { "x": 120, "y": 600, "l": 240, "h": 64 } },
+      "role": "bouton", "position": { "x": 120, "y": 600 }, "taille": { "l": 240, "h": 64 }, "contenu": "Valider", "ecran": "exemple#ecran-1"
+    },
+    {
+      "type": "etat", "id": "exemple#etat-1", "confiance": "lu",
+      "source": { "page": 2, "zone": { "x": 120, "y": 600, "l": 240, "h": 64 } },
+      "citations": [{ "page": 2, "ligne": 14, "extrait": "le bouton est grisé tant que le formulaire est vide" }],
+      "nom": "vide", "cible": "exemple#composant-1"
+    },
+    {
+      "type": "texte", "id": "exemple#texte-1", "confiance": "lu",
+      "source": { "page": 1, "zone": { "x": 140, "y": 612, "l": 120, "h": 28 } },
+      "libelle": "Valider", "role": "bouton"
+    },
+    {
+      "type": "jeton", "id": "exemple#jeton-1", "confiance": "mesure",
+      "source": { "page": 1, "zone": { "x": 120, "y": 600, "l": 240, "h": 64 } },
+      "categorie": "couleur", "valeur": "#c81e28", "point": { "x": 130, "y": 610 },
+      "contraste": { "texte": "#ffffff", "fond": "#c81e28", "ratio": 5.9 }
+    },
+    {
+      "type": "table", "id": "exemple#table-1", "confiance": "lu",
+      "source": { "page": 3, "zone": { "x": 100, "y": 400, "l": 1500, "h": 300 } },
+      "colonnes": ["Code", "Sens", "Unité"],
+      "lignes": [["T", "température", "K"], ["P", "pression", "Pa"]]
+    },
+    {
+      "type": "gabarit", "id": "exemple#gabarit-1", "confiance": "lu",
+      "source": { "page": 4, "zone": { "x": 100, "y": 300, "l": 1500, "h": 500 } },
+      "nom": "message d'observation",
+      "champs": [
+        { "nom": "date", "obligatoire": true, "format": "AAAAMMJJ" },
+        { "nom": "vent", "obligatoire": false, "format": "entier", "min": 0, "max": 360 }
+      ]
+    },
+    {
+      "type": "schema", "id": "exemple#schema-1", "confiance": "lu",
+      "source": { "page": 5, "zone": { "x": 100, "y": 300, "l": 1500, "h": 900 } },
+      "noeuds": [{ "id": "capteur", "libelle": "Capteur" }, { "id": "serveur", "libelle": "Serveur" }],
+      "flux": [{ "de": "capteur", "vers": "serveur", "libelle": "envoie la mesure", "direction": "de_vers" }]
+    },
+    {
+      "type": "lien", "id": "exemple#lien-1", "confiance": "lu",
+      "source": { "page": 5, "zone": { "x": 100, "y": 300, "l": 1500, "h": 900 } },
+      "figure": "Figure 1 — chaîne de mesure", "passage": { "page": 5, "ligne": 3, "extrait": "comme le montre la figure ci-dessous" }, "constat": "confirme"
+    },
+    {
+      "type": "statut", "id": "exemple#statut-1", "confiance": "lu",
+      "source": { "page": 1, "zone": { "x": 1400, "y": 20, "l": 200, "h": 40 } },
+      "libelle": "Proposal", "couvre": ["exemple#ecran-1", "exemple#composant-1"]
+    },
+    {
+      "type": "silence", "id": "exemple#silence-1", "confiance": "incertain",
+      "source": { "page": 2 },
+      "cause": "le document ne montre aucun écran d'erreur",
+      "question": "Que voit l'utilisateur quand le serveur ne répond pas ?"
+    }
+  ]
+}

package/templates/orchestrate/accept-back.md

@@ -16,3 +16,4 @@ Report: `commits`, `nonVerifie` (what you could not run or check), `choix`, `que
 
 You are one short session of an orchestrated wave: do not launch subagents (the Agent tool is disabled).
 Give your final report as the structured output, not as free text.
+{{tmp}}

package/templates/orchestrate/accept.md

@@ -16,3 +16,4 @@ Report: `commits`, `nonVerifie` (what you could not run or check), `choix`, `que
 
 You are one short session of an orchestrated wave: do not launch subagents (the Agent tool is disabled).
 Give your final report as the structured output, not as free text.
+{{tmp}}

package/templates/orchestrate/fiche.md

@@ -12,3 +12,4 @@ Read the project's CLAUDE.md first, then the sheet, then the code and the tests
 Rank the findings blocking / major / minor, never on taste: a blocking or major finding sends the sheet back to the spec writer (one more pass only), a minor one becomes a note of the lot.
 You are read-only: do not modify, commit, push or run `raf review|ux|done`. Do not launch subagents. Leave `sousTaches` empty: a sheet has no bug to sub-task.
 Give your report as the structured output: counts of blocking / major / minor findings, each finding (severity, file, line, text), what you could not verify, and a one-line verdict.
+{{tmp}}

package/templates/orchestrate/fix-docs.md

@@ -0,0 +1,18 @@
+Work in `{{chemin}}` on lot `{{lot}}` — "{{titre}}" — of its plan, as the librarian (doc-keeper agent).
+The program computed that the commits of the lot touch code without touching the documentation that describes it (cadence.yaml docs.sync). Update the documentation, and nothing else: no code, no test.
+{{repos}}
+Commits of the lot so far:
+{{commits}}
+
+Documentation behind the lot:
+{{constats}}
+
+Read the diff of each commit above (`git show <sha>`), the project's CLAUDE.md, the README, the pages of `docs/`, the CHANGELOG and the news entries; update each document the change makes false or leaves out. A document that the change really leaves true is left alone: say why under "choix".
+Rules: commit each document as soon as it is right, with explicit paths (never `git add -A` or `commit -a`), and a message that cites the lot (`docs({{lot}}): …`); run the project's documentation checks if it has any, and its full test suite and build if a test reads the documents, before reporting; do not push, deliver, run `raf done`, `raf ux` or `raf review`.
+Never run `git checkout` or `git switch` to another commit or branch in this repository: the orchestrator watches it and a moved HEAD breaks the other sessions of the wave. To look at another sha, use a throwaway `git worktree add --detach <tmp> <sha>`, removed afterwards.
+{{elsewhere}}
+Do not stop to ask: an interpretation you settle yourself goes under "choix" with the alternative you did not take; "questions" stays empty. Making no commit is a valid outcome when every document is already true.
+You are one short session of an orchestrated wave: do not launch subagents (the Agent tool is disabled).
+Give your final report as the structured output (commits, tests, build, what you could not verify, choices).
+{{reponse}}
+{{tmp}}

package/templates/orchestrate/fix-minors.md

@@ -25,4 +25,5 @@ You are one short session of an orchestrated wave: do not launch subagents (the
 Give your final report as the structured output (commits, tests, build, what you could not verify, choices).
 {{reponse}}
 {{captures}}
-Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository: give screenshots, snapshots and traces a relative file name only (e.g. `page-home.png`), they land there. Never an absolute path, never the `--output-dir` option (the server's launch argument, which a session cannot set). If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository. {{shots}} If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+{{tmp}}

package/templates/orchestrate/fix.md

@@ -18,10 +18,12 @@ Self-check before handing back (the recurring findings of the reviews), covering
 - documentation: the README and the architecture documentation describe the behaviour, updated in the same commits as the behaviour (and the CHANGELOG);
 - tests: one test per rule of the fiche, named « Rn — … »; with no fiche, one test per business rule of the lot, named after it;
 - no dead code, and no test that cannot fail: a test whose assertion is always true, or that does not exercise the rule it names;
-- screens: for a modified screen, the capture due of each state, at 1440 and 390 px, with a relative file name; a lot with no modified screen owes none, and says so;
+- screens: for a modified screen, the capture due of each state, at 1440 and 390 px, with a file name (where it goes is the Playwright paragraph's rule); a lot with no modified screen owes none, and says so;
 - no false comment: a comment, a docstring or a message never describes a behaviour the code no longer has or does not have.
 A point you cannot hold is written under "choix" or "nonVerifie" of your report, not left unsaid.
 
+Auto-verification once the tests are green, before the review: when the full test suite and the build pass, re-read the complete diff of your fix commits (`git diff <HEAD before your first fix>..HEAD`, run in each repository where you committed a fix: the project and any neighbouring repository above) against the grid of the code-reviewer agent: code bug; architecture drift; docs/architecture.md (or the project's architecture documentation) up to date; edge cases; one test per changed behaviour. What you find in your own fix, fix it at once (a `fix({{lot}}): …` commit) and rerun the suite and the build; touch nothing else. Then write in "resume" a paragraph that starts with « auto-vérification »: what you re-read, what you found and fixed, what you could not hold. It is one reading of the diff, not a second review: no subagent, no new exploration, no re-reading of files the diff does not touch.
+
 If a finding is wrong, say so under "choix" with the reason. Ask (under "questions") only when a fix needs a decision that passes the rule below.
 A question is legitimate only if it names what it would change: the scope of the lot, the architecture, or a costly rollback (data, production, public API);
 otherwise it is a choice: decide, write the alternative you did not take, go on. Minor choices to settle yourself:
@@ -35,4 +37,5 @@ You are one short session of an orchestrated wave: do not launch subagents (the
 Give your final report as the structured output (commits, tests, build, what you could not verify, choices, questions).
 {{reponse}}
 {{captures}}
-Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository: give screenshots, snapshots and traces a relative file name only (e.g. `page-home.png`), they land there. Never an absolute path, never the `--output-dir` option (the server's launch argument, which a session cannot set). If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository. {{shots}} If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+{{tmp}}

package/templates/orchestrate/implement.md

@@ -1,5 +1,5 @@
 Work in `{{chemin}}` on lot `{{lot}}` — "{{titre}}" — of its plan
-(`docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`; read the lot, its notes and sub-tasks, and the project's CLAUDE.md first).
+(`.cadence/raf.yaml`, the legacy `docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`; read the lot, its notes and sub-tasks, and the project's CLAUDE.md first).
 Goal: {{objectif}}
 {{repos}}
 {{fiche}}
@@ -14,10 +14,12 @@ Self-check before handing back (the recurring findings of the reviews). Go throu
 - documentation: the README and the architecture documentation describe the behaviour, updated in the same commits as the behaviour (and the CHANGELOG);
 - tests: one test per rule of the fiche, named « Rn — … »; with no fiche, one test per business rule of the lot, named after it;
 - no dead code, and no test that cannot fail: a test whose assertion is always true, or that does not exercise the rule it names;
-- screens: for a modified screen, the capture due of each state, at 1440 and 390 px, with a relative file name; a lot with no modified screen owes none, and says so;
+- screens: for a modified screen, the capture due of each state, at 1440 and 390 px, with a file name (where it goes is the Playwright paragraph's rule); a lot with no modified screen owes none, and says so;
 - no false comment: a comment, a docstring or a message never describes a behaviour the code no longer has or does not have.
 A point you cannot hold is written under "choix" or "nonVerifie" of your report, not left unsaid.
 
+Auto-verification once the tests are green, before the review: when the full test suite and the build pass, re-read the complete diff of the lot, commit by commit (the commits `raf commits {{lot}}` lists, each with `git show <sha>`; never a `git diff` range, which would take in the commits of other lots) against the grid of the code-reviewer agent: code bug (wrong result, unhandled error, input trusted); architecture drift (a responsibility put in the wrong module, a duplicated block, a layer skipped); docs/architecture.md (or the project's architecture documentation) up to date; edge cases (empty, absent, twice, wrong order, refused); one test per changed behaviour. What you find, fix it at once (test first, a `fix({{lot}}): …` commit) and rerun the suite and the build. Then write in "resume" a paragraph that starts with « auto-vérification »: what you re-read, what you found and fixed, what you could not hold. It is one reading of the diff, not a second review: no subagent, no new exploration, no re-reading of files the diff does not touch.
+
 Decide minor interpretation questions yourself (the wording of a message, a name, a default, the
 reading of an ambiguous line of the lot) and list each one under "choix" in your report, with the
 alternative you did not take — the reviewer re-reads them. Stop and ask (under "questions") only on a real blocker.
@@ -39,4 +41,5 @@ Give your final report as the structured output, not as free text. If the plan i
 {{news}}
 {{commits}}
 {{reponse}}
-Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository: give screenshots, snapshots and traces a relative file name only (e.g. `page-home.png`), they land there. Never an absolute path, never the `--output-dir` option (the server's launch argument, which a session cannot set). If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository. {{shots}} If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+{{tmp}}

package/templates/orchestrate/maquette.md

@@ -11,4 +11,5 @@ Check the sample data of the mockup: recompute the weekday of every date shown (
 Ground every finding in a named rule (Nielsen heuristic, WCAG 2.2 AA criterion) or a measurement, or in a mismatch between the mockup and the sheet. Rank them blocking / major / minor: a blocking or major finding sends the mockup back to the spec writer, a minor one becomes a note of the lot.
 You are read-only: do not modify, commit, push or run `raf review|ux|done`; this review is NOT the `raf ux` verdict (the conformity pass after the code keeps that role). Do not launch subagents. Leave `sousTaches` empty: a mockup has no bug to sub-task.
 Give your report as the structured output: counts of blocking / major / minor findings, each finding (severity, file, line, text), what you could not verify, and a one-line verdict.
-Playwright (browser MCP): this session's Playwright server was launched by the orchestrator with its own output directory, which lies in the orchestrator's run directory, outside the repository. Every screenshot, snapshot and trace you take lands there, so give each one a relative file name only (e.g. `maquette-erreur-390-revue.png`), never an absolute path, never the `--output-dir` option, and never write browser outputs anywhere else; the repository must stay clean.
+Playwright (browser MCP): this session's Playwright server was launched by the orchestrator with its own output directory, which lies in the orchestrator's run directory, outside the repository. {{shots}} Never write browser outputs anywhere else; the repository must stay clean.
+{{tmp}}

package/templates/orchestrate/precheck.md

@@ -2,10 +2,11 @@ Pre-check for lot `{{lot}}` — "{{titre}}" — of the repository `{{chemin}}`,
 Question: is the deliverable of this lot ALREADY in the repository (done by another lot, or by a correction)?
 Goal of the lot: {{objectif}}
 {{repos}}
-Read the lot, its notes and sub-tasks in the plan (`docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`),
+Read the lot, its notes and sub-tasks in the plan (`.cadence/raf.yaml`, the legacy `docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`),
 then look for the deliverable in the code and tests (`git log`, `grep`, reading the files the lot names). Do not
 implement anything and do not run the full test suite: this is a quick look.
 Answer `oui` only when every part of the lot is present, with a proof for each (file:line or commit sha); `partiel` when
 some parts are present (say which); `non` otherwise. When in doubt, answer `non`: an implementation session follows.
 You are read-only: do not modify, commit, push or run `raf start|done|note|review|ux`. Do not launch subagents.
 Give your report as the structured output: `dejaPresent` (oui | partiel | non), `preuves` (the proofs), `resume` (one sentence).
+{{tmp}}

package/templates/orchestrate/review-recheck.md

@@ -4,6 +4,7 @@ treated them. Check that the minor findings fixed are fixed, that the fixes brok
 rest of the lot is still sound: read the diff yourself from the commits that cite the lot
 (`raf commits {{lot}}`, or `git log`), run the checks, report real defects only. A new minor finding
 is reported, not a reason to ask for another pass. This is a code review only.
+Goal of the lot (it takes precedence over the title in the plan): {{objectif}}
 {{repos}}
 {{checks}}
 {{choix}}
@@ -12,3 +13,4 @@ You are read-only: do not modify, commit, push or run `raf review|ux|done`. Do n
 Give your report as the structured output: counts of blocking / major / minor findings, each finding
 (severity, file, line, text), proposed sub-tasks, what you could not verify, and the one-line verdict
 for `raf review {{lot}}`.
+{{tmp}}

package/templates/orchestrate/review-small.md

@@ -2,7 +2,9 @@ Review lot `{{lot}}` — "{{titre}}" — of the repository `{{chemin}}`, followi
 This lot is small: one single pass covers the code review AND the usability review.
 You are given the repository path and the lot id only: read the diff yourself from the commits that
 cite the lot (`raf commits {{lot}}`, or `git log`), run the checks, report real defects only.
+Goal of the lot (it takes precedence over the title in the plan): {{objectif}}
 {{repos}}
+{{integration}}
 {{fiche}}
 {{ux}}
 {{checks}}
@@ -15,4 +17,6 @@ Give your report as the structured output: counts of blocking / major / minor fi
 findings included, each tied to a named rule — Nielsen heuristic or WCAG 2.2 AA criterion — or a
 measurement), each finding (severity, file, line, text), proposed sub-tasks, what you could not
 verify, and the one-line verdict for `raf review {{lot}}`.
-Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository: give screenshots, snapshots and traces a relative file name only (e.g. `page-home.png`), they land there. Never an absolute path, never the `--output-dir` option (the server's launch argument, which a session cannot set). If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+Browser (Playwright): if a Playwright MCP server is available in this session (only in an orchestrated wave: a brief delegated by hand has none), the orchestrator launched it with its own output directory, in the orchestrator's run directory outside the repository. {{shots}} If no such server is available, do not install or start one; if you use the Playwright CLI, write its outputs under the OS temp directory (or the temporary folder the project's CLAUDE.md names), never inside the repository, which must stay clean.
+In an orchestrated wave a capture reaches the run directory, outside the repository, only through the absolute path above: never at the repository root (romans-1440px.png, expenses-390px.png), never through a script or a shell command that writes into the repository.
+{{tmp}}

package/templates/orchestrate/review.md

@@ -1,6 +1,7 @@
 Review lot `{{lot}}` — "{{titre}}" — of the repository `{{chemin}}`, following your agent instructions.
 You are given the repository path and the lot id only: read the diff yourself from the commits that
 cite the lot (`raf commits {{lot}}`, or `git log`), run the checks, report real defects only.
+Goal of the lot (it takes precedence over the title in the plan): {{objectif}}
 {{repos}}
 {{fiche}}
 {{checks}}
@@ -12,3 +13,4 @@ You are read-only: do not modify, commit, push or run `raf review|ux|done`. Do n
 Give your report as the structured output: counts of blocking / major / minor findings, each finding
 (severity, file, line, text), proposed sub-tasks, what you could not verify, and the one-line verdict
 for `raf review {{lot}}`.
+{{tmp}}

package/templates/orchestrate/spec-back.md

@@ -1,7 +1,7 @@
 Spec of the behaviour of lot `{{lot}}` — "{{titre}}" — in `{{chemin}}`, as the spec writer: you write a machine-readable sheet (use cases, rules, contracts, data) BEFORE any code, so that the later steps (review of the sheet, acceptance tests, implementation) share one reference. There is no screen part: only the sheet.
 Goal of the lot: {{objectif}}
 {{repos}}
-Read the lot, its notes and sub-tasks in the plan (`docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`), the project's CLAUDE.md, and the code and tests of the modules the lot touches (the services, controllers or jobs, their tests, the API contracts and error messages already present): the rules already coded are sources, and a new rule must not contradict them.
+Read the lot, its notes and sub-tasks in the plan (`.cadence/raf.yaml`, the legacy `docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`), the project's CLAUDE.md, and the code and tests of the modules the lot touches (the services, controllers or jobs, their tests, the API contracts and error messages already present): the rules already coded are sources, and a new rule must not contradict them.
 {{spec}}
 
 What you produce, in `<dir>/<sujet>/`:
@@ -24,3 +24,4 @@ Report: `fiche` (path of the sheet relative to the repository, e.g. `docs/specs/
 
 You are one short session of an orchestrated wave: do not launch subagents (the Agent tool is disabled).
 Give your final report as the structured output, not as free text.
+{{tmp}}

package/templates/orchestrate/spec.md

@@ -1,12 +1,12 @@
 Spec of the screen of lot `{{lot}}` — "{{titre}}" — in `{{chemin}}`, as the spec writer: you write a static mockup and a machine-readable sheet BEFORE any code, so that the later steps (UX review of the mockup, acceptance tests, implementation) share one reference.
 Goal of the lot: {{objectif}}
 {{repos}}
-Read the lot, its notes and sub-tasks in the plan (`docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`), the project's CLAUDE.md, its charter (existing CSS and variables, neighbouring components, `docs/qa/expectations.md`) and the routes and API contracts already present.
+Read the lot, its notes and sub-tasks in the plan (`.cadence/raf.yaml`, the legacy `docs/plan/raf.yaml`, or the file named by `plan:` in `cadence.yaml`), the project's CLAUDE.md, its charter (existing CSS and variables, neighbouring components, `docs/qa/expectations.md`) and the routes and API contracts already present.
 {{spec}}
 
 What you produce, in `<dir>/<écran>/`:
 1. `maquette.html`: static HTML + CSS, to the project's charter (reuse its variables, fonts and components; invent no style when an equivalent exists), no business JavaScript. Every state is an addressable section: `<section id="etat-vide">`, `etat-chargement`, `etat-erreur`, and `etat-charge` when the screen has data. Every field of the sheet carries `data-testid="<id of the field>"`.
-2. The captures described above, one per state and per width, copied from the Playwright output directory of this wave into the folder (a Playwright capture lands outside the repository: give it a relative file name only, then copy it).
+2. The captures described above, one per state and per width, copied from the Playwright output directory of this wave into the folder (give a capture the absolute path of that directory, as the Playwright paragraph says, then copy it).
 3. `fiche.yaml`, in the format of the template below. Check it with `cadence spec check <fiche>` until it is valid, and derive the QA expectations with `cadence spec qa <fiche>` only if the lot asks for it.
 
 Sheet rules:
@@ -25,5 +25,6 @@ Report: `fiche` (path of the sheet relative to the repository, e.g. `docs/specs/
 
 You are one short session of an orchestrated wave: do not launch subagents (the Agent tool is disabled).
 Give your final report as the structured output, not as free text.
-Browser (Playwright): the orchestrator launched the Playwright MCP server with its own output directory, in the orchestrator's run directory outside the repository: give screenshots, snapshots and traces a relative file name only (e.g. `maquette-vide-1440.png`), they land there. Never an absolute path, never the `--output-dir` option (the server's launch argument, which a session cannot set).
+Browser (Playwright): the orchestrator launched the Playwright MCP server with its own output directory, in the orchestrator's run directory outside the repository. {{shots}}
 {{captures}}
+{{tmp}}

package/templates/orchestrate/ux.md

@@ -1,6 +1,7 @@
 Review the usability and accessibility of lot `{{lot}}` — "{{titre}}" — of the repository `{{chemin}}`,
 following your agent instructions. Read the diff yourself from the commits that cite the lot
 (`raf commits {{lot}}`, or `git log`).
+Goal of the lot (it takes precedence over the title in the plan): {{objectif}}
 {{ux}}
 {{fiche}}
 A proposed sub-task describes an observable bug (a wrong output, a crash, a measured regression); any other minor finding stays a note of this lot, not a sub-task.
@@ -10,4 +11,5 @@ describe a mockup before proposing any redesign, never code it.
 Give your report as the structured output: counts of blocking / major / minor findings, each finding
 (severity, file, line, text), proposed sub-tasks, what you could not verify, and the one-line verdict
 for `raf ux {{lot}}`.
-Playwright (browser MCP): this session's Playwright server was launched by the orchestrator with its own output directory, which lies in the orchestrator's run directory, outside the repository. Every screenshot, snapshot and trace you take lands there, so give each one a relative file name only (e.g. `page-home.png`, `home-390px.png`): the lead will look at them in that directory. Never an absolute path (such as one under `/tmp`), never the `--output-dir` option (it is the server's launch argument, which a session cannot set), and never write browser outputs anywhere else; the repository must stay clean.
+Playwright (browser MCP): this session's Playwright server was launched by the orchestrator with its own output directory, which lies in the orchestrator's run directory, outside the repository. {{shots}} Never write browser outputs anywhere else; the repository must stay clean.
+{{tmp}}