codebyplan 1.13.3 → 1.13.4

package/dist/cli.js

@@ -14,7 +14,7 @@ var VERSION, PACKAGE_NAME;
 var init_version = __esm({
   "src/lib/version.ts"() {
     "use strict";
-    VERSION = "1.13.3";
+    VERSION = "1.13.4";
     PACKAGE_NAME = "codebyplan";
   }
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codebyplan",
-  "version": "1.13.3",
+  "version": "1.13.4",
   "description": "CLI for CodeByPlan — AI-powered development planning and tracking",
   "type": "module",
   "bin": {

package/templates/hooks/README.md

@@ -2,7 +2,7 @@
 
 The `codebyplan` npm package ships a small, portable set of Claude Code hooks. They run in your project, use only generic primitives (`git rev-parse`, `${CLAUDE_PROJECT_DIR}`, `${CLAUDE_PLUGIN_ROOT}`), and degrade gracefully (exit 0) when their preconditions aren't met.
 
-Hook registration lives in [`hooks/hooks.json`](./hooks.json) — PreToolUse, PostToolUse, and Notification events are wired. (`SessionStart`, `SessionEnd`, `Stop`, and `SubagentStop` are also schema-permitted but unused here.)
+Hook registration lives in [`hooks/hooks.json`](./hooks.json) — PreToolUse and PostToolUse events are wired. (`Notification`, `SessionStart`, `SessionEnd`, `Stop`, and `SubagentStop` are also schema-permitted but unused here.)
 
 **`cbp-statusline.sh` is auto-wired via `settings.project.base.json`.** The `statusLine` block is shipped inside `templates/settings.project.base.json` and merged into the consumer's `.claude/settings.json` automatically by `codebyplan claude install` (and on every `codebyplan claude update`). No manual copy-paste is required.
 
@@ -176,22 +176,6 @@ Walks up from the edited file to the nearest `package.json` and uses that packag
 
 ---
 
-### `notify.sh` — Notification, matcher `*`
-
-Sends a desktop notification when Claude Code emits a notification event (waiting for input, task complete, etc.). Title is `[<project-name>] Claude Code`; body is the notification message; clicking the notification focuses VS Code at the project directory (macOS only).
-
-**Cross-platform graceful skip**: exits 0 silently when `terminal-notifier` is not on `$PATH`. Linux, Windows, and macOS hosts without Homebrew see a no-op — no errors, no warnings.
-
-**VS Code click action**: only attached when running on macOS (`$OSTYPE` matches `darwin*`) AND the `code` CLI is on `$PATH`. On other hosts the notification still fires but is non-clickable.
-
-**Install hint** (macOS): `brew install terminal-notifier`. On other platforms the hook is a no-op — substitute your own notification mechanism via a settings.json override if desired.
-
-**Blocks vs warns**: never blocks — exit 0 always. Notification hooks must never block Claude.
-
-**Opt out**: settings.json override or plugin disable.
-
----
-
 ### `auto-test-hooks.sh` — PostToolUse, matcher `Edit|Write`
 
 Triggers `test-hooks.sh` automatically when any `*/hooks/*.sh` file is edited. Catches accidental breakage of the plugin's own hooks (or your project's `.claude/hooks/` if you author your own) at edit time, before the broken hook runs against future tool calls.
@@ -244,9 +228,9 @@ After a `complete_round` MCP call succeeds, reconciles the round's `files_change
 
 ### `test-hooks.sh` — invoked by `auto-test-hooks.sh`
 
-Test suite for the plugin's 10 registered hooks. Runs two passes:
+Test suite for the plugin's 9 registered hooks. Runs two passes:
 
-1. **Header check** — every registered hook (`lint-format-on-edit`, `test-coverage-gate`, `pre-commit-quality-gate`, `maestro-yaml-validate`, `notify`, `auto-test-hooks`, `mcp-migration-guard`, `validate-git-stash-deny`, `cbp-mcp-round-sync`) carries the required `# Hook:` and `# Purpose:` header comments. `statusline` uses its own `# Claude Code Status Line` marker.
+1. **Header check** — every registered hook (`lint-format-on-edit`, `test-coverage-gate`, `pre-commit-quality-gate`, `maestro-yaml-validate`, `auto-test-hooks`, `mcp-migration-guard`, `validate-git-stash-deny`, `cbp-mcp-round-sync`) carries the required `# Hook:` and `# Purpose:` header comments. `statusline` uses its own `# Claude Code Status Line` marker.
 2. **Functional smoke tests** — each hook is invoked with synthetic stdin matching its fast-path / graceful-degrade input; all must exit 0.
 
 Not in `hooks.json` — invoked indirectly via `auto-test-hooks.sh` on hook edits, or directly via `bash ${CLAUDE_PLUGIN_ROOT}/hooks/test-hooks.sh`.

package/templates/hooks/cbp-test-hooks.sh

@@ -62,7 +62,7 @@ for hook_file in "$HOOKS_DIR"/*.sh; do
 
   # Check for header comments (required for documentation generation).
   # Accept either marker convention used across the plugin's hooks:
-  #   - "# Hook:" + "# Purpose:" (used by notify, auto-test-hooks, etc.)
+  #   - "# Hook:" + "# Purpose:" (used by auto-test-hooks, etc.)
   #   - "# @event:" + a description line (used by maestro-yaml-validate, etc.)
   if (grep -q '^# Hook:' "$hook_file" && grep -q '^# Purpose:' "$hook_file") \
      || grep -q '^# @event:' "$hook_file"; then
@@ -77,14 +77,6 @@ echo ""
 # ===== FUNCTIONAL SMOKE TESTS =====
 echo "## Functional Smoke Tests"
 
-# cbp-notify.sh — graceful-degrade: exit 0 whether or not terminal-notifier is installed
-ACTUAL_EXIT=$(echo '{"message":"test","cwd":"/tmp"}' | bash "$HOOKS_DIR/cbp-notify.sh" >/dev/null 2>&1; echo $?)
-if [ "$ACTUAL_EXIT" = "0" ]; then
-  test_result "cbp-notify.sh graceful-degrade exits 0" "passed" "passed"
-else
-  test_result "cbp-notify.sh graceful-degrade exits 0" "passed" "failed"
-fi
-
 # cbp-lint-format-on-edit.sh — graceful-degrade: CLAUDE_PROJECT_DIR unset → exit 0
 if [ ! -f "$HOOKS_DIR/cbp-lint-format-on-edit.sh" ]; then
   test_result "cbp-lint-format-on-edit.sh present" "passed" "missing"

package/templates/hooks/hooks.json

@@ -60,17 +60,6 @@
           }
         ]
       }
-    ],
-    "Notification": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/cbp-notify.sh"
-          }
-        ]
-      }
     ]
   }
 }

package/templates/skills/cbp-setup-eslint/SKILL.md

@@ -181,13 +181,14 @@ command + which apps still need their `eslint.config.mjs` generated.
   `reference/*.md`, never silently skip
 - `codebyplan eslint init` failure is non-fatal — print the manual command and still write eslint.json
 - Atomic write (tmp + mv) — never leave eslint.json partial
-- Reference docs track the **latest official** flat-config setup and flag where CBP's DB
-  presets diverge (e.g. ESLint v10 + `eslint-plugin-react-hooks@7` bundled compiler rules)
+- Reference docs contain **only the official upstream ESLint setup** per stack (verbatim from each
+  tool's own docs) — they are not CBP preset opinions. `codebyplan eslint init` generates from the DB
+  presets, which may differ; the reference docs are the canonical official guidance
 
 ## Additional resources
 
 - TypeScript foundation (ESLint v10 flat config): [reference/base.md](reference/base.md)
-- Next.js: [reference/nextjs.md](reference/nextjs.md) · React (+ Storybook): [reference/react.md](reference/react.md)
+- Next.js: [reference/nextjs.md](reference/nextjs.md) · React: [reference/react.md](reference/react.md)
 - Node / Hono / Express: [reference/node.md](reference/node.md) · NestJS: [reference/nestjs.md](reference/nestjs.md)
 - CLI tools: [reference/cli.md](reference/cli.md) · Tailwind CSS: [reference/tailwind.md](reference/tailwind.md)
 - React Native / Expo: [reference/react-native.md](reference/react-native.md)

package/templates/skills/cbp-setup-eslint/reference/base.md

@@ -1,82 +1,71 @@
-# base — TypeScript foundation (ESLint v10 flat config)
+# base — TypeScript (official typescript-eslint setup)
 
-The foundation every TypeScript app shares: ESLint flat config, type-checked
-`typescript-eslint` rules, security scanning, and Prettier. Maps to the CBP **`base`** DB
-preset (`tech_match.requires: ["TypeScript"]`).
+> **Official source**: https://typescript-eslint.io/getting-started/ (+ typed-linting). Verified
+> 2026-05-31. ESLint flat config (`eslint.config.mjs`). This is the typescript-eslint quickstart
+> verbatim — no additions.
 
-> **Verified 2026-05-31.** ESLint is on **v10** — flat config (`eslint.config.mjs`) is the
-> only native format (legacy `.eslintrc*` was removed). `defineConfig` from `eslint/config`
-> is the canonical wrapper for every stack below.
+The foundation for any TypeScript project.
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint` | `10.4.1` | the linter (flat config only) |
-| `@eslint/js` | `10.0.1` | `js.configs.recommended` |
-| `typescript-eslint` | `8.60.0` | unified parser + plugin + presets |
-| `eslint-config-prettier` | `10.x` | turns off formatting rules (subpath `/flat`) |
-| `eslint-plugin-security` | `^3` | OWASP-style heuristics |
-| `eslint-plugin-no-secrets` | `^2.1` | high-entropy string detection |
-| `globals` | `17.6.0` | env global definitions |
+## Install
 
 ```bash
-pnpm add -D eslint @eslint/js typescript-eslint eslint-config-prettier \
-  eslint-plugin-security eslint-plugin-no-secrets globals
+npm install --save-dev eslint @eslint/js typescript typescript-eslint
 ```
 
-## Flat config
+## eslint.config.mjs — quickstart (no type info)
 
 ```js
-// eslint.config.mjs
+// @ts-check
+import js from "@eslint/js";
 import { defineConfig } from "eslint/config";
+import tseslint from "typescript-eslint";
+
+export default defineConfig(
+  js.configs.recommended,
+  tseslint.configs.recommended,
+);
+```
+
+## eslint.config.mjs — typed linting (recommended by typescript-eslint)
+
+```js
 import js from "@eslint/js";
+import { defineConfig } from "eslint/config";
 import tseslint from "typescript-eslint";
-import security from "eslint-plugin-security";
-import noSecrets from "eslint-plugin-no-secrets";
-import prettier from "eslint-config-prettier/flat";
 
-export default defineConfig([
+export default defineConfig(
   js.configs.recommended,
-  ...tseslint.configs.recommendedTypeChecked, // type-aware: no-floating-promises, etc.
-  security.configs.recommended,
-  { plugins: { "no-secrets": noSecrets }, rules: { "no-secrets/no-secrets": ["warn", { tolerance: 4.5 }] } },
+  tseslint.configs.recommended,
+  tseslint.configs.recommendedTypeChecked,
   {
     languageOptions: {
       parserOptions: {
-        projectService: true,                 // current type-info mechanism
-        tsconfigRootDir: import.meta.dirname,
+        projectService: true,
       },
     },
   },
-  { rules: { "security/detect-object-injection": "off" } }, // famously noisy
-  prettier, // MUST be last
-]);
+);
 ```
 
-## Gotchas
+## Run
 
-- **`recommended` vs `recommendedTypeChecked`.** The type-checked preset is what enables the
-  genuinely valuable rules (`no-floating-promises`, `no-misused-promises`, `no-unsafe-*`) but
-  needs type info and is **much slower** — scope it to `**/*.ts`/`**/*.tsx` and disable on JS
-  config files with `tseslint.configs.disableTypeChecked`.
-- **`projectService: true`** replaces the old `project: "./tsconfig.json"`. It auto-finds the
-  nearest `tsconfig.json` per file and lints out-of-project files (like `eslint.config.mjs`)
-  without a `tsconfig.eslint.json`. Always pair it with `tsconfigRootDir: import.meta.dirname`.
-- **`tseslint.config()` is deprecated** in favour of core `defineConfig` from `eslint/config`
-  (a near-exact clone). The `tseslint.configs.*` presets are unchanged.
-- **Prettier last.** `eslint-config-prettier/flat` must come after every rule-defining config
-  so it can switch off conflicting stylistic rules.
+```bash
+npx eslint .
+```
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-CBP's `base` DB preset currently pins `eslint: ^9.0.0` / `typescript-eslint: ^8.0.0` and
-keeps several `@typescript-eslint/no-unsafe-*` rules at `warn`. The setup above reflects the
-**latest** (`eslint@10`); both are flat-config and interoperate. Bumping the preset to v10 is
-out of scope for the skill (no DB/preset changes) — adopt v10 per-repo when you regenerate.
+- The base recommended config is `js.configs.recommended` (from `@eslint/js`, imported as `js`) —
+  **not** `eslint.configs.recommended`. `defineConfig` is imported from `eslint/config`.
+- `tseslint.configs.recommendedTypeChecked` adds rules that **require type information**; enable it
+  with `parserOptions.projectService: true`.
+- typescript-eslint *"strongly recommend[s] you do use type-aware linting,"* while noting it incurs a
+  performance penalty (TypeScript builds the project before ESLint lints).
+- `// @ts-check` type-checks the config file itself (optional). Use `eslint.config.js` if
+  `package.json` has `"type": "module"`.
+- Stricter presets are available: `strict` / `strictTypeChecked`, `stylistic` / `stylisticTypeChecked`.
 
-## Official docs
+## Source
 
-- Configuration files: https://eslint.org/docs/latest/use/configure/configuration-files
-- Typed linting: https://typescript-eslint.io/getting-started/typed-linting/
-- `projectService`: https://typescript-eslint.io/blog/project-service/
+- https://typescript-eslint.io/getting-started/
+- https://typescript-eslint.io/getting-started/typed-linting/

package/templates/skills/cbp-setup-eslint/reference/cli.md

@@ -1,56 +1,63 @@
-# cli — Node CLI tool overrides
+# cli — Node CLI tool (convention — no official preset)
 
-For Node CLI packages with a `bin` (the CBP `codebyplan` package). Layers a small **override
-block** on top of [base](base.md) + [node](node.md). Maps to the CBP **`cli`** DB preset
-(`tech_match.requires_capabilities: ["cli-bin"]`).
+> **There is no official "CLI" ESLint config or preset.** Neither ESLint nor Node publishes one. A
+> "CLI config" is a convention: a scoped `files` override inside your normal flat config that relaxes
+> a few rules a CLI legitimately trips. Only the individual official rule/plugin docs below are
+> authoritative (verified 2026-05-31).
 
-> **Verified 2026-05-31.** There is no "CLI" ESLint plugin — the convention is a scoped
-> rule-override block.
+## What a CLI override does
 
-## What it does
-
-A CLI legitimately (a) talks to the user via `console`, and (b) operates on user-supplied
-filesystem paths and dynamic keys — so the `eslint-plugin-security` heuristics that flag those
-produce noise, not findings. Relax them, **scoped narrowly** to the CLI surface.
-
-## Flat config (override block)
+A CLI prints to stdout/stderr and operates on user-supplied paths, so two official rules are commonly
+relaxed **scoped to the CLI source**:
 
 ```js
-// eslint.config.mjs — appended after base + node + security configs
+// eslint.config.mjs — appended after your base config
 export default [
-  // ...base, node, security.configs.recommended, etc.
+  // ...your base config (e.g. typescript-eslint, see base.md)...
   {
-    files: ["bin/**/*.{js,ts,mjs}", "src/cli/**/*.{js,ts}"],
+    files: ["bin/**", "src/cli/**"],
     rules: {
-      "no-console": "off", // console output IS the CLI's UI
-
-      // CLIs operate on user paths and dynamic keys by design:
+      "no-console": "off",
+      // only if eslint-plugin-security is installed (see below):
       "security/detect-non-literal-fs-filename": "off",
       "security/detect-object-injection": "off",
-
-      // optional, if eslint-plugin-n is in use (CLIs call process.exit):
-      // "n/no-process-exit": "off",
     },
   },
 ];
 ```
 
-## Gotchas
+## Official sources for the individual rules
+
+### `no-console` (core ESLint rule)
+Disallows `console` calls (treated as debugging output). It is **off** in `eslint:recommended`, so you
+only need to turn it `off` if your base config enabled it. The rule page shows the inline form, e.g.:
+
+```js
+/* eslint no-console: ["error", { allow: ["warn", "error"] }] */
+```
+
+Source: https://eslint.org/docs/latest/rules/no-console
 
-- **Scope via `files`** — do NOT disable these repo-wide; the same rules are valuable in
-  server/library code.
-- The two `security/*` lines require `eslint-plugin-security` to be installed and registered
-  (otherwise ESLint errors "rule not found"). If the project has no security plugin, only the
-  `no-console: "off"` line applies.
+### `eslint-plugin-security` (official community plugin)
+The `security/*` rules above exist only if this plugin is installed and registered:
+
+```bash
+npm install --save-dev eslint-plugin-security
+```
+
+```js
+const pluginSecurity = require('eslint-plugin-security');
+module.exports = [pluginSecurity.configs.recommended];
+```
 
-## CBP preset divergence
+Its README notes the plugin *"finds a lot of false positives which need triage by a human"* — which is
+why CLIs relax `detect-non-literal-fs-filename` / `detect-object-injection` on user-path code.
 
-The CBP `cli` preset matches the rule set above exactly (`no-console`,
-`security/detect-non-literal-fs-filename`, `security/detect-object-injection` all off) and is
-capability-gated on `cli-bin`. The repo's own `packages/codebyplan-package/eslint.config.mjs`
-already applies this. No divergence — this doc just documents the convention.
+Source: https://github.com/eslint-community/eslint-plugin-security
 
-## Official docs
+## Notes
 
-- Convention (no upstream doc); rules: https://eslint.org/docs/latest/rules/no-console and
-  https://github.com/eslint-community/eslint-plugin-security
+- Keep the relaxations **narrowly scoped via `files`** — do not disable these repo-wide.
+- If your project does not use `eslint-plugin-security`, only the `no-console: "off"` line applies.
+- The ESLint `no-console` page does **not** ship a full standalone `eslint.config.mjs` example — only
+  the inline-comment and `rules`-object forms shown above.

package/templates/skills/cbp-setup-eslint/reference/e2e.md

@@ -1,68 +1,78 @@
-# e2e — Playwright / WebdriverIO / Mocha test rules
+# e2e — Playwright / WebdriverIO / Mocha (official setups)
 
-For end-to-end specs. Three runners appear across CBP repos: **Playwright** (web), **WebdriverIO**
-(Tauri desktop), and **Mocha** (the framework WDIO drives). Each is a **directory-scoped**
-override. Playwright maps to the CBP **`testing-e2e`** preset
-(`tech_match.requires: ["Playwright"]`); WebdriverIO + Mocha are **gap stacks — no preset**.
+> **Official sources** (verified 2026-05-31):
+> - Playwright — https://github.com/mskelton/eslint-plugin-playwright
+> - WebdriverIO — https://github.com/webdriverio/webdriverio/tree/main/packages/eslint-plugin-wdio
+> - Mocha — https://github.com/lo1tuma/eslint-plugin-mocha
 
-> **Verified 2026-05-31.** Version traps: Playwright is **2.10.4** (not the 0.15.x search
-> sometimes returns); Mocha 11.x uses **`configs.recommended`** — NOT `configs.flat.recommended`.
+Each E2E runner has its own official plugin. Use the one(s) matching your test runner.
 
-## Packages
-
-| Package | Latest | Flat key |
-| ------- | ------ | -------- |
-| `eslint-plugin-playwright` | `2.10.4` | `configs['flat/recommended']` |
-| `eslint-plugin-wdio` | `9.27.2` | `configs['flat/recommended']` |
-| `eslint-plugin-mocha` | `11.3.0` | `configs.recommended` (NOT `.flat`) |
+## Playwright
 
 ```bash
-pnpm add -D eslint-plugin-playwright   # web
-pnpm add -D eslint-plugin-wdio eslint-plugin-mocha   # Tauri / WebdriverIO desktop
+npm install -D eslint-plugin-playwright
 ```
 
-## Flat config
-
 ```js
-// eslint.config.mjs
+import { defineConfig } from "@eslint/config";
 import playwright from "eslint-plugin-playwright";
-// desktop: import { configs as wdioConfigs } from "eslint-plugin-wdio";
-// desktop: import mocha from "eslint-plugin-mocha";
 
-export default [
-  // Playwright — scope to the web e2e dir
+export default defineConfig([
   {
-    ...playwright.configs["flat/recommended"],
-    files: ["e2e/**", "**/*.e2e.{ts,js}"],
-    rules: { ...playwright.configs["flat/recommended"].rules, "no-console": "off" },
+    files: ["tests/**"],
+    extends: [playwright.configs["flat/recommended"]],
+    rules: {
+      // Customize Playwright rules
+    },
   },
