Fizz Sync Skill, fizz-sync

Reconcile a project previously processed by the Fizz skill with a changed source tree. This is the re-use entry point: after the user modifies Solidity sources, fizz-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 fizz 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 fizz skill when the harness was generated.
• META_DIR: Metadata directory relative to project root (default: fizz_data). Use the same value that was passed to the fizz skill.

Arguments

• --init, one-time bootstrap: create {META_DIR}/last-run.json from the current state. Use this the first time fizz-sync runs on a project (or when adopting fizz-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, fizz-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 fizz 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 fizz first.

---