The "press [?] for shortcuts" hint and the trailing `?` in the footer
advertised a keyboard-shortcut affordance that doesn't exist yet. Drop
both (and the now-unused .shortcuts rule) so the chrome doesn't
promise something we haven't built.

Assisted-by: Claude Opus 4.7 via Claude Code

diff --git a/templates/_css.html b/templates/_css.html
index 242f2eb..e9e0ef2 100644
--- a/templates/_css.html
+++ b/templates/_css.html
@@ -45,7 +45,6 @@ pre { white-space: pre-wrap; word-break: break-word; }
 .page-nav .q-mark { color: var(--ink); display: block; }
 .page-nav .nav-crumb { color: var(--muted); }
 .page-nav .sep { color: var(--rule2); }
-.page-nav .shortcuts { font-size: 11px; color: var(--mutedFaint); }
 
 .page-main { padding: 22px 56px 32px; }
 
diff --git a/templates/_footer.html b/templates/_footer.html
index 20d8835..082fc29 100644
--- a/templates/_footer.html
+++ b/templates/_footer.html
@@ -1,4 +1,3 @@
 <footer class="page-footer">
   <span>v{{ self.version() }}</span>
-  <span>?</span>
 </footer>
diff --git a/templates/_nav.html b/templates/_nav.html
index c3085e9..0e65aad 100644
--- a/templates/_nav.html
+++ b/templates/_nav.html
@@ -17,5 +17,4 @@
     <span class="nav-crumb">{{ crumb }}</span>
     {% endfor %}
   </div>
-  <div class="shortcuts">press [?] for shortcuts</div>
 </nav>