memento-mori-jester 0.1.90 → 0.1.92

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to Memento Mori Jester are tracked here.
 
 ## Unreleased
 
+## 0.1.92
+
+- Added a checked public-safe support closeout checklist for docs clarification, fixture backlog, and rule-review candidate outcomes.
+- Extended `npm run support:check` and production-readiness checks so closeout records stay aligned with the maintainer triage playbook and response snippets.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and release notes for deterministic support decision recording.
+
+## 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.

package/README.md

@@ -76,7 +76,7 @@ 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) to turn sanitized reports into a docs example, fixture backlog item, or rule-review candidate without changing behavior first.
+Maintainers can use the checked [support triage playbook](examples/support), [response snippets](examples/support/response-snippets.md), and [support closeout checklist](examples/support/closeout-checklist.md) to turn sanitized reports into a docs example, fixture backlog item, or rule-review candidate without changing behavior first.
 
 Expected vibe:
 
@@ -451,6 +451,8 @@ More setup examples:
 - [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)
+- [Support Closeout Checklist](examples/support/closeout-checklist.md)
 - [Security Policy](SECURITY.md)
 - [Maintainer Triage](docs/MAINTAINER_TRIAGE.md)
 - [Changelog](CHANGELOG.md)
@@ -473,6 +475,8 @@ Framework CI examples:
 - [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)
+- [Support Closeout Checklist](examples/support/closeout-checklist.md)
 - [Next.js CI](examples/ci/nextjs.yml)
 - [Vite React CI](examples/ci/vite-react.yml)
 - [Express API CI](examples/ci/express-api.yml)
@@ -529,7 +533,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, the report gallery feedback path, or the [support triage playbook](examples/support); it verifies the public templates ask 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), [response snippets](examples/support/response-snippets.md), or [support closeout checklist](examples/support/closeout-checklist.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 support closeout checklist in v0.1.92, recording whether docs clarifications shipped or queued, fixture backlogs were created, or rule-review candidates were opened.
+- 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.
@@ -80,7 +82,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.
-- Use repeated playbook outcomes to prioritize the next redacted fixture or report-gallery update.
+- Use repeated playbook outcomes, response snippets, and closeout records 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,7 +21,7 @@ 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.
+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, then use [closeout-checklist.md](../examples/support/closeout-checklist.md) to record whether the docs clarification shipped or queued, fixture backlog was created, or rule-review candidate was opened.
 
 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).
 
@@ -65,6 +65,8 @@ Use the playbook outcomes consistently:
 - `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. After the reply, record the closeout with the matching checklist entry so the issue has a public-safe decision record. Do not add private code, private paths, tokens, full logs, or exploitable details to the response or closeout.
+
 After editing report support docs or issue templates, run:
 
 ```powershell

package/docs/PRODUCTION_READINESS.md

@@ -47,7 +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 for first response, classification, and follow-up outcomes from sanitized support reports.
+- `examples/support` provides a checked maintainer triage playbook, response snippets, and closeout checklist for first response, classification, follow-up outcomes, and public-safe decision records 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`.
 
@@ -60,14 +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.
+- `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 and record the closeout.
 - `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, the report gallery feedback template, and the maintainer triage playbook 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, response snippets, and closeout checklist 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.

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/docs/RELEASE_NOTES_v0.1.92.md

@@ -0,0 +1,58 @@
+# Memento Mori Jester v0.1.92
+
+## Summary
+
+This release adds a checked support closeout checklist for the three maintainer support outcomes: docs clarification, fixture backlog, and rule-review candidate. The goal is to make the final decision record as deterministic and public-safe as the first response.
+
+## What Changed
+
+- Added `examples/support/closeout-checklist.md`.
+- Added `examples/support/closeout-checklist.json`.
+- Extended `scripts/check-support-triage.mjs` to validate closeout records.
+- Extended production-readiness checks for the closeout checklist.
+- 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 support closeout records.
+
+## 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.92 checked support closeout checklist"
+```
+
+Expected:
+
+- `support:check` verifies issue templates, feedback templates, the maintainer triage playbook, response snippets, and closeout checklist.
+- `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.92` 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/support/README.md

@@ -2,7 +2,7 @@
 
 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). It covers three common support outcomes:
+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). Use [closeout-checklist.md](closeout-checklist.md) to record what happened after the response. The closeout source is [closeout-checklist.json](closeout-checklist.json).
 
 | ID | Source | Classification | Follow-up |
 | --- | --- | --- | --- |
