docs: lock device to one linear branch via Publish-is-sync principle

The user's mental model of Publish is a Google Doc backed by git, not a
curated commit log. Branches fall out of scope under that framing; the
device tracks one stream of work on whichever branch the remote was
cloned on, and never switches. Drops :Gbranch from v0.7 to match.
This commit is contained in:
Julien Calixte
2026-05-17 12:38:36 +02:00
parent ffcd49588a
commit cbdd6aa197
2 changed files with 6 additions and 1 deletions

View File

@@ -71,7 +71,6 @@ Out of scope: Vim, palette, multiple files, branches, conflict handling.
- [ ] `/` forward search, `n N`
- [ ] `:Gpull` (fetch + fast-forward only; refuse on conflict and surface it)
- [ ] `:Gbranch` to switch branches; refuse with dirty tree
## v0.8 — Power: battery + sleep — [ ]