Start with the top-level README for the five-minute install and first session. Use Getting started for the complete install, run, update, and development workflow. Maintainers should use Releasing for the fork-to-upstream release flow.
| Guide | Scope |
|---|---|
| Projects | Repository tabs and per-project terminal limits |
| Views | Status, commit log, tree, notices, and repository picker |
| Keyboard and mouse | Leader commands, navigation, terminal input, and mouse routing |
| Session state | Recent-activity indicator and files written between runs |
| Web viewer | Browser access, cloning, mobile layout, and security |
| Configuration | ~/.nightcrow/config.toml, defaults, validation, and reload scope |
| Notifications | nightcrow notify, agent completion hooks, plugin notices, and Web Push |
| Plugins | Plugin installation, opt-in, and bundled recovery plugin |
| Orchestrating agents | One coordinating agent assigning tasks to worker panes through shared memory |
| Releasing | Patch-only versioning, fork promotion, and official binary Releases |
Each guide is authoritative for its surface. Cross-links point back here or to the guide that owns a shared rule; design rationale and module boundaries remain in Architecture, and historical decisions remain in Design decisions.
- Getting started → Building and testing contains the repository verification gates.
- Architecture documents system boundaries and implementation responsibilities.