hex-audit 0.6.3 → 0.8.0

package/dist/skills/fuzz-convert/SKILL.md

@@ -0,0 +1,249 @@
+---
+name: fuzz-convert
+description: Convert English-language properties in .hex/fuzz/PROPERTIES.md (produced by the Hex /fuzz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. First adds an entry for every newly accepted Hex invariant that has no property yet (fork of pashov's fizz-convert). Trigger on "fuzz-convert", "convert properties", "fuzz the newly accepted invariants", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".
+---
+
+# Property Conversion Skill — fuzz-convert
+
+> **Hex fork.** pashov's `fizz-convert` (MIT; see `../fuzz/UPSTREAM.md` and `../fuzz/LICENSE`), shipped by Hex as a top-level skill next to `fuzz`. `PROPERTIES.md` is `.hex/fuzz/PROPERTIES.md`, and every entry carries the Hex invariant it fuzzes (`- [ ] **GL-07** (INV-012) — …`). STEP 0 adds entries for invariants the auditor accepted after `/fuzz` ran. Everything else is upstream.
+
+You are an expert Solidity fuzzing engineer working inside a project that was set up by the **fuzz** skill. Your job is to convert English-language properties in `.hex/fuzz/PROPERTIES.md` into Solidity code inside the existing harness, then flip their checkboxes from `[ ]` to `[x]`.
+
+**Arguments**: optional space-separated property IDs (e.g., `GL-01 SP-03`) passed when the user invokes the skill. If no IDs are given, convert ALL properties currently marked `[ ]`.
+
+## Parameters
+
+- `SUITE_DIR`: Solidity suite directory relative to project root (default: `test/fizz`). Use the same value that was passed to the `fuzz` skill when the harness was generated.
+- `META_DIR`: Metadata directory relative to project root (default: `.hex/fuzz/fizz_data`). Use the same value that was passed to the `fuzz` skill.
+- `PROPERTIES.md` means `{PROJECT_ROOT}/.hex/fuzz/PROPERTIES.md` throughout this skill.
+- `FUZZ_SKILL_PATH`: the sibling `fuzz` skill's directory, which holds `references/` and `scripts/`. Take this skill's base directory (Claude Code prints it as `Base directory for this skill: …` when the skill loads) and use `<base directory>/../fuzz`. Only if the base directory is missing, Glob exactly `.claude/skills/fuzz/references/hex-invariants.md` (or `.claude/skills/fuzz/scripts/<script>.js`) for the file you need. Never a broader Glob: pashov's upstream fizz may be installed too.
+- Call the Hex CLI as `npx --no-install hex …`, never `npx hex …`: an unrelated npm package named `hex` exists.
+
+## Checkbox states and how they map to actions
+
+`PROPERTIES.md` uses three states. The action you take depends on BOTH the current checkbox AND whether tagged Solidity for that Spec ID already exists in `Properties.sol` / handlers.
+
+**Tagged Solidity** = a function whose natspec starts with `/// @notice <ID>:` (e.g. `/// @notice GL-05:`). The implementer agents are required to emit this doctag for every property they write, so it is the canonical way to find the existing code for any Spec ID. Search both `{SUITE_DIR}/Properties.sol` and every file under `{SUITE_DIR}/handlers/`.
+
+Action matrix:
+
+| Current checkbox | Tagged Solidity exists? | Action |
+|---|---|---|
+| `[ ]` | NO | **Implement fresh.** Normal pending case. On success → `[x]`. On infeasible/skip → `[-]`. |
+| `[ ]` | YES | **Regenerate.** The user manually downgraded `[x]`→`[ ]` because they want it re-implemented (description changed, prior impl was wrong, etc.). Delete the existing tagged function AND any handler call sites (for `SP-*`), then implement fresh as if it were the row above. On success → `[x]`. |
+| `[x]` | YES | **Skip.** Already implemented. Never re-implement, never overwrite. If the user explicitly listed this ID in arguments, warn and skip. |
+| `[x]` | NO | **DRIFT — stop and warn.** The spec claims it's done but no tagged Solidity exists. This means either the user deleted the function manually without updating PROPERTIES.md, or the doctag was lost. Do NOT silently rewrite the spec. Print a warning naming the ID and ask the user to either restore the function, flip the checkbox to `[ ]`, or flip it to `[-]`. Skip this ID for the rest of this run. |
+| `[-]` | NO | **Leave alone.** Manual / do-not-touch. Never read as a target, never flip, never write Solidity. If the user explicitly listed a `[-]` ID, refuse and tell them to flip it to `[ ]` first. |
+| `[-]` | YES | **Drop.** The user manually downgraded `[x]`→`[-]` because they want the property removed entirely. Delete the existing tagged function AND any handler call sites (for `SP-*`). Leave the checkbox as `[-]`. Report under "Dropped" in the summary. |
+
+**Hard rule**: never modify a `[x]`+YES line and never flip `[x]`→anything automatically except as part of a build-failure rollback for a property you generated in the same run.
+
+---
+
+## STEP 0 (Hex): ADD ENTRIES FOR NEWLY ACCEPTED INVARIANTS
+
+Read `{FUZZ_SKILL_PATH}/references/hex-invariants.md`, then:
+
+1. Run `npx --no-install hex invariant list --status accepted --json`.
+2. An accepted invariant is **new** when no `PROPERTIES.md` line carries its `(INV-NNN)` tag and its `test.property_id` (if any) names no Spec ID in `PROPERTIES.md`.
+3. For each new invariant, append one entry to the right section of `PROPERTIES.md`:
+   - Use the next unused `GL-NN` if it must hold after any call, or the next unused `SP-NN` if it is a postcondition of one handler (give `After:`).
+   - Write it in the format of STEP 2, with the tag: `- [ ] **GL-NN** (INV-NNN) — …`.
+   - Set Guarantee by the usual rule: `SHOULD-HOLD` only with concrete evidence, otherwise `EXPLORATORY`.
+   - Write `Sources: Hex INV-NNN`.
+   - Then record the mapping: `npx --no-install hex invariant set-test INV-NNN --tool fizz --property GL-NN --file {SUITE_DIR}/Properties.sol --status not_written`.
+4. A `PROPERTIES.md` entry without an `(INV-NNN)` tag was added by hand. Before converting it, propose it as a Hex invariant ("Proposing an invariant" in `hex-invariants.md`). Put the new id in its line after the Spec ID and record the mapping as above. It is converted as usual. Tell the auditor it is tracked as *proposed* until they accept it.
+
+If the user passed explicit IDs, these new entries join the working set only if the user named them, or named their `INV-NNN`.
+
+## STEP 1: READ CURRENT STATE
+
+Read in parallel:
+
+1. `.hex/fuzz/PROPERTIES.md` — the source of truth for what needs to be converted
+2. `{SUITE_DIR}/Properties.sol` — where property functions live
+3. `{SUITE_DIR}/Base.sol` — for the `Ghosts` struct, `actors` array, `NUMBER_OF_ACTORS`, available contract instances
+4. `{SUITE_DIR}/Snapshots.sol` — for the `State` struct, `stateBefore` / `stateAfter`, and `_takeSnapshot`
+5. `{SUITE_DIR}/handlers/` — every handler file, to see existing function names, `snapshotBefore()` / `snapshotAfter()` placement, and ghost update conventions
+6. `{META_DIR}/property-plan.md` if it exists — for the ghost/snapshot/wiring tables that back each Spec ID
+7. The relevant in-scope source contracts (only the ones referenced by the properties you are about to convert)
+
+If `.hex/fuzz/PROPERTIES.md` does not exist, stop and tell the user to run `/fuzz` (Step 9) first.
+
+---
+
+## STEP 1.5: RECONCILE SPEC WITH CODE
+
+For every Spec ID in `PROPERTIES.md` (regardless of checkbox state), check whether tagged Solidity exists. The doctag pattern is exact:
+
+```
+/// @notice GL-NN:
+/// @notice SP-NN:
+```
+
+Grep `{SUITE_DIR}/Properties.sol` and `{SUITE_DIR}/handlers/**/*.sol` for each pattern. Build a single in-memory map: `spec_id → {checkbox, has_tagged_solidity, function_name_if_found, file_if_found, handler_call_sites_if_SP}`.
+
+Then classify each ID against the action matrix above. The four action types are:
+
+- **IMPLEMENT** (`[ ]` + NO Solidity) — process in STEP 4 normally.
+- **REGENERATE** (`[ ]` + Solidity) — first delete, then process in STEP 4.
+- **DROP** (`[-]` + Solidity) — delete only, no STEP 4 work.
+- **DRIFT_WARN** (`[x]` + NO Solidity) — print a warning and skip this ID. Do NOT touch the checkbox.
+- **SKIP** (`[x]` + Solidity, or `[-]` + NO Solidity) — no work.
+
+### Deletion procedure (used by REGENERATE and DROP)
+
+For a Spec ID whose tagged Solidity must be removed:
+
+1. **Locate the function block** in `Properties.sol`. Start at the line `/// @notice <ID>:` and read upward to capture any preceding `///` natspec lines that belong to the same block. Read downward through the function signature and body until the matching closing `}` at the function's brace depth. Delete the entire span (natspec + signature + body), plus any single blank line immediately following.
+2. **For `SP-*` only**, scan every file under `{SUITE_DIR}/handlers/` for call sites of the deleted function name. The grep target is the bare function name followed by `(` (e.g. `property_depositIncreasesTotalSupply(`). Delete each such call line. If the call has surrounding comments specific to that property (e.g. `// SP-01 postcondition`), delete those too.
+3. **Do not touch** any other functions, ghost variables, or snapshot fields. If the deleted property was the only consumer of a ghost field or snapshot field, leave the field in place — it is safer to have an unused field than to risk breaking another property's wiring.
+4. After all deletions for this run are queued, perform them in a single edit pass per file (so line numbers don't shift mid-stream).
+
+### Argument-list handling
+
+If the user passed explicit IDs:
+- Apply the matrix above to each requested ID.
+- Requested ID is `DRIFT_WARN` → warn, skip, continue with the others.
+- Requested ID is `SKIP` because already `[x]` + Solidity → warn ("already implemented"), skip.
+- Requested ID is `[-]` + NO Solidity → refuse and tell the user to flip to `[ ]` first (this is the same rule as before).
+- Requested ID does not exist in `PROPERTIES.md` → stop and report.
+
+---
+
+## STEP 2: IDENTIFY PROPERTIES TO CONVERT
+
+Parse `PROPERTIES.md`. The format is:
+
+```
+- [ ] **GL-01** (INV-003) — <english description>. (Category: ...; Guarantee: SHOULD-HOLD|EXPLORATORY; Priority: ...; Sources: ...)
+- [ ] **SP-01** (INV-007) — <english description>. (Category: ...; Guarantee: SHOULD-HOLD|EXPLORATORY; After: <handler>; Priority: ...; Sources: ...)
+```
+
+(Hex) The `(INV-NNN)` after the Spec ID names the Hex invariant the entry fuzzes. Never change or drop it.
+
+The parenthetical fields are metadata; only `After:` affects wiring. **Preserve the entire parenthetical verbatim** when you flip a checkbox — never strip the `Guarantee:` tag, since downstream triage (a violated SHOULD-HOLD = confirmed bug, EXPLORATORY = human review) depends on it. If you add a brand-new property of your own, tag it `Guarantee: EXPLORATORY` unless you can cite a doc/spec/standard or exact identity that makes it SHOULD-HOLD.
+
+Use the action map you built in STEP 1.5. The set of IDs that get Solidity work in STEP 4 is the union of:
+- All IDs classified as `IMPLEMENT`
+- All IDs classified as `REGENERATE` (these will have their existing Solidity deleted first)
+
+`DROP` IDs get deletion-only in STEP 4 (no new Solidity). `SKIP` and `DRIFT_WARN` IDs do nothing.
+
+If the user passed explicit IDs, intersect the working set with their list (per the rules in STEP 1.5).
+
+For each selected property, classify:
+
+| Prefix | Type | Where it lives | Visibility | When it runs |
+|--------|------|---------------|------------|--------------|
+| `GL-` | Global | `Properties.sol` | `public function property_*()` | After every handler call (fuzzer auto-discovers) |
+| `SP-` | Specific | `Properties.sol` | `internal function property_*()` | Called explicitly at the end of a specific handler, after `snapshotAfter()` |
+
+---
+
+## STEP 3: PLAN EACH IMPLEMENTATION
+
+For each selected property, work out:
+
+1. **Function name** — `property_<camelCaseDescription>`. If `property-plan.md` already lists a name for this Spec ID, use that exact name.
+2. **Reads from `stateBefore` / `stateAfter`?** — if yes, list the snapshot fields. If a needed field is missing from `Snapshots.sol`'s `State` struct, you must add it (and update `_takeSnapshot` to populate it).
+3. **Reads from `ghosts`?** — if yes, list the ghost fields. If a needed field is missing from `Base.sol`'s `Ghosts` struct, you must add it AND wire its update into the relevant handler(s).
+4. **Assertion helper** — pick the right one: `eq`, `gt`, `gte`, `lt`, `lte`, `t` (boolean). Always include a descriptive failure message string.
+5. **For SP-* only** — which handler to wire it into. Match against the `After:` field in PROPERTIES.md and the actual function name in `handlers/<Contract>Handler.sol`. The call site is **after** `snapshotAfter()` and after any ghost updates.
+6. **Loop safety** — no unbounded loops in global properties. Loops over `actors` are fine (NUMBER_OF_ACTORS is small).
+
+If any property cannot be implemented as a real assertion (missing source data, requires unbounded iteration, requires state the harness cannot reach), do NOT write a fake assertion. Skip it, **flip its checkbox to `[-]`** (so future runs leave it alone), and report it under "Skipped" in the final summary.
+
+---
+
+## STEP 4: APPLY EDITS
+
+Process in this order:
+
+### 4a. Deletions first (REGENERATE + DROP)
+
+For every ID classified as `REGENERATE` or `DROP` in STEP 1.5, perform the deletion procedure (locate tagged function block, delete it, delete handler call sites for `SP-*`). Do all deletions BEFORE any new insertions, in a single edit pass per file. This keeps line numbers stable and avoids the situation where a regenerated property's new function lands on top of its own old line range.
+
+### 4b. Insertions (IMPLEMENT + REGENERATE)
+
+For each property in the implementation set, in turn:
+
+1. If new ghost fields are needed: edit `Base.sol`'s `Ghosts` struct.
+2. If new snapshot fields are needed: edit `Snapshots.sol`'s `State` struct AND `_takeSnapshot` so the field is populated for both before and after.
+3. Add the property function to `Properties.sol` in the appropriate section (Global properties section for `GL-*`, Specific properties section for `SP-*`). Match the existing comment-banner style. **MANDATORY**: the natspec MUST start with `/// @notice <ID>: <one-line description>` so future runs can find and reconcile this function.
+4. For `SP-*`: edit the relevant handler file in `{SUITE_DIR}/handlers/` and call the property function after `snapshotAfter()`. If ghost updates are needed, add them before the property call.
+
+### 4c. Checkbox flips
+
+After STEP 5 (build) confirms success:
+
+- For each `IMPLEMENT` or `REGENERATE` ID where the new Solidity compiled and (for `SP-*`) the call site is wired: change its checkbox to `[x]`.
+- For each `IMPLEMENT` or `REGENERATE` ID you decided to skip mid-implementation (infeasible, requires harness restructuring, etc.): change its checkbox to `[-]`. **For `REGENERATE` IDs that you abandoned mid-flight, the deletion in 4a still stands** — the user explicitly asked for it to be re-done by downgrading from `[x]`, so leaving the old code in place would contradict their intent.
+- For each `DROP` ID: leave the checkbox as `[-]` (deletion was the whole job; the checkbox is already correct).
+- For each `DRIFT_WARN` ID: do not modify the checkbox at all.
+
+Match by exact Spec ID. Do NOT renumber, reorder, or rewrite other lines. Never modify a line that was already `[x]` and had matching Solidity at the start of the run (those are `SKIP`).
+
+Respect the existing inheritance chain in `{FUZZ_SKILL_PATH}/references/template-map.md` if present — do not invent new files.
+
+---
+
+## STEP 5: BUILD
+
+Run from the project root:
+
+```
+forge build
+```
+
+If `foundry.toml` defines a `[profile.fuzz]` section, prefer:
+
+```
+FOUNDRY_PROFILE=fuzz forge build
+```
+
+Fix any compile errors caused by your edits. Do NOT touch unrelated compile errors that already existed before your changes — report them instead.
+
+If a property you wrote fails to compile and you cannot fix it within 2 attempts:
+- Revert that single property's edits (Properties.sol + any handler wiring + any ghost/snapshot fields you added solely for it)
+- Flip its checkbox to `[-]` so future runs leave it alone
+- Report it under "Failed to compile" in the summary
+
+For a `REGENERATE` ID whose new Solidity fails to compile: do NOT restore the deleted old version. The user downgraded `[x]`→`[ ]` deliberately; restoring the old code would silently undo their intent. Treat this exactly like an `IMPLEMENT` failure — flip to `[-]` and report. The user can manually reinstate the old function from git if they want it back.
+
+---
+
+## STEP 6: REPORT
+
+Print a concise summary:
+
+```
+fuzz-convert results
+
+Implemented (NEW, checkbox flipped to [x]):
+  GL-01  property_solvency
+  SP-03  property_depositIncreasesShares (wired into vault_deposit)
+
+Regenerated (deleted + re-implemented, checkbox stays [x]):
+  GL-05  property_oTokenB_perTokenSolvency
+  SP-02  property_roundTripNoFreeValue (wired into vault_roundTrip)
+
+Dropped (deleted, checkbox stays [-]):
+  GL-12  removed property_oldHelper
+
+Skipped (checkbox flipped to [-]):
+  GL-07  reason: requires unbounded loop over historical state
+
+Drift warnings (NO change made):
+  GL-09  PROPERTIES.md says [x] but no /// @notice GL-09: function found.
+         Please restore the function or flip the checkbox to [ ] / [-].
+
+Failed to compile (reverted, flipped to [-]):
+  SP-09  reason: <error>
+
+Build: PASS / FAIL
+```
+
+Do NOT mark a property `[x]` unless its Solidity exists, the build passes, and (for SP-*) it is actually called from a handler.
+
+(Hex) List the `INV-NNN` next to each Spec ID in the summary, and the invariants STEP 0 added. Converting a property does not run it. Tell the auditor to run a campaign: `/fuzz` Step 10, or `node {FUZZ_SKILL_PATH}/scripts/run_medusa.js {PROJECT_ROOT} --timeout 600`. Then run `npx --no-install hex invariant sync-fuzz` to record the results on the invariants and the board.

package/dist/skills/fuzz-sync/SKILL.md

@@ -0,0 +1,342 @@
+---
+name: fuzz-sync
+description: Reconcile the Hex /fuzz harness (test/fizz, .hex/fuzz) with a changed source tree (fork of pashov's fizz-sync). Detects added/removed/changed contract functions, quarantines stale properties (their Hex invariants then show as broken), regenerates drifted handler stubs, and refreshes the snapshot. Trigger on "fuzz-sync", "resync fuzzing", "sync fuzz harness", "refresh fuzzing properties", "fuzzing drift check".
+---
+
+# Fizz Sync Skill — fuzz-sync
+
+> **Hex fork.** pashov's `fizz-sync` (MIT; see `../fuzz/UPSTREAM.md` and `../fuzz/LICENSE`), shipped by Hex as a top-level skill next to `fuzz`, whose scripts it runs. `PROPERTIES.md` is `.hex/fuzz/PROPERTIES.md`, the metadata lives in `.hex/fuzz/fizz_data/`, and each property's `(INV-NNN)` tag maps it to a Hex invariant. After an applied sync, Step 8 records the result in Hex (`hex invariant sync-fuzz`). Everything else is upstream.
+
+Reconcile a project previously processed by the **fuzz** skill with a changed source tree. This is the re-use entry point: after the user modifies Solidity sources, `fuzz-sync` detects drift, quarantines stale properties, regenerates drifted handler stubs, and refreshes the snapshot — WITHOUT re-running the full 11-step pipeline.
+
+## When to use
+
+- The source contracts under `src/` changed since `/fuzz` last ran.
+- A property in `PROPERTIES.md` fails to compile or references a function that no longer exists.
+- The user added new external functions they want fuzzed.
+- The user wants a "is anything stale?" health check before re-running a campaign.
+
+## Parameters
+
+- `SUITE_DIR`: Solidity suite directory relative to project root (default: `test/fizz`). Use the same value that was passed to the `fuzz` skill when the harness was generated.
+- `META_DIR`: Metadata directory relative to project root (default: `.hex/fuzz/fizz_data`). Use the same value that was passed to the `fuzz` skill.
+- `PROPERTIES.md` means `{PROJECT_ROOT}/.hex/fuzz/PROPERTIES.md` throughout this skill.
+- `FUZZ_SKILL_PATH`: the sibling `fuzz` skill's directory, which holds the scripts. Take this skill's base directory (Claude Code prints it as `Base directory for this skill: …` when the skill loads) and use `<base directory>/../fuzz`. Only if the base directory is missing, Glob exactly `.claude/skills/fuzz/scripts/<script>.js` for the script you need. Never a broader Glob (`**/fizz_sync.js`): pashov's upstream fizz may be installed too, and its scripts write to upstream's paths.
+
+## Arguments
+
+- `--init` — one-time bootstrap: create `{META_DIR}/last-run.json` from the current state. Use this the first time fuzz-sync runs on a project (or when adopting fuzz-sync on a project that was fuzzed before the snapshot format existed).
+- `--only <Contract>` — scope the sync to a single contract name.
+- `--apply` — actually perform the automatic fixes. Without `--apply`, fuzz-sync runs in dry-run mode and only reports drift.
+- `--no-property-quarantine` — skip the property quarantine phase (useful if the user wants to handle stale properties manually).
+
+The default (no flags) runs a dry-run drift report.
+
+## Preconditions
+
+- The project must have been processed by the `fuzz` skill at least once. Look for:
+  - `{PROJECT_ROOT}/{META_DIR}/contracts.json`
+  - `{PROJECT_ROOT}/{META_DIR}/entry-point-selection.json`
+  - `{PROJECT_ROOT}/{SUITE_DIR}/` (suite directory)
+- If any of the above are missing, stop and tell the user to run `/fuzz` first.
+
+---
+
+## STEP 0: REBUILD CURRENT ABIS
+
+The snapshot diff compares against `contracts.json` and `entry-point-selection.json`. Those files reflect the state from the last `/fuzz` run, NOT the current source tree. You must refresh them first.
+
+Run sequentially:
+
+1. `cd {PROJECT_ROOT} && forge build --skip 'test/**/*.sol'`
+
+   The `--skip` flag is critical: if the user's source change broke downstream call sites in `test/`, a plain `forge build` will fail on the harness code — which is exactly the drift fuzz-sync is supposed to fix. Skipping `test/` means we only validate that the SOURCE compiles cleanly, which is all we need to refresh the ABI.
+
+   If the build still fails with `--skip 'test/**/*.sol'`, the source itself has a compile error. Stop and report it. Fuzz-sync cannot proceed without valid source artifacts.
+
+2. `node {FUZZ_SKILL_PATH}/scripts/extract_abis.js {PROJECT_ROOT} --meta-dir {META_DIR}`
+
+   This refreshes `contracts.json` from the latest artifacts. It overwrites the old file in place.
+
+3. **Do NOT re-run `select_functions.js` automatically.** The existing `entry-point-selection.json` encodes the user's prior tier assignments and selection choices. fuzz-sync treats it as the source of truth for what's "in scope" and diffs only within that scope.
+
+   If new contracts have been added that the user probably wants to fuzz, the drift report will surface them and the user can manually add them to `entry-point-selection.json` and re-run fuzz-sync.
+
+---
+
+## STEP 1: HANDLE --init
+
+If the user passed `--init`:
+
+1. Run:
+
+   ```
+   node {FUZZ_SKILL_PATH}/scripts/fizz_sync.js {PROJECT_ROOT} --init
+   ```
+
+2. If the script reports the snapshot already exists, ask the user whether they want to overwrite with `--force` (they usually do NOT — it would erase drift history).
+
+3. Report the number of contracts and properties captured, then stop. No further steps.
+
+---
+
+## STEP 2: RUN THE DRIFT REPORT
+
+Run:
+
+```
+node {FUZZ_SKILL_PATH}/scripts/fizz_sync.js {PROJECT_ROOT}
+```
+
+The script:
+- Reads `{META_DIR}/last-run.json` (created by `--init` or by Step 11 of the main `fuzz` skill).
+- Builds a fresh snapshot from the current `entry-point-selection.json`, source file hashes, and `PROPERTIES.md`.
+- Diffs them and writes `{META_DIR}/sync-report.json`.
+- Prints a human-readable summary.
+- Exits 0 if no drift, 1 if drift was detected.
+
+If exit 0 and no drift, stop and tell the user the harness is already in sync.
+
+Read the JSON report:
+
+```
+{PROJECT_ROOT}/{META_DIR}/sync-report.json
+```
+
+The JSON schema is:
+
+```json
+{
+  "generatedAt": "...",
+  "hasDrift": true,
+  "contracts": {
+    "added":          [{"name":"...", "sourcePath":"...", "functions":[{"signature":"...", "tier":"primary"}]}],
+    "removed":        [{"name":"...", "handlerFile":"...Handler.sol"}],
+    "changed":        [{"name":"...", "functionsAdded":[...], "functionsRemoved":[...], "functionsChanged":[{"oldSignature":"...","newSignature":"...","handlerMethodName":"..."}], "tierChanged":[...]}],
+    "sourcesChanged": [{"name":"...", "sourcePath":"..."}]
+  },
+  "handlers": {
+    "orphan":   [{"file":"...", "contract":"..."}],
+    "modified": [{"file":"..."}],
+    "missing":  [{"file":"..."}]
+  },
+  "properties": {
+    "referencingRemoved": [{"file":"...", "reference":"lender_oldMethod", "reason":"..."}],
+    "fromSnapshot":       [{"id":"GL-01", "checkbox":"x", "functionName":"property_..."}]
+  }
+}
+```
+
+Use this object as the canonical work list for the rest of the skill.
+
+---
+
+## STEP 3: DRY-RUN SUMMARY (ALWAYS)
+
+Regardless of whether `--apply` was passed, print a concise summary to the user that mirrors the report:
+
+```
+fuzz-sync drift report
+──────────────────────
+Added contracts:     N
+Removed contracts:   N
+Drifted contracts:   N  (M added / M removed / M changed functions)
+Orphan handlers:     N
+Stale properties:    N
+Modified handlers:   N  (user-edited since last snapshot)
+```
+
+If fuzz-sync was invoked WITHOUT `--apply`, stop here and tell the user:
+
+> Dry-run complete. Re-run with `--apply` to regenerate handlers and quarantine stale properties, or handle items manually using the report at `{META_DIR}/sync-report.json`.
+
+---
+
+## STEP 4: APPLY — HANDLER REGENERATION
+
+Only run this step if `--apply` was passed.
+
+### 4a. Back up user-modified handlers
+
+For every entry in `report.handlers.modified`, the user has hand-edited that handler since the last snapshot. Regenerating it would destroy their clamping logic. The script already backs up `<file>.pre-sync.bak`, but the user should be warned.
+
+Print a warning listing every modified handler and ask the user whether to proceed. If the user says no, skip to Step 5.
+
+### 4b. Regenerate drifted handlers
+
+Run:
+
+```
+node {FUZZ_SKILL_PATH}/scripts/fizz_sync.js {PROJECT_ROOT} --apply-handlers
+```
+
+The script:
+- Regenerates handler files for contracts listed in `report.contracts.added` and `report.contracts.changed`.
+- Creates `<name>Handler.sol.pre-sync.bak` backups next to each regenerated file.
+- Uses the existing `generate_handlers.js` under the hood with a scoped selection file, so tier assignments are respected.
+
+After the script runs, for each regenerated handler:
+
+1. Read the `.pre-sync.bak` version and the new version.
+2. Port any still-valid clamping bodies and ghost wiring from the backup into the new handler. Functions whose signature did not change can usually be copied verbatim. Functions whose signature changed must be manually rewritten against the new signature.
+3. Keep `/// @notice SP-NN:` doctags intact — they are how `fuzz-convert` and future `fuzz-sync` runs identify which Solidity corresponds to which Spec ID.
+4. For functions that were REMOVED from the source contract, delete the corresponding handler method from the regenerated file AND delete any call sites elsewhere.
+
+### 4c. Handle orphan handlers
+
+For every entry in `report.handlers.orphan`, the contract no longer exists in the selection. Offer the user two choices:
+
+1. **Delete** — remove the handler file entirely and remove its inheritance line from `handlers/Handlers.sol`. Also remove any `contract_handler` field wiring.
+2. **Quarantine** — leave the file in place but rename it `<name>Handler.sol.orphan` so `generate_suite.js` does not re-pick it up, and comment out its inheritance line in `Handlers.sol` with a `// FUZZ-SYNC: orphan — contract removed` marker.
+
+Default to quarantine. Only delete if the user explicitly confirms.
+
+### 4d. Handle missing handlers
+
+For every entry in `report.handlers.missing`, the file disappeared since the last snapshot. If the contract still exists in `contracts.changed` / unchanged, treat this as a regeneration case — re-run the generate step without `--only` scoping (or manually invoke `generate_handlers.js`) to recreate it.
+
+---
+
+## STEP 5: APPLY — PROPERTY QUARANTINE
+
+Skip if `--no-property-quarantine` was passed.
+
+This is the most delicate phase. A property can be stale for several reasons:
+- Its tagged handler function was renamed or removed (detected in `report.properties.referencingRemoved`).
+- A ghost variable it depends on was deleted.
+- The source function it asserts against changed semantics without changing signature (`report.contracts.sourcesChanged`).
+- It no longer compiles at all.
+
+### 5a. Compile-first triage
+
+Run the scoped build that skips non-harness test files:
+
+```
+cd {PROJECT_ROOT} && FOUNDRY_PROFILE=fuzz forge build $(find test -maxdepth 1 -name '*.sol' -exec echo --skip {} \;)
+```
+
+(fall back to plain `forge build ...` without `FOUNDRY_PROFILE=fuzz` if no `fuzz` profile is configured).
+
+The `find ... --skip` wrapper is essential: without it, compile errors in the user's own top-level test files (e.g. `test/MyContract.t.sol`, which is outside the fuzzing harness and NOT managed by this skill) would block the build and prevent fuzz-sync from running its quarantine logic. Those top-level test files are the user's responsibility to fix; this skill only owns `{SUITE_DIR}/`.
+
+If the build FAILS, parse every error. For each error whose location is inside `{SUITE_DIR}/`:
+
+1. Identify the enclosing function (walk up from the error line until you hit a `function <name>(` header).
+2. Check whether that function has a `/// @notice (GL-NN|SP-NN):` doctag — if yes, the Spec ID is the source of truth for reconciliation.
+3. Quarantine the function:
+   - Replace the entire function body with a single `revert("FUZZ-SYNC: quarantined");` statement.
+   - Move the old body into a multi-line comment (`/* ... */`) directly above the function so the user can see the original logic and restore it manually when ready.
+   - Add a single-line annotation above the comment:
+     ```solidity
+     // FUZZ-SYNC: quarantined — <short reason from build error>. Restore by deleting the revert body and uncommenting the block above.
+     ```
+   - `if (false) { ... }` is NOT a valid quarantine strategy — Solidity type-checks dead branches and the original compile error will persist.
+4. If the function had a Spec ID, flip its checkbox in `PROPERTIES.md` from `[x]` to `[~]` and append ` (stale — source changed, re-opened)` to the description. Keep the `(INV-NNN)` tag after the Spec ID as it is.
+5. Rebuild. Repeat up to 3 cycles. If errors persist after 3 cycles, stop and report the remaining errors to the user — they need manual help.
+
+**Important**: do NOT quarantine handler methods this way. If a handler method fails to compile, the fix belongs in Step 4b (handler regeneration) or 4c (orphan handling), not here.
+
+### 5b. Semantic-drift sweep
+
+After the compile triage passes, scan `report.properties.referencingRemoved`. For each entry:
+
+1. Find the enclosing tagged function in the named file.
+2. Read the whole function body.
+3. If the dead reference is the ONLY purpose of the property (e.g., the property exists solely to check a post-condition of a now-removed handler call), quarantine it per the same procedure as 5a.
+4. If the dead reference is incidental (e.g., the property also checks other state), leave it alone but add a `// FUZZ-SYNC: references removed method <name>` marker at the reference site. Rely on the compile triage to catch it on the next cycle if it actually breaks.
+
+### 5c. Source-hash-only drift
+
+For every entry in `report.contracts.sourcesChanged` that did NOT appear in `contracts.changed` (i.e., the source file changed but the ABI did not):
+
+- This is a semantic refactor. Properties still compile but might assert the wrong thing.
+- Do NOT auto-quarantine. Instead, list the affected contracts under a "Review recommended" section in the final report so the user can eyeball the properties tied to those contracts.
+
+---
+
+## STEP 6: REBUILD AND VALIDATE
+
+Run:
+
+```
+cd {PROJECT_ROOT} && FOUNDRY_PROFILE=fuzz forge build $(find test -maxdepth 1 -name '*.sol' -exec echo --skip {} \;)
+```
+
+(fall back to `forge build ...` without the profile variable if no `fuzz` profile is configured).
+
+If it fails, go back to Step 5a for one more cycle. If it has already been through 3 cycles, stop and report.
+
+If it succeeds, proceed to snapshot refresh.
+
+---
+
+## STEP 7: REFRESH SNAPSHOT
+
+Only after Step 6 succeeds and the user is happy with the result:
+
+```
+node {FUZZ_SKILL_PATH}/scripts/fizz_sync.js {PROJECT_ROOT} --refresh-snapshot
+```
+
+This overwrites `{META_DIR}/last-run.json` with the post-sync state. Future `fuzz-sync` runs will diff against this new baseline.
+
+---
+
+## STEP 8: REPORT
+
+Print a concise summary:
+
+```
+fuzz-sync results
+─────────────────
+
+Handlers regenerated:
+  VaultHandler.sol          (3 added, 1 removed, 1 signature changed)
+  LendingPoolHandler.sol    (2 added)
+
+Handlers ported from backup:
+  VaultHandler.sol          (5/6 clamping bodies preserved)
+
+Orphan handlers:
+  OldStakingHandler.sol     quarantined (renamed .orphan)
+
+Properties quarantined:
+  SP-04  referenced removed function lender_oldDeposit
+  SP-07  build error on line 128
+
+Properties untouched (review recommended):
+  GL-02  source hash changed but ABI stable — verify semantic intent
+  GL-09  idem
+
+Build: PASS
+Snapshot refreshed: {META_DIR}/last-run.json
+```
+
+### Record the sync in Hex
+
+After an `--apply` run whose build passed, run:
+
+```
+cd {PROJECT_ROOT} && npx --no-install hex invariant sync-fuzz
+```
+
+Always `npx --no-install hex`, never `npx hex`: an unrelated npm package named `hex` exists. The command marks the invariant of each quarantined (`[~]`) property `broken`. Add a line per affected invariant to the summary, for example `INV-007  broken (SP-04 quarantined)`. Leave the other statuses as the last campaign set them. A dry run changes nothing, so do not run it after a dry run.
+
+### Next actions
+
+Tell the user:
+
+- For newly added functions without handler bodies: re-run `/fuzz` Step 7 for just those contracts, or use the `fuzz-convert` skill if the user also wants to regenerate properties for them.
+- For quarantined properties: either rewrite them manually (flip `[~]` back to `[ ]` in `PROPERTIES.md` and run `/fuzz-convert`), or leave them quarantined.
+- For source-changed contracts without ABI drift: read the diff manually to confirm existing properties still encode the intended semantics.
+
+---
+
+## RULES
+
+- Never run a full fuzz pipeline as part of a sync. Sync is surgical by design.
+- Never regenerate ALL handlers — only the drifted subset.
+- Never auto-delete orphan handlers without user confirmation.
+- Never flip a `[ ]` or `[-]` checkbox to `[x]` in this skill. Only `[x] → [~]` for quarantining is allowed.
+- Always back up files before destructive edits. The `.pre-sync.bak` files are the user's safety net.
+- Always refresh the snapshot at the end of a successful `--apply` run, and NEVER refresh it mid-run before Step 6 passes — that would bake in the broken state.

package/dist/skills/generate-poc.md

@@ -4,16 +4,12 @@ description: "Validate an issue and generate a proof-of-concept test"
 
 # Skill: Generate Proof of Concept
 
-**Recommended model:** Opus
-
 ## Context Assembly
 
 Read:
 - The issue description provided by the auditor
-- Run: `npx hex context --target <relevant_contract>` for focused context
-- `<output_dir>/state-vars.json` — for relevant state variable info
-- `<output_dir>/access-control.json` — for access restrictions
-- `<output_dir>/external-calls.json` — for external call surface (if relevant)
+- The relevant source files (read them in full).
+- Exact facts from the compiler: `npx --no-install hex facts query function <Contract.fn>` (modifiers, calls, reads, writes, external calls), `callers` / `reach` (which entry points reach the bug), `writers <Contract.var>` (who else can change the state the exploit depends on), `layout <Contract>` (storage slots, for `vm.store` setups).
 
 ## Step 0: Understand the Project's Test Infrastructure
 
@@ -160,27 +156,13 @@ If it fails, debug and fix. Iterate until the PoC passes.
 
 ## Output
 
-**Always produce a validation memo** at `<output_dir>/validations/<finding_id_or_short_name>_memo.md`:
-
-```markdown
-# Validation Memo: <Title>
-
-**Verdict:** Valid / Invalid / Uncertain
-**Date:** <YYYY-MM-DD>
-
-## Reasoning
-[Step-by-step reasoning from Step 1]
-
-## Execution Path
-[Traced call path: function1() -> function2() -> ...]
+The validation memo is written by the caller (`/validate-finding` or `/prevalidate`) at `<output_dir>/validations/<id>_memo.md`, with one template for every caller: **Claim**, **Analysis** (the traced path), **Protections evaluated**, **Reality gate**, **PoC** (file and result, or why there is none), **Verdict**. Add the PoC section's content from this skill: the test file path, the command, and the observed impact.
 
-## Protections Considered
-[Existing guards, checks, or mitigations evaluated and why they don't prevent the issue]
+Record the PoC on the card so the board shows it and fix review can re-run it:
 
-## Conclusion
-[If valid: summary of exploit + pointer to PoC file]
-[If invalid: clear explanation of why not exploitable]
-[If uncertain: specific questions for manual investigation]
+```bash
+npx --no-install hex issue validation <id> --verdict reproduced --by <auditor|agent> \
+  --poc test/hex-pocs/<id>_<name>.t.sol --poc-status passing --memo <output_dir>/validations/<id>_memo.md
 ```
 
-If valid, also write the test file to the project's test directory.
+A PoC that cannot be made to pass is evidence too: record `--poc-status failing` with `--verdict uncertain` and say in the memo what blocked it.