swactor/docs/DOCUMENTING.md
Developer 548396ba4a feat: in-browser runtime, WebSocket gateway, dashboard improvements
- NodeAddr abstraction replacing SocketAddr across distribution crate (~30 files)
- Core wasm32 compatibility: web-time, cfg-gated threads, wire encoding extraction
- WebSocket transport (browser) with GatewayControl protocol
- WebSocket gateway (native) with session routing and control protocol
- BrowserRuntime API: JS actor support, connect/spawn/send/tick
- Dashboard: extracted HTML to static files, gossip protocol panel with
  membership event log, visual fixes, click-to-filter, worker-colored rows

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 17:51:36 +00:00

7 lines
No EOL
462 B
Markdown

When requested to document your changes:
- read the `docs/` folder
- summarize your changes and add them to the `docs/development_history`
- use the extant files as a guide for how you should write the document
- add a section `verifying` that shows how a user can verify the changes work as expected
- check the relevant md and svg files in `docs` and add any changes
- add new docs to the folder if necessary, but do not clutter