Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/playground/src/App.vue`:
- Around line 161-169: The CI failure is due to formatting issues in the
router-link JSX/HTML in App.vue (the <router-link> elements for "Go to Features
(name)", "Go to Features (string)" and "Go to Feature one"); run the formatter
(oxfmt --write) or your project format script (e.g., pnpm format), re-check with
oxfmt --check, and commit the updated formatting changes so the <router-link>
blocks are properly formatted.

In `@packages/router/src/matcher/index.ts`:
- Around line 328-334: The name-based resolution branch is not stripping empty
optional params like the path-based branch does (see matcher.keys.forEach check
that deletes params[key.name] when key.optional and params[key.name] === ''),
causing divergence between path vs name resolution; update the name-based branch
(the code around the existing name-resolution logic) to run the same
empty-optional stripping over its params — iterate matcher.keys and delete
params[key.name] when key.optional && params[key.name] === '' — so both
resolution paths normalize optional empty-string params the same way and keep
isActive comparisons consistent.

---

Nitpick comments:
In `@packages/playground/src/router.ts`:
- Around line 162-166: The route for path '/features/:pathMatch(.*)*' is using
the User component which expects an id prop (defineProps<{ id: string }>()),
causing the view to show undefined; update the route definition (the object with
name 'features' and component: User) to instead use a component that reads and
renders route.params.pathMatch (either replace with the already-imported Generic
or NotFound component, or provide a small inline/view component that returns
route.params.pathMatch) so the page displays the pathMatch value and preserves
active-link verification.

In `@packages/router/__tests__/matcher/resolve.spec.ts`:
- Around line 697-714: Add two tighter test cases using assertRecordMatch: (1)
resolve the same URL both by path '/features' and by name 'features' with no
params and also with params: { pathMatch: '' }, and assert the resulting route
objects (especially params) are deep-equal to ensure RouterLink active-class
comparisons remain consistent; (2) add a case for a repeatable optional route
like { path: '/a/:p*', name: 'a' } resolved at '/a' and assert that params.p is
omitted (not '' or []) — use the existing assertRecordMatch helper and the
same-style test block as the 'drops missing optional splat when resolving by
path' spec to add both assertions.

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@packages/router/__tests__/matcher/resolve.spec.ts`:
- Around line 864-877: The test "keeps optional params passed as empty strings"
contradicts the matcher resolve behavior that treats empty strings (and
encodeParam(null)) as absent optional params; update the test in resolve.spec.ts
to expect empty string and null to be removed from resolved params (i.e.,
optional params treated as absent/undefined), or alternatively add a new test
that asserts null is handled like undefined via encodeParam/RouteParamValueRaw;
specifically adjust assertions referencing the route record for '/:a/:b?' and
the resolved locations so that params { b: '' } (and null) are not preserved,
matching the deletion logic in matcher.resolve (and encodeParam behavior).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/router/src/matcher/index.ts`:
- Around line 328-336: Fix the spelling typo in the comment inside the
matcher.keys.forEach block: change "noramlizes" to "normalizes" in the comment
that explains deleting optional params for falsy values; keep the existing logic
referencing params[key.name], key.optional, and parse() unchanged.