Work in progressUnder active development — not tested as ready for use. Breaking changes land without notice, stored data may need to be discarded between revisions, and there is no auth or security model. These docs describe the intended design as much as the current state.
26. A single main branch
Date: 2026-06-18
Status
Accepted
Context
This is a fresh public GitHub repository — the clean rebuild starts its history here, with no legacy branch to carry forward. It needs a simple, conventional branch model that a public contributor (or the owner's future self) recognises immediately.
Decision
mainis the single primary branch. It is always releasable; CI (ci.yml) runs lint/typecheck/build on every push and PR to it.- Work happens on short-lived
feat/<topic>(orfix/<topic>) branches, merged back intomainvia pull requests. - Releases are cut from
mainby pushing avX.Y.Ztag (ADR 0012).
See branching.md.
Consequences
- The standard GitHub flow — no integration branch, no long-lived release branch — keeps contribution friction low and history easy to follow.
- The repo is developed locally until its GitHub remote is created; this model takes effect the moment
originexists.