docs: update READMEs for v1.8.0/v0.5.0/v0.7.0 features

- Root README: bump ext version to 0.7.0, add includeMswHandlers option,
  expand mocks section with /testing entry and injectMockResource,
  expand extension section with Scenarios, History inspector, local mocks
- openapi-resource-gen README: add includeMswHandlers option and output
  structure entries, add MSW handlers section, update implementation notes
- openapi-resource-mocks README: add /testing sub-entry section covering
  mockResource(), MockResourceHandle, and sequence mocking
- openapi-resource-devtools README: expand History tab with request
  inspector details, add Scenarios to toolbar table, add Local mocks section

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: constantant

README.md

@@ -93,6 +93,7 @@ Re-run the generator command whenever your spec changes — it overwrites genera
 | `namingConvention` | no | `kebab` | `kebab` or `camel` — controls file names |
 | `providedIn` | no | `none` | `none` (use `provideX()` helpers) or `root` (self-registering) |
 | `includeMocks` | no | `false` | Co-generate `.mock.ts` providers, `index.mock.ts` barrels, and `mocks.manifest.json` — requires `@constantant/openapi-resource-mocks` |
+| `includeMswHandlers` | no | `false` | Co-generate `.msw.ts` MSW 2.x handler files and `index.msw.ts` barrels — requires [`msw`](https://mswjs.io) >= 2.0.0 |
 | `specId` | no | derived | Identifier embedded in `MockResourceMeta` and `mocks.manifest.json`. Defaults to `baseUrlToken` with `_BASE_URL` stripped (e.g. `PETSTORE_BASE_URL` → `petstore`). Must match when importing into the DevTools panel. |
 | `verbose` | no | `false` | Print a `+`/`~`/`-` summary of created, updated, and deleted files after generation. |
 
@@ -257,17 +258,27 @@ A companion package that provides zero-HTTP, pure-DI mocks for generated tokens.
 - `provideMockResourceBus()` — registers the bus; exposes `window.__openApiMocks__` and `openApiMock(key)` for Playwright
 - `provideMockResource(token, key, initialBehavior?, meta?)` — replaces a token's factory with a mock; the optional `meta` (`MockResourceMeta`) is embedded automatically in generated `.mock.ts` files and used by the DevTools panel to resolve response schemas
 - DOM event bridge (`openapi-mock-event` / `openapi-mock-control`) — lets the Chrome Extension DevTools panel observe and control mocks in real time
+- `injectMockResource<T>(key)` — retrieves the `MockResourceRef<T>` for a registered key inside an injection context (e.g. `TestBed.runInInjectionContext`)
 - `MockResourceRef<T>` — `resolve()`, `setLoading()`, `fail()`, `reset()`, `simulateProgress()`, `getHistory()`
+- **`/testing` sub-entry** — `mockResource(token, behavior?)` returns a `MockResourceHandle<T>` extending `FactoryProvider`; drop directly into `TestBed` providers without a full bus setup; supports `{ sequence: [...] }` for multi-step per-call responses
 
 See [`tools/openapi-resource-mocks/README.md`](tools/openapi-resource-mocks/README.md) for full documentation.
 
 ---
 
 ## Chrome DevTools Extension — OpenAPI Resource Mocks DevTools
 
-Current version: **0.6.0** | Status: pending Chrome Web Store review
+Current version: **0.7.0** | Status: pending Chrome Web Store review
 
-A Chrome DevTools panel that connects to any Angular app running `@constantant/openapi-resource-mocks`. It lists every registered mock token, shows live state, and lets you resolve, fail, catch, or reset mocks without touching code. The **Specs** tab lets you import a `mocks.manifest.json` or full OpenAPI spec to enable schema-aware features in the Respond tab: auto-generated example payloads (⚡ Example) and JSON schema validation (✓ Validate).
+A Chrome DevTools panel that connects to any Angular app running `@constantant/openapi-resource-mocks`. It lists every registered mock token, shows live state, and lets you resolve, fail, catch, or reset mocks without touching code.
+
+Key panel features:
+- **Mock table** — live status, catch mode toggle, resolve/fail/reset actions per token
+- **Respond tab** — JSON editor with schema-aware ⚡ Example generation and ✓ Validate; delay control; catch mode release
+- **History tab** — reverse-chronological event log; for `request`/`caught` events shows the filled URL (`GET /pet/42`), path-param rows labeled by name, and Query / Body sections for remaining args; binary payloads (`[FormData]`, `[Blob]`, etc.) shown as inline badges
+- **Specs tab** — import `mocks.manifest.json` or a full OpenAPI spec (JSON or YAML, file or URL) to enable schema-aware features
+- **Scenarios** toolbar button — save named snapshots of the full mock table state, load / delete them, or export / import as JSON for cross-machine sharing
+- **＋ New mock** button — create a panel-managed (local) mock before `provideMockResource()` exists in the app, pre-configure catch mode and a response value, and have it promoted in-place when the key is registered
 
 ### Install
 

tools/openapi-resource-devtools/README.md

@@ -87,7 +87,17 @@ Manually resolve, fail, or control the selected mock:
 
 ### History tab
 
-Reverse-chronological event log for the selected mock (up to 200 entries). Each row shows the timestamp, event type badge, and a truncated JSON preview of the value or error. A **Clear** button wipes the log.
+Reverse-chronological event log for the selected mock (up to 200 entries). A **Clear** button wipes the log.
+
+Each row shows the timestamp, event type badge, and a one-line preview. For `request` and `caught` events the preview shows the **filled URL** — e.g. `GET /pet/42` — derived from the operation's path template and the actual args the component passed.
+
+Clicking a row expands a structured detail view:
+
+- **Filled URL** — the path with `{param}` placeholders substituted by positional args (e.g. `GET /pet/{petId}` → `GET /pet/42`)
+- **Path param rows** — one row per `{param}`, labeled by name from the spec, showing the actual value passed
+- **Query / Body section** — remaining args after path params are labeled **Query** (GET/HEAD/DELETE) or **Body** (POST/PUT/PATCH)
+- **Binary badges** — `[FormData]`, `[Blob]`, `[ArrayBuffer]`, and `[File: name]` are displayed as inline badges instead of quoted strings
+- **Response / Error sections** — shown for `resolve` and `error` events
 
 ---
 
@@ -145,10 +155,28 @@ After each release, if catch mode is still on, the resource is immediately re-in
 | ⏸ Catch All | Toggles catch mode on every registered mock |
 | Clear | Removes all mocks from the panel (does not affect the page) |
 | Reset All | Calls `reset()` on every mock, returning them to `idle` |
+| Scenarios | Opens the Scenarios dialog — save named snapshots of the full mock table state, load / delete them, or export / import as JSON for cross-machine sharing |
 | Filter… | Filters the mock table by key name |
 
 ---
 
+## Local (unregistered) mocks
+
+The **＋ New mock** button in the mock table toolbar lets you create a panel-managed mock before `provideMockResource()` exists in the Angular app. Use this to pre-configure a mock response while you're still writing the component code:
+
+1. Click **＋ New mock** — the **Create mock** dialog opens.
+2. Pick a spec from the **Specs** tab (the spec must already be imported), then select an operation.
+3. The key is auto-generated from the operationId (e.g. `findPetsByStatus` → `FIND_PETS_BY_STATUS`). Edit it if needed.
+4. Click **Create** — the new entry appears in the mock table with status `local`.
+
+Local mock entries support all panel controls: catch mode, the Respond tab (including ⚡ Example and ✓ Validate when a spec is imported), and the History tab. Control messages to the page are silently ignored until the matching key is registered by the app.
+
+When the app registers `provideMockResource(..., 'FIND_PETS_BY_STATUS', ...)`, the local entry is **promoted in-place** — its status transitions to `idle`, catch mode is preserved, and any pending catch-mode control is re-sent to the now-live bus.
+
+Local mock entries are persisted across DevTools sessions in `chrome.storage.local`.
+
+---
+
 ## Local development
 
 ```bash

tools/openapi-resource-gen/README.md

@@ -87,6 +87,7 @@ Re-run the same command whenever your spec changes — the generator overwrites
 | `namingConvention` | no | `kebab` | `kebab` → `find-pets-by-status.token.ts`; `camel` → `findPetsByStatus.token.ts` |
 | `providedIn` | no | `none` | `none` or `root` — see table above |
 | `includeMocks` | no | `false` | Emit a `.mock.ts` per endpoint plus `index.mock.ts` barrels and a `mocks.manifest.json` — requires [`@constantant/openapi-resource-mocks`](https://www.npmjs.com/package/@constantant/openapi-resource-mocks) |
+| `includeMswHandlers` | no | `false` | Emit a `.msw.ts` per endpoint plus `index.msw.ts` barrels — requires [`msw`](https://mswjs.io) >= 2.0.0 |
 | `specId` | no | derived from `baseUrlToken` | Identifier embedded in every generated `MockResourceMeta` and in `mocks.manifest.json`. Defaults to `baseUrlToken` with `_BASE_URL` stripped and lowercased (e.g. `PETSTORE_BASE_URL` → `petstore`). Must match the value used when importing the spec into the DevTools panel. |
 | `verbose` | no | `false` | Print a `+`/`~`/`-` summary of created, updated, and deleted files after generation. |
 
@@ -101,12 +102,15 @@ Re-run the same command whenever your spec changes — the generator overwrites
   {scheme}.security-token.ts        # one per security scheme (if any)
   index.ts                          # re-exports all tag barrels + base-url + security tokens
   index.mock.ts                     # (--includeMocks) re-exports all tag mock barrels
+  index.msw.ts                      # (--includeMswHandlers) re-exports all tag MSW handler arrays
   mocks.manifest.json               # (--includeMocks) machine-readable endpoint list + specId for the DevTools panel
   {tag}/
     index.ts                        # re-exports all token files in this tag folder
     index.mock.ts                   # (--includeMocks) re-exports all mock files in this tag
+    index.msw.ts                    # (--includeMswHandlers) re-exports all MSW handlers in this tag
     {operation-id}.token.ts         # one file per endpoint
     {operation-id}.mock.ts          # (--includeMocks) typed mock provider per endpoint
+    {operation-id}.msw.ts           # (--includeMswHandlers) MSW 2.x handler factory + pre-called array
 ```
 
 Tags map to subfolders; untagged operations go into `default/`.
@@ -235,6 +239,70 @@ Stale tag folders (left empty after their barrels are removed) are also deleted.
 
 ---
 
+## MSW handlers (`--includeMswHandlers`)
+
+Pass `--includeMswHandlers` to co-generate [MSW 2.x](https://mswjs.io) handler files
+alongside every `.token.ts`. Requires `msw >= 2.0.0`:
+
+```bash
+npm install -D msw
+
+npx nx g @constantant/openapi-resource-gen:api-resource \
+  --specPath=specs/petstore.yaml \
+  --outputDir=libs/petstore-data-access/src \
+  --baseUrlToken=PETSTORE_BASE_URL \
+  --includeMswHandlers
+```
+
+### Generated MSW file
+
+Each `.msw.ts` file exports a handler factory and a pre-called array:
+
+```typescript
+// pet/find-pets-by-status.msw.ts  (generated)
+import { http, HttpResponse } from 'msw';
+import type { FindPetsByStatusResponse } from './find-pets-by-status.token';
+
+export function findPetsByStatusHandler(body?: FindPetsByStatusResponse | null) {
+  return http.get('/pet/findByStatus', () =>
+    body !== undefined
+      ? HttpResponse.json(body)
+      : new HttpResponse(null, { status: 204 }),
+  );
+}
+
+export const findPetsByStatusHandlers = [findPetsByStatusHandler()];
+```
+
+Path params (`{id}`) are converted to MSW `:id` syntax. DELETE and other no-response endpoints
+emit `new HttpResponse(null, { status: 204 })` by default.
+
+### Barrel imports
+
+The generator registers a `/msw` path alias in `tsconfig.base.json` automatically:
+
+```json
+"@myapp/petstore-data-access/msw": ["libs/petstore-data-access/src/index.msw.ts"]
+```
+
+Use the pre-built arrays for a quick setup, or import the factory to override the response:
+
+```typescript
+import { findPetsByStatusHandlers } from '@myapp/petstore-data-access/msw';
+import { findPetsByStatusHandler } from '@myapp/petstore-data-access/msw';
+
+// In your MSW setup file:
+server.use(...findPetsByStatusHandlers);
+
+// Override with a specific response in a test:
+server.use(findPetsByStatusHandler([{ id: 1, name: 'Rex', status: 'available' }]));
+```
+
+MSW handler files are intentionally kept out of the main `index.ts` barrel so they
+are never bundled into a production build.
+
+---
+
 ## Generated token anatomy
 
 ### GET with query params
@@ -736,7 +804,7 @@ navigation in and destroyed on navigation out, with no cross-route state leakage
 | Type generation | `openapi-typescript` programmatic API | Emit `schema.d.ts` — the single source of truth for all request/response types |
 | Spec dereferencing | `@apidevtools/swagger-parser` | Resolve all `$ref` chains for endpoint extraction |
 | Security parsing | `parseSecuritySchemes(api)` | Extract scheme definitions; resolve per-operation overrides |
-| Code generation | `renderTokenFile()` / `renderSecurityTokenFile()` / `renderMockFile()` | Direct string assembly for token and mock files |
+| Code generation | `renderTokenFile()` / `renderSecurityTokenFile()` / `renderMockFile()` / `renderMswFile()` | Direct string assembly for token, mock, and MSW handler files |
 | Formatting | `@nx/devkit` `formatFiles()` | Runs Prettier over all written files |
 
 Hyphenated path parameter names (e.g. `{enterprise-team}` in the GitHub spec)

tools/openapi-resource-mocks/README.md

@@ -111,6 +111,74 @@ Types come from the generated lib — no hand-written interfaces needed.
 
 ---
 
+## Unit test helpers (`/testing`)
+
+`@constantant/openapi-resource-mocks/testing` is a lightweight sub-entry for unit tests and
+Storybook. It does not import `MockResourceBus`, register DOM events, or touch `window` —
+it simply wraps a token with a `MockResourceRef` and drops it into `TestBed` as a
+`FactoryProvider`.
+
+```typescript
+import { mockResource } from '@constantant/openapi-resource-mocks/testing';
+import { FIND_PETS_BY_STATUS } from '@myapp/petstore-data-access';
+
+const petsMock = mockResource(FIND_PETS_BY_STATUS, { value: [] });
+
+TestBed.configureTestingModule({
+  imports: [PetsComponent],
+  providers: [petsMock],   // MockResourceHandle extends FactoryProvider — drop it in directly
+});
+
+fixture.detectChanges();
+
+petsMock.ref.resolve([{ id: 1, name: 'Rex', status: 'available', photoUrls: [] }]);
+fixture.detectChanges();
+
+petsMock.expectCalled();
+petsMock.expectCalledWith({ status: 'available' });
+console.log(petsMock.calls); // readonly unknown[][]  — all factory invocations and their args
+```
+
+### `mockResource<T>(token, behaviorOrOptions?)`
+
+Returns `MockResourceHandle<T>`, which extends `FactoryProvider`.
+
+The second argument sets the initial mock state (same shapes as `provideMockResource`):
+
+| Shape | Effect |
+|-------|--------|
+| `{ value: T }` | Resolves immediately |
+| `{ value: T, delay: ms }` | Loading for `ms` ms, then resolves |
+| `{ loading: true }` | Stays loading indefinitely |
+| `{ error: unknown }` | Fails immediately |
+| `{ error: unknown, delay: ms }` | Loading for `ms` ms, then fails |
+
+### Response sequences
+
+Pass `{ sequence: [...] }` to advance through multiple states — each factory call (and
+each `reload()` in resolved state) consumes the next entry; the last entry repeats when exhausted:
+
+```typescript
+const mock = mockResource(FIND_PETS_BY_STATUS, {
+  sequence: [
+    { loading: true },
+    { error: new Error('timeout') },
+    { value: [{ id: 1, name: 'Rex', status: 'available', photoUrls: [] }] },
+  ],
+});
+```
+
+### `MockResourceHandle<T>`
+
+| Member | Description |
+|--------|-------------|
+| `.ref` | `MockResourceRef<T>` — the underlying ref; call `.resolve()`, `.fail()`, etc. to change state mid-test |
+| `.calls` | `readonly unknown[][]` — all args the factory was invoked with |
+| `.expectCalled()` | Throws if the factory was never called |
+| `.expectCalledWith(...args)` | Throws if no call matches (deep equality via recursive comparison) |
+
+---
+
 ## File upload / download progress
 
 ### In-process (unit tests / Storybook)