Fix @aware resolution when folding across template boundaries

[calebporzio]

Fixes #186

Root cause

Two separate bugs, both surfaced in #186:

1. Folding bakes in wrong @aware values across template boundaries (the actual <flux:select> crash).

When a foldable component that consumes @aware props sits at the root of a template — i.e. it's rendered through an @include partial or from a nested component's view — its real parent only exists at runtime. The folder resolved @aware lexically, found nothing, and baked in the prop defaults.

Concretely: <flux:select.option> declares @aware(['variant', 'indicator']). Rendered through a partial inside <flux:select variant="listbox">, it folded to the default variant's native <option> markup instead of the listbox's <ui-option> markup. flux.js then finds no & > ui-option children in the listbox, treats the list as empty, and hits create._activatable.activate(true) in a state it never expects — the uncaught TypeError kills init for every select on the page. This matches the reporter's repro matrix exactly (inline children fold correctly because the parent is lexically visible; slot/include boundaries crash).

2. The temporary fold cache goes stale across processes (Undefined array key at Unblaze.php:87).

Since #116 the temporary fold cache persists between compiles, but Unblaze::$unblazeReplacements only ever lived in memory in the process that compiled the file. Any other process reusing a cached compiled file (with [STARTCOMPILEDUNBLAZE:…] tokens baked in) missed the lookup, logged the undefined key warning the reporter found, and silently aborted the fold.

Fix

• The folder no longer folds a component whose @aware props can't be resolved from the template itself (not passed directly, no value from a lexically visible parent, and no component ancestors in the template) — it renders normally and @aware resolves at runtime.
• hasAwareDescendant() now also detects @aware consumers hiding behind @include/@each and nested component templates (recursive source scan), so folded parents still push their data for that runtime lookup.
• @unblaze replacement content is now stored from within the compiled file itself (base64-encoded), so any process that renders a cached file repopulates the replacement map. Stale files from older versions purge the temp cache and abort the fold gracefully once.

Tests

• ComparisonTest: @aware through an include partial and through a nested component (both fail on main, byte-identical to Blade after the fix).
• FluxProTest: the exact @blaze folding breaks Flux <flux:select> — uncaught _activatable TypeError destroys all selects on the page #186 scenario — <flux:select variant="listbox" searchable> with flux:select.option + flux:select.option.create emitted from an @include and from a nested component.
• FolderTest: unfoldable at template root with unresolvable @aware; still folds when the prop is passed directly.
• UnblazeTest: fold succeeds when the temp compiled file was cached by a previous process (fails on main with the reporter's exact Unblaze.php:87 error).

Full suite: 220 passed (including flux + flux-pro comparison suites run locally).

🤖 Generated with Claude Code

[github-actions]

Benchmark Result: Default

Attempt	Blade	Blaze	Improvement
#1	351.25ms	15.89ms	95.5%
#2	350.29ms	15.66ms	95.5%
#3	350.60ms	15.60ms	95.6%
#4	347.62ms	15.52ms	95.5%
#5	349.67ms	15.69ms	95.5%
#6 *	355.23ms	16.22ms	95.4%
#7 *	355.36ms	15.83ms	95.5%
#8	350.30ms	15.74ms	95.5%
#9	350.09ms	15.51ms	95.6%
#10	348.18ms	15.85ms	95.4%
Snapshot	351.19ms	15.83ms	95.5%
Result	350.19ms (~)	15.68ms (~)	95.5% (~)

_{Median of 10 attempts (* = outlier, excluded from result), 5000 iterations x 10 rounds, 46.16s total}

_{To run a specific benchmark, comment /benchmark <name> where name is one of: attributes, aware, class, default, forwarding, merge, named-slots, no-attributes, slot}