docs: write the interim no-apply-mainnet rule into deployments/ - #81
Conversation
Hillary's #75 review proposed this rule explicitly and asked for a yes/no. Yes -- writing it where it has to be seen: the directory itself, not just a table row in CONTRACT_INVENTORY.md someone has to already know to read. States the rule, why (D5/D6, the 57-contract/26-test-file plan, the five undeployed successor names it would permanently occupy), what to do instead (-p <path>, never bare --mainnet or -d against an auto-generated plan), and what's already in this directory including the archived gen-1 plan. Deliberately does not touch CONTRACT_INVENTORY.md's D5/D6 rows here -- #75 is still open on those exact lines with Hillary's pending re-review; cross-linking this file from there is a one-line follow-up once #75 lands, not worth conflicting with it now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
unixwhisperer
left a comment
unixwhisperer
left a comment
There was a problem hiding this comment.
Content's correct — matches the D5/D6 evidence and the mechanism (Clarinet.toml regenerating the plan fresh, not a stale plan file) that we already nailed down across #74/#75/#76. Good call putting the rule in deployments/README.md where it's actually in the way, rather than a row someone has to know to go look for.
One non-blocking note: the "Dependency Audit" check is currently red, but that run is from 2026-10-01T00:04 — before #80 (the Next.js critical RCE fix) merged at 01:20 the same day. It's the same stale pre-existing-vuln failure #80 was tracked against, not anything this PR introduced. Should clear once the branch is updated against current main; flagging so it isn't mistaken for a real blocker before merge.
Approving.
This branch was successfully deployed
2 participants
Summary
Hillary's #75 review proposed this rule explicitly and asked for a yes/no. Yes — writing it where it has to actually be seen:
deployments/README.md, not a row inCONTRACT_INVENTORY.mdsomeone has to already know to check.What it says
clarinet deployments apply --mainnet, with or without-d.contracts/test/, including the five undeployed audit-track successor names it would permanently occupy).-p <path>with an explicit, reviewed plan; prefer thescripts/path.Deliberately not touched here
CONTRACT_INVENTORY.md's D5/D6 rows — #75 is still open on those exact lines, pending Hillary's re-review. Cross-linking this README from there is a one-line follow-up once #75 lands, not worth conflicting with it now.Verification
Docs-only. Suite 258 passed / 1 expected fail (259),
clarinet check211/0 — both unchanged.🤖 Generated with Claude Code