prizmkit 1.1.85 → 1.1.87

package/bundled/skills/prizmkit-test/references/boundary-coverage-protocol.md

@@ -0,0 +1,220 @@
+# Boundary Coverage Protocol
+
+Use this protocol during `/prizmkit-test` Phase 4 and update it during Phase 5. The goal is to prevent a common false positive: treating "there is a test for this interface" as equivalent to "this interface is safely covered." A happy path proves that the interface can work once; boundary tests prove that the interface handles realistic invalid inputs, authorization failures, ownership rules, state transitions, and dependency failures.
+
+## Required Boundary Matrix
+
+Build this matrix before writing tests and update it after generated tests pass or produce `needs-review` findings. In `scope=this-change`, build the matrix only for in-scope feature interfaces/endpoints; unrelated interfaces are recorded under `Out of Scope Gaps` and do not trigger generated tests.
+
+| Module | Interface | Service Type | Happy Path | Request Validation | Auth / Permission / Ownership | Domain Invariants | Collection / Pagination | Date / Time | State Transitions | Dependency Failure | Response Contract | N/A Reasons | Final Status |
+|--------|-----------|--------------|------------|--------------------|-------------------------------|-------------------|-------------------------|-------------|-------------------|-------------------|-------------------|-------------|--------------|
+| auth | POST /auth/login | Auth / Session | covered | generated | N/A — public route | generated | N/A — no collection input | N/A — no date input | covered | skipped — password hasher not injectable | covered | ... | boundary-covered |
+
+## Status Values
+
+Use these values consistently:
+
+- `covered` — an existing test already asserts this behavior.
+- `generated` — this run generated a test and the test passed.
+- `needs-review` — a generated test is valid, but production behavior mismatched the expected contract.
+- `unresolved` — the test could not be made runnable after the allowed fix attempts.
+- `skipped` — not applicable or not practical in this run, with a concrete reason in `N/A Reasons`.
+- `boundary-missing` — applicable boundary exists but no test covers it yet.
+
+## Completion Gate
+
+An in-scope interface is complete only when:
+
+1. It has happy-path coverage when a happy path exists.
+2. Every applicable boundary category is `covered`, `generated`, or `needs-review`.
+3. Every non-applicable category has a concrete reason.
+4. No applicable category remains `boundary-missing`.
+5. The final status is one of:
+   - `boundary-covered`
+   - `generated-needs-review`
+   - `skipped-with-reason`
+
+If an interface has only happy-path coverage, set `Final Status` to `boundary-missing` and continue generating applicable boundary tests. Do not call the run complete while any in-scope interface is `boundary-missing` or `happy-path-only`.
+
+## How to Decide Whether Existing Tests Count
+
+An existing test counts for a boundary category only when it:
+
+- targets the same public interface or endpoint,
+- creates the boundary input, state, dependency failure, or authorization context,
+- asserts the expected error code, exception, state change, response shape, or side effect,
+- verifies behavior rather than only checking that the call returned a response.
+
+Examples:
+
+- `POST /users/create` returns HTTP 200 with non-empty data → happy path only.
+- `POST /users/create` with missing email asserts `code=10001` → request validation boundary.
+- `POST /items/delete` with another user's item asserts forbidden/not-found code → ownership boundary.
+- Service create method with mocked repository failure asserts no partial side effect → dependency failure boundary.
+
+## Boundary Categories
+
+### Request Validation
+
+Use when the interface accepts client input or public parameters.
+
+Generate applicable cases for:
+- missing required fields,
+- empty string / empty array / empty object,
+- malformed JSON or wrong content type when the framework exposes that behavior,
+- wrong type,
+- unsupported enum,
+- invalid numeric values: zero, negative, min/max, just above max,
+- invalid string format: URL, email, phone, date, timestamp, UUID/ULID, object key.
+
+### Auth / Permission / Ownership
+
+Use when the interface depends on identity, roles, tenant, ownership, entitlement, or token state.
+
+Generate applicable cases for:
+- missing auth,
+- malformed auth header,
+- invalid/expired/revoked token,
+- authenticated user accessing another user's resource,
+- missing role/permission/entitlement,
+- default-deny when ownership cannot be proven.
+
+### Domain Invariants
+
+Use when business rules constrain combinations of fields or state.
+
+Generate applicable cases for:
+- ratios or totals that must sum to a value,
+- start date before end date,
+- calorie/weight/amount ranges,
+- unsupported lifecycle status,
+- duplicate unique identifiers,
+- device binding requirements,
+- token rotation/reuse semantics,
+- image quality / provider classification rules,
+- product-specific thresholds such as 90%-110% calorie hit boundaries.
+
+### Collection / Pagination
+
+Use when the interface accepts or returns lists, pages, filters, or cursors.
+
+Generate applicable cases for:
+- empty result,
+- one item,
+- many items,
+- duplicate IDs,
+- omitted page / page size defaults,
+- page 0, negative page, max page size, max + 1,
+- invalid filters,
+- nullable filters such as true/false/null,
+- stable ordering or total count when specified.
+
+### Date / Time
+
+Use when the interface parses, stores, filters, expires, schedules, or compares time.
+
+Generate applicable cases for:
+- invalid date / timestamp format,
+- timezone assumptions,
+- inclusive vs exclusive date range boundaries,
+- start after end,
+- exact expiry instant and just before/after expiry,
+- today/yesterday/stale streak or schedule semantics,
+- leap day/month end when relevant.
+
+### State Transitions
+
+Use when the interface creates, updates, deletes, confirms, unbinds, retries, logs out, refreshes, or changes status.
+
+Generate applicable cases for:
+- create then read,
+- update sets expected derived fields,
+- delete excludes from later reads,
+- double delete / unbind idempotency when specified,
+- refresh rotates token and rejects old token,
+- batch operation with empty list vs explicit IDs,
+- retry count below/at/above max,
+- no partial writes when one operation fails.
+
+### Dependency Failure
+
+Use when collaborators are mockable or the test layer can safely simulate failures.
+
+Generate applicable cases for:
+- repository/database error,
+- storage/signing provider failure,
+- SMS/push/email provider failure,
+- LLM/API client error,
+- timeout/network failure,
+- malformed provider response,
+- ID/random/clock failure when injectable.
+
+If a dependency cannot be mocked in the current test layer, mark it `skipped` with a reason and consider a lower-level unit test where it can be mocked.
+
+### Response Contract
+
+Use for API endpoints and public adapters.
+
+Generate applicable cases for:
+- unified envelope fields (`code`, `message`, `data`) or framework-specific response format,
+- fixed business error codes,
+- response field names and snake_case/camelCase contract,
+- omitted vs empty data shape,
+- generated IDs and derived fields,
+- side-effect visibility in response.
+
+## Endpoint and Interface Mapping
+
+Use names, routes, methods, schemas, binding tags, repository calls, and service logic to choose categories. When names and behavior disagree, trust behavior.
+
+| Pattern | Likely Categories |
+|---------|-------------------|
+| register / signup / create user | request validation, auth/session, domain invariants, dependency failure, response contract |
+| login | request validation, auth/session, rate limit, token response, dependency failure |
+| refresh / logout | token state, rotation/revocation, idempotency, dependency failure |
+| get / detail | auth/ownership, not found, response contract, dependency failure |
+| list / search / trends | auth, filters, pagination/empty result, date range, response contract, dependency failure |
+| create | request validation, domain invariants, state transition, dependency failure, response contract |
+| update / set goal / confirm | request validation, ownership, partial update semantics, domain invariants, state transition |
+| delete / unbind | request validation, ownership, not found, soft delete, double operation behavior |
+| upload / sign url | request validation, file/storage rules, provider failure, response contract |
+| AI / provider / recognize | request validation, date/time, provider error mapping, quality classifications, async job state |
+| stats / analytics | date range, empty data, boundary thresholds, response shape, dependency failure |
+| achievement / streak | empty state, date continuity, threshold boundaries, state persistence |
+
+## N/A Reason Rules
+
+A skipped category must explain why it does not apply or why it cannot be exercised at this level.
+
+Good reasons:
+- `N/A — public route; no authenticated principal expected`
+- `N/A — endpoint has no collection input or paginated response`
+- `N/A — dependency is not injectable at handler level; covered by service unit test`
+- `N/A — function is pure and has no stateful side effects`
+- `N/A — E2E skipped because project has no UI layer`
+
+Bad reasons:
+- `N/A`
+- `not tested`
+- `probably fine`
+- `covered by happy path`
+
+## Report Requirements
+
+The final report must include:
+
+1. The Boundary Matrix.
+2. A Completion Gate summary:
+   - interfaces total,
+   - boundary-covered count,
+   - generated-needs-review count,
+   - skipped-with-reason count,
+   - boundary-missing count,
+   - happy-path-only count.
+3. A clear final status:
+   - `All tests passing and boundary coverage complete`, or
+   - `Tests passing, but boundary coverage incomplete`, or
+   - `Tests failing`, or
+   - `Needs human review`.
+
+If any interface remains `boundary-missing` or `happy-path-only`, the final report must not say "ready for commit" without qualifying that boundary coverage is incomplete.