+]);
+```
+
+Key: **`playwright.configs["flat/recommended"]`**. The README notes you may need to change `files` to
+match your Playwright test patterns.
+
+## WebdriverIO
+
+```bash
+npm install eslint-plugin-wdio --save-dev
+```
+
+```js
+// eslint.config.mjs
+import { configs as wdioConfig } from "eslint-plugin-wdio";
 
-  // WebdriverIO + Mocha (Tauri desktop) — scope to the wdio spec dir
-  // { ...wdioConfigs["flat/recommended"], files: ["test/**", "e2e/**"] },
-  // { ...mocha.configs.recommended, files: ["test/**/*.{ts,js}"] },
+export default [
+  wdioConfig["flat/recommended"],
 ];
 ```
 
-## Gotchas
+Key: **`configs["flat/recommended"]`**. Requires ESLint v9 + flat config.
+
+## Mocha
+
+```bash
+npm install --save-dev eslint-plugin-mocha
+```
+
+```js
+import mochaPlugin from "eslint-plugin-mocha";
+
+export default [
+  mochaPlugin.configs.recommended, // or `mochaPlugin.configs.all`
+];
+```
 
-- **Scope every e2e override via `files`** — Playwright/WDIO/Mocha rules false-positive on
-  unit tests, and Testing-Library rules false-positive on e2e specs.
-- **Mocha 11.x = `mocha.configs.recommended`** — `mocha.configs.flat.recommended` is
-  `undefined` in 11.x (it only exists on the unreleased 12.x main branch) and crashes config
-  load. Don't copy a `.flat.recommended` example.
-- **WebdriverIO**: `eslint-plugin-wdio@9` requires ESLint 9+; when `typescript-eslint` is
-  present its recommended config auto-swaps `wdio/await-expect` → `wdio/no-floating-promise`.
-- The CBP web app keeps Playwright specs in `e2e/**` with a Vitest sibling override for
-  `e2e/**/__tests__/**` — mirror that split if you co-locate unit tests under `e2e/`.
+Key (latest published v11.x): **`mochaPlugin.configs.recommended`** — **NOT** `configs.flat.recommended`
+and **NOT** `configs["flat/recommended"]`. Plain dot-notation, no `flat` segment. Scope to your spec
+files via a `{ files: [...], ...mochaPlugin.configs.recommended }` wrapper if needed.
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-CBP's `testing-e2e` preset covers **Playwright only** (`eslint-plugin-playwright: ^2.0.0`,
-`no-console: off`). There is **no** preset for WebdriverIO or Mocha — the Tauri desktop e2e
-config is manual. The skill does not add presets for the gap runners.
+- Scope each runner's config to its test directory via `files` so the rules don't bleed onto other
+  files.
+- **No `flat/` prefix** on the key: Mocha (`configs.recommended`). **Bracketed `flat/` key**:
+  Playwright, WebdriverIO. Mocha's README is flat-config only (no legacy `.eslintrc` shown).
 
-## Official docs
+## Source
 
-- Playwright: https://github.com/mskelton/eslint-plugin-playwright
-- WebdriverIO: https://github.com/webdriverio/webdriverio/tree/main/packages/eslint-plugin-wdio
-- Mocha: https://github.com/lo1tuma/eslint-plugin-mocha
+See the three URLs above.

package/templates/skills/cbp-setup-eslint/reference/jest.md

@@ -1,59 +1,43 @@
-# jest — Jest test-file rules
+# jest — Jest test files (official eslint-plugin-jest setup)
 
-For apps that test with Jest (CBP `apps/backend` NestJS specs, `livebyplan` Expo). **Gap
-stack — no CBP DB preset** (the `testing` preset is Vitest-only). Layers a test-scoped
-override on top of [base](base.md).
+> **Official source**: https://github.com/jest-community/eslint-plugin-jest (verified 2026-05-31). This
+> is the plugin's official flat-config usage.
 
-> **Verified 2026-05-31.** `eslint-plugin-jest` uses the **bracketed** flat-config keys
-> `configs['flat/recommended']` / `['flat/style']` (the un-prefixed keys are legacy eslintrc).
-
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `eslint-plugin-jest` | `29.15.2` | Jest rules |
+## Install
 
 ```bash
-pnpm add -D eslint-plugin-jest
+npm install --save-dev eslint eslint-plugin-jest
 ```
 
-Peers: `eslint ^8.57 || ^9 || ^10`, `@typescript-eslint/eslint-plugin ^8`, `jest`.
-
-## Flat config
+## eslint.config.mjs — recommended config
 
 ```js
-// eslint.config.mjs
 import jest from "eslint-plugin-jest";
 
 export default [
   {
-    files: ["**/*.{test,spec}.{ts,tsx,js,jsx}", "**/__tests__/**/*.{ts,tsx,js,jsx}"],
+    // update this to match your test files
+    files: ["**/*.spec.js", "**/*.test.js"],
     ...jest.configs["flat/recommended"],
