docs(journey): keep keybinding audit state aligned with PR #203

COHERENCE.md

@@ -392,10 +392,10 @@ Two of that observation's three examples have been answered — opening a
 file by `C-x C-f` (#162) and opening a terminal by `C-c t` (#173).
 **Running a build still has no binding on `main`**; PR #203 is open and
 adds `C-c c`. **The quote stays as written either way**: it names a standing bias in how new work gets bound,
-not three isolated omissions, and three fixes do not retire a bias. What
-has changed is that the bias no longer has an uncontested example in the
-golden journey — the next new surface that ships without a binding is
-evidence the pattern is live again, and should be read that way.
+not three isolated omissions, and two fixes do not retire a bias.
+**Running a build remains its uncontested golden-journey example until
+#203 lands.** A new surface that ships without a binding would be further
+evidence the pattern is live, and should be read that way.
 
 ---
 

docs/active-work.md

@@ -264,8 +264,9 @@ If it does not, stop and repair the remote/fetch configuration.
   ships them as *in flight*, because `COHERENCE.md` §25 says a grade
   changes only on landed evidence and the PR is open: `COHERENCE.md`
   §2's step-9 verdict row (Partial → **Works**), §2's post-table
-  keybinding-inversion paragraph (third example answered), §20 Priority
-  1 and its arc list (in flight → done), and
+  keybinding-inversion paragraph (third example answered; the build is
+  no longer its uncontested example), §20 Priority 1 and its arc list (in
+  flight → done), and
   `docs/agent-handoff.md` §1's arc bullet (IMPLEMENTED → LANDED).
   **Recorded here because an unowned doc flip is exactly how this
   ledger's drift starts** — the same rule-4 precondition that kept #176's