core/vault
Shay 1ac4284f21
feat(vault): wire vault-recall E2 re-thaw per ADR-0006 (W-004) (#251)
Closes W-004 wiring debt surfaced by L2 audit (#238) and predicted
by L1 audit's forward note (#237). ADR-0006 §"Integration Points"
states: "Vault recall re-activates the region to E2 transiently,
then lets it cool again." Prior to this commit, vault.recall()
returned entries with no energy field at all — the re-thaw was
spec-only.

Changes:
- vault/store.py: import EnergyClass / EnergyProfile from
  core.physics.energy. Define module-level _VAULT_RECALL_RETHAW_ENERGY
  singleton (raw=0.50, energy_class=E2, mid-band). Both .recall() and
  .recall_batch() stamp each returned entry with the re-thaw profile
  via a new "energy_profile" key in the result dict.
- tests/test_vault_recall_rethaw.py: 6 tests pinning the contract —
  recall returns E2 profile, recall_batch returns E2 profile,
  singleton is byte-identical across calls (replay determinism),
  empty vault is no-op, min_status filtering preserves the field,
  raw value sits unambiguously in E2 band [0.37, 0.62).

Architectural notes:
- The re-thaw is *declared* by the vault, not derived through the
  energy operator. ADR-0006 makes the assertion directly; vault
  recall is the moment the assertion applies.
- The singleton (rather than a per-call construction) preserves
  byte-identical replay: same recall sequence => identical
  EnergyProfile object => stable trace if downstream folds it.
- Cool-down per ADR-0006 is downstream field propagation's
  responsibility via FieldEnergyOperator's natural recency decay.
  Once the recalled entry is no longer being injected into the
  active field state, recency drops and energy class falls.
- "energy_profile" is added to recall result dicts, alongside the
  existing "epistemic_state" field. Existing consumers (generate/
  stream.py:169, chat/runtime.py:1643, vault/decompose.py:124,179,
  session/context.py:347) ignore unknown keys — no breakage.

Unlocks W-005 (energy-modulated surface readback) — now that E0/E2
distinction exists at the runtime data shape, downstream readback
modulation can become meaningful instead of moot.

Verification:
- tests/test_vault_recall_rethaw.py: 6 passed
- tests/test_vault_*.py: 48 passed, 4 skipped (no regression)
- core test --suite smoke: 67 passed
- core test --suite cognition: 120 passed, 1 skipped
- core test --suite algebra: 82 passed, 50 skipped
- scripts/verify_lane_shas.py: 7/7 match pinned SHAs (byte-identity preserved)
2026-05-24 19:40:29 -07:00
..
__init__.py feat(dialogue-fluency): wire multi-turn dialogue runtime 2026-05-15 21:05:59 -07:00
decompose.py feat(epistemic): Leak C read-side audit — INV-24 callsite registry, Leak C fully closed 2026-05-17 09:48:39 -07:00
store.py feat(vault): wire vault-recall E2 re-thaw per ADR-0006 (W-004) (#251) 2026-05-24 19:40:29 -07:00