spotbugs(OPM) suppress OPM_OVERLY_PERMISSIVE_METHOD project-wide

Defers the 25-site scope-tightening pass until after the planned
package-architecture refactor. Same rationale and decision recorded in
workspace/crossrepostatus.md alongside the parallel BAF suppression.

Why suppress instead of fix now:
- Current jllama package layout groups production code in
  net.ladenthin.llama + a thin sibling package set. Any method called
  only by same-package callers is flagged as "could be package-private".
  Correct today, false tomorrow once the refactor splits the root
  package into proper layers — cross-layer calls then need public.
- Tightening every site now creates mechanical churn the refactor
  would revert.
- TODO marker added to workspace/crossrepostatus.md under the
  "Affects BAF + jllama (multi-package repos)" section so the rule
  can be re-enabled deliberately the week the layers stabilise.

Cross-repo alignment: same suppression added to BAF
(BitcoinAddressFinder/spotbugs-exclude.xml, 33 sites there).

Author: claude

spotbugs-exclude.xml

@@ -205,4 +205,32 @@ SPDX-License-Identifier: MIT
         <Bug pattern="USBR_UNNECESSARY_STORE_BEFORE_RETURN"/>
     </Match>
 
+    <!--
+        fb-contrib OPM_OVERLY_PERMISSIVE_METHOD ("Method is declared more
+        permissively than is used in the code base") suppressed PROJECT-WIDE.
+
+        Rationale (kept aligned cross-repo with BitcoinAddressFinder):
+        - Current package layout groups most production Java in
+          net.ladenthin.llama + a thin sibling package set. Any method
+          called only from same-package callers is flagged as "could be
+          package-private". Those answers are correct today but unstable:
+          once the planned package-architecture refactor splits the root
+          package into proper layers, methods that today are correctly
+          package-private will need to become public to cross the new
+          boundaries. Tightening now produces mechanical churn highly
+          likely to be reverted by the refactor.
+
+        - Cross-repo decision + per-category breakdown recorded in
+          workspace/crossrepostatus.md ("OPM scope-tightening — after
+          package refactor"). The same rule is suppressed in BAF.
+
+        TODO: re-enable this rule (delete this Match block) once the
+        package refactor has settled — at that point genuine "method
+        exposed beyond its actual call site" findings become stable
+        signals worth fixing.
+    -->
+    <Match>
+        <Bug pattern="OPM_OVERLY_PERMISSIVE_METHOD"/>
+    </Match>
+
 </FindBugsFilter>