docs: make edge the development branch

Author: luccahuguet

AGENTS.md

@@ -10,13 +10,23 @@ or planning bead until the user has chosen that direction
 
 ## Git Workflow
 
-Work directly on `main` by default. Do not create a separate branch unless the
-user explicitly requests one or another repository instruction requires it.
+Keep one linear history with this ancestry invariant:
 
-`edge` is the opt-in channel for experimental dogfooding. Work on it only when
-the user explicitly chooses that channel. A change intended for release must
-land on `main` and follow the normal `stable` promotion contract; never promote
-`stable` directly from `edge`.
+```text
+stable ⊆ main ⊆ edge
+```
+
+All tracked changes originate on `edge`, including fixes, reverts,
+documentation, and Beads updates. Work directly on `edge` by default. Do not
+create another branch unless the user explicitly requests one or another
+repository instruction requires it.
+
+`edge` is the active development and experimental dogfood channel. `main` is a
+promotion-only accepted-development channel: do not commit on it directly.
+After an `edge` revision is accepted and verified for `main`, advance `main` to
+that exact revision with `git push origin <sha>:main`. Never create merge
+commits, rebase published channel history, or cherry-pick between the channel
+branches, and never promote `stable` directly from `edge`.
 
 `stable` is a promotion-only user channel. Do not commit on it or advance it
 unless the user explicitly requests a promotion. A candidate must be a
@@ -25,8 +35,8 @@ Linux and cache checks, pass the release checks for its changed surface, and
 have fresh-session dogfood for user-visible runtime interaction changes. Do not
 promote a commit with a known P0 or P1 regression. Promote the exact verified
 SHA with `git push origin <sha>:stable`; never force-push or delete `stable`.
-Rollbacks use a new revert commit on `main`, followed by normal verification and
-promotion.
+Rollbacks use a new revert commit on `edge`, followed by normal verification and
+fast-forward promotion through `main` and then `stable`.
 
 ## Method
 

README.md

@@ -359,6 +359,6 @@ See [Development](docs/development.md) for CI and local checks,
 
 ## LOC Scorecard
 
-Yazelix owns **25,905 lines** of tracked text project files. The
+Yazelix owns **25,915 lines** of tracked text project files. The
 [reproducible scorecard](docs/development.md#loc-scorecard) excludes Beads,
 lockfiles, and binary assets.

docs/development.md

@@ -100,7 +100,7 @@ git ls-files | grep -Ev '^\.beads/|\.lock$|^assets/' | xargs wc -l
 | --- | ---: |
 | Ignore (`.gitignore`) | 19 |
 | License | 201 |
-| Markdown | 2986 |
+| Markdown | 2996 |
 | Nix | 1606 |
 | Shell | 84 |
 | YAML | 456 |
@@ -110,4 +110,4 @@ git ls-files | grep -Ev '^\.beads/|\.lock$|^assets/' | xargs wc -l
 | Lua | 245 |
 | Rust | 19540 |
 | Text | 41 |
-| Total | 25905 |
+| Total | 25915 |