feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law

The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.

- The reserved-name write door DIES: add/update/relate/updateRelation
  metadata bags accept EVERY name (confidence, type, id, data, level,
  content, ...) as ordinary user fields — indexed, filterable, sortable,
  aggregatable, identical to any other field. The remap/enforce/warn
  machinery, the reservedFieldPolicy config (now a typed init refusal),
  and the compile-time metadata key bans are all removed. The one write
  refusal left: keys spelled 'system.*' (namespace forgery), now enforced
  on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
  nested verbatim under 'metadata', sealed by a format stamp — by-name
  storage discrimination is unsound once colliders are admitted. Legacy
  flat records stay readable forever through the shape-aware splitters
  (sound for them: the old door refused colliders). Time travel rides the
  same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
  excludeFields/indexedFields knobs and their silent-[] holes are gone;
  bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
  the frozen 'system.type' column (addToIndex sort, affinity tracking,
  cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
  pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
  (bare 'visibility' was a silent no-op under the law — VFS/system
  entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
  reads the bag first (colliders were absent-shadowed by its own guard)
  and never serves system addresses from the bag; blob history refs read
  the bag shape-aware; migration transforms now receive ONE normalized
  view (engine fields + nested bag) regardless of stored era, and stray
  flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
  gates-green): all ten collider names + plumbing names written as user
  fields, verified verbatim + queryable across live reads, flush+reopen,
  a forced epoch rebuild, and asOf time travel; relation mirror; forgery
  refusals; legacy flat-record compat. 8/8 green.

Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).

src/db/fieldAddressing.ts

@@ -174,23 +174,26 @@ export function readEntityFieldAddress(
       : null
 
   if (address.scope === 'system') {
-    // Entity views carry system scalars top-level; raw storage shapes carry
-    // them inside the stored metadata record (where `type` is spelled `noun`).
-    // Read top-level first, then the record — never the user's namespace.
+    // System scalars live at the record's top level, NEVER in the user's
+    // bag — a user field named `confidence` must be unreachable from
+    // system.confidence (and vice versa). Entity views carry the scalars
+    // top-level directly; record-derived views spell the type `noun`.
     const top = rec[address.field]
     if (top !== undefined) return top
-    if (bag) {
-      if (address.field === 'type') return bag.type ?? bag.noun
-      return bag[address.field]
-    }
+    if (address.field === 'type') return rec.noun
     return undefined
   }
 
-  // User scope. The write-path remap guarantees the user can never OWN a
-  // field named like a system scalar (those lift top-level at write), so a
-  // bare system name reads as ABSENT — reading the stored record's reserved
-  // key here would re-create the shadow this module exists to kill. Same for
-  // plumbing and the legacy 'noun' spelling.
+  // User scope: the bag IS the user's namespace, authoritative — EVERY name
+  // reads from it, engine spellings included (`bag.confidence` is the user's
+  // confidence field under the field-addressing law).
+  if (bag) return bag[address.field]
+
+  // No bag at all: a LEGACY flat record (pre-nested-bag storage). Its keys
+  // matching system/plumbing names are the ENGINE's — the pre-law write door
+  // refused user colliders — so a bare system name reads as ABSENT rather
+  // than resurrecting the shadow this module exists to kill. Same for the
+  // legacy 'noun' spelling.
   if (
     SYSTEM_ENTITY_SCALARS.has(address.field) ||
     PLUMBING_FIELDS.has(address.field) ||
@@ -198,7 +201,6 @@ export function readEntityFieldAddress(
   ) {
     return undefined
   }
-  if (bag) return bag[address.field]
   return rec[address.field]
 }