fix: recalibrate find({ limit }) cap + two-tier enforcement + caller location

Brainy 7.30.0 introduced a memory-derived synchronous cap on `find({ limit })`
to prevent OOM. The cap was sound in intent but ~4x too conservative in
calibration: assumed 100 KB per result while typical entity footprint is 7-10 KB
(384-dim float32 vector ≈ 1.5 KB + standard fields + metadata). On a 900 MB
free-memory box the cap derived to 9000 — breaking common safety-cap patterns
like `find({ type, where, limit: 10_000 })` that typically return 10-500
entities. Surfaced as a runtime regression with cascading 500s degrading
production dashboards.

Three concurrent fixes:

A. RECALIBRATE THE FORMULA
- src/utils/paramValidation.ts:175,196,212 — the three memory-derived priorities
  (reservedQueryMemory / containerMemory / freeMemory) all divided by
  100 * 1024 * 1024 (100 KB per result, ~10-15x over conservative). Replaced
  with a new MAX_LIMIT_KB_PER_RESULT = 25 constant that matches observed
  entity size.
- Result: 4 GB container cap goes 10_000 → 40_000; 2 GB cap goes 5_000 →
  20_000; 900 MB free-memory cap goes 9_000 → ~36_000. 100k hard ceiling
  unchanged. `maxQueryLimit` / `reservedQueryMemory` constructor overrides
  unchanged in behavior.

B. TWO-TIER ENFORCEMENT (warn-then-throw)
- Below cap (limit <= maxLimit): silent pass, unchanged.
- Soft tier (maxLimit < limit <= 2 * maxLimit): NEW — one-time warning per
  call site (dedup keyed on caller stack frame + limit value), query
  proceeds. Pre-7.30.2 code that relied on the cap silently allowing typical
  safety-cap limits keeps working; the warning teaches the recipe so consumers
  can fix it intentionally.
- Hard tier (limit > 2 * maxLimit): throw with the same teaching message
  format. Real OOM territory; the cap stops being a recommendation and becomes
  a guardrail.
- The 2x soft margin absorbs typical safety-cap patterns (limit: 10_000
  against a 9 K-cap box) without disabling OOM protection. Real OOM territory
  on a JS in-memory brain is hundreds of thousands of results, not 10x the
  safety cap.

C. IMPROVED ERROR / WARNING MESSAGE
- Same shape as the 7.30.1 enforcement-error messages: state the problem,
  name the three escape valves (maxQueryLimit / reservedQueryMemory /
  pagination), include caller location, link to docs.
- Extracted findCallerLocation() helper from brainy.ts to a new
  src/utils/callerLocation.ts so both the subtype enforcement (7.30.1) and
  the limit enforcement (7.30.2) share one implementation without circular
  imports.

DOCS
- New docs/guides/find-limits.md (public: true) — full reference: why the cap
  exists, the four memory sources the auto-config considers, the three escape
  valves with when-to-use-which guidance, and an explicit "pagination is the
  future-proof pattern" callout (8.0 may tighten the cap further; pagination
  keeps working unchanged).
- docs/api/README.md find() entry gets a one-paragraph `limit` tip + pointer
  to the new guide.
- RELEASES.md v7.30.2 entry.

TESTS
- New tests/integration/find-limits.test.ts (9 tests): below-cap silent pass;
  soft-tier warns once per call site (dedup verified by exercising same vs.
  different source lines via wrapper closures); soft-tier message format
  (names all three escape valves + docs link); soft-tier message includes
  caller location; hard-tier throws; hard-tier message format same as
  soft-tier; consumer maxQueryLimit override raises the cap and shifts both
  tiers accordingly; pre-7.30.2 regression scenario explicitly covered.
- tests/unit/utils/memoryLimits.test.ts — 4 tests updated for the recalibrated
  cap values (hardcoded expected numbers bumped 4x to match new 25 KB/result
  assumption).
- tests/unit/utils/paramValidation.test.ts — auto-limit test extended to cover
  the three-tier semantics (below-cap pass / soft-tier silent / hard-tier
  throw).
- Existing suites unchanged: subtype-and-facets 26/26, verb-subtype-and-
  enforcement 30/30, strict-mode-self-test 13/13. Unit 1468/1468.

