Repository navigation
Add AGENTS.md and a running list of Seaport 1.7 candidates - #1428
Conversation
AGENTS.md states the one rule for this repo (the deployed 1.6 bytecode must not change), the layout, the pinned toolchain, and the build and test commands. CLAUDE.md imports it. docs/Seaport-1.7-candidates.md collects ideas from past PRs and issues that would change the deployed bytecode, each linked to its source. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude Code reads AGENTS.md directly, so the CLAUDE.md import is not needed. The root file now covers only the bytecode rule, layout, and commands; test/foundry/AGENTS.md covers precompiled artifacts, profiles, and fuzz-test pitfalls. The 1.7 list drops the optimizer runs note, since max runs reproduces the deployed bytecode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟡 Changes recommended
The documentation incorrectly equates DifferentialTestAssertionFailed() with a behavioral mismatch, although it can also wrap a failure shared by both implementations.
1 open issue
What changed in this PR
This documentation-only PR adds contributor guidance for preserving deployed Seaport 1.6 bytecode and collects bytecode-changing ideas for a possible future release. No Seaport 1.7 release is planned.
Changes:
- Documents repository layout, build commands, and the deployed-bytecode constraint.
- Adds Foundry-specific guidance on profiles, precompiled artifacts, and fuzz-test pitfalls.
- Collects linked future-release candidates and adds a README link.
| File | Description |
|---|---|
test/foundry/AGENTS.md |
Adds Foundry build and test troubleshooting guidance. |
README.md |
Links to the Seaport 1.7 candidate list. |
docs/Seaport-1.7-candidates.md |
Collects potential future changes and their sources. |
AGENTS.md |
Documents repository-wide constraints, layout, and commands. |
Review effort: Balanced
assertPass raises it for any run that didn't end in the expected passing status, including failures both implementations share, so it doesn't by itself mean the optimized and reference builds disagree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review: safe to merge, 9/10. This PR is docs only. Every command, path, profile and env var it names exists in the branch and matches CI. Nothing in it is security-sensitive: each 1.7 item links to an issue or PR that is already public. P0: none
Optional: In |
Name the settings the optimized profile inherits from the default profile, note that tests need both builds, add the single bytecode check command, and correct who closed seaport-core#10. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks @tomhirst. All three are in 4d25eda:
|

Stacked on #1427. It retargets to
mainonce that merges.AGENTS.mdat the root covers the one rule (the deployed 1.6 bytecode must not change), the layout, and the commands.test/foundry/AGENTS.mdadds what's specific to the Foundry tests: precompiled artifacts, profiles, and fuzz pitfalls. Claude Code readsAGENTS.mddirectly, so there's noCLAUDE.md.docs/Seaport-1.7-candidates.mdis a running list of ideas from past PRs and issues that would change the deployed bytecode, each linked to its source. No 1.7 is planned; this keeps them in one place.Docs only, no code changes.
🤖 Generated with Claude Code