WIP: preserve Next development and output-settlement work

[0thernet]

Recovery checkpoint, not merge-ready

This draft preserves retained Next development/HMR and output-settlement source that was not previously pushed. It is intentionally separate from the active production/compiler successor in PR #57.

The checkpoint retains all 60 source, fixture, test, metadata and generated-artifact paths exactly as found, rooted at older commit d683d9cd3f4bd4ce098881697bb67f1c65a5b921. It includes mixed older Vite 7/8 and compiler-map work. Do not merge the branch wholesale or assume those older copies supersede current main or PR #57.

Work to recover

• Next 16.2.12 development adapter, native CSS entry/loaders, compiler-revision convergence, last-good recovery, and explicit stable-variable/theme restart boundary.
• Provider-neutral isolated output-settlement helper and tests.
• Packed Next development/HMR fixtures and bounded diagnostics/restart harness.
• Associated public entrypoints, metadata and candidate generated artifacts.

Evidence and remaining work

Publication-safety scan found no actual private-host paths or credential markers in the exact 60-file checkpoint; all files were ordinary non-symlink source/artifact files, and git diff --check passed. No build, native HMR acceptance, aggregate check or release validation was run for this recovery commit. Historical package-version and README claims are unvalidated candidate text, not support or publication evidence; the existing v0.5.5 tag must never move.

A taker must compare against current main and PR #57, retain only distinct unfinished work, update to a new unoccupied successor version after the active production train, and complete independent source/privacy/process-custody review, native HMR/recovery tests, artifact regeneration, final checks and current-head CI. Preserve all newer production adapter, source-map, provenance and lifecycle fixes. No release or consumer adoption is authorized by this checkpoint alone.

The migration owner continues implementation and coherent pushes; this draft exists so the work cannot be lost or stranded locally.

[0thernet]

Recovery checkpoint 1853342 (tree b65596dac060ca961caa964c348d72441872d176) adds the portable packed-Bun metafile observer in a separate diagnostic-only directory. Both finite observation modes, raw import metadata, plugin results and path hypotheses are retained; consumer and private output are explicit. No historical raw receipts, private host paths or production export changes were published. Pure checks: 7 tests, 71 assertions, 20 ms; no real build or browser run. Original experimental evidence is preserved separately. The prior Next-development candidate is still unvalidated and must be compared against current main and PR57; do not merge this recovery branch wholesale or move the existing v0.5.5 tag.

[0thernet]

Independent takeover audit at 1853342: do not merge this old mixed candidate wholesale. Common baseline is v0.5.3 (d683d9c); current main 5cd105b already delivers mapped compiler transforms and stronger privacy/union policy. Unique successor slices are output settlement (2 files), Next-development core/tests (5), packed fixture (13), and native diagnostics/restart verification (5). Keep the separate five-file packed-Bun diagnostic bundle independent. Reconcile onto current main in that order without importing old package/lock/generated/Vite/Bun/compiler code. Required repairs: next-dev-session currently uses the legacy CSS serializer; native smoke writes survivors:0 and success before collecting browser.close and lacks outer cancellation custody; aggregate test/type selection omits new diagnostics/restart/native evidence. Preserve current production gates and the finite Next 16.2.12 / Webpack 5 / genuine Node 24 profile. Atomic HMR only; defineVars/createTheme changes require restart. Output settlement is provider-neutral and not a publication barrier. This is source-review evidence, not runtime acceptance. PR remains a draft recovery checkpoint.