Files
ratatoskr/persistent-memory.d/2026-07-06-playwright-no-python-playwright-module-in-the.md
T
vh ff1f9ca1e8 memory: /snapshot — #368 silo test passed; two-tier migration; stores scrubbed
- #368 (user,character) memory silo test DONE + PASSED live (WT b127):
  write-side conjunctive {end_user,agent_self} scoping + read-side cross-
  character isolation both proven end-to-end; betty (throwaway) deleted,
  Sindra intact. Full record in persistent-memory.d/2026-07-18-368-silo-
  test-passed.md. Retired the stale "silo test in progress" in-flight blocks.
- Two-tier migration: split 152 over-threshold dated entries into
  persistent-memory.d/ detail files, leaving one-line pointers in the index
  (startup load ~196KB -> ~53KB; bodies now load on demand).
- Tier-3 stores scrubbed clean (memory 0 / affect 0, provider restarted
  empty); persistent-memory + detail file updated to reflect the scrub.
2026-07-17 21:39:18 -07:00

618 B

[2026-07-06] Playwright: no python playwright module in the venv; use NODE playwright + an explicit executablePath. Shared box browsers live at /opt/ms-playwright build 1223; npm i playwright (latest) wants build 1228 -> "Executable doesn't exist" mismatch. Fix: chromium.launch({ executablePath: '/opt/ms-playwright/chromium-1223/chrome-linux64/chrome' }) (+ export PLAYWRIGHT_BROWSERS_PATH=/opt/ms-playwright). A node script drives the SPA (pick agent -> open -> assert transcript). The Playwright DOM check is the only lens that catches SPA JS-render bugs — unit tests can't reach them.