Join our community: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
contracts/stream_contract/test_snapshots/ is tracked in git (per the .gitignore mismatch already flagged separately) but there's no explanation anywhere of what these snapshot files are for, when they're regenerated, or what a contributor should do if their local test run produces a diff against a committed snapshot. This is the kind of tooling detail that blocks a first-time contributor's PR when their cargo test output unexpectedly differs.
Acceptance criteria
Files to touch
contracts/stream_contract/test_snapshots/
contracts/stream_contract/README.md
Out of scope
- Fixing the
.gitignore mismatch (tracked separately)
- Changing the snapshot testing framework
Why this matters
contracts/stream_contract/test_snapshots/is tracked in git (per the.gitignoremismatch already flagged separately) but there's no explanation anywhere of what these snapshot files are for, when they're regenerated, or what a contributor should do if their local test run produces a diff against a committed snapshot. This is the kind of tooling detail that blocks a first-time contributor's PR when theircargo testoutput unexpectedly differs.Acceptance criteria
contracts/stream_contract/README.md) explaining snapshot purpose and regeneration commandFiles to touch
contracts/stream_contract/test_snapshots/contracts/stream_contract/README.mdOut of scope
.gitignoremismatch (tracked separately)