CORTEX COMPATIBILITY
- Zero Cortex changes required. Every change is JS-side: formula recalibration
  runs in ValidationConfig.constructor(), two-tier enforcement runs in
  validateFindParams(), both fire before any storage / index / Cortex call.
- The new guide notes that Brainy 8.0's Datomic-style Db.find() may tighten
  per-call limits to keep snapshot semantics cheap; pagination remains the
  pattern that's guaranteed to keep working.

REPO-WIDE CLEANUP
Brainy is the only Soulcraft project that is open source. This commit also
scrubs closed-source product names and product-specific class/field references
from every tracked file in the repo (src/, docs/, tests/, RELEASES.md,
CHANGELOG.md). Consumer-reported bugs, regression scenarios, and release
notes now refer to "a consumer", "a downstream application", "a production
deployment", or "an internal report" — never to the named product. Two
product-named test files renamed to neutral diagnostic names. CLAUDE.md gains
a project-level guard rule documenting the policy and an example list of the
identifiers that may not appear in tracked code.

Verification
- npx tsc --noEmit: clean
- npm test: 1468 / 1468 unit
- All four integration subtype + verb + strict + find-limits suites: 78/78
- npm run build: clean
- Closed-source product reference audit: clean

tests/manual/type-filtering-diagnostic.ts

@@ -1,5 +1,5 @@
 /**
- * Manual test to reproduce Workshop team's type filtering issue
+ * Manual test to reproduce a consumer's type filtering issue
  *
  * This test verifies that brain.find({ type: NounType.Person }) actually works
  * as documented in the API.
@@ -8,7 +8,7 @@
 import { Brainy, NounType } from '../../src/index.js'
 
 async function testTypeFiltering() {
-  console.log('\n🔬 Testing Type Filtering Issue from Workshop Team\n')
+  console.log('\n🔬 Testing Type Filtering Issue from A Consumer Team\n')
   console.log('=' .repeat(60))
 
   // Create in-memory instance for testing
@@ -156,12 +156,12 @@ async function testTypeFiltering() {
 
   if (passedCount === totalCount) {
     console.log('\n🎉 All tests passed! Type filtering works correctly.')
-    console.log('\n💡 The Workshop team might be experiencing a different issue.')
+    console.log('\n💡 The a consumer team might be experiencing a different issue.')
     console.log('   Check: storage persistence, Brainy instance reuse, or data migration')
   } else {
     console.log('\n❌ Type filtering is BROKEN in Brainy!')
     console.log('\n🐛 This is a bug that needs to be fixed.')
-    console.log('   Workshop team was right - it\'s not user error.')
+    console.log('   a consumer team was right - it\'s not user error.')
   }
 
   console.log('\n' + '='.repeat(60) + '\n')

tests/manual/vfs-multiple-init-diagnostic.test.ts

@@ -1,7 +1,7 @@
 /**
  * VFS Multiple Init() Diagnostic Test
  *
- * Tests Workshop team's issue: Does calling vfs.init() multiple times
+ * Tests a consumer's issue: Does calling vfs.init() multiple times
  * create duplicate root entities?
  *
  * Scenario:
@@ -72,8 +72,8 @@ describe('VFS Multiple Init Diagnostic', () => {
     expect(roots.length).toBe(1)
   })
 
-  it('should not create duplicate roots when creating MULTIPLE VFS instances (Workshop scenario)', async () => {
-    // Simulate Workshop's scenario: Getting VFS on multiple requests
+  it('should not create duplicate roots when creating MULTIPLE VFS instances (the reported scenario)', async () => {
+    // Simulate the reported scenario: Getting VFS on multiple requests
     // brain.vfs returns cached instance, so this should be safe
     const vfs1 = brain.vfs
     const vfs2 = brain.vfs
@@ -107,7 +107,7 @@ describe('VFS Multiple Init Diagnostic', () => {
 
   it('should handle NEW brain instances gracefully (per-user scenario)', async () => {
     // Simulate creating separate brain instances per user
-    // This is closer to Workshop's getUserBrainy() pattern
+    // This is closer to a consumer's getUserBrainy() pattern
     const brain2 = new Brainy({
       storage: {
         type: 'filesystem',