memento-mori-jester 0.1.89 → 0.1.91

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to Memento Mori Jester are tracked here.
 
 ## Unreleased
 
+## 0.1.91
+
+- Added checked public-safe maintainer response snippets for `docs-example`, `fixture-backlog`, and `rule-review-candidate` support outcomes.
+- Extended `npm run support:check` and production-readiness checks so response snippets stay aligned with the checked triage playbook.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and release notes for lower-friction support replies.
+
+## 0.1.90
+
+- Added `examples/support`, a checked maintainer triage playbook for sanitized report-gallery and false-positive reports.
+- Extended `npm run support:check` and production-readiness checks so the playbook keeps public-safe examples, first responses, classifications, and follow-up outcomes aligned.
+- Updated README, report docs, maintainer triage docs, release docs, production-readiness docs, roadmap, and release notes for deterministic support handling.
+
 ## 0.1.89
 
 - Added a report-gallery feedback issue template for public-safe reports about confusing or stale checked examples, and strengthened false-positive reports with version and redacted `doctor --json` prompts.

package/README.md

@@ -76,6 +76,8 @@ For trust-building output examples, see [examples/reports](examples/reports). `n
 
 If one of those reports is confusing or stale, use the public-safe [report gallery feedback template](examples/reports/feedback-template.md). It asks for version, nearest gallery example, sanitized command/output summaries, and redacted diagnostics without private repo code or secrets.
 
+Maintainers can use the checked [support triage playbook](examples/support) and [response snippets](examples/support/response-snippets.md) to turn sanitized reports into a docs example, fixture backlog item, or rule-review candidate without changing behavior first.
+
 Expected vibe:
 
 ```text
@@ -448,6 +450,8 @@ More setup examples:
 - [Consumer Quickstart Smoke](examples/consumer-quickstart)
 - [Real-World Report Gallery](examples/reports)
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
+- [Support Triage Playbook](examples/support)
+- [Maintainer Response Snippets](examples/support/response-snippets.md)
 - [Security Policy](SECURITY.md)
 - [Maintainer Triage](docs/MAINTAINER_TRIAGE.md)
 - [Changelog](CHANGELOG.md)
@@ -469,6 +473,8 @@ Framework CI examples:
 - [Consumer Quickstart Smoke](examples/consumer-quickstart)
 - [Real-World Report Gallery](examples/reports)
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
+- [Support Triage Playbook](examples/support)
+- [Maintainer Response Snippets](examples/support/response-snippets.md)
 - [Next.js CI](examples/ci/nextjs.yml)
 - [Vite React CI](examples/ci/vite-react.yml)
 - [Express API CI](examples/ci/express-api.yml)
@@ -525,7 +531,7 @@ Maintainers can use [docs/MAINTAINER_TRIAGE.md](docs/MAINTAINER_TRIAGE.md) to tu
 Run `npm run fixtures:check` before merging fixture changes; it catches duplicate IDs, missing rule metadata, weak descriptions, unsafe-looking content, and duplicate content.
 Run `npm run fixtures:report` to see fixture coverage by rule, rule family, preset slice, kind, verdict, quiet-pass boundaries, feasible pass-case gaps, and curation-next guidance before choosing the next fixture. Use `npm run fixtures:report -- --markdown` when you want a paste-ready summary for release notes or GitHub issues.
 Run `npm run reports:check` after editing [examples/reports](examples/reports); it verifies the public report gallery against an installed package in a temporary consumer project.
-Run `npm run support:check` after editing issue templates, support docs, or the report gallery feedback path; it verifies the public report template asks for useful redacted context without inviting secrets or private code.
+Run `npm run support:check` after editing issue templates, support docs, the report gallery feedback path, the [support triage playbook](examples/support), or [response snippets](examples/support/response-snippets.md); it verifies the public templates ask for useful redacted context without inviting secrets or private code.
 Run `npm run promo:card` to regenerate the repo-local social preview card after changing its copy or design.
 Run `npm run promo:check` after editing promo assets; it checks the current demo video, stills, docs, and fixture evidence numbers stay in sync.
 Run `npm run site:check` after editing the repo-local landing page; it verifies the start command, demo links, social card, repo, release, and npm links.

package/ROADMAP.md

@@ -6,6 +6,8 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
 
 ## Recently Shipped
 
+- Checked maintainer response snippets in v0.1.91, adding public-safe reply templates for docs examples, fixture backlog items, and rule-review candidates.
+- Checked maintainer triage playbook in v0.1.90, showing how sanitized reports become docs examples, fixture backlog items, or rule-review candidates.
 - Checked adopter feedback path in v0.1.89, adding a report-gallery issue template, package-shipped feedback template, and support triage guard.
 - Checked report gallery in v0.1.88, proving fresh `doctor`, destructive-command `summary`, and blocked-command reports from an installed consumer project.
 - Consumer quickstart registry-mode fix in v0.1.87, proving the same smoke against `memento-mori-jester@latest` after publish.
@@ -79,7 +81,7 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
 ## Product Ideas
 
 - Collect real-world reports and fold the strongest redacted cases into more framework tuning cookbook recipes.
-- Turn repeated report-gallery feedback into clearer gallery examples or redacted fixtures.
+- Use repeated playbook outcomes and response snippets to prioritize the next redacted fixture or report-gallery update.
 - Add a hosted-page option or GitHub Pages instructions once the static page has settled.
 
 ## Quality And Safety

package/docs/MAINTAINER_TRIAGE.md

@@ -21,6 +21,8 @@ For users who just need to understand what a healthy report looks like, point th
 
 For users who say a gallery report is confusing, stale, or hard to compare with their local output, point them at [examples/reports/feedback-template.md](../examples/reports/feedback-template.md) or the GitHub [report gallery feedback issue template](../.github/ISSUE_TEMPLATE/report_gallery_feedback.yml). It asks for the nearest checked example, sanitized command and output summaries, version, and redacted diagnostics without asking for private code.
 
+When a report has enough public-safe detail to triage, compare it with the checked [support triage playbook](../examples/support). The playbook walks sanitized report-gallery and false-positive reports through first response, classification, and a follow-up outcome. Use [response-snippets.md](../examples/support/response-snippets.md) to reply consistently after choosing the outcome.
+
 Do not ask users to paste secrets, private code, customer data, live credentials, complete CI logs, or unredacted SARIF. If the report involves credential exposure, command execution, unexpected network access, private code disclosure, package publishing, or MCP data exposure, route it through [SECURITY.md](../SECURITY.md).
 
 ## Triage Labels