package/bundled/skills/prizmkit-test/references/examples.md

@@ -26,17 +26,26 @@ Scope: Full project (all modules, all specs)
 | payment | api/checkout | integration | missing |
 | — | Checkout flow | e2e | missing |
 
-**Phase 4**: Generated 5 unit tests (3 passing, 2 assertion failures marked "needs-review"), 1 integration test (passing), 1 E2E test (passing).
+**Phase 4 — Boundary Matrix** (excerpt):
+| Module | Interface | Service Type | Happy Path | Request Validation | Auth / Permission / Ownership | Domain Invariants | Dependency Failure | Final Status |
+|--------|-----------|--------------|------------|--------------------|-------------------------------|-------------------|-------------------|--------------|
+| auth | login() | Auth / Session | covered | boundary-missing | boundary-missing | skipped | boundary-missing | boundary-missing |
+| payment | processPayment() | Payment / Billing | covered | boundary-missing | boundary-missing | boundary-missing | boundary-missing | boundary-missing |
 
-**Phase 5 — Report Summary**:
+**Phase 5**: Generated 5 unit boundary tests (3 passing, 2 assertion failures marked `needs-review`), 1 integration boundary test (passing), 1 E2E test (passing).
+
+**Phase 6 — Report Summary**:
 ```
 Generated: 5 unit (2 needs-review), 1 integration, 1 E2E
+Boundary gate: failed — 2 interfaces need human review
 Report: .prizmkit/test/2026_05_23_14_30_00_testresult/test-report.md
 Needs human review: processPayment (returns 400 for negative amounts, expected 422), refund (missing authorization header causes 500 instead of 401)
 ```
 
 ## Example 2: Single-Feature Targeted Test
 
