fix(ledger): Gate F follow-up, Filbert's notes 1 to 3 (#1506)

Darkwing's follow-up to the T3 thread source: manifest 382f5bb0 pins t3.mjs, ledger.test.mjs and README.md. Filbert approved it (review 6fd693b6). Ledger 51/51; the eight suites pass on the index. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-26 16:57:51 -05:00
parent a4d38a3d93
commit 3a209eeafe
9 changed files with 268 additions and 7 deletions
@@ -146,6 +146,13 @@ at every gate. Started 2026-09-12 during the control board MVP.
  query in one read transaction, but no test proves a write landing during
  the read stays invisible. Filbert's note 4 on the Gate F build (e47ec6da).
  Notes 1 to 3 go to Darkwing's follow-up. (2026-09-26, #1506)
+- **A T3 sender role with spaces counts as human.** The SetSpark lead's
+  reply to Sage (21:41:24Z) used the role "main content-engine agent". The
+  6a rule requires a one-word role, so the ledger counts that message as
+  human in Sage's row. Gate F reads only Filbert's row, so it is not
+  affected. Filbert found it through the live diagnostic (14 went to 15).
+  Sage asked the SetSpark lead to use a one-word role. The rule stays as
+  it is. (2026-09-26, #1506)

 ## Queue