chore: willboosterify this repo

[WillBooster-bot]

Applies the latest wbfy (wb 16) to this repository.

Notable changes

• Migrated to Bun's isolated linker with a global store, moved tool versions to mise.toml, renamed renovate.json → renovate.jsonc, and refreshed shared config/doc files.
• Bumped tooling (wb 16, oxfmt 0.60, oxlint 1.75) and pinned the typescript peer dependency.

Fixes for isolated-linker type checking

The isolated-linker migration exposed two type-checking breakages, now fixed:

1. Fixture tsconfig shim paths — next/* shims are now resolved from the fixture-local node_modules, where the isolated linker places vinext (previously hoisted to the repo root).
2. Root project pulling in the framework fixture — the root tsconfig.json now excludes e2e/fixture/app, so the fixture's app sources are type-checked only by their own tsconfig (which shims next/* via paths), not by the root project. This was fixed generally in wbfy itself: fix(wbfy): exclude framework workspace app dirs from the root tsconfig shared#1062.

bun verify passes.

[gemini-code-assist]

Code Review

This pull request updates the project configuration, guidelines, and dependencies, including transitioning from .tool-versions to mise.toml, switching Bun's linker to isolated in bunfig.toml, and adding a comprehensive E2E test fixture. Feedback on the changes suggests restoring the exclusion of e2e/fixture from the root tsconfig.json to prevent type-checking errors and eliminate redundancy, as well as reverting the empty typescript peer dependency range in package.json back to "*" to ensure compatibility.

[gemini-code-assist]

Including e2e/fixture files in the root tsconfig.json compilation will cause type-checking errors (e.g., during bun wb typecheck) because the root configuration lacks the specific path mappings (like next/link shims) and dependencies (like vinext) defined in the fixture's own tsconfig.json and package.json.

Additionally, explicitly listing subdirectories of e2e/fixture in include is redundant since e2e/**/* is already included, violating the repository style guide rule to eliminate redundancy.

We should restore the exclusion of e2e/fixture from the root compilation and let it be type-checked independently via its own configuration.

  "exclude": ["e2e/fixture", "test/fixtures"],
  "extends": "@tsconfig/bun/tsconfig.json",
  "include": [
    "*.config.ts",
    "e2e/**/*",
    "scripts/**/*",
    "src/**/*",
    "test/**/*",
    "types/**/*"
  ]

References

1. Simplify code as much as possible to eliminate redundancy. Including specific subdirectories of e2e/fixture when e2e/**/* is already included is redundant. ^(link)

[gemini-code-assist]

Using an empty string "" as a version range for typescript in peerDependencies is highly non-standard and can cause warnings or resolution failures in strict package managers. It should be restored to "*" to indicate compatibility with any version.

Suggested change

	"typescript": ""
	"typescript": "*"