+This is an interactive single-feature selection. It is different from headless `scope=this-change`, which is driven by `.prizmkit/specs/<FEATURE_SLUG>/` and changed files.
+
 **User**: `/prizmkit-test`
 
 **Phase 0 — Architecture Detection**:
@@ -49,22 +58,86 @@ Test framework: Vitest
 ```
 Scope: Single feature — 042-payment-gateway
 Test files in scope: 2
+```
 
 **Phase 2 — Existing Tests**: 2 test files, 8 tests, all passing.
 
 **Phase 3 — Gap Analysis** (excerpt):
 | Module | Interface | Type | Status |
 |--------|-----------|------|--------|
-| payment | processPayment() | unit | missing |
-| payment | refund() | unit | missing |
+| payment | processPayment() | unit | boundary-missing |
+| payment | refund() | unit | boundary-missing |
+
+**Phase 4 — Boundary Matrix**:
+| Module | Interface | Service Type | Happy Path | Request Validation | Auth / Permission / Ownership | Domain Invariants | State Transitions | Dependency Failure | Final Status |
+|--------|-----------|--------------|------------|--------------------|-------------------------------|-------------------|-------------------|-------------------|--------------|
+| payment | processPayment() | Payment / Billing | covered | boundary-missing | boundary-missing | boundary-missing | generated | boundary-missing | boundary-missing |
+| payment | refund() | Payment / Refund | covered | boundary-missing | boundary-missing | boundary-missing | boundary-missing | skipped — provider sandbox unavailable | boundary-missing |
 
-**Phase 4**: Generated 2 unit tests (both passing). No integration/E2E applicable for this scope.
+**Phase 5**: Generated 8 unit tests covering amount boundaries, currency mismatch, missing entitlement, duplicate idempotency key, partial refund, full refund, over-refund, and repository failure. All passing.
 
