docs(remediation): roll D-11 capability/identity bullets to the ledger (D-43: roll out, never reword)

Third application of D-43's rule today. Those two bullets restated D-11/D-11a/D-11b, which live
authoritatively in TASKS.md, so they were a second copy waiting to go stale. Rolled verbatim; the board
keeps a pointer plus the one operational line that is not a restatement — assert the differential as
that seat, because a single endpoint can be true for anyone or 403 for an unrelated scope.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

docs/remediation/BOARD-LEDGER.md

@@ -60,3 +60,13 @@ because that repetition is what went stale.
 Builds 1-5, the cross-cutting retirements, and DECISION-1's corrected wire-in target are stated once in
 the charter and `TASKS.md` §5. **Not repeated here** — the previous copy of DECISION-1's status on this
 board is one of the six stale restatements below.
+
+<!-- board-roll: capability/seat-identity bullets rolled verbatim from BOARD.md 2026-08-01
+     (D-43: roll out, never reword). Authoritative home: TASKS.md D-11 / D-11a / D-11b. -->
+
+- Capability is **per-path** (D-11b → **superseded in part by D-13/D-15**): a token file is **necessary,
+  not sufficient**. Three layers — token file (raw-API), `tea` login (tea paths), **repository permission**
+  (writes). Before dispatch, assert `permissions.push == true` **as that seat**, not token existence and
+  not a 200 on a read. Mos owns provisioning; escalate missing pairs.
+- Seat identity (D-11a): token identity AND `git config user.name`/`user.email` must BOTH be set and
+  agree. Exporting `MOSAIC_GIT_IDENTITY` alone does NOT fix commit authorship.