Delete the "load-bearing" filler

[thedavidmeister]

Removes the banned load-bearing filler from this repo's committed source.

The phrase rates a finding instead of stating one, and the reader can do the rating.
Where the surrounding sentence already named the consequence, the phrase is simply
deleted; otherwise it is replaced by the consequence it was standing in for. No
substitute rating word ("crucial", "key", "critical", "the crux", "significant",
"notably") was introduced anywhere in the diff.

Closes nothing — no issue exists for this. Part of an org-wide sweep; one PR per
affected repo. GitHub code search finds only some of the forms, so the sweep was run
against fresh clones of all 151 org repos, matching load[-_ ]?bearing case-insensitively
plus a check for the phrase wrapped across two comment lines.

Occurrences removed

File	Count
CLAUDE.md	1

QA

• Discriminating tests: n/a — nothing in the diff changes behaviour, so there is no
  behaviour for a test to discriminate.
• Mutations applied: n/a — the diff is comments and prose only. mutation-probe mutates
  source lines and asks whether the suite kills them; this diff changes no source line,
  so every mutant it could generate is a mutant of code this PR did not touch.
• Oracle: the code each comment describes. Every rewrite states the consequence the
  phrase was gesturing at, read off the surrounding implementation rather than invented.
• Category check: the request is "remove every occurrence from committed source";
  this repo's occurrences are all removed and a re-grep over the branch finds none.

Summary by CodeRabbit

• Documentation
  • Clarified the architecture documentation regarding opcode lists used by tests.
  • Documented that removing these lists would affect testing only, not production functionality.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8e10a7aa-facd-49bc-9943-a466ccb3ede8

📥 Commits

Reviewing files that changed from the base of the PR and between e22a887 and 7a52810.

📒 Files selected for processing (1)

• CLAUDE.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The architecture documentation clarifies that NON_STATIC_OPS and INTERPRETER_DISALLOWED_OPS are consumed by test/src/lib/EVMOpcodes.t.sol and are not load-bearing in src/.

Changes

Documentation clarification

Layer / File(s)	Summary
Document opcode consumers CLAUDE.md	The documentation identifies the test-suite consumer of the two opcode bitmaps and retains their non-production status.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 7a528

This PR makes a localized documentation-only wording change and does not alter product behavior, runtime configuration, or permissions. No actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: removing the banned "load-bearing" filler phrase from CLAUDE.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/drop-filler-phrase

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}