@@ -57,6 +59,14 @@ Use report-gallery feedback when the issue is about understanding installed-pack
 - a small docs update,
 - or a redacted fixture only if the report exposes a reusable rule boundary.
 
+Use the playbook outcomes consistently:
+
+- `docs-example`: the behavior is expected but the report or wording is unclear.
+- `fixture-backlog`: the reduced report looks safe and should become a pass or quiet-pass fixture.
+- `rule-review-candidate`: repeated sanitized reports suggest guidance or matching may need review, but not from a single report.
+
+Use the matching response snippet for the first public reply, then adapt only the project-neutral parts: the rule id, minimal command summary, fixture id, and next command. Do not add private code, private paths, tokens, full logs, or exploitable details to the response.
+
 After editing report support docs or issue templates, run:
 
 ```powershell

package/docs/PRODUCTION_READINESS.md

@@ -47,6 +47,7 @@ This checklist defines what "production grade" means for Memento Mori Jester rig
 - `README.md` leads with a no-write first run, project bootstrap, agent setup, and optional hooks/CI.
 - `docs/GETTING_STARTED.md`, `docs/CLI.md`, `docs/RELEASE.md`, and `docs/TRUSTED_PUBLISHING.md` cover the core adoption and release paths.
 - `examples/reports` provides checked, public-safe report examples for fresh install diagnostics, summary output, blocked command reviews, and report-gallery feedback.
+- `examples/support` provides a checked maintainer triage playbook and response snippets for first response, classification, and follow-up outcomes from sanitized support reports.
 - `site/index.html` gives maintainers a static one-page share surface that reuses the demo, social card, start command, and public links.
 - Every public release has matching `CHANGELOG.md` notes and `docs/RELEASE_NOTES_vX.Y.Z.md`.
 
@@ -59,13 +60,14 @@ This checklist defines what "production grade" means for Memento Mori Jester rig
 - GitHub issue templates collect bug reports, false-positive reports, report-gallery feedback, and feature requests with the diagnostic context maintainers need.
 - `SECURITY.md` routes vulnerability reports away from public issues and asks for redacted diagnostics.
 - `docs/MAINTAINER_TRIAGE.md` explains how to turn useful false-positive reports into fixture coverage before changing rule logic.
+- `examples/support` shows maintainers how to classify sanitized reports as a docs example, fixture backlog item, or rule-review candidate before changing behavior, then reply with public-safe response snippets.
 - `npm run fixtures:check` validates fixture IDs, metadata, unsafe-looking content, duplicate content, and explicit expected/absent rule intent.
 - `npm run fixtures:report` shows fixture coverage by rule, rule family, preset slice, kind, verdict, quiet-pass rule boundaries, and feasible pass-case gaps so maintainers can pick the next fixture target; `npm run fixtures:report -- --markdown` produces a paste-ready maintainer snapshot.
 - `npm run framework:tuning:check` keeps the framework tuning guide, cookbook JSON, cookbook README, and fixture IDs aligned.
 - `npm run framework:tuning:doctor` runs the cookbook tune commands through the built CLI with temporary preset configs, so package consumers do not inherit stale recipes.
 - `npm run consumer:quickstart:check` installs the package into a temporary minimal project and runs `doctor`, `summary`, and packaged framework tuning checks from that consumer side.
 - `npm run reports:check` installs the package into a temporary minimal project and runs the report gallery's `doctor`, `summary`, and blocked-command examples through that consumer side.
-- `npm run support:check` verifies issue templates, support docs, and the report gallery feedback template stay public-safe and ask for useful redacted context.
+- `npm run support:check` verifies issue templates, support docs, the report gallery feedback template, the maintainer triage playbook, and response snippets stay public-safe and ask for useful redacted context.
 - `npm run promo:card` regenerates the deterministic social preview card, and `npm run promo:check` verifies current repo-local promo assets against the current fixture evidence before maintainers post or refresh the demo.
 - `npm run site:check` verifies the static landing page before maintainers post or host it.
 - npm publish has a manual workflow fallback, but the normal release path is tag-driven trusted publishing.
@@ -97,4 +99,4 @@ This checklist defines what "production grade" means for Memento Mori Jester rig
 ## Known Next Gaps
 
 - Continue expanding real-world preset fixtures and false-positive examples so tuning remains evidence-based.
-- Fold the strongest redacted support reports into fixture or report-gallery updates.
+- Fold the strongest redacted support reports into fixture, playbook, or report-gallery updates.

package/docs/RELEASE.md

@@ -30,7 +30,7 @@ Move the current changelog bullets into a matching version section and add `docs
 ## 2. Tag And Push
 
 ```powershell
-git add package.json package-lock.json CHANGELOG.md docs/RELEASE_NOTES_v0.1.x.md docs/PRODUCTION_READINESS.md docs/MAINTAINER_TRIAGE.md docs/FRAMEWORK_TUNING.md docs/GITHUB_ACTIONS.md examples/ci examples/consumer-quickstart examples/reports examples/tuning scripts/check-ci-adoption.mjs scripts/check-consumer-quickstart.mjs scripts/check-report-gallery.mjs scripts/check-support-triage.mjs scripts/check-framework-tuning.mjs scripts/doctor-framework-tuning.mjs SECURITY.md .github/ISSUE_TEMPLATE
+git add package.json package-lock.json CHANGELOG.md docs/RELEASE_NOTES_v0.1.x.md docs/PRODUCTION_READINESS.md docs/MAINTAINER_TRIAGE.md docs/FRAMEWORK_TUNING.md docs/GITHUB_ACTIONS.md examples/ci examples/consumer-quickstart examples/reports examples/support examples/tuning scripts/check-ci-adoption.mjs scripts/check-consumer-quickstart.mjs scripts/check-report-gallery.mjs scripts/check-support-triage.mjs scripts/check-framework-tuning.mjs scripts/doctor-framework-tuning.mjs SECURITY.md .github/ISSUE_TEMPLATE
 git commit -m "Release v0.1.x"
 git tag -a v0.1.x -m "Memento Mori Jester v0.1.x"
 git push origin main

package/docs/RELEASE_NOTES_v0.1.90.md

@@ -0,0 +1,58 @@
+# Memento Mori Jester v0.1.90
+
+## Summary
+
+This release adds a checked maintainer triage playbook for sanitized support reports. The goal is to make report handling deterministic after users submit public-safe report-gallery feedback or false-positive reports: first response, classification, and follow-up outcome are now documented and checked.
+
+## What Changed
+
+- Added `examples/support/README.md`.
+- Added `examples/support/triage-playbook.json`.
+- Extended `scripts/check-support-triage.mjs` to validate the playbook.
+- Extended production-readiness checks for the playbook.
+- Updated README, report gallery docs, maintainer triage docs, release docs, production-readiness docs, roadmap, and changelog.
+
+## Public Interface
+
+- No CLI command changes.
+- No MCP tool changes.
+- No config schema changes.
+- No review rule, scoring, matching, or verdict behavior changes.
+- No GitHub Action input changes.
+- Support docs and package examples now include a checked maintainer playbook.
+
+## Release Validation
+
+```powershell
+npm.cmd test
+npm.cmd run support:check
+npm.cmd run reports:check
+npm.cmd run demo:svg:check
+npm.cmd run promo:card:check
+npm.cmd run promo:check
+npm.cmd run fixtures:report
+npm.cmd run fixtures:report -- --json
+npm.cmd run fixtures:report -- --markdown
+npm.cmd run pack:dry
+git diff --check
+node .\dist\cli.js doctor
+node .\dist\cli.js summary --kind command "git reset --hard"
+git diff | node .\dist\cli.js diff --fail-on block --subject "v0.1.90 checked maintainer triage playbook"
+```
+
+Expected:
+
+- `support:check` verifies issue templates, feedback templates, and the maintainer triage playbook.
+- `reports:check` still verifies the installed-package report gallery.
+- fixture report still shows `Fixtures: 222`.
+- GitHub Release and npm Publish complete from the `v0.1.90` tag.
+
+After publish:
+
+```powershell
+npm.cmd view memento-mori-jester version --silent
+npx.cmd -y memento-mori-jester@latest doctor
+npx.cmd -y memento-mori-jester@latest summary --kind command "git reset --hard"
+npm.cmd run support:check
+npm.cmd run reports:check -- --package memento-mori-jester@latest
+```

package/docs/RELEASE_NOTES_v0.1.91.md

@@ -0,0 +1,58 @@
+# Memento Mori Jester v0.1.91
+
+## Summary
+
+This release adds checked maintainer response snippets for the three support outcomes introduced by the triage playbook: docs clarification, fixture backlog, and rule-review candidate. The goal is to reduce response friction while keeping public replies safe, consistent, and evidence-based.
+
+## What Changed
+
+- Added `examples/support/response-snippets.md`.
+- Added `examples/support/response-snippets.json`.
+- Extended `scripts/check-support-triage.mjs` to validate response snippets.
+- Extended production-readiness checks for response snippets.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and changelog.
+
+## Public Interface
+
+- No CLI command changes.
+- No MCP tool changes.
+- No config schema changes.
+- No review rule, scoring, matching, or verdict behavior changes.
+- No GitHub Action input changes.
+- Support docs and package examples now include checked maintainer response snippets.
+
+## Release Validation
+
+```powershell
+npm.cmd test
+npm.cmd run support:check
+npm.cmd run reports:check
+npm.cmd run demo:svg:check
+npm.cmd run promo:card:check
+npm.cmd run promo:check
+npm.cmd run fixtures:report
+npm.cmd run fixtures:report -- --json
+npm.cmd run fixtures:report -- --markdown
+npm.cmd run pack:dry
+git diff --check
+node .\dist\cli.js doctor
+node .\dist\cli.js summary --kind command "git reset --hard"
+git diff | node .\dist\cli.js diff --fail-on block --subject "v0.1.91 checked maintainer response snippets"
+```
+
+Expected:
+
+- `support:check` verifies issue templates, feedback templates, the maintainer triage playbook, and response snippets.
+- `reports:check` still verifies the installed-package report gallery.
+- fixture report still shows `Fixtures: 222`.
+- GitHub Release and npm Publish complete from the `v0.1.91` tag.
+
+After publish:
+
+```powershell
+npm.cmd view memento-mori-jester version --silent
+npx.cmd -y memento-mori-jester@latest doctor
+npx.cmd -y memento-mori-jester@latest summary --kind command "git reset --hard"
+npm.cmd run support:check
+npm.cmd run reports:check -- --package memento-mori-jester@latest
+```

package/examples/reports/README.md

@@ -30,6 +30,8 @@ If a report-gallery example is confusing, stale, or does not match what you see
 
 The useful public details are the package version, nearest gallery example, a sanitized command summary, a few relevant output lines, and redacted `doctor --json` output. Do not paste secrets, private repository code, customer data, full CI logs, unredacted SARIF, or private paths.
 
+Maintainers should handle those reports with the checked [Maintainer Triage Playbook](../support), which shows first responses, classifications, and follow-up outcomes for docs examples, fixture backlog items, and rule-review candidates.
+
 Maintainers can keep this support path aligned with:
 
 ```powershell