-**Phase 5 — Report Summary**:
+**Phase 6 — Report Summary**:
 ```
-Generated: 2 unit tests (all passing)
+Generated: 8 unit tests (all passing)
+Boundary gate: passed
 Report: .prizmkit/test/2026_05_23_15_00_00_testresult/test-report.md
-All tests passing. Ready for commit.
+All tests passing and boundary coverage complete. Ready for commit.
+```
+
+## Example 3: Existing Happy Path Is Not Enough
+
+**User**: `/prizmkit-test user module`
+
+**Existing tests found**:
+```
+TestHandler_UpdateProfile_Success
+TestHandler_GetProfile_Success
+```
+
+**Boundary Matrix result**:
+| Module | Interface | Service Type | Happy Path | Request Validation | Auth / Permission / Ownership | Domain Invariants | Dependency Failure | Final Status |
+|--------|-----------|--------------|------------|--------------------|-------------------------------|-------------------|-------------------|--------------|
+| user | POST /user/update-profile | Validation / CRUD | covered | boundary-missing | boundary-missing | boundary-missing | boundary-missing | boundary-missing |
+| user | POST /user/get-profile | CRUD / Auth | covered | N/A — empty request | boundary-missing | N/A — no domain input | boundary-missing | boundary-missing |
+
+**Correct action**:
+Generate tests for:
+- missing auth,
+- invalid gender,
+- invalid activity level,
+- implausible height/weight when specified by service contract,
+- user not found,
+- repository failure,
+- response envelope shape.
+
+**Incorrect action**:
+Do not report `user` as covered just because both endpoints have success tests.
+
+
+## Example 3: Feature Pipeline this-change Run
+
+**Caller**: `/prizmkit-test scope=this-change artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`
+
+**Expected behavior**:
+- Reads `.prizmkit/specs/{{FEATURE_SLUG}}/spec.md`, `plan.md`, and optional `context-snapshot.md`.
+- Builds in-scope files from changed files and feature artifacts.
+- Generates or updates only tests for this feature's changed files, public interfaces, and acceptance criteria.
+- Records unrelated historical gaps under `Out of Scope Gaps`.
+- Does not generate tests for unrelated modules.
+- Does not infer this-change mode from `.prizmkit/bugfix/{{BUG_ID}}/` or `.prizmkit/refactor/{{REFACTOR_ID}}/`.
+
+**Report excerpt**:
+```markdown
+## Scope
+- Mode: this-change
+- Artifact Dir: .prizmkit/specs/{{FEATURE_SLUG}}/
+- Generation Policy: in-scope-only
+
+## Out of Scope Gaps
+- payment: missing legacy tests, but this feature did not change payment code.
+
+## Verdict
+PASS
 ```
 
-**HANDOFF**: Independent skill — no handoff. User may proceed to `/prizmkit-committer` if all tests pass, or fix issues manually if tests are marked "needs-review".
+**HANDOFF**: Independent skill — no handoff. User may proceed to `/prizmkit-committer` only if tests pass and the boundary completion gate passes, or fix issues manually if tests are marked `needs-review`.

package/bundled/skills/prizmkit-test/references/service-boundary-test-catalog.md

