The pager's Tab completion (BRO-013) anchors its two sources inconsistently with the navigated context: _fsCompletions (pager.js:602-623) resolves against be.wt_root || be.cwd, ignoring the view's //authority, and _compTok (pager.js:590-595) makes ./-relative inserts against the TRACKED view path while candidates come from ON-SCREEN hunk paths — the two disagree in cross-dir result views. Runtime-VERIFIED, 2026-07-07 audit. Method Issues.
ls //OTHERTREE/be, Tab's FS fallback readdirs <launch wt_root>/be — completions from the WRONG tree (both bare and dir-qualified stems).//WT/test, hit row //WT/shared/util.js; :./u<Tab> inserts ./shared/util.js (full wt path with ./ prepended, since the candidate is not under the view path); Enter drives grep //WT/test/shared/util.js — nonexistent, "no hunks".h help key inherits the WHOLE current address (help://WT/x?feat); an unresolvable authority turns the help key into "err: NAVNONE"../ insert is correct relative to what the SPELL will resolve against — candidate paths not under the view dir insert as wt-relative (no ./)../ insert round-trips to an existing path.views/bro/pager.js _completions/_fsCompletions/_compTok; keep the on-screen-first, FS-fallback order (BRO-013).