The terminal's search lists the explorer's rows for any explore word (owner:, updated:, archived:), as /explore does #7926

Intent: one explore line means the same thing on the web, in the terminal and through MCP.

Today src/tui/screens/dashboard.ts treats a search as the explorer's only when it has kind: or sort: (the exploring regex), so owner:trevato or updated:7d alone in the terminal filters the board, while /explore and MCP explore read them as explore words. MCP explore's query description names only kind: sort: updated:7d.

Done:

• [ ] src/actions/explore.ts exports one predicate (e.g. isExploreLine(line)) that is true when the line has any word readExploreLine reads as a key: kind, sort, updated, owner, archived.
• [ ] The terminal dashboard uses that predicate in place of its own regex; owner:trevato alone lists trevato's apps and the person, ranked as /explore?q=owner:trevato does.
• [ ] MCP explore's doc and query description name every word: kind: sort: updated: owner: archived:.
• [ ] Tests fail without the change: test/explore.test.ts covers the predicate for each key and for a plain word (false); test/tui-dashboard-explore.test.ts shows owner:<name> alone giving explore rows.
• [ ] By eye in the terminal: typing /owner:trevato shows explorer rows.

Files: src/actions/explore.ts, src/tui/screens/dashboard.ts, src/http/mcp/tools/explore.ts, test/explore.test.ts, test/tui-dashboard-explore.test.ts. Risks: a board search that legitimately contains owner: text now goes to the explorer; that matches /explore's reading and is intended.