aboutsummaryrefslogtreecommitdiffstats
path: root/CLAUDE.md
diff options
context:
space:
mode:
Diffstat (limited to 'CLAUDE.md')
-rw-r--r--CLAUDE.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/CLAUDE.md b/CLAUDE.md
index 528ee0e..284841a 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -144,6 +144,18 @@ These are about working on the tree rather than about the design:
- **The SPA served in production may be older than this tree.** Check the served
`/a/<hash>/` against `meshbay_hub.api.webapp.ASSET_V` before concluding a fix
is missing. `site/` and the Caddy config have never been deployed
+- **`test_sticky_header.py[firefox]` needs no Firefox instance on the machine,
+ and says nothing about the code when one is there.** The harness launches
+ `firefox --headless --screenshot` with `HOME` pointed at a throwaway
+ directory, which isolates the *profile* and not snap's single instance: with
+ any Firefox already up it prints "Firefox is already running, but is not
+ responding", never loads the page, and the fixture times out at 60 s — eleven
+ errors at setup that look like a regression and are not. Neither
+ `--no-remote` nor `--new-instance` changes it; a failed run also appears to
+ leave a process behind, which blocks the next one. Before reading anything
+ into these: `ps -eo pid,etimes,args | grep firefox`, and re-run against a
+ stashed tree. The `[chrome]` half of the same file covers the same geometry
+ and is the one to trust meanwhile
- **One UI source.** `packages/meshbay-hub/src/meshbay_hub/static/` is the
interface, for the web and the app alike; `packages/meshbay-client/scripts/
sync-ui.js` copies it (`npm run sync-ui`) and CI fails if the copy drifts —