meta-dream-naplisted

# meta-dream-nap The NAP: a light, frequent consolidation of ONLY the cwd's altitude chain (project -> ancestors -> anchor). It exists because the full dream is tree-wide and heavy; skipping consolidation at a compaction loses detail, and silently cherry-picking the full dream's steps leaves a half-consolidated store. A nap does the chain-internal basics fast and REPORTS what it deferred. **REQUIRED BACKGROUND:** `bitranox:meta-dream-tree` -> `references/dream-core.md` - the shared core (mode, capture-first, backup+manifest, dedup semantics, routing prompt, verification, tiers) lives there and applies here unchanged; this file only carries the nap's SCOPE DELTA. The storage spec is `bitranox:meta-self-improve` -> `references/memory-backend.md`. ## Scope (the delta) The nap's scope is the cwd's ALTITUDE CHAIN ONLY: the project level, each ancestor level, and the anchor. SIBLING projects, sibling departments, and other trees are OUT OF SCOPE - a nap never reads or writes them (the acceptance harness asserts they stay byte-identical). Everything cross-sibling belongs to `bitranox:meta-dream-tree`; everything cross-tree to `bitranox:meta-dream-crosstree`. **The one carve-out is CAPTURE (step 1), and only at the level that OWNS the fact's pointer.** Capture routes by SUBJECT, and `meta-self-improve`'s dedup rule requires an existing fact to be upserted at its owning level - which is sometimes a sibling. Without the carve-out a nap that learns something about a sibling-owned f