package/examples/support/README.md

@@ -0,0 +1,42 @@
+# Maintainer Triage Playbook
+
+This playbook shows how to handle sanitized adopter reports without turning every surprise into an immediate rule change. It pairs with [docs/MAINTAINER_TRIAGE.md](../../docs/MAINTAINER_TRIAGE.md), the [report gallery feedback template](../reports/feedback-template.md), and the GitHub issue templates.
+
+The checked source is [triage-playbook.json](triage-playbook.json). Use [response-snippets.md](response-snippets.md) for copy-paste replies after a report is classified. The snippet source is [response-snippets.json](response-snippets.json).
+
+| ID | Source | Classification | Follow-up |
+| --- | --- | --- | --- |
+| `gallery-expected-block-docs` | report-gallery feedback | expected docs clarification | docs example |
+| `false-positive-fixture-backlog` | false-positive report | plausible safe boundary | fixture backlog |
+| `repeated-risky-domain-rule-review` | false-positive report | repeated surprise pattern | rule-review candidate |
+
+## Maintainer Flow
+
+1. Confirm the report is public-safe. If it includes secrets, private code, full CI logs, exploitable details, package publishing concerns, MCP data exposure, or credential handling, route it through [SECURITY.md](../../SECURITY.md).
+2. Ask for the smallest redacted reproduction plus `jester doctor --json`.
+3. For noisy rules, ask for `jester tune <rule-id> --json`.
+4. Classify the report as `docs`, `false-positive`, `rules`, `bug`, or `security`.
+5. Choose one follow-up outcome:
+   - `docs-example`: improve wording or a checked report example.
+   - `fixture-backlog`: add a pass or quiet-pass fixture before changing behavior.
+   - `rule-review-candidate`: collect repeated sanitized reports before changing guidance or matching.
+6. Close with the next command the user can run.
+7. Use the matching response snippet so replies stay public-safe and consistent.
+
+## Checks
+
+Run this after editing support docs, issue templates, the playbook, or response snippets:
+
+```powershell
+npm run support:check
+```
+
+Run these when a report becomes fixture work:
+
+```powershell
+npm run fixtures:check
+npm run fixtures:report
+npm run fixtures:report -- --markdown
+```
+
+The playbook is intentionally synthetic and public. Do not add private repository names, private paths, tokens, customer data, or full logs.

