[mikkel]

Pending demo apply operations could replace manual edits/additions, undo could erase subsequent edits, and MARVIS replies could reappear after clearing/loading a conversation. Transient model-catalog failures also stayed cached, while incomplete SSE prefixes could be accepted as complete output.

Project runs now use immutable inputs/settings plus revision/generation checks before applying or publishing. Manual changes invalidate unsafe undo. MARVIS clear/load cancels and invalidates pending chat, persona and portrait work while valid persona apply/undo preserves live conversation. Catalog fallbacks retry, credential transitions invalidate rendered picker/pricing state, and all six inline completion clients require an explicit terminal event or successful finish reason with nonblocking cleanup.

Validation:

• Full examples JS suite: 125 passed (including 37 lifecycle, 26 stream and 12 catalog regressions).
• Python example checks: 1 + 34 passed; offline checker passed for 29 JS / 21 Python fixtures.
• All six inline modules parse; diff checks passed.
• Covers edits/add/delete during generation/apply, success and undo controls, MARVIS clear/load/late-finalizer races, discarded direction recovery, EOF/truncation/pricing, stalled stream cancellation and auth/catalog races.

Compatibility / release:

• Undo intentionally becomes unavailable after subsequent manual changes. Saved JSON formats, dependencies and standalone/file:// use remain compatible; no new relative module imports.
• Incomplete streams reject rather than publishing a prefix; failed requests are not automatically replayed.
• Feature branch only; Pages is configured for master. No merge, release, deployment, credential changes or paid inference.
• Tests exercise real inline functions with mocked DOM/transports; no browser or native visual walkthrough was used for this fix pass.

Related drafts: 255BITS/patchling#16 and 255BITS/patchling-py#34. This repository currently has no PR validation workflows/checks; results above are local. Pages API confirms legacy deployment source master at /.