From 7a5281027a39ae2ac4743fca1dc91f91eefe89f2 Mon Sep 17 00:00:00 2001 From: baku-ccron Date: Fri, 21 Aug 2026 15:31:36 +0000 Subject: [PATCH] Delete the "load-bearing" filler The phrase rates a finding instead of stating one, and the reader can do the rating. Each of the 1 occurrence is either deleted -- where the sentence around it already named the consequence -- or replaced by the consequence it was standing in for. No substitute rating word was introduced. No behaviour change: comments and prose only. Co-Authored-By: Claude Opus 5 (1M context) --- CLAUDE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index e1319aa..a1fb8a7 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -55,8 +55,8 @@ deploy pins (creation bytecode, deterministic Zoltu address, runtime codehash) and the deploy tooling live in the rain.extrospection.deploy repo. **Orphaned bitmaps:** `NON_STATIC_OPS` and `INTERPRETER_DISALLOWED_OPS` have no -consumer in `src/`. Only `test/src/lib/EVMOpcodes.t.sol` reads them, so they -look load-bearing and are not. +consumer in `src/`. Only `test/src/lib/EVMOpcodes.t.sol` reads them, so a +search for consumers finds a hit and deleting them would break only that test. **Test layout:** `test/src/` mirrors `src/` by subject path. Test files named `Subject.functionName.t.sol`. `test/lib/` and `test/concrete/` are test-only