Developer guide

If you've never touched the code, Architecture internals is where to start — it covers the module map, the 1Hz run-loop walkthrough, on-disk persistence, and the concurrency model. From there, IPC contract lists every Tauri command the renderer can call and the events the backend emits, and Contributing is the quick reference for branch workflow, the test suites, and what CI checks. Cross-platform testing covers how to exercise Windows and Linux behaviour from a macOS dev machine.

The user-facing Architecture section covers the high-level "how Entracte works" — useful as a refresher but not where to start when you're editing the code.

Plugin API design is the review-gate design doc for the longer-term local-only plugin API (#156) — it settles the security boundary, manifest schema, permission model, and threat model before any implementation.

Releases describes the tag-triggered pipeline that cuts and signs bundles, and where the in-app updater fits in. The API references (Rust via rustdoc over the Tauri crate with private items, TypeScript via typedoc over the React frontend) are flat browsers over every symbol in the source tree with the same one-line summaries that appear in IDE hovers — useful when you remember a name but not where it lives.