@@ -21,10 +21,12 @@ The checked source is [triage-playbook.json](triage-playbook.json). It covers th
    - `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.
+8. Record the closeout with the matching checklist entry: docs clarification shipped or queued, fixture backlog created, or rule-review candidate opened.
 
 ## Checks
 
-Run this after editing support docs, issue templates, or the playbook:
+Run this after editing support docs, issue templates, the playbook, response snippets, or closeout checklist:
 
 ```powershell
 npm run support:check

package/examples/support/closeout-checklist.json

@@ -0,0 +1,53 @@
+[
+  {
+    "id": "docs-clarification-closeout",
+    "outcome": "docs-example",
+    "decisionRecord": {
+      "status": "shipped-or-queued",
+      "publicSummary": "Clarified the checked report-gallery wording so the expected block verdict is easier to understand.",
+      "userReply": "Thanks again. I have linked the docs clarification, and the checked gallery still passes.",
+      "followUpLinkPlaceholder": "<docs-pr-or-commit>",
+      "nextCommand": "npm run reports:check"
+    },
+    "requiredEvidence": [
+      "No private code, paths, tokens, full logs, or customer data are included.",
+      "The related report-gallery example still passes.",
+      "The issue links to the docs change or backlog item."
+    ],
+    "requiredChecks": ["npm run reports:check", "npm run support:check"]
+  },
+  {
+    "id": "fixture-backlog-closeout",
+    "outcome": "fixture-backlog",
+    "decisionRecord": {
+      "status": "backlog-created",
+      "publicSummary": "Created a redacted fixture backlog item for a plausible quiet-pass boundary.",
+      "userReply": "Thanks. This is now tracked as a fixture backlog item; behavior stays unchanged until a checked fixture proves the boundary.",
+      "followUpLinkPlaceholder": "<fixture-backlog-issue>",
+      "nextCommand": "npm run fixtures:report"
+    },
+    "requiredEvidence": [
+      "The reduced example is public-safe and minimal.",
+      "The backlog item names the candidate rule id and expected quiet-pass or pass boundary.",
+      "The report does not request a rule change before fixture coverage exists."
+    ],
+    "requiredChecks": ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"]
+  },
+  {
+    "id": "rule-review-closeout",
+    "outcome": "rule-review-candidate",
+    "decisionRecord": {
+      "status": "candidate-opened",
+      "publicSummary": "Opened a rule-review candidate after repeated sanitized reports suggested a possible guidance or matching boundary.",
+      "userReply": "Thanks. I have linked this to a rule-review candidate. The rule remains unchanged while maintainers compare fixture evidence.",
+      "followUpLinkPlaceholder": "<rule-review-issue>",
+      "nextCommand": "node .\\dist\\cli.js tune <rule-id> --json"
+    },
+    "requiredEvidence": [
+      "At least two sanitized reports are linked or summarized.",
+      "Fixture evidence or `jester tune <rule-id> --json` output is referenced.",
+      "The public record avoids secrets, private project details, full logs, and exploitable security details."
+    ],
+    "requiredChecks": ["npm run fixtures:report -- --markdown", "npm run support:check"]
+  }
+]

package/examples/support/closeout-checklist.md

@@ -0,0 +1,74 @@
+# Support Closeout Checklist
+
+Use this checklist after a maintainer has classified a sanitized support report and sent a response snippet. It records what happened next without changing rule behavior or exposing private project details.
+
+The checked source is [closeout-checklist.json](closeout-checklist.json). Keep closeout outcomes aligned with the [triage playbook](triage-playbook.json) and [response snippets](response-snippets.md):
+
+- `docs-example`
+- `fixture-backlog`
+- `rule-review-candidate`
+
+## Closeout Record
+
+Every public closeout should include:
+
+- outcome,
+- public-safe summary,
+- shipped or queued status,
+- link placeholder for the docs change, fixture backlog item, or rule-review issue,
+- next command for the user or maintainer,
+- evidence that secrets, private code, private paths, customer data, full logs, and exploitable details were not included.
+
+## Docs Clarification
+
+Use when behavior was expected and the right follow-up is clearer wording.
+
+```text
+Outcome: docs-example
+Status: shipped-or-queued
+Public summary: Clarified the checked report-gallery wording so the expected block verdict is easier to understand.
+Follow-up: <docs-pr-or-commit>
+Next command: npm run reports:check
+```
+
+## Fixture Backlog
+
+Use when the report describes a plausible safe boundary but behavior should not change until fixture evidence exists.
+
+```text
+Outcome: fixture-backlog
+Status: backlog-created
+Public summary: Created a redacted fixture backlog item for a plausible quiet-pass boundary.
+Follow-up: <fixture-backlog-issue>
+Next command: npm run fixtures:report
+```
+
+## Rule Review Candidate
+
+Use when repeated sanitized reports suggest guidance or matching may need review.
+
+```text
+Outcome: rule-review-candidate
+Status: candidate-opened
+Public summary: Opened a rule-review candidate after repeated sanitized reports suggested a possible guidance or matching boundary.
+Follow-up: <rule-review-issue>
+Next command: node .\dist\cli.js tune <rule-id> --json
+```
+
+## Checks
+
+Run this after editing closeout records or support docs:
+
+```powershell
+npm run support:check
+```
+
+Run fixture checks before closing a fixture-backed issue:
+
+```powershell
+npm run fixtures:check
+npm run fixtures:report
+npm run fixtures:report -- --markdown
+```
+
+Do not include secrets, tokens, private repository code, private paths, customer data, full CI logs, unredacted SARIF, or exploitable security details in a public closeout. Use [SECURITY.md](../../SECURITY.md) for sensitive reports.

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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memento-mori-jester",
-  "version": "0.1.90",
+  "version": "0.1.92",
   "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

