@sylad/cadence 0.11.0 → 0.12.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.
@@ -3,9 +3,12 @@ This lot is small: one single pass covers the code review AND the usability revi
3
3
  You are given the repository path and the lot id only: read the diff yourself from the commits that
4
4
  cite the lot (`raf commits {{lot}}`, or `git log`), run the checks, report real defects only.
5
5
  {{ux}}
6
+ {{checks}}
6
7
  {{choix}}
8
+ 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.
7
9
  You are read-only: do not modify, commit, push or run `raf review|ux|done`. Do not launch subagents.
8
10
  Give your report as the structured output: counts of blocking / major / minor findings (usability
9
11
  findings included, each tied to a named rule — Nielsen heuristic or WCAG 2.2 AA criterion — or a
10
12
  measurement), each finding (severity, file, line, text), proposed sub-tasks, what you could not
11
13
  verify, and the one-line verdict for `raf review {{lot}}`.
14
+ Browser (Playwright): if a Playwright MCP server is available in this session, it was launched by the orchestrator 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.
@@ -1,7 +1,9 @@
1
1
  Review lot `{{lot}}` — "{{titre}}" — of the repository `{{chemin}}`, following your agent instructions.
2
2
  You are given the repository path and the lot id only: read the diff yourself from the commits that
3
3
  cite the lot (`raf commits {{lot}}`, or `git log`), run the checks, report real defects only.
4
+ {{checks}}
4
5
  {{choix}}
6
+ 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.
5
7
  You are read-only: do not modify, commit, push or run `raf review|ux|done`. Do not launch subagents.
6
8
  Give your report as the structured output: counts of blocking / major / minor findings, each finding
7
9
  (severity, file, line, text), proposed sub-tasks, what you could not verify, and the one-line verdict
@@ -2,9 +2,11 @@ Review the usability and accessibility of lot `{{lot}}` — "{{titre}}" — of t
2
2
  following your agent instructions. Read the diff yourself from the commits that cite the lot
3
3
  (`raf commits {{lot}}`, or `git log`).
4
4
  {{ux}}
5
+ 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.
5
6
  You are read-only: do not modify, commit, push or run `raf review|ux|done`. Do not launch subagents.
6
7
  Ground every finding in a named rule (Nielsen heuristic, WCAG 2.2 AA criterion) or a measurement;
7
8
  describe a mockup before proposing any redesign, never code it.
8
9
  Give your report as the structured output: counts of blocking / major / minor findings, each finding
9
10
  (severity, file, line, text), proposed sub-tasks, what you could not verify, and the one-line verdict
10
11
  for `raf ux {{lot}}`.
12
+ 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.