fix(search): match complete paths in file and project search

Treat slash-separated fragments as searchable text and use the same full-path fuzzy matcher for daemon results and remembered project paths.

packages/protocol/src/search/text-match.test.ts

@@ -5,6 +5,7 @@ import {
   fuzzyPolicyForToken,
   matchRanges,
   scoreMatch,
+  scorePathMatch,
   scoreTextFields,
 } from "./text-match.js";
 
@@ -171,6 +172,28 @@ describe("scoreMatch typo tolerance", () => {
   });
 });
 
+describe("scorePathMatch", () => {
+  it("matches a literal fragment anywhere in the complete path", () => {
+    expect(
+      scorePathMatch("skills/", "something/something-else/skills/paseo-advisor/SKILL.md"),
+    ).not.toBeNull();
+  });
+
+  it("fuzzy-matches spaced text against a compact path", () => {
+    expect(scorePathMatch("blank page editor", "blankpage/editor")).toEqual({
+      tier: 0,
+      offset: 0,
+    });
+  });
+
+  it("keeps the original path offset for compact matches", () => {
+    expect(scorePathMatch("blank page editor", "projects/blankpage/editor")).toEqual({
+      tier: 4,
+      offset: 9,
+    });
+  });
+});
+
 describe("scoreTextFields", () => {
   it("requires every token to match some field", () => {
     expect(scoreTextFields("stripe billing", ["add stripe billing system"])).not.toBeNull();