@@ -0,0 +1,225 @@
+# Service Boundary Test Catalog
+
+Use this catalog during `/prizmkit-test` Phase 4a when generating unit tests for service-like functions or class methods. The goal is to turn "write boundary tests" into service-specific scenarios that match the unit's business responsibility.
+
+## How to Use This Catalog
+
+1. Classify the tested unit by reading its name, module path, parameters, dependencies, state changes, and related Prizm docs/spec acceptance criteria.
+2. Select every service type that applies. A function can be both a payment service and an idempotency service, or both a repository and pagination service.
+3. Map candidate boundaries to the actual contract in code/docs. Assert behavior that is specified or clearly implied; if expected behavior is unclear, mark the case as `needs-review` instead of inventing production behavior.
+4. Mock external dependencies for unit tests: databases, network calls, file storage, queues, payment gateways, email providers, clocks, and random ID generators.
+5. Record non-applicable categories as `N/A` with a short reason in the boundary coverage report so skipped categories are explicit.
+
+## Service Type Detection
+
+| Signal | Likely Service Type |
+|--------|---------------------|
+| login, logout, signup, password, session, token, jwt, oauth, refresh | Auth / Session / Token |
+| role, permission, policy, access, entitlement, plan, quota, ownership | Authorization / Permission / Entitlement |
+| payment, wallet, billing, subscription, invoice, refund, balance, currency | Payment / Wallet / Billing / Refund |
+| repository, model, dao, create, read, update, delete, insert, save, remove | CRUD / Repository / Database |
+| search, list, page, cursor, filter, sort, query, limit, offset | Search / List / Pagination |
+| validate, parse, normalize, transform, schema, sanitize, format | Validation / Parser / Normalizer |
+| upload, download, storage, file, blob, s3, image, mime, path | File Upload / Storage |
+| notify, email, sms, webhook, template, recipient, provider | Notification / Email / Webhook |
+| job, queue, worker, scheduler, cron, retry, backoff, task | Job / Queue / Scheduler |
+| cache, ttl, rate limit, throttle, idempotency, dedupe, lock | Cache / Rate Limit / Idempotency |
+| client, sdk, request, fetch, provider, api key, endpoint, response | API Client / Third-Party Integration |
+| date, time, expiry, expiration, ttl, schedule, window, timezone | Date / Time / Expiration |
+
+When names and behavior disagree, trust behavior and dependencies over names. For example, `createCheckoutSession()` is payment-related even if it lives in a controller module.
+
+## Universal Boundary Matrix
+
+Apply these categories to every public function/class method before adding service-specific cases:
+
+- **Valid input**: typical valid input, minimal valid input, and complex valid input when supported.
+- **Empty input**: `null` / `undefined` / `None`, empty string, empty array/object, whitespace-only string.
+- **Numeric boundaries**: zero, one, minimum allowed value, maximum allowed value, just below/above limits.
+- **Collection boundaries**: zero items, one item, many items, duplicate items, first/last element behavior.
+- **Type and format errors**: wrong type, malformed string, unsupported enum, missing required parameter.
+- **Branch paths**: each `if/else`, `switch/case/default`, ternary side, and loop path with zero/one/many iterations.
+- **State and side effects**: before/after state, writes, emitted events, dependency method calls, call count/order/arguments.
+- **Dependency failures**: mocked database errors, network timeouts, storage failures, provider errors, clock/randomness behavior.
+
+## Service-Specific Boundary Cases
+
+### Auth / Session / Token Services
+
+Generate applicable cases for:
+
+- Missing identifier, missing password, empty credentials, malformed email/username.
+- Identifier normalization: uppercase/lowercase email, leading/trailing whitespace, Unicode usernames when supported.
+- User not found, wrong password, unverified account, disabled account, locked account.
+- Failed login count just below/at/above lock threshold.
+- Successful login creates exactly one session/token with expected expiry and persisted state.
+- Token missing, malformed, invalid signature, wrong algorithm, expired, not-yet-valid, revoked.
+- Refresh token rotation: old refresh token reuse, missing refresh token, expired refresh token, revoked refresh token.
+- Logout idempotency: logout with valid token, already logged-out token, missing token.
+- OAuth/callback flows: missing code, missing state, state mismatch, provider error, provider returns incomplete profile.
+- Dependency failures: user store error, password hasher error, token signer/verifier error, clock skew.
+
+### Authorization / Permission / Entitlement Services
+
+Generate applicable cases for:
+
+- Missing principal, anonymous principal, principal without roles/permissions.
+- Default-deny behavior when no policy matches.
+- Role hierarchy: basic role, elevated role, admin override, deny rule precedence.
+- Resource ownership: owner, non-owner, tenant mismatch, organization mismatch.
+- Entitlement states: active, expired, canceled, trial, disabled feature, missing plan.
+- Quota boundaries: usage below limit, exactly at limit, one over limit, reset window boundary.
+- Duplicate or conflicting permissions.
+- Policy conditions with missing attributes, malformed attributes, unknown action/resource.
+- Dependency failures: policy store error, entitlement lookup error, quota service timeout.
+
+### Payment / Wallet / Billing / Refund Services
+
+Generate applicable cases for:
+
+- Amount zero, negative amount, minimum billable unit, maximum allowed amount, just above maximum.
+- Currency precision: too many decimal places, integer minor units, rounding at half-unit boundaries.
+- Balance boundaries: balance exactly equals debit amount, balance one minor unit below amount, zero balance.
+- Currency mismatch between wallet, invoice, and payment request.
+- Idempotency: missing key, duplicate key with same payload, duplicate key with different payload.
+- Transaction states: pending, succeeded, failed, canceled, already paid, already refunded.
+- Refund boundaries: zero refund, partial refund, full refund, cumulative refunds equal original amount, cumulative refunds exceed original amount.
+- Concurrent debit/refund attempts against the same account or transaction.
+- Subscription/billing cycles: trial start/end, expired subscription, canceled subscription, renewal at boundary time.
+- Provider failures: timeout, 4xx/5xx, malformed response, duplicate provider event, out-of-order webhook.
+- Side effects: ledger entry count, balance mutation, webhook/event emission, provider call arguments.
+
+### CRUD / Repository / Database Services
+
+Generate applicable cases for:
+
+- Create with missing required fields, nullable fields set to `null`, optional fields omitted.
+- Duplicate unique key, generated ID collision, invalid foreign key, unknown enum value.
+- Read/update/delete with nonexistent ID, malformed ID, deleted/soft-deleted ID.
+- Partial update semantics: omitted field vs `undefined` vs `null`, empty patch object.
+- Optimistic locking: expected version, stale version, missing version.
+- Soft delete behavior: excluded by default, included only when requested, double delete idempotency.
+- Transaction behavior: rollback when one write fails, no partial side effects after failure.
+- Database dependency errors: connection failure, constraint violation, timeout.
+- Repository side effects: correct query arguments, write count, returned entity shape.
+
+### Search / List / Pagination / Sorting Services
+
+Generate applicable cases for:
+
+- Empty query, whitespace query, special characters, Unicode query, injection-like strings treated as data.
+- No results, one result, many results, duplicate ranking/sort values.
+- Page/offset pagination: page 0, page 1, last page, beyond last page, negative page/offset.
+- Cursor pagination: missing cursor, malformed cursor, expired cursor, cursor at final item.
+- Limit boundaries: omitted limit, limit 0, limit 1, maximum limit, maximum + 1.
+- Sorting: default sort, invalid sort field, invalid direction, stable ordering with ties.
+- Filters: empty filter set, unknown filter, conflicting filters, inclusive/exclusive date ranges.
+- Total count and hasNext/hasPrevious flags at page boundaries.
+- Dependency failures: search index unavailable, database query error, stale index response.
+
+### Validation / Parser / Normalizer Services
+
+Generate applicable cases for:
+
+- Missing input, `null` / `undefined` / `None`, empty string, whitespace-only string.
+- Minimum and maximum length; just below/above configured length boundaries.
+- Special characters, Unicode, emoji, newline/control characters, normalization-sensitive characters.
+- Wrong type, mixed-type arrays, numeric strings vs numbers, booleans represented as strings.
+- Unknown fields in strict mode, extra fields in permissive mode, duplicate keys/items.
+- Invalid formats: email, URL, date, UUID, JSON, CSV, phone number, currency.
+- Normalization idempotency: applying the normalizer twice yields the same result.
+- Error shape: path/field name, code, message, and aggregation of multiple errors.
+- Parser failures: malformed payload, truncated payload, unsupported version/schema.
+
+### File Upload / Storage Services
+
+Generate applicable cases for:
+
+- Zero-byte file, one-byte file, just below max size, exactly max size, just above max size.
+- MIME/type mismatch between content, extension, and declared header.
+- Unsupported file type, missing extension, uppercase extension, compound extension.
+- Filename boundaries: empty name, very long name, Unicode name, duplicate name, path traversal characters.
+- Storage key collisions and deterministic key generation.
+- Checksum/hash mismatch, corrupted stream, interrupted upload, storage write failure.
+- Image/media metadata boundaries: dimensions too small/large, unsupported codec, malformed metadata.
+- Delete/read behavior for missing object, already-deleted object, permission-denied object.
+- Side effects: storage provider call arguments, metadata record creation, cleanup on failure.
+
+### Notification / Email / Webhook Services
+
+Generate applicable cases for:
+
+- Missing recipient, invalid email/phone/URL, empty recipient list, duplicate recipients.
+- Recipient preferences: unsubscribed, disabled channel, quiet hours, blocked user.
+- Template variables: missing required variable, extra variable, `null` variable, special characters/HTML escaping.
+- Provider selection: unsupported channel, fallback provider, disabled provider.
+- Deduplication: duplicate notification key, repeated webhook event, retry with same id.
+- Provider responses: success, rate limit, timeout, 4xx/5xx, malformed response, partial multi-recipient failure.
+- Webhook security: missing signature, invalid signature, timestamp outside tolerance, replayed event.
+- Side effects: event status persisted, retry scheduled or suppressed, provider called with expected payload.
+
+### Job / Queue / Scheduler Services
+
+Generate applicable cases for:
+
+- Missing payload, empty payload, malformed payload, unsupported job type/version.
+- Duplicate job ID, idempotent processing of already-completed job, requeue behavior.
+- Retry boundaries: first failure, retry count just below max, at max, over max, poison/dead-letter path.
+- Backoff calculation: zero delay, minimum delay, maximum delay, jitter bounds when deterministic/mocked.
+- Schedule boundaries: run in past, run now, run in future, invalid cron, daylight-saving transition.
+- Concurrency: two workers claim same job, lock acquisition failure, stale lock recovery.
+- Cancellation: before start, during processing, after completion.
+- Side effects: ack/nack calls, status transitions, retry scheduling, emitted events.
+
+### Cache / Rate Limit / Idempotency Services
+
+Generate applicable cases for:
+
+- Cache miss, hit, stale hit, expired entry, invalidation, key collision.
+- TTL boundaries: zero TTL, negative TTL, one unit TTL, exact expiry instant, just before/after expiry.
+- Serialization/deserialization failure, corrupted cached value, unsupported value type.
+- Cache stampede: concurrent misses for the same key should not duplicate expensive work when guarded.
+- Rate limit boundaries: count below limit, exactly at limit, one above limit, window rollover.
+- Missing actor key: anonymous user, missing IP, shared tenant/global scope.
+- Idempotency key: missing, malformed, reused with same payload, reused with different payload, expired record.
+- Lock behavior: lock unavailable, lock timeout, release on success, release on failure.
+- Backing store failures: Redis/cache down, slow response, partial write.
+
+### API Client / Third-Party Integration Services
+
+Generate applicable cases for:
+
+- Missing base URL, missing API key, malformed configuration, unsupported region/environment.
+- Request building: query encoding, header inclusion, body serialization, path parameter escaping.
+- Response handling: 200 with valid body, 204/no body, malformed JSON, missing required field, unknown extra field.
+- Error responses: 400, 401/403, 404, 409, 429, 500/503; retryable vs non-retryable classification.
+- Timeout, network error, DNS/connect failure, aborted request.
+- Retry boundaries: zero retries, one retry then success, max retries exhausted, backoff capped.
+- Pagination: empty page, last page, next token missing/malformed, duplicate page token.
+- Auth refresh/signing: expired access token, refresh failure, invalid signature, clock skew.
+- Circuit breaker or fallback behavior when present.
+
+### Date / Time / Expiration Services
+
+Generate applicable cases for:
+
+- Exact boundary: `now == startsAt`, `now == expiresAt`, one millisecond/second before and after.
+- Inclusive vs exclusive interval ends according to the contract.
+- Start after end, zero-length interval, negative duration, missing timezone.
+- Time zones: UTC vs local time, DST jump forward/back, leap day, month end, year end.
+- Clock skew tolerance for tokens, webhooks, scheduled jobs, and signed requests.
+- Recurring schedules: first occurrence, last occurrence, skipped occurrence, invalid cron/expression.
+- TTL/window calculations: zero TTL, negative TTL, max TTL, rollover between windows.
+
+## When Multiple Service Types Apply
+
+Combine the relevant sections and remove duplicate cases. Prioritize tests that exercise business invariants over tests that only repeat generic invalid input handling. For example, a wallet debit function should cover payment amount boundaries, idempotency replay, and date/expiration behavior if it also accepts an expiring authorization.
+
+## N/A Rules
+
+Mark a category `N/A` when the unit has no corresponding input, state, or dependency. Include a short reason:
+
+- `N/A — no external provider dependency`
+- `N/A — function is pure and has no stateful side effects`
+- `N/A — pagination is handled by caller, not this unit`
+- `N/A — concurrency safety belongs to integration test because unit has no shared mutable state`