Potion Yjs Dev Browser Test

Purpose

Use Potion as a live behavioral oracle, not as the product under test. The skill records how to isolate one Potion tab offline with dev-browser and then replay the current bug's repro steps. Do not bake one historical repro into the workflow.

Workflow

1. Confirm the user is logged in to the persistent debug Chrome connected at 127.0.0.1:9222.
2. Use the existing debug browser, never a disposable browser, unless the user explicitly asks.
3. Use a disposable or agreed Potion document. Only reset or overwrite content when the current repro requires it.
4. Open two named pages, usually potion-yjs-reference-a and potion-yjs-reference-b, pointing at the same Potion URL.
5. Use per-page CDP to make only B offline. Never use page.context().setOffline(true) for this workflow; it affects the whole browser context and usually disconnects both tabs.
6. Execute the current repro steps exactly:
   • B-only local edits while B is offline
   • A-side online edits while A remains connected
   • B reconnect
   • observe final convergence, selection, history, or presence state
7. Compare the observed Potion result with the local Slate Yjs result. Treat Potion as reference evidence, not automatic proof; confirm the local schema and operation shape are equivalent.