fix(ci): silence typos on patches/ + fix respone typo in design doc

typos 1.45.1 rejected the PR because:
- `./patches/vite.patch` includes Vite's own hunk-header line containing
  a truncated identifier (`environmen`) that looks like a typo but isn't
  ours to fix. Add `patches` to `.typos.toml` extend-exclude.
- `docs/runner-task-ipc/index.md:39` had a real typo `respone` → `respond`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: wan9chi

.typos.toml

@@ -9,4 +9,6 @@ extend-exclude = [
   # Intentional typos for testing fuzzy matching and "did you mean" suggestions
   "crates/vite_select/src/fuzzy.rs",
   "crates/vite_task_bin/tests/e2e_snapshots/fixtures/task_select",
+  # pnpm patch files — hunk context includes third-party code we don't own
+  "patches",
 ]

docs/runner-task-ipc/index.md

@@ -36,7 +36,7 @@ Notes:
 Workflow:
 
 1. `vite_task_server` uses crate `interprocess` to create a server along with a unique name, and listens to messages from tools.
-2. `vite_task` calls vite_task_server to run server for every spawn execution. and collect what's reported from tools, and respone with requested envs
+2. `vite_task` calls vite_task_server to run server for every spawn execution. and collect what's reported from tools, and respond with requested envs
 3. `vite_task` embed `vite_task_client_napi` dylib and write to temp folder in the same way as `crates/fspy/src/unix/mod.rs:56`. (we should extract crates/fspy/src/artifact.rs into a separate crate)
 4. `vite_task` passes both the dylib path and the IPC connection info to the tool's process env, via env vars that `vite_task_client` knows to look up.
 5. the tool is expected to use `@voidzero-dev/vite-task-client`