diff options
Diffstat (limited to 'CLAUDE.md')
| -rw-r--r-- | CLAUDE.md | 23 |
1 files changed, 22 insertions, 1 deletions
@@ -122,7 +122,7 @@ that produced it. | Looking for | Read | |---|---| | What a label means (`C1`, `H3`, `NS6`, `T3`, `C5b`, `W2`, `E9`, `F1`, `AV4`, …) | `docs/MESHBAY_DESIGN.md` §13 | -| What one member can cost the others (`AV1`–`AV12`) | §13.5b — the newest category, and the one the first three reviews had no question for | +| What one member can cost the others (`AV1`–`AV15`) | §13.5b — the newest category, and the one the first three reviews had no question for | | Trust model, and what the project may and may not claim | §2 | | Identity, devices, admission, recovery, the keypair bundle | §3 | | Cryptography, key hierarchy, the group and chat envelopes | §4 | @@ -148,6 +148,27 @@ These are about working on the tree rather than about the design: 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 — **never edit `packages/meshbay-client/ui/` by hand** +- **A test fixture narrower than production tests the fixture — and when it + writes down *why* it has to be narrow, that is a bug report nobody filed.** + `test_federation.py` built its MHP envelopes by hand without an `aud`, and + `test_public_groups_toggle.py` signed its own token with a comment saying + `_issue_mhp_token` "binds `_hub_sk_pem` at import time, before the lifespan + loads it, so it cannot be used from a test", and another saying PyJWT + rejects a token carrying `aud` when decode is given none. Both observations + were exactly right. Between them, MHP could not complete a single + authenticated request between two real hubs, and the hub announced itself as + `meshbay.org` whatever it was configured as — for a month, with the suite + green. When a test has to route around the code to run, the thing it routed + around is the finding. Federation's tokens now come from the real issuer + +- **A global's state is not a given, in a test least of all.** One assertion — + that a refusal never logs the address — took three attempts: `caplog` saw + nothing because the app configures logging, then a handler on the module's + own logger saw nothing because an earlier test had raised its level, then + because `logger.disabled` was left True. Each version passed alone and + failed in the full run. Pin what you depend on (level, `.disabled`, + `logging.disable`) or assert on a value instead of on a side effect + - **A blocking call in an async handler is the whole instance's problem.** `mail._send` is `smtplib` with a ten-second timeout, and it was called straight from four handlers: while the MTA thought about it, nothing else was |