A mistyped explore word offers the nearest one as a single link: sort:froks → sort:forks #9174

A mistyped kind:, sort:, updated: or archived: word on /explore now gets one suggestion, and the API and the MCP tool return the same suggestion. bun x tsc --noEmit, bun scripts/gate.ts, bun scripts/design-lint.ts and the four test files below passed. Those are test/explore-unknown-words.test.ts, test/explore-timing.test.ts, test/mcp-size.test.ts and test/explore-mcp-q.test.ts. I ran no other tests.

• How it works: exploreSuggestion(line) in src/actions/explore.ts takes an unknown word and finds the nearest known value of its key within edit distance 2. It looks nothing up, so it should not affect the timing budget.
• Page: the note on /explore ends with Did you mean <a href="/explore?q=garden%20sort%3Aforks">sort:forks</a>?. The link keeps the rest of the line, and the text is escaped where it's drawn.
• API and MCP: GET /api/v1/explore and the MCP explore tool add suggest: "garden sort:forks", the whole corrected line. The field is absent when there is no suggestion. I added it to the existing tool, so there is no new MCP tool and no ceiling raised.
• Tests: test/explore-unknown-words.test.ts covers the matching rules, the page link, the API field and absence, the MCP result, and sort:<script> producing no tag. I did not run the new tests against main to confirm they fail there.

Choices you may want to change:

• One word per line: if several words are unknown, only the first one with a close match is corrected. The other typos stay in the line until the next pass.
• owner:: it gets no suggestion, because there is no fixed list of names to match against.
• Short answers: yes, no and the windows (1d, 7d, 30d) match loosely at distance 2, so odd inputs like updated:2y can now suggest a window. That follows the issue as written.

To try it, open /explore?q=garden sort:froks.

Closes #9076

A mistyped kind:, sort:, updated: or archived: word on /explore now gets one suggestion, and the API and the MCP tool return the same suggestion. bun x tsc --noEmit, bun scripts/gate.ts, bun scripts/design-lint.ts and the four test files below passed. Those are test/explore-unknown-words.test.ts, test/explore-timing.test.ts, test/mcp-size.test.ts and test/explore-mcp-q.test.ts. I ran no other tests.

• How it works: exploreSuggestion(line) in src/actions/explore.ts takes an unknown word and finds the nearest known value of its key within edit distance 2. It looks nothing up, so it should not affect the timing budget.
• Page: the note on /explore ends with Did you mean <a href="/explore?q=garden%20sort%3Aforks">sort:forks</a>?. The link keeps the rest of the line, and the text is escaped where it's drawn.
• API and MCP: GET /api/v1/explore and the MCP explore tool add suggest: "garden sort:forks", the whole corrected line. The field is absent when there is no suggestion. I added it to the existing tool, so there is no new MCP tool and no ceiling raised.
• Tests: test/explore-unknown-words.test.ts covers the matching rules, the page link, the API field and absence, the MCP result, and sort:<script> producing no tag. I did not run the new tests against main to confirm they fail there.

Choices you may want to change:

• One word per line: if several words are unknown, only the first one with a close match is corrected. The other typos stay in the line until the next pass.
• owner:: it gets no suggestion, because there is no fixed list of names to match against.
• Short answers: yes, no and the windows (1d, 7d, 30d) match loosely at distance 2, so odd inputs like updated:2y can now suggest a window. That follows the issue as written.

To try it, open /explore?q=garden sort:froks.

The failed check was the gate rule that wants a "Try:" line in a commit message. I added an empty commit carrying that line and pushed it, so the code is unchanged. bun scripts/gate.ts printed nothing when I ran it locally, and I haven't seen the forge's re-run of the check yet.

I did not re-run tsc or the tests, since nothing but a commit message changed.

What changed: a mistyped kind:, sort:, updated: or archived: word on /explore now gets one suggestion. The note ends with Did you mean <a href="/explore?q=…">sort:forks</a>?, and the link keeps the rest of the line. GET /api/v1/explore and the MCP explore tool return suggest: "garden sort:forks", the whole corrected line, and leave the field out when nothing is within edit distance 2. The match is a pure function of the line, with no lookups. It is escaped where drawn, and a test feeds sort:<script> and finds no tag.

What I chose not to do:

• One word per line: only the first unknown word with a close match is corrected.
• No owner: suggestions: there is no fixed list of names to match against.
• No new MCP tool: suggest is a field on the existing explore tool, so no MCP ceiling was raised.

Try: open /explore?q=garden sort:froks on the preview and follow "Did you mean sort:forks". Or call GET /api/v1/explore?q=garden sort:froks and read suggest.

All four review points are addressed and pushed. bun x tsc --noEmit and bun scripts/gate.ts are clean. I ran test/explore-unknown-words.test.ts, test/tui-dashboard-explore.test.ts, test/mcp-size.test.ts and test/explore-timing.test.ts, and they all pass.

1. Terminal: the explorer's "Read as:" line in src/tui/screens/dashboard.ts now says · Did you mean kind:app sort:forks? in plain text. I put it before the note because the note is long and the terminal cut off whatever came last. A new test in test/tui-dashboard-explore.test.ts covers it.
2. Docs: docs/features/explore.md now describes the link, the suggest field on the API and MCP, the terminal line, and the two edge rules below.
3. Tests: the MCP test now checks that suggest is absent for sort:forks and for sort:zzzzzzzz, and that the far case still returns the "is not a sort" note. The sort:<script> page test also asserts the note reads sort:<script> is not a sort. With src/actions/explore.ts swapped for main's, both test files fail. That is a coarse failure, since the import of exploreSuggestion breaks, not each assertion failing on its own. I restored the file afterwards.
4. Edge rules:

- Short junk: a suggestion now needs distance ≤ 2 and below the value's length. archived:x and updated:2y get none, and archived:ye still gives archived:yes. - Several unknown words: only the first word with a close match is mended per line, and a repeated typo is mended everywhere. Tests pin both.

One slip along the way: I briefly checked out main's src over my work to confirm the failures and had to reset and restore the stash. Nothing was lost, and the pushed tree contains only this pull's changes.