Skip to content

doctor: resolve duplicate stems in the indexer's order - #226

Merged
joedanz merged 1 commit into
mainfrom
fix/doctor-stem-order
Oct 5, 2026
Merged

joedanz merged 1 commit into
mainfrom
fix/doctor-stem-order

Conversation

@joedanz

@joedanz joedanz commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Two doctor checks (cross-space refs, the up-exemption stem map) built their stem map in component-sorted order; the indexer and relink use plain string order. With duplicate stems under a/ and a-b/, doctor could judge a different note than search resolves — a false cross-space leak warning in the test. Both now iterate sorted(rels).

Test added first, failed on the old order. Full suite 1884 passed; ruff 0.16.0 clean.

https://claude.ai/code/session_012XGaE1cGxpYryus7cxfAFD

Two doctor checks built their stem map from component-sorted paths while the
indexer (and relink) use plain string order, so a bare [[Dup]] could resolve
to a different note in cross-refs and near-duplicate checks than in search.

Claude-Session: https://claude.ai/code/session_012XGaE1cGxpYryus7cxfAFD
@vercel

vercel Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
brainkit-docs Ready Ready Preview Oct 5, 2026 7:17pm UTC

Request Review

@joedanz
joedanz merged commit dd08087 into main Oct 5, 2026
7 checks passed
@joedanz
joedanz deleted the fix/doctor-stem-order branch October 5, 2026 19:19

This branch was successfully deployed

1 active deployment
Preview — f2ade9d9 Deployed Oct 5, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant