test(CommandPalette): cover the b24ui-only useTokenSearch argument

[IgorShevchik]

Linked issue

Closes #363.

Rescoped. This PR previously also fixed #362. @arsalan507 has since sent #379 for that, smaller and covering #375 as well, so the overlapping work has been dropped from here. What remains touches no src/ at all.

Type of change

• Documentation (updates to the documentation or readme)
• Bug fix (a non-breaking change that fixes an issue)
• Enhancement (improving an existing functionality)
• New feature (a non-breaking change that adds functionality)
• Chore (updates to the build process or auxiliary tools and libraries)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

highlight() takes a fifth parameter, useTokenSearch, that upstream does not have — and it had no test at all.

Where it came from. c502157b added the tokens / minTokenLength pair and 6743f793 the parameter itself, both against the file's old name src/runtime/utils/fuse.ts; both shipped in v2.8.0. Immediately before c502157b the function took four parameters and computed no minTokenLength, which is what establishes it as locally authored — not the absence of an Upstream: trailer, which is too sparse a convention here to carry an inference (16 of ~3200 commits).

Why nobody noticed. The port 557a5178 renamed fuse.ts to search.ts and carried the divergence across, so git log -S useTokenSearch -- src/runtime/utils/search.ts returns exactly one commit — that port, which does carry a trailer. --follow is needed to see the two that introduced it.

Why it matters. Replaying upstream's four-parameter signature would drop a feature shipped in v2.8.0 and nothing would go red.

Unit cases pin the threshold the argument moves: the whole term's length when off, the shortest word's when on, and the fallback to the whole term when the tokenizer matches nothing — an emoji-only query matches no \p{L} token, and the threshold must stay the term's length rather than collapsing to zero and marking everything.

Component cases cover the wiring, which the unit tests cannot reach. matches is only populated when includeMatches is set, which CommandPalette leaves to the caller — so no existing case in CommandPalette.spec.ts reached highlight() at all, and the with searchTerm snapshot contains no <mark>. These fail if the fifth argument stops being forwarded from processGroupItems.

Recorded as a §2 invariant in .sync/PORTING.md, stating plainly that upstream itself was not re-inspected — the divergence is established from b24ui's own history.

Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

Verified failing against a revert to upstream's four-parameter signature, and against dropping the fifth argument at the call site. eslint and vue-tsc --noEmit clean.