-    rules: {
-      ...jest.configs["flat/recommended"].rules,
-      ...jest.configs["flat/style"].rules, // optional stylistic rules
-      // type-aware: hand the unbound-method check to the jest-aware version
-      "@typescript-eslint/unbound-method": "off",
-      "jest/unbound-method": "error",
-    },
   },
 ];
 ```
 
-## Gotchas
-
-- Keys are **`configs['flat/recommended']`** / **`['flat/style']`** (bracketed) — the
-  unprefixed `configs.recommended` is the legacy eslintrc preset.
-- **`jest/unbound-method`** extends `@typescript-eslint/unbound-method`; turn the base rule
-  off on test files and enable the jest version (needs `@typescript-eslint/parser` + type
-  info). Type-aware jest rules safely no-op when type info is absent.
-- Avoid pinning `flat/all` long-term — it enables every rule and can break on minor releases.
+The README's manual-rules example registers globals explicitly:
+`languageOptions: { globals: jest.environments.globals.globals }`.
 
-## CBP preset divergence
+## Notes (from the official docs)
 
-There is **no** CBP `testing-jest` preset. NestJS/Expo Jest specs are currently linted only by
-the base rules. Add the override above per-repo; the skill does not add a preset.
+- Config keys: **`jest.configs["flat/recommended"]`** and **`jest.configs["flat/style"]`** (the
+  `flat/`-prefixed keys are the flat-config ones; unprefixed keys are legacy `.eslintrc`).
+- Rules assume test files, so the README says it's *"generally not suitable to include them in your
+  top-level configuration"* — scope with `files`/`ignores`.
+- **Type-aware `unbound-method`**: the README notes *"`unbound-method` depends on
+  `@typescript-eslint/eslint-plugin`, as it extends the original `unbound-method` rule."* To use it you
+  need `@typescript-eslint/parser` with type info, and you turn off the base rule in favour of
+  `jest/unbound-method`.
+- The README shows both legacy `.eslintrc` and flat config.
 
-## Official docs
+## Source
 
-- eslint-plugin-jest: https://github.com/jest-community/eslint-plugin-jest
+- https://github.com/jest-community/eslint-plugin-jest