The audit's non-blocking half

.claude/hooks/__tests__/guards.test.mjs

@@ -101,7 +101,9 @@ describe('git-restore-guard', () => {
 
   it('fires on a checkout naming a path that exists', () => {
     const cwd = dirtyRepo()
-    expect(fire('git-restore-guard', { command: 'git checkout -- a.ts' }, { cwd })).toContain('a.ts')
+    expect(fire('git-restore-guard', { command: 'git checkout -- a.ts' }, { cwd })).toContain(
+      'a.ts'
+    )
   })
   it('fires on git restore', () => {
     const cwd = dirtyRepo()

.claude/hooks/__tests__/prose-trigger.test.mjs

@@ -16,7 +16,10 @@ const HOOK = join(dirname(fileURLToPath(import.meta.url)), '..', 'prose-trigger.
 
 /** What the hook says, or '' when it declined. Throws when it exits non-zero. */
 const fire = (toolInput, sessionId = `test-${Math.random()}`) => {
-  const payload = JSON.stringify({ session_id: sessionId, ...(toolInput ? { tool_input: toolInput } : {}) })
+  const payload = JSON.stringify({
+    session_id: sessionId,
+    ...(toolInput ? { tool_input: toolInput } : {})
+  })
   const out = execFileSync('node', [HOOK], { input: payload, encoding: 'utf8' })
   return out.trim() ? JSON.parse(out).hookSpecificOutput.additionalContext : ''
 }

.claude/hooks/__tests__/test-trigger.test.mjs

@@ -48,9 +48,7 @@ describe('test-trigger stays quiet on', () => {
 
 describe('test-trigger reaches a test written through Bash', () => {
   it('fires on a heredoc naming a test path', () =>
-    expect(
-      fire({ command: "cat > src/shared/__tests__/a.test.ts <<'EOF'\nx\nEOF" })
-    ).not.toBe(''))
+    expect(fire({ command: "cat > src/shared/__tests__/a.test.ts <<'EOF'\nx\nEOF" })).not.toBe(''))
   it('fires on a heredoc carrying a test call', () =>
     expect(fire({ command: "python3 - <<'PY'\ns = \"it('works', () => {})\"\nPY" })).not.toBe(''))
   it('stays quiet on a heredoc that writes neither', () =>

.claude/hooks/bulk-edit-guard.mjs

@@ -23,8 +23,8 @@ const REMINDER =
   'A scripted edit fails quietly in three directions: it removes what you did not name, it ' +
   'eats half a sentence in prose and leaves no symbol behind, or it raises before writing and ' +
   'changes nothing. After it runs: `git diff --stat -- <the files you named>` (empty means ' +
-  'nothing happened), `git diff | grep \'^-\' | grep -E \'const |function |export \'` (what ' +
-  'left, by name), and for prose `git diff | grep -E \'^[-+][[:space:]]*(//|\\*)\'`. Not ' +
+  "nothing happened), `git diff | grep '^-' | grep -E 'const |function |export '` (what " +
+  "left, by name), and for prose `git diff | grep -E '^[-+][[:space:]]*(//|\\*)'`. Not " +
   '`--word-diff`, which prefixes every line with a space so those filters return nothing.'
 
 /** Every firing after it asks the question instead of repeating the rule. */

.claude/hooks/git-restore-guard.mjs

@@ -79,7 +79,7 @@ const rest = atRisk.length > 10 ? ', and more' : ''
 const REMINDER = isStash
   ? `These files hold unstaged changes: ${listed}${rest}. \`git stash\` with nothing to stash ` +
     'succeeds anyway, so a later `git stash pop` takes whatever was already on the stack, ' +
-    'possibly another branch\'s work. To carry work to another branch, `git checkout <branch>` ' +
+    "possibly another branch's work. To carry work to another branch, `git checkout <branch>` " +
     'brings it along when nothing conflicts. To measure another commit, use a worktree.'
   : `These files hold unstaged changes: ${listed}${rest}. \`${verb(command)}\` naming a path ` +
     'restores from the index, and for an unstaged file the index is HEAD, so it deletes ' +

.claude/skills/audit/SKILL.md

@@ -13,14 +13,14 @@ finding, including the one-line obvious ones.
 
 Split by what the code shares, not by directory size. One area per run.
 
-| area | what it is |
-| --- | --- |
-| `modbus` | `main/modules/modbusClient.ts`, `modbusServer.ts` and `modbusServer/` |
-| `boundary` | `main/ipc.ts`, `preload/`, `shared/types/ipc.ts`, `main/state.ts`, `main/windows.ts` |
-| `shared` | `shared/` minus `types/ipc.ts`: schemas, migrations, pure helpers |
-| `stores` | `renderer/src/context/` |
-| `client-ui` | `renderer/src/components/client/` |
-| `server-ui` | `renderer/src/components/server/`, `components/shared/`, `containers/` |
+| area        | what it is                                                                           |
+| ----------- | ------------------------------------------------------------------------------------ |
+| `modbus`    | `main/modules/modbusClient.ts`, `modbusServer.ts` and `modbusServer/`                |
+| `boundary`  | `main/ipc.ts`, `preload/`, `shared/types/ipc.ts`, `main/state.ts`, `main/windows.ts` |
+| `shared`    | `shared/` minus `types/ipc.ts`: schemas, migrations, pure helpers                    |
+| `stores`    | `renderer/src/context/`                                                              |
+| `client-ui` | `renderer/src/components/client/`                                                    |
+| `server-ui` | `renderer/src/components/server/`, `components/shared/`, `containers/`               |
 
 ## Before you start
 
@@ -35,17 +35,17 @@ Apply all eight. Do not merge them and do not skip the cosmetic ones.
 
 1. **What the conformance suite cannot see.** The store-versus-component IPC
    rule, the folder-per-component judgement, and anything else CONTRIBUTING
-   states as prose under *The rules no test can see*.
+   states as prose under _The rules no test can see_.
 2. **Duplication.** Search for the shape, not the name. Two functions doing one
    job often share no word, so a search for what one is called returns neither.
    Report identical copies too, because they diverge later. A duplication claim
-   carries its own burden of proof, under *Verification*.
+   carries its own burden of proof, under _Verification_.
    → [WHY: a meter is a claim too](./references/a-meter-is-a-claim.md)
 3. **Dead code.** Unused exports, unreachable branches, config entries pointing
    at deleted paths, comments naming files that are gone.
 4. **Deferred comments.** Every `TODO`, `FIXME`, `for now`, `later`, `until we`,
    with its exact location and text.
-5. **Test coverage.** What is *not* covered. Think like someone with a field
+5. **Test coverage.** What is _not_ covered. Think like someone with a field
    device, not like the author: a unit id of 0 and of 248, an address at 65535
    with a data type needing four registers, a serial port that disappears
    mid-read, a config file from two versions ago.
@@ -60,6 +60,7 @@ Apply all eight. Do not merge them and do not skip the cosmetic ones.
    alone. Count code lines and test lines separately: a file that looks like the
    worst offender is sometimes a thin one with a large test block bolted on, and
    the two call for opposite conclusions.
+
 7. **Architecture fit.** Does this block RTU over TCP, a second client, the
    gateway idea, or anything `CHANGELOG.md` says is coming?
 8. **What modbus-serial actually does.** For `modbus`, `boundary` and `shared`:
@@ -113,11 +114,11 @@ and its output) · `proposal` · `recipe` if reproduced.
 **severity — what the app does to a user decides it, not how much it annoys
 you.**
 
-| | |
-| --- | --- |
+|              |                                                                                                                                                                                                         |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **blocking** | A user gets a wrong answer, a crash, or lost configuration. A malformed frame reaching the socket. A register read as the wrong type. Also: dead code that makes something look covered when it is not. |
-| **annoying** | Right behaviour, wrong construction. Duplication, a rule enforced in one of two places, untested logic. Nothing a user sees today; the next change here is where it bites. |
-| **cosmetic** | Neither. A stale comment, an unused export, a name that misleads. |
+| **annoying** | Right behaviour, wrong construction. Duplication, a rule enforced in one of two places, untested logic. Nothing a user sees today; the next change here is where it bites.                              |
+| **cosmetic** | Neither. A stale comment, an unused export, a name that misleads.                                                                                                                                       |
 
 **size — how much work the proposal is, not how large the defect is.** **S** is
 one file and no decision. **M** touches several call sites or needs a small
@@ -168,14 +169,14 @@ Two exceptions, where the burden runs the other way:
 
 ## What a finding is worth once it is written
 
-| part | trust |
-| --- | --- |
-| the file, the symbol, the evidence | high, and verifiable |
-| the claim, if reproduced | high |
-| the claim, if only read | good |
-| **the recipe** | **low** — the most common defect in an audit is a recipe describing an input that does not trigger the behaviour |
-| **the proposal** | **low** — a guess by someone who did not read the rest of the file |
-| any summary or state | **low** — a compression, and compressions interpret |
+| part                               | trust                                                                                                            |
+| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| the file, the symbol, the evidence | high, and verifiable                                                                                             |
+| the claim, if reproduced           | high                                                                                                             |
+| the claim, if only read            | good                                                                                                             |
+| **the recipe**                     | **low** — the most common defect in an audit is a recipe describing an input that does not trigger the behaviour |
+| **the proposal**                   | **low** — a guess by someone who did not read the rest of the file                                               |
+| any summary or state               | **low** — a compression, and compressions interpret                                                              |
 
 Open the file, reproduce, then decide. Being written down is not evidence.
 

.claude/skills/audit/references/a-meter-is-a-claim.md

@@ -21,7 +21,7 @@ fix. Expanding the glob with `globSync` answers the question that was asked; a
 rule about the shape of the string answers a different one.
 
 **It matched the name and not the thing.** Renaming `rootState` to `clientState`
-with a regex renamed the `clientState` *field* on the store as well, producing
+with a regex renamed the `clientState` _field_ on the store as well, producing
 `clientState.clientState`. The language service knows which binding an
 identifier is on; a search and replace knows only the characters.
 

.claude/skills/audit/references/one-bug-three-reports.md

@@ -3,11 +3,11 @@
 Six areas were audited in parallel. The agents could not see each other, which is
 what makes a refutation reviewer worth having and also what produces this:
 
-| the area | names it as | claim |
-| --- | --- | --- |
-| modbus | `modbusServer.ts removeRegister` | clears a fixed 24 registers where `addRegister` wrote `length ?? 10` |
-| server-ui | `DeleteButton` and `addRegister.zustand.ts submit` | removing a utf8 register blanks unrelated registers past its end |
-| shared | `addressGrouping.ts getRegisterLength` | returns 24 with no `nextAddress`, and takes no `length` parameter at all |
+| the area  | names it as                                        | claim                                                                    |
+| --------- | -------------------------------------------------- | ------------------------------------------------------------------------ |
+| modbus    | `modbusServer.ts removeRegister`                   | clears a fixed 24 registers where `addRegister` wrote `length ?? 10`     |
+| server-ui | `DeleteButton` and `addRegister.zustand.ts submit` | removing a utf8 register blanks unrelated registers past its end         |
+| shared    | `addressGrouping.ts getRegisterLength`             | returns 24 with no `nextAddress`, and takes no `length` parameter at all |
 
 One defect. Three blocking findings. Three different files named, and **none of
 the three is where the fix belongs**: the width is stated in several places that

.claude/skills/handover/SKILL.md

@@ -16,10 +16,10 @@ never from what was interesting.
 Two paths. `/compact` writes its own summary of the conversation, so step 4 has
 no reader on that path and step 4b replaces it.
 
-| next | steps |
-| --- | --- |
-| `/clear`, or a new session | 1, 2, 3, 4, 5 |
-| `/compact` | 1, 2, 3, 4b, 5 |
+| next                       | steps          |
+| -------------------------- | -------------- |
+| `/clear`, or a new session | 1, 2, 3, 4, 5  |
+| `/compact`                 | 1, 2, 3, 4b, 5 |
 
 ## 1. Inventory, by destination
 
@@ -36,13 +36,13 @@ Then sort each item by **where it belongs**, not by how interesting it was.
 `/todo` owns the destinations: invoke it rather than deciding here. Two things
 it does not own:
 
-| what it is | where it goes |
-| --- | --- |
+| what it is                                             | where it goes                        |
+| ------------------------------------------------------ | ------------------------------------ |
 | state: branch, commits, what is green, what is running | the prompt, or the compact paragraph |
-| the next instruction | the user writes it, step 5 |
+| the next instruction                                   | the user writes it, step 5           |
 
-**One question makes it mechanical.** For each item: *if a future session needed
-this and I were gone, where would it look?* A file, then it goes in the file.
+**One question makes it mechanical.** For each item: _if a future session needed
+this and I were gone, where would it look?_ A file, then it goes in the file.
 Nowhere, because it only matters for the next hour, then the prompt. **"It would
 ask me" is the item most likely to be dropped and the one that must be written.**
 
@@ -94,7 +94,7 @@ standing list here, so the paragraph carries itself: state has files, the repo
 answers its own shape, and a sentence repeating either spends the space that was
 actually at risk.
 
-What is left is a judgement about *this* session. Hand over the line to type and
+What is left is a judgement about _this_ session. Hand over the line to type and
 nothing else:
 
 ```sh

.claude/skills/precommit/SKILL.md

@@ -8,7 +8,7 @@ description: Run the checklist before committing or merging — read the diff, l
 ## While you work
 
 **`git add` before you mutate anything.** `git checkout` naming a path restores
-from the *index*, which on an unstaged file is HEAD — so the command undoing one
+from the _index_, which on an unstaged file is HEAD — so the command undoing one
 mutation deletes everything else you wrote in that file.
 
 **A scripted edit leaves no name behind.** After any edit you did not type line
@@ -39,7 +39,7 @@ git diff --staged
 Read **every** changed file, and untracked files in full: a new file has no diff,
 and is where a fresh copy of something the project already owns lands.
 
-Then, against `CONTRIBUTING.md` *Code style* and `CLAUDE.md`:
+Then, against `CONTRIBUTING.md` _Code style_ and `CLAUDE.md`:
 
 - **A store selector returning an object** is a whole-store subscription wearing
   a selector's clothes. One selector per field.
@@ -86,11 +86,11 @@ for minutes, and running it per commit is how a branch stops being worked on.
 **Report what every step above produced.** A waiver covers the permission, never
 the checklist.
 
-| what you are about to do | ask first? |
-| --- | --- |
-| `git commit` | no |
-| `git push`, `gh` | **yes** — the line is whether it leaves the machine |
-| merge | **yes**, and show the squash message first |
+| what you are about to do | ask first?                                          |
+| ------------------------ | --------------------------------------------------- |
+| `git commit`             | no                                                  |
+| `git push`, `gh`         | **yes** — the line is whether it leaves the machine |
+| merge                    | **yes**, and show the squash message first          |
 
 ## 6. Commit
 

.claude/skills/precommit/references/what-a-script-moved.md

@@ -2,14 +2,14 @@
 
 **A split left six section banners naming the wrong thing.** `AddRegister.tsx`
 was 900 lines and 27 components; a script cut it into five files on each `const`
-line. A banner sits *above* the component it introduces, so every one of them
+line. A banner sits _above_ the component it introduces, so every one of them
 stayed behind with the component before it.
 
-| the banner | what ended up under it |
-| --- | --- |
-| `// Min Max components` | `IntervalInputForward` |
-| `// Fixed Or Generator` | `CommentField` |
-| `// MAIN`, `// Comment`, `// Shared submit logic` | nothing, end of file |
+| the banner                                        | what ended up under it |
+| ------------------------------------------------- | ---------------------- |
+| `// Min Max components`                           | `IntervalInputForward` |
+| `// Fixed Or Generator`                           | `CommentField`         |
+| `// MAIN`, `// Comment`, `// Shared submit logic` | nothing, end of file   |
 
 Jens found the first by reading the diff. The sweep that found the other five
 was a script too: