Distillation

Date: Sep 16, 2026

• 🔴 (13:34) User-provided embedding code states telemetry must never break the embedding path; failures in the telemetry hook are isolated from embedding execution.
• 🔴 (13:34) User-provided embedding code defines lastSelfHealProbeAt as the epoch milliseconds of the last self-heal re-probe; 0 means never and is primed on the first tick.
• 🔴 (13:34) User-provided stream-consumption code requires that a host logger/sink must never interrupt stream consumption.
• 🔴 (13:34) User-provided worker-resolution code distinguishes module runtimes as follows: CJS uses __filename, which is always defined; ESM uses import.meta.url.
• 🔴 (13:34) User-provided worker-resolution code states the relevant ESM value is always defined there, while retaining a shim so the source remains natural.
• 🟡 (13:34) The embedding worker path selects workerPrefix as "../" when selfUrl.endsWith(".ts"), otherwise "./".
• 🟡 (13:34) The embedding runtime seeds lastOomCap from the persisted known-bad cap so an upward re-probe does not immediately retry a previously failing cap.
• 🟡 (13:34) After a native worker reports that it cannot parse the model, the embedding runtime forces WASM for the replacement worker.
• 🟡 (13:34) Jujutsu workflow guidance loaded for this repository: use jj, not Git, for mutations when .jj/ exists; never use interactive flags; always pass -m "msg" for describe/commit operations; verify mutations with jj st and jj log; prefer stable letter-based change IDs; do not rewrite immutable commits; use jj undo or jj op restore <op-id> for recovery.
• 🟡 (13:34) Jujutsu working-copy semantics noted: @ is itself a mutable commit with automatic snapshotting and no staging area; bookmarks do not auto-advance; after jj commit, content is in @- and the new @ is empty; jj new creates a new empty change rather than committing the current one.
• 🟡 (13:34) Jujutsu conflict guidance noted: operations can create commits containing conflicts rather than failing; inspect with jj st, resolve markers manually, and do not use interactive jj resolve.
• 🟡 (13:35) Current six-step work plan, preserving order and state: 1. “Address native resolver review findings with fail-first regressions” — completed, high priority; 2. “Finish cgroup headroom and admission review findings” — in progress, high priority; 3. “Prove critical guards with parent failures and mutation checks” — pending, high priority; 4. “Run complete validation and freeze exact candidate” — pending, high priority; 5. “Obtain independent correctness and security reviews” — pending, high priority; 6. “Commit completed Jujutsu change and report root causes” — pending, medium priority.