package/examples/support/response-snippets.json

@@ -0,0 +1,41 @@
+[
+  {
+    "id": "docs-example-response",
+    "outcome": "docs-example",
+    "title": "Expected behavior, docs clarification",
+    "useWhen": "A sanitized report matches checked behavior, but the user expected different wording or severity.",
+    "labels": ["docs"],
+    "body": [
+      "Thanks for the report. This looks like expected behavior for the checked example, but the wording can be clearer.",
+      "Please do not paste private repo code, full logs, secrets, or private paths. If your local output differs from the checked example, share redacted `jester doctor --json` output and the smallest sanitized command summary.",
+      "Maintainer next step: update the report gallery wording or docs example, then run `npm run reports:check` and `npm run support:check`."
+    ],
+    "requiredChecks": ["npm run reports:check", "npm run support:check"]
+  },
+  {
+    "id": "fixture-backlog-response",
+    "outcome": "fixture-backlog",
+    "title": "Plausible false positive, fixture backlog",
+    "useWhen": "A sanitized false-positive report describes a safe boundary that should be protected before changing rule behavior.",
+    "labels": ["false-positive", "rules"],
+    "body": [
+      "Thanks, this looks like a plausible safe boundary. Please keep the reproduction minimal and redacted, then share `jester tune <rule-id> --json`, redacted `jester doctor --json`, and the smallest command, plan, diff, or final-answer text that reproduces the result.",
+      "We will not loosen the rule from one report. If the reduced example is valid, the next step is a pass or quiet-pass fixture with `expectedRuleIds` or `absentRuleIds`.",
+      "Maintainer next step: add the fixture backlog item, then run `npm run fixtures:check`, `npm run fixtures:report`, and `npm run support:check`."
+    ],
+    "requiredChecks": ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"]
+  },
+  {
+    "id": "rule-review-candidate-response",
+    "outcome": "rule-review-candidate",
+    "title": "Repeated surprise, rule review candidate",
+    "useWhen": "A report may be expected on its own, but repeated sanitized reports suggest the rule guidance or matching boundary may need review.",
+    "labels": ["false-positive", "rules"],
+    "body": [
+      "Thanks. This may be expected caution for now, but repeated sanitized reports can become a rule-review candidate.",
+      "Please share redacted `jester doctor --json`, redacted `jester tune <rule-id> --json`, and the smallest public-safe input that reproduces the surprise. Do not paste secrets, private project details, full logs, or private paths.",
+      "Maintainer next step: collect at least two sanitized examples, compare `fixtureEvidence`, and only then decide whether this is docs, fixture backlog, guidance, or rule-matching work."
+    ],
+    "requiredChecks": ["npm run fixtures:report -- --markdown", "npm run support:check"]
+  }
+]

package/examples/support/response-snippets.md

@@ -0,0 +1,51 @@
+# Maintainer Response Snippets
+
+These public-safe snippets reduce maintainer response friction after a report has been classified with the [triage playbook](triage-playbook.json). They are intentionally generic: no private repository names, no customer data, no full logs, and no real credentials.
+
+The checked source is [response-snippets.json](response-snippets.json). Keep the outcome IDs aligned with the playbook:
+
+- `docs-example`
+- `fixture-backlog`
+- `rule-review-candidate`
+
+## Docs Example Response
+
+Use for `docs-example` outcomes when behavior is expected but wording or examples could be clearer.
+
+```markdown
+Thanks for the report. This looks like expected behavior for the checked example, but the wording can be clearer.
+
+Please do not paste private repo code, full logs, secrets, or private paths. If your local output differs from the checked example, share redacted `jester doctor --json` output and the smallest sanitized command summary.
+
+Maintainer next step: update the report gallery wording or docs example, then run `npm run reports:check` and `npm run support:check`.
+```
+
+## Fixture Backlog Response
+
+Use for `fixture-backlog` outcomes when a minimized false-positive report looks like a safe boundary worth preserving.
+
+```markdown
+Thanks, this looks like a plausible safe boundary. Please keep the reproduction minimal and redacted, then share `jester tune <rule-id> --json`, redacted `jester doctor --json`, and the smallest command, plan, diff, or final-answer text that reproduces the result.
+
+We will not loosen the rule from one report. If the reduced example is valid, the next step is a pass or quiet-pass fixture with `expectedRuleIds` or `absentRuleIds`.
+
+Maintainer next step: add the fixture backlog item, then run `npm run fixtures:check`, `npm run fixtures:report`, and `npm run support:check`.
+```
+
+## Rule Review Candidate Response
+
+Use for `rule-review-candidate` outcomes when repeated sanitized reports suggest a rule boundary or guidance may need review.
+
+```markdown
+Thanks. This may be expected caution for now, but repeated sanitized reports can become a rule-review candidate.
+
+Please share redacted `jester doctor --json`, redacted `jester tune <rule-id> --json`, and the smallest public-safe input that reproduces the surprise. Do not paste secrets, private project details, full logs, or private paths.
+
+Maintainer next step: collect at least two sanitized examples, compare `fixtureEvidence`, and only then decide whether this is docs, fixture backlog, guidance, or rule-matching work.
+```
+
+Run the guard after editing snippets:
+
+```powershell
+npm run support:check
+```