@@ -94,6 +94,10 @@ for (const path of [
   "examples/reports/feedback-template.md",
   "examples/reports/report-gallery.json",
   "examples/support/README.md",
+  "examples/support/closeout-checklist.md",
+  "examples/support/closeout-checklist.json",
+  "examples/support/response-snippets.md",
+  "examples/support/response-snippets.json",
   "examples/support/triage-playbook.json",
   "examples/presets/README.md",
   "examples/tuning/README.md",
@@ -124,6 +128,8 @@ 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", /closeout-checklist\.md/, "support closeout checklist 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");
@@ -145,6 +151,8 @@ requireText("docs/PRODUCTION_READINESS.md", /consumer:quickstart:check/, "consum
 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", /closeout checklist/i, "support closeout checklist 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");
@@ -169,6 +177,8 @@ requireText("docs/MAINTAINER_TRIAGE.md", /absentRuleIds/, "fixture absent rule g
 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", /closeout-checklist\.md/, "support closeout checklist 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");
@@ -201,12 +211,27 @@ requireText("examples/reports/feedback-template.md", /tune <rule-id> --json/, "f
 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", /closeout-checklist\.md/, "support closeout checklist 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/support/closeout-checklist.md", /Support Closeout Checklist/, "support closeout checklist heading");
+requireText("examples/support/closeout-checklist.md", /closeout-checklist\.json/, "support closeout checklist JSON link");
+requireText("examples/support/closeout-checklist.md", /shipped-or-queued/, "support docs closeout status");
+requireText("examples/support/closeout-checklist.md", /backlog-created/, "support fixture closeout status");
+requireText("examples/support/closeout-checklist.md", /candidate-opened/, "support rule-review closeout status");
+requireText("examples/support/closeout-checklist.json", /docs-clarification-closeout/, "support docs closeout record");
+requireText("examples/support/closeout-checklist.json", /fixture-backlog-closeout/, "support fixture closeout record");
+requireText("examples/support/closeout-checklist.json", /rule-review-closeout/, "support rule-review closeout record");
 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");
@@ -240,6 +265,8 @@ requireText("scripts/check-report-gallery.mjs", /destructive-command-summary/, "
 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", /closeout-checklist\.json/, "support closeout checklist 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,7 +25,11 @@ const supportFiles = [
   ".github/ISSUE_TEMPLATE/config.yml",
   "examples/reports/feedback-template.md",
   "examples/reports/README.md",
+  "examples/support/closeout-checklist.md",
+  "examples/support/closeout-checklist.json",
   "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",
@@ -76,7 +80,9 @@ requireText("examples/reports/README.md", /npm run support:check/, "support chec
 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", /closeout-checklist\.md/, "support closeout checklist link");
 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");
@@ -87,23 +93,53 @@ requireText("examples/support/README.md", /fixture-backlog/, "fixture backlog ou
 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/closeout-checklist.md", /Support Closeout Checklist/, "closeout checklist heading");
+requireText("examples/support/closeout-checklist.md", /closeout-checklist\.json/, "closeout checklist JSON link");
+requireText("examples/support/closeout-checklist.md", /docs-example/, "docs closeout outcome");
+requireText("examples/support/closeout-checklist.md", /fixture-backlog/, "fixture closeout outcome");
+requireText("examples/support/closeout-checklist.md", /rule-review-candidate/, "rule-review closeout outcome");
+requireText("examples/support/closeout-checklist.md", /shipped-or-queued/, "docs closeout status");
+requireText("examples/support/closeout-checklist.md", /backlog-created/, "fixture closeout status");
+requireText("examples/support/closeout-checklist.md", /candidate-opened/, "rule-review closeout status");
+requireText("examples/support/closeout-checklist.md", /npm run support:check/, "support checker closeout command");
+requireText("examples/support/closeout-checklist.md", /SECURITY\.md/, "closeout security redirect");
+requireText("examples/support/closeout-checklist.json", /docs-clarification-closeout/, "docs closeout record");
+requireText("examples/support/closeout-checklist.json", /fixture-backlog-closeout/, "fixture closeout record");
+requireText("examples/support/closeout-checklist.json", /rule-review-closeout/, "rule-review closeout record");
+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", /closeout-checklist\.md/, "support closeout checklist 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", /closeout-checklist\.md/, "support closeout checklist 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();
+checkCloseoutChecklist();
 
 if (failures.length > 0) {
   console.error("Support triage check failed:");
@@ -232,3 +268,169 @@ function checkTriagePlaybook() {
     }
   }
 }
+
+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}.`);
+      }
+    }
+  }
+}
+
+function checkCloseoutChecklist() {
+  const path = "examples/support/closeout-checklist.json";
+  const closeouts = readJson(path);
+  if (!closeouts) {
+    return;
+  }
+
+  if (!Array.isArray(closeouts) || closeouts.length !== 3) {
+    failures.push(`${path} should contain exactly three support closeout records.`);
+    return;
+  }
+
+  const expected = [
+    {
+      id: "docs-clarification-closeout",
+      outcome: "docs-example",
+      status: "shipped-or-queued",
+      checks: ["npm run reports:check", "npm run support:check"]
+    },
+    {
+      id: "fixture-backlog-closeout",
+      outcome: "fixture-backlog",
+      status: "backlog-created",
+      checks: ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"]
+    },
+    {
+      id: "rule-review-closeout",
+      outcome: "rule-review-candidate",
+      status: "candidate-opened",
+      checks: ["npm run fixtures:report -- --markdown", "npm run support:check"]
+    }
+  ];
+  const seenIds = new Set();
+
+  for (const [index, closeout] of closeouts.entries()) {
+    const expectedCloseout = expected[index];
+    if (closeout?.id !== expectedCloseout.id) {
+      failures.push(`${path} entry ${index + 1} should have id ${expectedCloseout.id}.`);
+      continue;
+    }
+
+    if (seenIds.has(closeout.id)) {
+      failures.push(`${path} has duplicate id ${closeout.id}.`);
+    }
+    seenIds.add(closeout.id);
+
+    if (closeout.outcome !== expectedCloseout.outcome) {
+      failures.push(`${closeout.id}.outcome should be ${expectedCloseout.outcome}.`);
+    }
+
+    if (closeout.decisionRecord?.status !== expectedCloseout.status) {
+      failures.push(`${closeout.id}.decisionRecord.status should be ${expectedCloseout.status}.`);
+    }
+
+    if (typeof closeout.decisionRecord?.publicSummary !== "string" || closeout.decisionRecord.publicSummary.length < 30) {
+      failures.push(`${closeout.id}.decisionRecord.publicSummary should be a useful public summary.`);
+    }
+
+    if (typeof closeout.decisionRecord?.userReply !== "string" || closeout.decisionRecord.userReply.length < 30) {
+      failures.push(`${closeout.id}.decisionRecord.userReply should be a useful closeout reply.`);
+    }
+
+    if (typeof closeout.decisionRecord?.followUpLinkPlaceholder !== "string" || !closeout.decisionRecord.followUpLinkPlaceholder.startsWith("<")) {
+      failures.push(`${closeout.id}.decisionRecord.followUpLinkPlaceholder should be a placeholder.`);
+    }
+
+    if (typeof closeout.decisionRecord?.nextCommand !== "string" || closeout.decisionRecord.nextCommand.length < 8) {
+      failures.push(`${closeout.id}.decisionRecord.nextCommand should include a next command.`);
+    }
+
+    if (!Array.isArray(closeout.requiredEvidence) || closeout.requiredEvidence.length < 3) {
+      failures.push(`${closeout.id}.requiredEvidence should contain at least three evidence checks.`);
+    } else {
+      const evidenceText = closeout.requiredEvidence.join("\n");
+      if (!/secret|private|redacted|public-safe/i.test(evidenceText)) {
+        failures.push(`${closeout.id}.requiredEvidence should include privacy or redaction evidence.`);
+      }
+    }
+
+    if (!Array.isArray(closeout.requiredChecks)) {
+      failures.push(`${closeout.id}.requiredChecks should be an array.`);
+      continue;
+    }
+
+    for (const check of expectedCloseout.checks) {
+      if (!closeout.requiredChecks.includes(check)) {
+        failures.push(`${closeout.id}.requiredChecks should include ${check}.`);
+      }
+    }
+  }
+}