feat: unlinked references in the backlinks panel (slice 3a)

fiatcode commented

2026-06-12 22:36:09 +07:00

Owner

Summary

Slice 3a of the connect roadmap (read-only half of "unlinked references + linkify"). When the backlinks panel (b) opens, peekseq now also lists unlinked references — bare-text mentions of the page elsewhere in pages/+journals/ that aren't yet [[linked]] — in a second section beneath the linked backlinks. enter on an unlinked row jumps to that page. Read-only; no files are written.

How it works

search.Mentions(graphPath, name) runs rg -w -F --ignore-case (whole-word, literal, case-insensitive) for the page name.
graph.FilterUnlinked (pure, unit-tested) drops hits that are inside an existing [[…]], inside a fenced code block, or in the page's own file.
The backlinks view moved to a flat-row model rendering linked refs + an "Unlinked references" section in one scroll; App.unlinkedRefs runs detection on panel-open and injects the result (view stays display-only).
graph imports search (verified no cycle); detection is by page name (no alias tracking exists).

Conscious deviations / notes

Match highlighting skipped. The spec mentioned Span-based emphasis of the matched text, but the existing linked backlink rows don't highlight either — emphasising only unlinked rows would make the two sections inconsistent. The Match span is still computed (it drives the inside-[[…]] filter and anchors the future linkify slice). Deferred for consistency.
Detection is synchronous on b-press — rg on one name over two dirs is fast; spec-sanctioned, with an async escape hatch noted if it ever drags.
ripgrep failure degrades gracefully to no unlinked section (an error hint would be invisible behind the overlay — the slice-1 hidden-hint lesson).

Scope

Out (future slice 3b → v1.4.0): one-key linkify (the first writer to files other than the current page). Also out: alias matching, namespaced-leaf matching, frequency/length caps.

Test plan

go vet ./... && go test ./... green
Unit: search.Mentions whole-word; FilterUnlinked (own-file / fenced / inside-[[]] / unreadable-file); App unlinkedRefs on a temp graph
teatest golden for the combined linked+unlinked panel; existing backlinks goldens unchanged (byte-identical)
Manual smoke on device: open b on a page with bare mentions; confirm the unlinked section + enter navigation

## Summary Slice 3a of the connect roadmap (read-only half of "unlinked references + linkify"). When the backlinks panel (`b`) opens, peekseq now also lists **unlinked references** — bare-text mentions of the page elsewhere in `pages/`+`journals/` that aren't yet `[[linked]]` — in a second section beneath the linked backlinks. `enter` on an unlinked row jumps to that page. Read-only; no files are written. ## How it works - `search.Mentions(graphPath, name)` runs `rg -w -F --ignore-case` (whole-word, literal, case-insensitive) for the page name. - `graph.FilterUnlinked` (pure, unit-tested) drops hits that are inside an existing `[[…]]`, inside a fenced code block, or in the page's own file. - The backlinks view moved to a flat-row model rendering linked refs + an "Unlinked references" section in one scroll; `App.unlinkedRefs` runs detection on panel-open and injects the result (view stays display-only). - `graph` imports `search` (verified no cycle); detection is by page **name** (no alias tracking exists). ## Conscious deviations / notes - **Match highlighting skipped.** The spec mentioned `Span`-based emphasis of the matched text, but the existing *linked* backlink rows don't highlight either — emphasising only unlinked rows would make the two sections inconsistent. The `Match` span is still computed (it drives the inside-`[[…]]` filter and anchors the future linkify slice). Deferred for consistency. - **Detection is synchronous** on `b`-press — `rg` on one name over two dirs is fast; spec-sanctioned, with an async escape hatch noted if it ever drags. - ripgrep failure degrades gracefully to no unlinked section (an error hint would be invisible behind the overlay — the slice-1 hidden-hint lesson). ## Scope Out (future **slice 3b → v1.4.0**): one-key linkify (the first writer to files other than the current page). Also out: alias matching, namespaced-leaf matching, frequency/length caps. ## Test plan - [x] `go vet ./... && go test ./...` green - [x] Unit: `search.Mentions` whole-word; `FilterUnlinked` (own-file / fenced / inside-`[[]]` / unreadable-file); App `unlinkedRefs` on a temp graph - [x] teatest golden for the combined linked+unlinked panel; existing backlinks goldens unchanged (byte-identical) - [x] Manual smoke on device: open `b` on a page with bare mentions; confirm the unlinked section + `enter` navigation

fiatcode added 8 commits

2026-06-12 22:36:09 +07:00

docs: spec for slice 3a — unlinked references in the backlinks panel 47678666b8

docs: implementation plan for slice 3a — unlinked references aaed32b04c

feat(search): add Mentions — whole-word page-name query 5a45182642

feat(graph): add FilterUnlinked — pure unlinked-reference filter e16da80354

refactor(views): flat-row backlinks model with an unlinked section 9e4d779c90

Introduces blRow flat-list model for the Backlinks overlay. NewBacklinks
now accepts an unlinked []graph.UnlinkedRef param so the App can supply
ripgrep-detected bare-text mentions alongside the linked backlinks. When
unlinked is nil/empty the rendered output is byte-identical to before.

feat(views): render and navigate the unlinked-references section 230a6f4076

Adds unlinkedFixture and three tests: navigation saturates at last
unlinked row, header rows are never selectable, and a golden that
verifies the full rendered output of the overlay with both linked and
unlinked sections present.

feat(views): compute unlinked references when the backlinks panel opens 76a5b215b9

docs: document unlinked references in help, README, AGENTS, CHANGELOG

CI / vet-and-test (pull_request) Successful in 2m28s

Details

622a05bbec

fiatcode self-assigned this

2026-06-12 22:40:36 +07:00

fiatcode added 1 commit

2026-06-12 22:55:09 +07:00

feat(views): focus the back-reference link when jumping from a backlink

CI / vet-and-test (pull_request) Successful in 26s

Details

13f581c84b

When the user presses enter on a linked backlink, the destination page
now lands with its link cursor positioned on the first link back to the
source page (auto-scrolled and highlighted). Unlinked refs are
intentionally excluded (no link to anchor). The cursor is persisted in
the history entry so [ / ] history navigation restores it correctly.

fiatcode added 1 commit

2026-06-12 23:10:50 +07:00

fix(graph): ExtractWikiLinks skips [[..]] inside inline code

CI / vet-and-test (pull_request) Successful in 2m27s

Details

36fd0d498a

fiatcode added 7 commits

2026-06-13 08:42:23 +07:00

docs: spec for slice 3a.1 — highlight unlinked mentions on arrival 325ff2542f

docs: implementation plan for slice 3a.1 — highlight on arrival b84a024ba3

feat(render): emphasis-term highlight with Finds offsets 4e3dfc9197

feat(views): PageView highlights and scrolls to an emphasis term 040e2c970b