chore(deps): upgrade Rslint to v0.8.1

[chenjiahan]

Summary

• Upgrade @rslint/core to v0.8.1 and refresh the lockfile where applicable.
• Disable no-undef globally to align with Rslint's planned default behavior for the next release.
• Preserve the existing recommended-rule coverage under Rslint 0.8.
• Resolve newly surfaced lint diagnostics where needed.
• Verify the relevant lint checks pass.

Related Links

• https://github.com/web-infra-dev/rslint/releases/tag/v0.8.1

[Copilot]

Pull request overview

Upgrades the repo’s linting toolchain to Rslint v0.8.0 and adjusts configuration/source to preserve existing recommended-rule coverage while addressing newly surfaced diagnostics.

Changes:

• Bump @rslint/core to ^0.8.0 and update pnpm-lock.yaml accordingly.
• Expand rslint.config.ts to include JS recommended rules and add targeted overrides for tests/** and example/**.
• Minor TypeScript changes to align with updated lint expectations (e.g., Error cause propagation; ESC handler refactor).

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/server.ts	Adds Error { cause } metadata when rethrowing missing optional dependency errors.
rslint.config.ts	Includes js.configs.recommended and adds per-folder rule overrides for tests/examples.
pnpm-lock.yaml	Refreshes lockfile for @rslint/core@0.8.0 and related dependency updates.
package.json	Updates @rslint/core dependency range to ^0.8.0.
client-src/overlay.ts	Refactors ESC key handler into a function declaration to satisfy linting/usage order.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d17bb2ea8a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".