Persist recorded entities for first-Brief derivation

[eamirian]

What changed

• persist the exact PREPARED Entity Snapshot already produced by each reviewed recorded-source mapping
• return mapped Entity Snapshots from recorded-source admission and exact replay
• require the authorized build to cover both connect_sources and map_concepts
• project the durable Entity as a first-class Intelligence resource after a fresh read

Why

Recorded admission previously persisted the acquisition receipt, source snapshot, and canonical Observation but discarded the activation-bound Entity Snapshot produced by the same declarative mapping. That left the shared Intelligence pipeline without the durable Observation → Entity baseline needed for Shift → Signal → Brief.

This change preserves that exact lineage without adding domain code, network acquisition, freshness claims, or new authority. The executor still cannot invent evidence; Core validates and persists the Pack-derived entity under the same product, activation, build-authority, and immutable-record preconditions.

Validation

• focused recorded-source admission: 5 passed
• recorded-source, source-mapping, prepared-ledger, resource-projection, and public-boundary matrix: 63 passed, 1 skipped
• Ruff check and format: passed
• diff integrity: passed

Boundary

This is the shared evidence-to-entity prerequisite only. It does not derive Shifts or Signals, synthesize a canonical Brief, provision authority, change the MCP surface, or modify a Domain Pack.