mirror of
https://github.com/vitorpamplona/amethyst.git
synced 2026-10-06 03:38:23 +00:00
Claude
1794ed5249
Two unrelated things that both amount to not paying for something nobody asked for. **`MirrorSyncThroughputTest` is a benchmark, so it now opts in.** It preloaded a million events and pulled them over a real WebSocket on every ordinary test run: 4,584 s of `:geode:test`'s 4,636 s — 98.9% of the module's test time for one test that asserts nothing about correctness and reported `skipped` at the end anyway. Every other benchmark in the module is already gated this way (`perf.LoadBenchmark`). It now bails before building anything, and enables on `-DrunLoadBenchmark=true` OR on any of its own sizing properties, so every invocation its kdoc documents still runs it — naming a size is itself the opt-in. Measured after: the test takes 5 ms, the module takes 64.8 s, and `-DsyncN=2000` still prints a throughput number. **The agent text stream QUIC path is kept but no longer advertised, and nothing starts it.** Nothing in the deployed network publishes those previews. So: - `SUPPORTED_COMPONENTS` drops `0x8006` and the leaf capabilities drop `0xF2D1`/`0xF2D2`/`0xF2D4`. A capability is a standing promise to every peer that reads our KeyPackage, and one for a path nobody exercises costs something and buys nothing. The captured reference KeyPackage in our own conformance vector does not advertise `0x8006` either. - The Android chat screen no longer builds a stream watcher and dials the brokers a kind:1200 advertises. That was a UDP connection attempt to a third-party endpoint on every feed change, on behalf of a feature with nothing to show — a service we start, not a capability we hold. The implementation stays and stays tested: `:marmotQuic`, the codecs, `amy marmot stream`, the direct path, the certificate pinning and the interop tests are all untouched. The module README records the posture and the exact way back. Three tests asserted the old advertisement and were reworked rather than deleted. The role-enforcement gate is still covered — the tests now build leaves that explicitly carry the roles, which is the better shape anyway, since a test that exercised the gate through OUR default was really asserting the default and stopped testing the gate the moment it changed. A new test pins the new default: our KeyPackage carries no role and is therefore refused by a group requiring one. That refusal is the deliberate cost, so it is asserted rather than discovered. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016kCuA6tc4JQzHPCDd39GHq