package/examples/support/triage-playbook.json

@@ -0,0 +1,96 @@
+[
+  {
+    "id": "gallery-expected-block-docs",
+    "source": "report-gallery-feedback",
+    "nearestReportExample": "destructive-command-summary",
+    "sanitizedReport": {
+      "version": "latest",
+      "kind": "command",
+      "command": "jester summary --kind command \"git reset --hard\"",
+      "observed": [
+        "Verdict: BLOCK",
+        "destructive-git-history",
+        "Suggested next: jester tune destructive-git-history"
+      ],
+      "question": "I expected this to warn, not block, because I only wanted to see the summary output."
+    },
+    "firstResponse": "Thanks. This looks like expected behavior for the destructive-command summary example: the command is intentionally blocked so the gallery can show a high-signal report. Please share redacted `jester doctor --json` output only if your local output differs from the checked example.",
+    "classification": {
+      "labels": ["docs"],
+      "decision": "expected-behavior-docs-example",
+      "rationale": "The reported command matches a checked gallery example and does not indicate a rule bug."
+    },
+    "maintainerChecks": [
+      "npm run reports:check",
+      "npm run support:check"
+    ],
+    "followUpOutcome": {
+      "type": "docs-example",
+      "action": "Clarify the report gallery row or README wording if multiple adopters expect a non-blocking example."
+    }
+  },
+  {
+    "id": "false-positive-fixture-backlog",
+    "source": "false-positive",
+    "nearestReportExample": "none",
+    "sanitizedReport": {
+      "version": "latest",
+      "kind": "diff",
+      "ruleId": "custom-web-storage-sensitive-value",
+      "command": "jester summary --kind diff <redacted-diff>",
+      "observed": [
+        "Verdict: BLOCK",
+        "custom-web-storage-sensitive-value",
+        "localStorage theme preference"
+      ],
+      "question": "This looks like a theme preference, not a token or password."
+    },
+    "firstResponse": "Thanks. Please keep the diff minimal and redacted, then include `jester tune custom-web-storage-sensitive-value --json` and redacted `jester doctor --json` output. If the reduced example only stores a non-sensitive preference, this should become a quiet-pass fixture candidate before any rule change.",
+    "classification": {
+      "labels": ["false-positive", "rules"],
+      "decision": "fixture-backlog",
+      "rationale": "The report describes a plausible safe boundary, but maintainers need a minimized redacted reproduction before changing matching behavior."
+    },
+    "maintainerChecks": [
+      "npm run fixtures:check",
+      "npm run fixtures:report",
+      "npm run support:check"
+    ],
+    "followUpOutcome": {
+      "type": "fixture-backlog",
+      "action": "Add a quiet-pass fixture with `absentRuleIds` for the noisy rule if the sanitized reproduction is valid and not already covered."
+    }
+  },
+  {
+    "id": "repeated-risky-domain-rule-review",
+    "source": "false-positive",
+    "nearestReportExample": "none",
+    "sanitizedReport": {
+      "version": "latest",
+      "kind": "plan",
+      "ruleId": "risky-domain",
+      "command": "jester summary --kind plan \"Update auth docs and verify links\"",
+      "observed": [
+        "Verdict: CAUTION",
+        "risky-domain",
+        "High-risk domain touched"
+      ],
+      "question": "The plan is documentation-only, but the rule still cautions because it mentions auth."
+    },
+    "firstResponse": "Thanks. This may be expected caution for plan text, but repeated reports can justify a rule-review candidate. Please share redacted `jester doctor --json` output, redacted `jester tune risky-domain --json` output, and the smallest plan text that reproduces the surprise. Do not paste private project details.",
+    "classification": {
+      "labels": ["false-positive", "rules"],
+      "decision": "rule-review-candidate",
+      "rationale": "One report is not enough to loosen a broad domain rule, but repeated sanitized reports may show the guidance or matching boundary needs review."
+    },
+    "maintainerChecks": [
+      "npm run fixtures:report -- --markdown",
+      "node .\\dist\\cli.js tune risky-domain --json",
+      "npm run support:check"
+    ],
+    "followUpOutcome": {
+      "type": "rule-review-candidate",
+      "action": "Collect at least two sanitized examples and compare fixture evidence before changing rule guidance or matching."
+    }
+  }
+]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memento-mori-jester",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "description": "A local court-jester sidecar for AI coding agents: review plans, commands, diffs, and final claims before they get too pleased with themselves.",
   "type": "module",
   "repository": {

package/scripts/check-production-readiness.mjs

@@ -93,6 +93,10 @@ for (const path of [
   "examples/reports/README.md",
   "examples/reports/feedback-template.md",
   "examples/reports/report-gallery.json",
+  "examples/support/README.md",
+  "examples/support/response-snippets.md",
+  "examples/support/response-snippets.json",
+  "examples/support/triage-playbook.json",
   "examples/presets/README.md",
   "examples/tuning/README.md",
   "examples/tuning/framework-tuning-cookbook.json",
@@ -121,6 +125,8 @@ requireText("README.md", /adoption-smoke\.yml/, "adoption smoke CI link");
 requireText("README.md", /consumer-quickstart/, "consumer quickstart smoke link");
 requireText("README.md", /examples\/reports/, "report gallery link");
 requireText("README.md", /feedback-template\.md/, "report gallery feedback template link");
+requireText("README.md", /examples\/support/, "support triage playbook link");
+requireText("README.md", /response-snippets\.md/, "support response snippets link");
 requireText("README.md", /report gallery feedback/i, "report gallery feedback guidance");
 requireText("README.md", /License: PolyForm Noncommercial/, "the noncommercial license badge");
 requireText("docs/PRODUCTION_READINESS.md", /npm package/i, "npm package readiness");
@@ -141,6 +147,8 @@ requireText("docs/PRODUCTION_READINESS.md", /adoption-smoke\.yml/, "adoption smo
 requireText("docs/PRODUCTION_READINESS.md", /consumer:quickstart:check/, "consumer quickstart smoke readiness");
 requireText("docs/PRODUCTION_READINESS.md", /reports:check/, "report gallery readiness");
 requireText("docs/PRODUCTION_READINESS.md", /support:check/, "support triage readiness");
+requireText("docs/PRODUCTION_READINESS.md", /examples\/support/, "support triage playbook readiness");
+requireText("docs/PRODUCTION_READINESS.md", /response snippets/i, "support response snippets readiness");
 requireText("docs/PRODUCTION_READINESS.md", /quiet-pass/, "quiet-pass fixture readiness");
 requireText("docs/CLI.md", /jester doctor --json/, "doctor JSON CLI docs");
 requireText("docs/CLI.md", /quiet-pass fixture/, "quiet-pass fixture CLI docs");
@@ -164,6 +172,11 @@ requireText("docs/MAINTAINER_TRIAGE.md", /expectedRuleIds/, "fixture expected ru
 requireText("docs/MAINTAINER_TRIAGE.md", /absentRuleIds/, "fixture absent rule guidance");
 requireText("docs/MAINTAINER_TRIAGE.md", /feedback-template\.md/, "report gallery feedback template link");
 requireText("docs/MAINTAINER_TRIAGE.md", /report_gallery_feedback\.yml/, "report gallery issue template link");
+requireText("docs/MAINTAINER_TRIAGE.md", /examples\/support/, "support triage playbook link");
+requireText("docs/MAINTAINER_TRIAGE.md", /response-snippets\.md/, "support response snippets link");
+requireText("docs/MAINTAINER_TRIAGE.md", /docs-example/, "docs example triage outcome");
+requireText("docs/MAINTAINER_TRIAGE.md", /fixture-backlog/, "fixture backlog triage outcome");
+requireText("docs/MAINTAINER_TRIAGE.md", /rule-review-candidate/, "rule review triage outcome");
 requireText("docs/MAINTAINER_TRIAGE.md", /support:check/, "support triage check guidance");
 requireText("examples/fixtures/README.md", /MAINTAINER_TRIAGE\.md/, "maintainer triage link");
 requireText("examples/fixtures/README.md", /Adding A Fixture From A Report/, "fixture report conversion guidance");
@@ -181,6 +194,7 @@ requireText("examples/consumer-quickstart/package.json", /framework:tuning:docto
 requireText("examples/reports/README.md", /report-gallery\.json/, "report gallery JSON link");
 requireText("examples/reports/README.md", /feedback-template\.md/, "report gallery feedback template link");
 requireText("examples/reports/README.md", /report_gallery_feedback\.yml/, "report gallery issue template link");
+requireText("examples/reports/README.md", /examples\/support|Maintainer Triage Playbook/i, "support triage playbook link");
 requireText("examples/reports/README.md", /npm run reports:check/, "report gallery check command");
 requireText("examples/reports/README.md", /npm run support:check/, "support triage check command");
 requireText("examples/reports/report-gallery.json", /fresh-install-doctor/, "fresh install doctor report");
@@ -191,6 +205,19 @@ requireText("examples/reports/feedback-template.md", /summary --kind command "gi
 requireText("examples/reports/feedback-template.md", /tune <rule-id> --json/, "feedback template tune diagnostics");
 requireText("examples/reports/feedback-template.md", /Privacy Checklist/, "feedback template privacy checklist");
 requireText("examples/reports/feedback-template.md", /SECURITY\.md/, "feedback template security redirect");
+requireText("examples/support/README.md", /triage-playbook\.json/, "support triage playbook JSON link");
+requireText("examples/support/README.md", /response-snippets\.md/, "support response snippets link");
+requireText("examples/support/README.md", /docs-example/, "support triage docs outcome");
+requireText("examples/support/README.md", /fixture-backlog/, "support triage fixture outcome");
+requireText("examples/support/README.md", /rule-review-candidate/, "support triage rule-review outcome");
+requireText("examples/support/triage-playbook.json", /gallery-expected-block-docs/, "support triage docs example");
+requireText("examples/support/triage-playbook.json", /false-positive-fixture-backlog/, "support triage fixture example");
+requireText("examples/support/triage-playbook.json", /repeated-risky-domain-rule-review/, "support triage rule-review example");
+requireText("examples/support/response-snippets.md", /Maintainer Response Snippets/, "support response snippets heading");
+requireText("examples/support/response-snippets.md", /response-snippets\.json/, "support response snippets JSON link");
+requireText("examples/support/response-snippets.json", /docs-example-response/, "support docs response snippet");
+requireText("examples/support/response-snippets.json", /fixture-backlog-response/, "support fixture response snippet");
+requireText("examples/support/response-snippets.json", /rule-review-candidate-response/, "support rule-review response snippet");
 requireText("examples/tuning/README.md", /framework-tuning-cookbook\.json/, "framework tuning cookbook JSON link");
 requireText("examples/tuning/README.md", /framework:tuning:doctor/, "framework tuning doctor guidance");
 requireText("examples/tuning/README.md", /jester tune <rule-id> --json|jester tune [a-z0-9-]+ --json/, "framework tuning command guidance");
@@ -223,6 +250,8 @@ requireText("scripts/check-report-gallery.mjs", /memento-mori-jester@latest/, "r
 requireText("scripts/check-report-gallery.mjs", /destructive-command-summary/, "report gallery summary guard");
 requireText("scripts/check-support-triage.mjs", /report_gallery_feedback\.yml/, "support triage issue template guard");
 requireText("scripts/check-support-triage.mjs", /feedback-template\.md/, "support triage feedback template guard");
+requireText("scripts/check-support-triage.mjs", /triage-playbook\.json/, "support triage playbook guard");
+requireText("scripts/check-support-triage.mjs", /response-snippets\.json/, "support response snippets guard");
 requireText("scripts/check-support-triage.mjs", /unsafeContentPatterns/, "support triage unsafe content checks");
 requireText("package.json", /"fixtures:check": "node scripts\/check-fixtures\.mjs"/, "fixture authoring check script");
 requireText("package.json", /"fixtures:report": "node scripts\/report-fixtures\.mjs"/, "fixture coverage report script");

package/scripts/check-support-triage.mjs

@@ -25,6 +25,10 @@ const supportFiles = [
   ".github/ISSUE_TEMPLATE/config.yml",
   "examples/reports/feedback-template.md",
   "examples/reports/README.md",
+  "examples/support/README.md",
+  "examples/support/response-snippets.md",
+  "examples/support/response-snippets.json",
+  "examples/support/triage-playbook.json",
   "docs/MAINTAINER_TRIAGE.md",
   "docs/PRODUCTION_READINESS.md",
   "README.md",
@@ -71,16 +75,53 @@ requireText("examples/reports/feedback-template.md", /npm run support:check/, "s
 requireText("examples/reports/README.md", /feedback-template\.md/, "feedback template link");
 requireText("examples/reports/README.md", /report_gallery_feedback\.yml/, "GitHub issue template link");
 requireText("examples/reports/README.md", /npm run support:check/, "support checker command");
+requireText("examples/reports/README.md", /examples\/support|Maintainer Triage Playbook/i, "maintainer triage playbook link");
+
+requireText("examples/support/README.md", /Maintainer Triage Playbook/, "maintainer playbook heading");
+requireText("examples/support/README.md", /triage-playbook\.json/, "maintainer playbook JSON link");
+requireText("examples/support/README.md", /response-snippets\.md/, "maintainer response snippets link");
+requireText("examples/support/README.md", /gallery-expected-block-docs/, "docs example playbook case");
+requireText("examples/support/README.md", /false-positive-fixture-backlog/, "fixture backlog playbook case");
+requireText("examples/support/README.md", /repeated-risky-domain-rule-review/, "rule review playbook case");
+requireText("examples/support/README.md", /doctor --json/, "doctor JSON playbook prompt");
+requireText("examples/support/README.md", /tune <rule-id> --json/, "tune JSON playbook prompt");
+requireText("examples/support/README.md", /docs-example/, "docs outcome");
+requireText("examples/support/README.md", /fixture-backlog/, "fixture backlog outcome");
+requireText("examples/support/README.md", /rule-review-candidate/, "rule review outcome");
+requireText("examples/support/README.md", /SECURITY\.md/, "security redirect");
+requireText("examples/support/README.md", /npm run support:check/, "support checker command");
+requireText("examples/support/response-snippets.md", /Maintainer Response Snippets/, "response snippets heading");
+requireText("examples/support/response-snippets.md", /response-snippets\.json/, "response snippets JSON link");
+requireText("examples/support/response-snippets.md", /docs-example/, "docs response outcome");
+requireText("examples/support/response-snippets.md", /fixture-backlog/, "fixture backlog response outcome");
+requireText("examples/support/response-snippets.md", /rule-review-candidate/, "rule review response outcome");
+requireText("examples/support/response-snippets.md", /jester doctor --json/, "doctor JSON response prompt");
+requireText("examples/support/response-snippets.md", /jester tune <rule-id> --json/, "tune JSON response prompt");
+requireText("examples/support/response-snippets.md", /npm run support:check/, "support checker response command");
+requireText("examples/support/response-snippets.json", /docs-example-response/, "docs response snippet");
+requireText("examples/support/response-snippets.json", /fixture-backlog-response/, "fixture response snippet");
+requireText("examples/support/response-snippets.json", /rule-review-candidate-response/, "rule review response snippet");
+
 requireText("docs/MAINTAINER_TRIAGE.md", /feedback-template\.md/, "feedback template triage link");
 requireText("docs/MAINTAINER_TRIAGE.md", /report_gallery_feedback\.yml/, "report gallery issue template triage link");
+requireText("docs/MAINTAINER_TRIAGE.md", /examples\/support/, "maintainer playbook triage link");
+requireText("docs/MAINTAINER_TRIAGE.md", /response-snippets\.md/, "maintainer response snippets triage link");
+requireText("docs/MAINTAINER_TRIAGE.md", /docs-example/, "docs example triage outcome");
+requireText("docs/MAINTAINER_TRIAGE.md", /fixture-backlog/, "fixture backlog triage outcome");
+requireText("docs/MAINTAINER_TRIAGE.md", /rule-review-candidate/, "rule review triage outcome");
 requireText("docs/MAINTAINER_TRIAGE.md", /npm(?:\.cmd)? run support:check/, "support checker triage command");
 requireText("docs/PRODUCTION_READINESS.md", /support:check/, "support checker readiness");
 requireText("README.md", /feedback-template\.md/, "feedback template README link");
+requireText("README.md", /examples\/support/, "maintainer triage playbook README link");
+requireText("README.md", /response-snippets\.md/, "maintainer response snippets README link");
 requireText("README.md", /report gallery feedback/i, "report gallery feedback guidance");
 
 requireText("package.json", /"support:check": "node scripts\/check-support-triage\.mjs"/, "support checker script");
 requireText("package.json", /npm run support:check/, "support checker in npm test");
 
+checkTriagePlaybook();
+checkResponseSnippets();
+
 if (failures.length > 0) {
   console.error("Support triage check failed:");
   for (const failure of failures) {
@@ -95,6 +136,15 @@ function read(path) {
   return readFileSync(join(root, path), "utf8");
 }
 
+function readJson(path) {
+  try {
+    return JSON.parse(read(path));
+  } catch (error) {
+    failures.push(`${path} should be valid JSON: ${error instanceof Error ? error.message : String(error)}`);
+    return null;
+  }
+}
+
 function requireFile(path) {
   if (!existsSync(join(root, path))) {
     failures.push(`${path} is missing.`);
@@ -112,3 +162,164 @@ function requireText(path, pattern, description) {
     failures.push(`${path} should include ${description}.`);
   }
 }
+
+function checkTriagePlaybook() {
+  const path = "examples/support/triage-playbook.json";
+  const playbook = readJson(path);
+  if (!playbook) {
+    return;
+  }
+
+  if (!Array.isArray(playbook) || playbook.length !== 3) {
+    failures.push(`${path} should contain exactly three maintainer triage examples.`);
+    return;
+  }
+
+  const expectedIds = [
+    "gallery-expected-block-docs",
+    "false-positive-fixture-backlog",
+    "repeated-risky-domain-rule-review"
+  ];
+  const expectedOutcomes = ["docs-example", "fixture-backlog", "rule-review-candidate"];
+  const expectedSources = ["report-gallery-feedback", "false-positive"];
+  const seenIds = new Set();
+
+  for (const [index, entry] of playbook.entries()) {
+    const expectedId = expectedIds[index];
+    if (entry?.id !== expectedId) {
+      failures.push(`${path} entry ${index + 1} should have id ${expectedId}.`);
+      continue;
+    }
+
+    if (seenIds.has(entry.id)) {
+      failures.push(`${path} has duplicate id ${entry.id}.`);
+    }
+    seenIds.add(entry.id);
+
+    if (!expectedSources.includes(entry.source)) {
+      failures.push(`${entry.id}.source should be one of ${expectedSources.join(", ")}.`);
+    }
+
+    if (typeof entry.nearestReportExample !== "string" || entry.nearestReportExample.length < 4) {
+      failures.push(`${entry.id}.nearestReportExample should be a useful string.`);
+    }
+
+    if (typeof entry.sanitizedReport?.version !== "string") {
+      failures.push(`${entry.id}.sanitizedReport.version should be present.`);
+    }
+
+    if (!["command", "plan", "diff", "final"].includes(entry.sanitizedReport?.kind)) {
+      failures.push(`${entry.id}.sanitizedReport.kind should be a review kind.`);
+    }
+
+    if (typeof entry.sanitizedReport?.command !== "string" || !entry.sanitizedReport.command.includes("jester")) {
+      failures.push(`${entry.id}.sanitizedReport.command should include a jester command.`);
+    }
+
+    if (!Array.isArray(entry.sanitizedReport?.observed) || entry.sanitizedReport.observed.length < 2) {
+      failures.push(`${entry.id}.sanitizedReport.observed should include stable output fragments.`);
+    }
+
+    if (typeof entry.sanitizedReport?.question !== "string" || entry.sanitizedReport.question.length < 20) {
+      failures.push(`${entry.id}.sanitizedReport.question should explain the adopter surprise.`);
+    }
+
+    if (typeof entry.firstResponse !== "string" || !entry.firstResponse.includes("doctor --json")) {
+      failures.push(`${entry.id}.firstResponse should ask for or mention redacted doctor --json diagnostics.`);
+    }
+
+    if (!Array.isArray(entry.classification?.labels) || entry.classification.labels.length === 0) {
+      failures.push(`${entry.id}.classification.labels should be a non-empty array.`);
+    }
+
+    if (typeof entry.classification?.decision !== "string" || entry.classification.decision.length < 8) {
+      failures.push(`${entry.id}.classification.decision should be present.`);
+    }
+
+    if (!Array.isArray(entry.maintainerChecks) || !entry.maintainerChecks.includes("npm run support:check")) {
+      failures.push(`${entry.id}.maintainerChecks should include npm run support:check.`);
+    }
+
+    if (entry.followUpOutcome?.type !== expectedOutcomes[index]) {
+      failures.push(`${entry.id}.followUpOutcome.type should be ${expectedOutcomes[index]}.`);
+    }
+
+    if (typeof entry.followUpOutcome?.action !== "string" || entry.followUpOutcome.action.length < 30) {
+      failures.push(`${entry.id}.followUpOutcome.action should describe the maintainer action.`);
+    }
+  }
+}
+
+function checkResponseSnippets() {
+  const path = "examples/support/response-snippets.json";
+  const snippets = readJson(path);
+  if (!snippets) {
+    return;
+  }
+
+  if (!Array.isArray(snippets) || snippets.length !== 3) {
+    failures.push(`${path} should contain exactly three maintainer response snippets.`);
+    return;
+  }
+
+  const expected = [
+    { id: "docs-example-response", outcome: "docs-example", checks: ["npm run reports:check", "npm run support:check"] },
+    { id: "fixture-backlog-response", outcome: "fixture-backlog", checks: ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"] },
+    { id: "rule-review-candidate-response", outcome: "rule-review-candidate", checks: ["npm run fixtures:report -- --markdown", "npm run support:check"] }
+  ];
+  const seenIds = new Set();
+
+  for (const [index, snippet] of snippets.entries()) {
+    const expectedSnippet = expected[index];
+    if (snippet?.id !== expectedSnippet.id) {
+      failures.push(`${path} entry ${index + 1} should have id ${expectedSnippet.id}.`);
+      continue;
+    }
+
+    if (seenIds.has(snippet.id)) {
+      failures.push(`${path} has duplicate id ${snippet.id}.`);
+    }
+    seenIds.add(snippet.id);
+
+    if (snippet.outcome !== expectedSnippet.outcome) {
+      failures.push(`${snippet.id}.outcome should be ${expectedSnippet.outcome}.`);
+    }
+
+    if (typeof snippet.title !== "string" || snippet.title.length < 10) {
+      failures.push(`${snippet.id}.title should be a useful string.`);
+    }
+
+    if (typeof snippet.useWhen !== "string" || snippet.useWhen.length < 30) {
+      failures.push(`${snippet.id}.useWhen should explain when to use the response.`);
+    }
+
+    if (!Array.isArray(snippet.labels) || snippet.labels.length === 0) {
+      failures.push(`${snippet.id}.labels should be a non-empty array.`);
+    }
+
+    if (!Array.isArray(snippet.body) || snippet.body.length !== 3) {
+      failures.push(`${snippet.id}.body should contain exactly three response paragraphs.`);
+      continue;
+    }
+
+    const bodyText = snippet.body.join("\n");
+    if (!bodyText.includes("doctor --json")) {
+      failures.push(`${snippet.id}.body should ask for or mention redacted doctor --json diagnostics.`);
+    }
+
+    if (!/secret|private|redacted/i.test(bodyText)) {
+      failures.push(`${snippet.id}.body should include privacy or redaction guidance.`);
+    }
+
+    if (!Array.isArray(snippet.requiredChecks)) {
+      failures.push(`${snippet.id}.requiredChecks should be an array.`);
+      continue;
+    }
+
+    for (const check of expectedSnippet.checks) {
+      if (!snippet.requiredChecks.includes(check)) {
+        failures.push(`${snippet.id}.requiredChecks should include ${check}.`);
+      }
+    }
+  }
+}