docs: note native addons can crash the threads pool (#1365)

Author: fi3ework

scripts/dictionary.txt

@@ -14,6 +14,7 @@ bundleless
 bytedance
 caniuse
 canyonjs
+catchable
 cdup
 CEHQ
 chunkhash

website/docs/en/config/test/pool.mdx

@@ -69,7 +69,7 @@ Consider switching to `threads` when:
 Stick with `forks` when:
 
 - Your tests mutate `process.chdir`, env vars, or signal handlers and rely on per-file isolation.
-- Your project depends on native modules that assume per-process initialization (e.g. `better-sqlite3`, `sharp`, `canvas`).
+- Your project uses native addons (e.g. `better-sqlite3`, `sharp`, `canvas`) — one not built for worker threads can abort the whole run under `threads` (`SIGSEGV` / `SIGABRT`, not a catchable error).
 - You want a hard crash in one test file contained inside its own worker, without risking the parent process or sibling tests.
 
 ## Control file-level parallelism

website/docs/zh/config/test/pool.mdx

@@ -69,7 +69,7 @@ Rstest 支持两种 pool 类型，它们共享同一套 scheduler、RPC 和结
 下列情况建议继续使用 `forks`：
 
 - 测试里会修改 `process.chdir`、环境变量、signal handler 等进程级状态，并依赖按文件之间互相隔离。
-- 项目依赖按进程初始化的 native module（如 `better-sqlite3`、`sharp`、`canvas` 等）。
+- 项目使用 native addon（如 `better-sqlite3`、`sharp`、`canvas`）—— 未针对 worker thread 设计的 addon 在 `threads` 下可能让整个运行直接 abort（`SIGSEGV` / `SIGABRT`，且无法捕获）。
 - 希望单个测试文件的硬性崩溃被限制在该 worker 内，不影响主进程和其他用例。
 
 ## 控制文件级并行度