docs: fix 41 unresolved dartdoc references

Convert non-resolving [refs] in doc comments to backtick code-spans across 24
lib/ files (param/field names out of doc scope, method refs on other classes,
non-API strings like regex char-classes and command ids). Verified 0
"unresolved doc reference" warnings via `dart doc --validate-links`. The
dart-doc CI gate (test.yml) never ran before — Gitea Actions was inactive — so
this debt had accumulated unchecked.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

lib/kernel/src/keymap/keymap_service.dart

@@ -13,7 +13,7 @@
 ///
 /// Scope context is a `Map<String, bool>` keyed by named flags (e.g.
 /// `palette.open`, `editor.focused`). Producing services call
-/// [setScopeFlag] when their state changes; consumers reference the
+/// `setScopeFlag` when their state changes; consumers reference the
 /// flag name in when-clauses.
 library;
 

lib/kernel/src/keymap/modifier_tap.dart

@@ -9,8 +9,8 @@
 ///
 /// Headless and clock-injected: the caller (the root shell's raw-keyboard
 /// handler) passes the event time so it neither reads a clock nor consumes
-/// events. Feed every [KeyDownEvent] to [down] and every [KeyUpEvent] to
-/// [up], passing the event's [KeyModifier] (null for non-modifier keys).
+/// events. Feed every [KeyDownEvent] to `down` and every [KeyUpEvent] to
+/// `up`, passing the event's [KeyModifier] (null for non-modifier keys).
 library;
 
 import 'key_chord.dart';

lib/kernel/src/keymap/pane_key_nav.dart

@@ -10,7 +10,7 @@
 /// While a `vim.normal` scope flag is set and this region holds focus, bare and
 /// shift-only chords (plus the two half-page chords `ctrl+d` / `ctrl+u`) feed
 /// the matcher against the live keymap; a fired [NavIntent] is handed to
-/// [onNav] with its repeat count. Everything else under `vim.normal` is
+/// `onNav` with its repeat count. Everything else under `vim.normal` is
 /// swallowed (vim normal mode is inert for unbound keys), except other-modifier
 /// chords (palette, quick-open, …) which bubble to the global handler. Under a
 /// non-vim preset or in insert mode the region is transparent — keys pass

lib/kernel/src/keymap/when_clause.dart

@@ -6,7 +6,7 @@
 ///   and   := unary ('&&' unary)*
 ///   unary := '!' unary | atom
 ///   atom  := IDENT | '(' expr ')'
-///   IDENT := [a-zA-Z_][a-zA-Z0-9._-]*
+///   IDENT := `[a-zA-Z_][a-zA-Z0-9._-]*`
 ///
 /// Identifiers resolve against a `Map<String, bool>` context. A missing
 /// identifier evaluates to `false` — bindings can assume any required

lib/kernel/src/log_ring.dart

@@ -2,9 +2,9 @@
 /// output dock (T-54 / D-87) reads on open.
 ///
 /// The [Logger] only live-broadcasts to its stream; a panel that opens late
-/// would see nothing. [LogRing] is a sink that keeps the last [capacity]
+/// would see nothing. [LogRing] is a sink that keeps the last `capacity`
 /// records (drop-oldest, same shape as the D-85 event ring) plus enough
-/// bookkeeping to drive the panel's filter dropdown (distinct [sources]) and
+/// bookkeeping to drive the panel's filter dropdown (distinct `sources`) and
 /// the status-bar health badge (level counts).
 ///
 /// Flutter-free (only `dart:async`/`dart:collection` + the [LogRecord] type)
@@ -42,7 +42,7 @@ class LogRing {
   int get length => _records.length;
   bool get isEmpty => _records.isEmpty;
 
-  /// Append a record (the [Logger] sink). Drops the oldest past [capacity].
+  /// Append a record (the [Logger] sink). Drops the oldest past `capacity`.
   void add(LogRecord r) {
     _records.addLast(r);
     _sourceCounts.update(r.source, (n) => n + 1, ifAbsent: () => 1);

lib/kernel/src/panels/view_pane_snapshot.dart

@@ -1,7 +1,7 @@
 /// Snapshots the kernel's live tabs into [ViewPane]s so `pane list` reflects
 /// the panes the user actually sees in the GUI (T-219, D-6 parity / D-83).
 ///
-/// Read-at-request-time: no state is mirrored into the IPC [PaneRegistry], so
+/// Read-at-request-time: no state is mirrored into the IPC `PaneRegistry`, so
 /// nothing can drift from the live UI. Lives in the kernel (not `lib/src/panes/`)
 /// because it reads Flutter-coupled kernel state; it produces the Flutter-free
 /// [ViewPane] the pane command serialises.