memento-mori-jester 0.1.93 → 0.1.95

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to Memento Mori Jester are tracked here.
 
 ## Unreleased
 
+## 0.1.95
+
+- Added checked public-safe support backlog records for turning closed/prioritized support outcomes into docs clarification, fixture backlog, or rule-review candidate artifacts.
+- Extended `npm run support:check` and production-readiness checks so backlog record IDs, evidence thresholds, required checks, and privacy guidance stay aligned with the support lifecycle.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and release notes for deterministic support backlog recording.
+
+## 0.1.94
+
+- Added a checked public-safe support outcome prioritization guide for deciding whether closed support reports become docs clarifications, fixture backlog items, or rule-review candidates.
+- Extended `npm run support:check` and production-readiness checks so prioritization thresholds, backlog destinations, and required evidence stay aligned with the support lifecycle.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and release notes for evidence-based follow-up prioritization.
+
 ## 0.1.93
 
 - Added a checked support lifecycle overview that ties report-gallery feedback, triage playbook entries, response snippets, and closeout records together by support outcome.

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 lifecycle overview](examples/support/support-lifecycle.md), [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.
+Maintainers can use the checked [support lifecycle overview](examples/support/support-lifecycle.md), [outcome prioritization guide](examples/support/outcome-prioritization.md), [support backlog records](examples/support/backlog-records.md), [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 Lifecycle Overview](examples/support/support-lifecycle.md)
+- [Support Outcome Prioritization](examples/support/outcome-prioritization.md)
+- [Support Backlog Records](examples/support/backlog-records.md)
 - [Support Triage Playbook](examples/support)
 - [Maintainer Response Snippets](examples/support/response-snippets.md)
 - [Support Closeout Checklist](examples/support/closeout-checklist.md)
@@ -476,6 +478,8 @@ Framework CI examples:
 - [Real-World Report Gallery](examples/reports)
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
 - [Support Lifecycle Overview](examples/support/support-lifecycle.md)
+- [Support Outcome Prioritization](examples/support/outcome-prioritization.md)
+- [Support Backlog Records](examples/support/backlog-records.md)
 - [Support Triage Playbook](examples/support)
 - [Maintainer Response Snippets](examples/support/response-snippets.md)
 - [Support Closeout Checklist](examples/support/closeout-checklist.md)
@@ -535,7 +539,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, the [support lifecycle overview](examples/support/support-lifecycle.md), [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 support:check` after editing issue templates, support docs, the report gallery feedback path, the [support lifecycle overview](examples/support/support-lifecycle.md), [outcome prioritization guide](examples/support/outcome-prioritization.md), [support backlog records](examples/support/backlog-records.md), [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 backlog records in v0.1.95, turning closed and prioritized support outcomes into public-safe docs clarification, fixture backlog, or rule-review candidate artifacts.
+- Checked support outcome prioritization in v0.1.94, helping maintainers turn closed support reports into docs, fixture backlog, or rule-review work based on public-safe evidence thresholds.
 - Checked support lifecycle overview in v0.1.93, tying report-gallery feedback, triage playbook entries, response snippets, and closeout records together by outcome.
 - 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.
@@ -83,7 +85,8 @@ 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 lifecycle outcomes, response snippets, and closeout records to prioritize the next redacted fixture or report-gallery update.
+- Use support backlog record counts to choose the next docs, fixture, report-gallery, or rule-guidance batch.
+- Use repeated prioritized support outcomes to choose the next redacted fixture, report-gallery update, or rule-guidance review.
 - 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, start with the checked [support lifecycle overview](../examples/support/support-lifecycle.md) to see the whole path from report to closeout. Then 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.
+When a report has enough public-safe detail to triage, start with the checked [support lifecycle overview](../examples/support/support-lifecycle.md) to see the whole path from report to closeout. Then 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. Use [outcome-prioritization.md](../examples/support/outcome-prioritization.md) after closeout to decide whether the follow-up work is low-priority docs, medium-priority fixture backlog, or high-priority rule review. Use [backlog-records.md](../examples/support/backlog-records.md) when that prioritized follow-up needs a public-safe backlog artifact.
 
 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,7 +65,7 @@ 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 lifecycle row and 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.
+Use the matching lifecycle row and 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. If follow-up work remains, choose its priority from the outcome prioritization guide before opening a docs, fixture, or rule-review backlog item, then record that choice with the matching backlog record. Do not add private code, private paths, tokens, full logs, or exploitable details to the response, closeout, or backlog item.
 
 After editing report support docs or issue templates, run:
 

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 support lifecycle overview, maintainer triage playbook, response snippets, and closeout checklist for first response, classification, follow-up outcomes, and public-safe decision records from sanitized support reports.
+- `examples/support` provides a checked support lifecycle overview, outcome prioritization guide, backlog records, maintainer triage playbook, response snippets, and closeout checklist for first response, classification, follow-up outcomes, public-safe decision records, backlog prioritization, and backlog artifacts 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 audit the support lifecycle, 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.
+- `examples/support` shows maintainers how to audit the support lifecycle, classify sanitized reports as a docs example, fixture backlog item, or rule-review candidate before changing behavior, then reply with public-safe response snippets, record the closeout, prioritize follow-up work, and create a public-safe backlog record.
 - `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, the support lifecycle overview, maintainer triage playbook, response snippets, and closeout checklist stay public-safe and ask for useful redacted context.
+- `npm run support:check` verifies issue templates, support docs, the report gallery feedback template, the support lifecycle overview, outcome prioritization guide, backlog records, 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.94.md

@@ -0,0 +1,58 @@
+# Memento Mori Jester v0.1.94
+
+## Summary
+
+This release adds a checked public-safe support outcome prioritization guide. It helps maintainers decide whether a closed support report should become a docs clarification, fixture backlog item, or rule-review candidate based on concrete evidence thresholds.
+
+## What Changed
+
+- Added `examples/support/outcome-prioritization.md`.
+- Added `examples/support/outcome-prioritization.json`.
+- Extended `scripts/check-support-triage.mjs` to validate outcome priorities, evidence thresholds, backlog destinations, and required checks.
+- Extended production-readiness checks for the prioritization guide.
+- 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 follow-up prioritization guidance.
+
+## 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.94 checked support outcome prioritization"
+```
+
+Expected:
+
+- `support:check` verifies issue templates, feedback templates, the support lifecycle overview, outcome prioritization guide, 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.94` 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.95.md

@@ -0,0 +1,58 @@
+# Memento Mori Jester v0.1.95
+
+## Summary
+
+This release adds checked public-safe support backlog records. It helps maintainers turn a closed and prioritized support outcome into a docs clarification, fixture backlog item, or rule-review candidate without changing rule behavior first.
+
+## What Changed
+
+- Added `examples/support/backlog-records.md`.
+- Added `examples/support/backlog-records.json`.
+- Extended `scripts/check-support-triage.mjs` to validate backlog record IDs, outcome mapping, source closeouts, evidence thresholds, required checks, and privacy review guidance.
+- Extended production-readiness checks for the backlog records.
+- 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 follow-up backlog 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.95 checked support backlog records"
+```
+
+Expected:
+
+- `support:check` verifies issue templates, feedback templates, the support lifecycle overview, outcome prioritization guide, backlog records, 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.95` 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,9 +2,9 @@
 
 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.
 
-Start with the checked [support lifecycle overview](support-lifecycle.md) when you need the whole path in one place. The lifecycle source is [support-lifecycle.json](support-lifecycle.json).
+Start with the checked [support lifecycle overview](support-lifecycle.md) when you need the whole path in one place. The lifecycle source is [support-lifecycle.json](support-lifecycle.json). Use [outcome-prioritization.md](outcome-prioritization.md) after closeout to decide whether follow-up work should become docs, fixture backlog, or rule-review work. Use [backlog-records.md](backlog-records.md) to turn that decision into a public-safe backlog artifact.
 
-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).
+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). The backlog source is [backlog-records.json](backlog-records.json).
 
 | ID | Source | Classification | Follow-up |
 | --- | --- | --- | --- |
@@ -25,10 +25,11 @@ The checked source is [triage-playbook.json](triage-playbook.json). Use [respons
 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.
+9. If follow-up work remains, create the matching backlog record: docs clarification, fixture backlog item, or rule-review candidate.
 
 ## Checks
 
-Run this after editing support docs, issue templates, the lifecycle overview, the playbook, response snippets, or closeout checklist:
+Run this after editing support docs, issue templates, the lifecycle overview, outcome prioritization, backlog records, the playbook, response snippets, or closeout checklist:
 
 ```powershell
 npm run support:check

package/examples/support/backlog-records.json

@@ -0,0 +1,78 @@
+[
+  {
+    "id": "docs-clarification-backlog-record",
+    "outcome": "docs-example",
+    "priority": "low",
+    "sourceCloseout": "docs-clarification-closeout",
+    "prioritizationSource": "outcome-prioritization.json",
+    "backlogType": "docs clarification",
+    "publicTitle": "Clarify checked report-gallery wording",
+    "publicSummary": "Update docs or report-gallery wording so expected behavior is easier to compare with local output.",
+    "evidence": [
+      "Nearest checked report or docs page is identified.",
+      "Observed output matches current behavior or differs only in wording/context.",
+      "No rule behavior change is requested before a clearer explanation is tried."
+    ],
+    "nextAction": "Open or update a docs issue with the public-safe wording change and link the matching checked report.",
+    "privacyReview": [
+      "No secrets, private code, private paths, customer data, full logs, or unredacted SARIF are included.",
+      "Any private project names are replaced with placeholders.",
+      "Sensitive reports are routed to SECURITY.md instead of a public backlog item."
+    ],
+    "requiredChecks": [
+      "npm run reports:check",
+      "npm run support:check"
+    ]
+  },
+  {
+    "id": "fixture-backlog-record",
+    "outcome": "fixture-backlog",
+    "priority": "medium",
+    "sourceCloseout": "fixture-backlog-closeout",
+    "prioritizationSource": "outcome-prioritization.json",
+    "backlogType": "pass or quiet-pass fixture",
+    "publicTitle": "Add a quiet-pass fixture for a minimized false-positive boundary",
+    "publicSummary": "Track a redacted fixture candidate before changing matching, scoring, or verdict behavior.",
+    "evidence": [
+      "Smallest sanitized command, plan, diff, or final-answer text is available.",
+      "Rule id and redacted `jester tune <rule-id> --json` evidence are available.",
+      "The safe boundary is not already covered by an existing pass or quiet-pass fixture."
+    ],
+    "nextAction": "Open a fixture backlog item with the candidate rule id, expected verdict, and absentRuleIds or expectedRuleIds.",
+    "privacyReview": [
+      "No secrets, private code, private paths, customer data, full logs, or unredacted SARIF are included.",
+      "The reduced reproduction uses placeholders such as <repo>, <path>, or <redacted>.",
+      "Sensitive reports are routed to SECURITY.md instead of a public backlog item."
+    ],
+    "requiredChecks": [
+      "npm run fixtures:check",
+      "npm run fixtures:report",
+      "npm run support:check"
+    ]
+  },
+  {
+    "id": "rule-review-candidate-backlog-record",
+    "outcome": "rule-review-candidate",
+    "priority": "high",
+    "sourceCloseout": "rule-review-closeout",
+    "prioritizationSource": "outcome-prioritization.json",
+    "backlogType": "rule-review candidate",
+    "publicTitle": "Compare repeated sanitized reports for a rule boundary",
+    "publicSummary": "Track repeated public-safe reports so maintainers can compare fixture evidence before changing guidance or matching.",
+    "evidence": [
+      "At least two sanitized reports or checked examples point at the same rule boundary.",
+      "Redacted `jester tune <rule-id> --json` or fixture report evidence is referenced.",
+      "The candidate explains why docs clarification or a single fixture backlog item is not enough."
+    ],
+    "nextAction": "Open a rule-review candidate issue linking the sanitized examples, fixture evidence, and current guidance.",
+    "privacyReview": [
+      "No secrets, private code, private paths, customer data, full logs, or unredacted SARIF are included.",
+      "Repeated examples are summarized without exposing private project details.",
+      "Sensitive reports are routed to SECURITY.md instead of a public backlog item."
+    ],
+    "requiredChecks": [
+      "npm run fixtures:report -- --markdown",
+      "npm run support:check"
+    ]
+  }
+]

package/examples/support/backlog-records.md

@@ -0,0 +1,57 @@
+# Support Backlog Records
+
+Use this after the [support lifecycle overview](support-lifecycle.md), [outcome prioritization guide](outcome-prioritization.md), and [closeout checklist](closeout-checklist.md) have identified follow-up work. The checked source is [backlog-records.json](backlog-records.json).
+
+These records show how a closed, prioritized, public-safe support outcome becomes a backlog artifact without changing rule behavior first.
+
+| Outcome | Priority | Backlog record | Destination | Required checks |
+| --- | --- | --- | --- | --- |
+| `docs-example` | low | `docs-clarification-backlog-record` | docs clarification | `npm run reports:check`, `npm run support:check` |
+| `fixture-backlog` | medium | `fixture-backlog-record` | pass or quiet-pass fixture | `npm run fixtures:check`, `npm run fixtures:report`, `npm run support:check` |
+| `rule-review-candidate` | high | `rule-review-candidate-backlog-record` | rule-review candidate | `npm run fixtures:report -- --markdown`, `npm run support:check` |
+
+## Docs Clarification
+
+Use `docs-clarification-backlog-record` when the behavior is expected but the checked report, README, or guide made it hard to compare local output with the known-good example.
+
+Enough evidence:
+
+- nearest checked report or docs page,
+- observed output summary,
+- confirmation that no rule behavior change is requested before clearer wording is tried.
+
+Next action: open or update a docs issue with the public-safe wording change and link the matching checked report.
+
+## Fixture Backlog
+
+Use `fixture-backlog-record` when a minimized false-positive report looks safe but should be protected by a pass or quiet-pass fixture before any matcher changes are considered.
+
+Enough evidence:
+
+- smallest sanitized command, plan, diff, or final-answer text,
+- candidate rule id plus redacted `jester tune <rule-id> --json` evidence,
+- confirmation that no existing pass or quiet-pass fixture covers the safe boundary.
+
+Next action: open a fixture backlog item with the candidate rule id, expected verdict, and `absentRuleIds` or `expectedRuleIds`.
+
+## Rule-Review Candidate
+
+Use `rule-review-candidate-backlog-record` when repeated sanitized reports point at the same rule boundary and a docs clarification or single fixture backlog item is not enough.
+
+Enough evidence:
+
+- at least two sanitized reports or checked examples,
+- fixture report or tune evidence for the rule,
+- a short explanation of why the decision needs rule-review attention.
+
+Next action: open a rule-review candidate issue linking the sanitized examples, fixture evidence, and current guidance.
+
+## Privacy
+
+Do not create a public backlog record when the report includes secrets, private code, private paths, customer data, full CI logs, unredacted SARIF, credential-handling details, command-execution vulnerability details, package publishing compromise, or MCP data exposure. Use [SECURITY.md](../../SECURITY.md) instead.
+
+Run this after editing support backlog records:
+
+```powershell
+npm run support:check
+```

package/examples/support/outcome-prioritization.json

@@ -0,0 +1,59 @@
+[
+  {
+    "outcome": "docs-example",
+    "priority": "low",
+    "title": "Clarify expected behavior in docs or checked examples",
+    "useWhen": "The report is public-safe, matches current checked behavior, and mainly shows confusing wording, missing context, or surprising severity in docs or report examples.",
+    "minimumEvidence": [
+      "Nearest checked report or docs page is identified.",
+      "Observed output matches current behavior or differs only in wording/context.",
+      "No rule behavior change is requested before a clearer explanation is tried."
+    ],
+    "backlogDestination": "docs clarification or report-gallery wording",
+    "notEnoughEvidence": [
+      "The report includes private details that belong in SECURITY.md.",
+      "The report asks to loosen a rule without a minimal reproduction.",
+      "The reported output cannot be compared with a checked example."
+    ],
+    "nextArtifact": "docs-clarification-closeout",
+    "requiredChecks": ["npm run reports:check", "npm run support:check"]
+  },
+  {
+    "outcome": "fixture-backlog",
+    "priority": "medium",
+    "title": "Capture a plausible safe boundary before changing behavior",
+    "useWhen": "A minimized public-safe report suggests the rule may be noisy, but the safer next move is fixture evidence rather than changing matching or severity.",
+    "minimumEvidence": [
+      "Smallest sanitized command, plan, diff, or final-answer text is available.",
+      "Rule id and redacted `jester tune <rule-id> --json` evidence are available.",
+      "The safe boundary is not already covered by an existing pass or quiet-pass fixture."
+    ],
+    "backlogDestination": "pass or quiet-pass fixture backlog item",
+    "notEnoughEvidence": [
+      "Only a broad complaint is available without a reduced reproduction.",
+      "The example still contains secrets, private code, private paths, or full logs.",
+      "The behavior is already clearly documented as expected."
+    ],
+    "nextArtifact": "fixture-backlog-closeout",
+    "requiredChecks": ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"]
+  },
+  {
+    "outcome": "rule-review-candidate",
+    "priority": "high",
+    "title": "Open a rule-review candidate for repeated sanitized surprises",
+    "useWhen": "Multiple public-safe reports point at the same guidance or matching boundary and fixture evidence suggests maintainers should compare the rule more deliberately.",
+    "minimumEvidence": [
+      "At least two sanitized reports or checked examples point at the same rule boundary.",
+      "Redacted `jester tune <rule-id> --json` or fixture report evidence is referenced.",
+      "The candidate explains why docs clarification or a single fixture backlog item is not enough."
+    ],
+    "backlogDestination": "rule-review candidate issue",
+    "notEnoughEvidence": [
+      "Only one report is available.",
+      "The rule id, review kind, or reproduction shape is unclear.",
+      "The candidate would require immediate behavior changes without fixture evidence."
+    ],
+    "nextArtifact": "rule-review-closeout",
+    "requiredChecks": ["npm run fixtures:report -- --markdown", "npm run support:check"]
+  }
+]

package/examples/support/outcome-prioritization.md

@@ -0,0 +1,66 @@
+# Support Outcome Prioritization
+
+Use this guide after a support report has been closed out and maintainers need to decide what follow-up work deserves a backlog item. It keeps the public support lifecycle useful without turning every report into a rule change.
+
+The checked source is [outcome-prioritization.json](outcome-prioritization.json). It pairs with the [support lifecycle overview](support-lifecycle.md), [triage playbook](triage-playbook.json), [response snippets](response-snippets.md), and [closeout checklist](closeout-checklist.md).
+
+## Priority Rows
+
+| Outcome | Priority | Backlog Destination | Enough Evidence |
+| --- | --- | --- | --- |
+| `docs-example` | `low` | docs clarification or report-gallery wording | checked behavior is correct, but wording or context confused someone |
+| `fixture-backlog` | `medium` | pass or quiet-pass fixture backlog item | minimal public-safe reproduction plus `jester tune <rule-id> --json` evidence |
+| `rule-review-candidate` | `high` | rule-review candidate issue | at least two sanitized reports point at the same rule boundary |
+
+## Evidence Thresholds
+
+### `docs-example`
+
+Use when the report matches current checked behavior and mainly needs clearer docs, report-gallery wording, or severity context.
+
+Enough evidence:
+
+- nearest checked report or docs page is identified,
+- observed output matches current behavior or differs only in wording/context,
+- no rule behavior change is requested before a clearer explanation is tried.
+
+### `fixture-backlog`
+
+Use when the report describes a plausible safe boundary, but maintainers should prove it with a pass or quiet-pass fixture before changing behavior.
+
+Enough evidence:
+
+- smallest sanitized command, plan, diff, or final-answer text is available,
+- rule id and redacted `jester tune <rule-id> --json` evidence are available,
+- the safe boundary is not already covered by an existing pass or quiet-pass fixture.
+
+### `rule-review-candidate`
+
+Use when repeated public-safe reports suggest the guidance or matching boundary may need deliberate review.
+
+Enough evidence:
+
+- at least two sanitized reports or checked examples point at the same rule boundary,
+- redacted `jester tune <rule-id> --json` or fixture report evidence is referenced,
+- the candidate explains why docs clarification or a single fixture backlog item is not enough.
+
+## Do Not Prioritize Publicly
+
+Do not create a public backlog item when the report includes secrets, private code, private paths, customer data, full CI logs, unredacted SARIF, credential-handling details, command-execution vulnerability details, package publishing compromise, or MCP data exposure. Use [SECURITY.md](../../SECURITY.md) instead.
+
+## Checks
+
+Run this after editing prioritization guidance or support lifecycle files:
+
+```powershell
+npm run support:check
+```
+
+Run the checks for the chosen outcome:
+
+```powershell
+npm run reports:check
+npm run fixtures:check
+npm run fixtures:report
+npm run fixtures:report -- --markdown
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memento-mori-jester",
-  "version": "0.1.93",
+  "version": "0.1.95",
   "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,8 +94,12 @@ for (const path of [
   "examples/reports/feedback-template.md",
   "examples/reports/report-gallery.json",
   "examples/support/README.md",
+  "examples/support/backlog-records.md",
+  "examples/support/backlog-records.json",
   "examples/support/closeout-checklist.md",
   "examples/support/closeout-checklist.json",
+  "examples/support/outcome-prioritization.md",
+  "examples/support/outcome-prioritization.json",
   "examples/support/response-snippets.md",
   "examples/support/response-snippets.json",
   "examples/support/support-lifecycle.md",
@@ -133,6 +137,8 @@ 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", /support-lifecycle\.md/, "support lifecycle overview link");
+requireText("README.md", /outcome-prioritization\.md/, "support outcome prioritization link");
+requireText("README.md", /backlog-records\.md/, "support backlog records 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");
@@ -157,6 +163,8 @@ requireText("docs/PRODUCTION_READINESS.md", /examples\/support/, "support triage
 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", /support lifecycle overview/i, "support lifecycle overview readiness");
+requireText("docs/PRODUCTION_READINESS.md", /outcome prioritization guide/i, "support outcome prioritization readiness");
+requireText("docs/PRODUCTION_READINESS.md", /backlog records/i, "support backlog records 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");
@@ -184,6 +192,8 @@ requireText("docs/MAINTAINER_TRIAGE.md", /examples\/support/, "support triage pl
 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", /support-lifecycle\.md/, "support lifecycle overview link");
+requireText("docs/MAINTAINER_TRIAGE.md", /outcome-prioritization\.md/, "support outcome prioritization link");
+requireText("docs/MAINTAINER_TRIAGE.md", /backlog-records\.md/, "support backlog records 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");
@@ -219,6 +229,8 @@ requireText("examples/support/README.md", /triage-playbook\.json/, "support tria
 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", /support-lifecycle\.md/, "support lifecycle overview link");
+requireText("examples/support/README.md", /outcome-prioritization\.md/, "support outcome prioritization link");
+requireText("examples/support/README.md", /backlog-records\.md/, "support backlog records 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");
@@ -247,6 +259,25 @@ requireText("examples/support/support-lifecycle.md", /rule-review-candidate/, "s
 requireText("examples/support/support-lifecycle.json", /docs-example-response/, "support lifecycle docs response");
 requireText("examples/support/support-lifecycle.json", /fixture-backlog-response/, "support lifecycle fixture response");
 requireText("examples/support/support-lifecycle.json", /rule-review-candidate-response/, "support lifecycle rule-review response");
+requireText("examples/support/outcome-prioritization.md", /Support Outcome Prioritization/, "support outcome prioritization heading");
+requireText("examples/support/outcome-prioritization.md", /outcome-prioritization\.json/, "support outcome prioritization JSON link");
+requireText("examples/support/outcome-prioritization.md", /docs-example/, "support outcome prioritization docs outcome");
+requireText("examples/support/outcome-prioritization.md", /fixture-backlog/, "support outcome prioritization fixture outcome");
+requireText("examples/support/outcome-prioritization.md", /rule-review-candidate/, "support outcome prioritization rule-review outcome");
+requireText("examples/support/outcome-prioritization.md", /at least two sanitized reports/, "support outcome prioritization evidence threshold");
+requireText("examples/support/outcome-prioritization.json", /docs-clarification-closeout/, "support outcome prioritization docs closeout");
+requireText("examples/support/outcome-prioritization.json", /fixture-backlog-closeout/, "support outcome prioritization fixture closeout");
+requireText("examples/support/outcome-prioritization.json", /rule-review-closeout/, "support outcome prioritization rule-review closeout");
+requireText("examples/support/backlog-records.md", /Support Backlog Records/, "support backlog records heading");
+requireText("examples/support/backlog-records.md", /backlog-records\.json/, "support backlog records JSON link");
+requireText("examples/support/backlog-records.md", /docs-clarification-backlog-record/, "support docs backlog record");
+requireText("examples/support/backlog-records.md", /fixture-backlog-record/, "support fixture backlog record");
+requireText("examples/support/backlog-records.md", /rule-review-candidate-backlog-record/, "support rule-review backlog record");
+requireText("examples/support/backlog-records.md", /jester tune <rule-id> --json/, "support backlog tuning evidence");
+requireText("examples/support/backlog-records.md", /SECURITY\.md/, "support backlog security redirect");
+requireText("examples/support/backlog-records.json", /docs-clarification-backlog-record/, "support docs backlog record JSON");
+requireText("examples/support/backlog-records.json", /fixture-backlog-record/, "support fixture backlog record JSON");
+requireText("examples/support/backlog-records.json", /rule-review-candidate-backlog-record/, "support rule-review backlog record JSON");
 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");
@@ -283,6 +314,8 @@ requireText("scripts/check-support-triage.mjs", /triage-playbook\.json/, "suppor
 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", /support-lifecycle\.json/, "support lifecycle overview guard");
+requireText("scripts/check-support-triage.mjs", /outcome-prioritization\.json/, "support outcome prioritization guard");
+requireText("scripts/check-support-triage.mjs", /backlog-records\.json/, "support backlog records 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,8 +25,12 @@ const supportFiles = [
   ".github/ISSUE_TEMPLATE/config.yml",
   "examples/reports/feedback-template.md",
   "examples/reports/README.md",
+  "examples/support/backlog-records.md",
+  "examples/support/backlog-records.json",
   "examples/support/closeout-checklist.md",
   "examples/support/closeout-checklist.json",
+  "examples/support/outcome-prioritization.md",
+  "examples/support/outcome-prioritization.json",
   "examples/support/README.md",
   "examples/support/response-snippets.md",
   "examples/support/response-snippets.json",
@@ -82,7 +86,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", /backlog-records\.md/, "support backlog records link");
 requireText("examples/support/README.md", /support-lifecycle\.md/, "support lifecycle overview link");
+requireText("examples/support/README.md", /outcome-prioritization\.md/, "support outcome prioritization link");
 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");
@@ -124,6 +130,35 @@ requireText("examples/support/support-lifecycle.md", /SECURITY\.md/, "lifecycle
 requireText("examples/support/support-lifecycle.json", /docs-example-response/, "docs lifecycle response");
 requireText("examples/support/support-lifecycle.json", /fixture-backlog-response/, "fixture lifecycle response");
 requireText("examples/support/support-lifecycle.json", /rule-review-candidate-response/, "rule-review lifecycle response");
+requireText("examples/support/outcome-prioritization.md", /Support Outcome Prioritization/, "support outcome prioritization heading");
+requireText("examples/support/outcome-prioritization.md", /outcome-prioritization\.json/, "support prioritization JSON link");
+requireText("examples/support/outcome-prioritization.md", /support lifecycle overview/, "support lifecycle prioritization link");
+requireText("examples/support/outcome-prioritization.md", /docs-example/, "docs prioritization outcome");
+requireText("examples/support/outcome-prioritization.md", /fixture-backlog/, "fixture prioritization outcome");
+requireText("examples/support/outcome-prioritization.md", /rule-review-candidate/, "rule-review prioritization outcome");
+requireText("examples/support/outcome-prioritization.md", /jester tune <rule-id> --json/, "tune JSON prioritization evidence");
+requireText("examples/support/outcome-prioritization.md", /at least two sanitized reports/, "rule-review evidence threshold");
+requireText("examples/support/outcome-prioritization.md", /SECURITY\.md/, "prioritization security redirect");
+requireText("examples/support/outcome-prioritization.json", /docs-clarification-closeout/, "docs prioritization closeout");
+requireText("examples/support/outcome-prioritization.json", /fixture-backlog-closeout/, "fixture prioritization closeout");
+requireText("examples/support/outcome-prioritization.json", /rule-review-closeout/, "rule-review prioritization closeout");
+requireText("examples/support/backlog-records.md", /Support Backlog Records/, "support backlog records heading");
+requireText("examples/support/backlog-records.md", /backlog-records\.json/, "support backlog records JSON link");
+requireText("examples/support/backlog-records.md", /support lifecycle overview/, "support lifecycle backlog link");
+requireText("examples/support/backlog-records.md", /outcome prioritization guide/, "support prioritization backlog link");
+requireText("examples/support/backlog-records.md", /closeout checklist/, "support closeout backlog link");
+requireText("examples/support/backlog-records.md", /docs-clarification-backlog-record/, "docs backlog record");
+requireText("examples/support/backlog-records.md", /fixture-backlog-record/, "fixture backlog record");
+requireText("examples/support/backlog-records.md", /rule-review-candidate-backlog-record/, "rule-review backlog record");
+requireText("examples/support/backlog-records.md", /docs-example/, "docs backlog outcome");
+requireText("examples/support/backlog-records.md", /fixture-backlog/, "fixture backlog outcome");
+requireText("examples/support/backlog-records.md", /rule-review-candidate/, "rule-review backlog outcome");
+requireText("examples/support/backlog-records.md", /jester tune <rule-id> --json/, "tune JSON backlog evidence");
+requireText("examples/support/backlog-records.md", /SECURITY\.md/, "backlog security redirect");
+requireText("examples/support/backlog-records.md", /npm run support:check/, "support checker backlog command");
+requireText("examples/support/backlog-records.json", /docs-clarification-backlog-record/, "docs backlog record JSON");
+requireText("examples/support/backlog-records.json", /fixture-backlog-record/, "fixture backlog record JSON");
+requireText("examples/support/backlog-records.json", /rule-review-candidate-backlog-record/, "rule-review backlog record JSON");
 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");
@@ -140,6 +175,8 @@ requireText("docs/MAINTAINER_TRIAGE.md", /feedback-template\.md/, "feedback temp
 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", /support-lifecycle\.md/, "support lifecycle triage link");
+requireText("docs/MAINTAINER_TRIAGE.md", /outcome-prioritization\.md/, "support prioritization triage link");
+requireText("docs/MAINTAINER_TRIAGE.md", /backlog-records\.md/, "support backlog records 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");
@@ -149,6 +186,8 @@ requireText("docs/MAINTAINER_TRIAGE.md", /npm(?:\.cmd)? run support:check/, "sup
 requireText("docs/PRODUCTION_READINESS.md", /support:check/, "support checker readiness");
 requireText("README.md", /feedback-template\.md/, "feedback template README link");
 requireText("README.md", /support-lifecycle\.md/, "support lifecycle README link");
+requireText("README.md", /outcome-prioritization\.md/, "support prioritization README link");
+requireText("README.md", /backlog-records\.md/, "support backlog records 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");
@@ -161,6 +200,8 @@ checkTriagePlaybook();
 checkResponseSnippets();
 checkCloseoutChecklist();
 checkSupportLifecycle();
+checkOutcomePrioritization();
+checkBacklogRecords();
 
 if (failures.length > 0) {
   console.error("Support triage check failed:");
@@ -545,3 +586,225 @@ function checkSupportLifecycle() {
     }
   }
 }
+
+function checkOutcomePrioritization() {
+  const path = "examples/support/outcome-prioritization.json";
+  const priorities = readJson(path);
+  if (!priorities) {
+    return;
+  }
+
+  if (!Array.isArray(priorities) || priorities.length !== 3) {
+    failures.push(`${path} should contain exactly three support outcome priorities.`);
+    return;
+  }
+
+  const expected = [
+    {
+      outcome: "docs-example",
+      priority: "low",
+      nextArtifact: "docs-clarification-closeout",
+      checks: ["npm run reports:check", "npm run support:check"],
+      evidence: ["Nearest checked report", "Observed output", "No rule behavior change"]
+    },
+    {
+      outcome: "fixture-backlog",
+      priority: "medium",
+      nextArtifact: "fixture-backlog-closeout",
+      checks: ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"],
+      evidence: ["Smallest sanitized", "jester tune <rule-id> --json", "existing pass or quiet-pass fixture"]
+    },
+    {
+      outcome: "rule-review-candidate",
+      priority: "high",
+      nextArtifact: "rule-review-closeout",
+      checks: ["npm run fixtures:report -- --markdown", "npm run support:check"],
+      evidence: ["At least two sanitized", "fixture report evidence", "single fixture backlog item is not enough"]
+    }
+  ];
+  const seenOutcomes = new Set();
+
+  for (const [index, entry] of priorities.entries()) {
+    const expectedEntry = expected[index];
+    if (entry?.outcome !== expectedEntry.outcome) {
+      failures.push(`${path} entry ${index + 1} should have outcome ${expectedEntry.outcome}.`);
+      continue;
+    }
+
+    if (seenOutcomes.has(entry.outcome)) {
+      failures.push(`${path} has duplicate outcome ${entry.outcome}.`);
+    }
+    seenOutcomes.add(entry.outcome);
+
+    if (entry.priority !== expectedEntry.priority) {
+      failures.push(`${entry.outcome}.priority should be ${expectedEntry.priority}.`);
+    }
+
+    if (typeof entry.title !== "string" || entry.title.length < 20) {
+      failures.push(`${entry.outcome}.title should explain the prioritization decision.`);
+    }
+
+    if (typeof entry.useWhen !== "string" || entry.useWhen.length < 60) {
+      failures.push(`${entry.outcome}.useWhen should explain when to choose this outcome.`);
+    }
+
+    if (typeof entry.backlogDestination !== "string" || entry.backlogDestination.length < 15) {
+      failures.push(`${entry.outcome}.backlogDestination should describe the follow-up destination.`);
+    }
+
+    if (entry.nextArtifact !== expectedEntry.nextArtifact) {
+      failures.push(`${entry.outcome}.nextArtifact should be ${expectedEntry.nextArtifact}.`);
+    }
+
+    if (!Array.isArray(entry.minimumEvidence) || entry.minimumEvidence.length !== 3) {
+      failures.push(`${entry.outcome}.minimumEvidence should contain exactly three evidence thresholds.`);
+    } else {
+      const evidenceText = entry.minimumEvidence.join("\n");
+      for (const expectedEvidence of expectedEntry.evidence) {
+        if (!evidenceText.includes(expectedEvidence)) {
+          failures.push(`${entry.outcome}.minimumEvidence should include ${expectedEvidence}.`);
+        }
+      }
+    }
+
+    if (!Array.isArray(entry.notEnoughEvidence) || entry.notEnoughEvidence.length !== 3) {
+      failures.push(`${entry.outcome}.notEnoughEvidence should contain exactly three guardrails.`);
+    } else {
+      const notEnoughText = entry.notEnoughEvidence.join("\n");
+      if (!/private|secret|SECURITY\.md|reproduction|rule/i.test(notEnoughText)) {
+        failures.push(`${entry.outcome}.notEnoughEvidence should include privacy, reproduction, or rule-change guardrails.`);
+      }
+    }
+
+    if (!Array.isArray(entry.requiredChecks)) {
+      failures.push(`${entry.outcome}.requiredChecks should be an array.`);
+      continue;
+    }
+
+    for (const check of expectedEntry.checks) {
+      if (!entry.requiredChecks.includes(check)) {
+        failures.push(`${entry.outcome}.requiredChecks should include ${check}.`);
+      }
+    }
+  }
+}
+
+function checkBacklogRecords() {
+  const path = "examples/support/backlog-records.json";
+  const records = readJson(path);
+  if (!records) {
+    return;
+  }
+
+  if (!Array.isArray(records) || records.length !== 3) {
+    failures.push(`${path} should contain exactly three support backlog records.`);
+    return;
+  }
+
+  const expected = [
+    {
+      id: "docs-clarification-backlog-record",
+      outcome: "docs-example",
+      priority: "low",
+      sourceCloseout: "docs-clarification-closeout",
+      backlogType: "docs clarification",
+      checks: ["npm run reports:check", "npm run support:check"],
+      evidence: ["Nearest checked report", "Observed output", "No rule behavior change"]
+    },
+    {
+      id: "fixture-backlog-record",
+      outcome: "fixture-backlog",
+      priority: "medium",
+      sourceCloseout: "fixture-backlog-closeout",
+      backlogType: "pass or quiet-pass fixture",
+      checks: ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"],
+      evidence: ["Smallest sanitized", "jester tune <rule-id> --json", "existing pass or quiet-pass fixture"]
+    },
+    {
+      id: "rule-review-candidate-backlog-record",
+      outcome: "rule-review-candidate",
+      priority: "high",
+      sourceCloseout: "rule-review-closeout",
+      backlogType: "rule-review candidate",
+      checks: ["npm run fixtures:report -- --markdown", "npm run support:check"],
+      evidence: ["At least two sanitized", "fixture report evidence", "single fixture backlog item is not enough"]
+    }
+  ];
+  const seenIds = new Set();
+
+  for (const [index, record] of records.entries()) {
+    const expectedRecord = expected[index];
+    if (record?.id !== expectedRecord.id) {
+      failures.push(`${path} entry ${index + 1} should have id ${expectedRecord.id}.`);
+      continue;
+    }
+
+    if (seenIds.has(record.id)) {
+      failures.push(`${path} has duplicate id ${record.id}.`);
+    }
+    seenIds.add(record.id);
+
+    if (record.outcome !== expectedRecord.outcome) {
+      failures.push(`${record.id}.outcome should be ${expectedRecord.outcome}.`);
+    }
+
+    if (record.priority !== expectedRecord.priority) {
+      failures.push(`${record.id}.priority should be ${expectedRecord.priority}.`);
+    }
+
+    if (record.sourceCloseout !== expectedRecord.sourceCloseout) {
+      failures.push(`${record.id}.sourceCloseout should be ${expectedRecord.sourceCloseout}.`);
+    }
+
+    if (record.prioritizationSource !== "outcome-prioritization.json") {
+      failures.push(`${record.id}.prioritizationSource should be outcome-prioritization.json.`);
+    }
+
+    if (record.backlogType !== expectedRecord.backlogType) {
+      failures.push(`${record.id}.backlogType should be ${expectedRecord.backlogType}.`);
+    }
+
+    if (typeof record.publicTitle !== "string" || record.publicTitle.length < 20) {
+      failures.push(`${record.id}.publicTitle should be a useful public title.`);
+    }
+
+    if (typeof record.publicSummary !== "string" || record.publicSummary.length < 50) {
+      failures.push(`${record.id}.publicSummary should be a useful public summary.`);
+    }
+
+    if (typeof record.nextAction !== "string" || record.nextAction.length < 40) {
+      failures.push(`${record.id}.nextAction should describe the backlog action.`);
+    }
+
+    if (!Array.isArray(record.evidence) || record.evidence.length !== 3) {
+      failures.push(`${record.id}.evidence should contain exactly three evidence items.`);
+    } else {
+      const evidenceText = record.evidence.join("\n");
+      for (const expectedEvidence of expectedRecord.evidence) {
+        if (!evidenceText.includes(expectedEvidence)) {
+          failures.push(`${record.id}.evidence should include ${expectedEvidence}.`);
+        }
+      }
+    }
+
+    if (!Array.isArray(record.privacyReview) || record.privacyReview.length !== 3) {
+      failures.push(`${record.id}.privacyReview should contain exactly three privacy checks.`);
+    } else {
+      const privacyText = record.privacyReview.join("\n");
+      if (!/secret|private|SECURITY\.md|redacted|placeholder/i.test(privacyText)) {
+        failures.push(`${record.id}.privacyReview should include privacy and security routing guidance.`);
+      }
+    }
+
+    if (!Array.isArray(record.requiredChecks)) {
+      failures.push(`${record.id}.requiredChecks should be an array.`);
+      continue;
+    }
+
+    for (const check of expectedRecord.checks) {
+      if (!record.requiredChecks.includes(check)) {
+        failures.push(`${record.id}.requiredChecks should include ${check}.`);
+      }
+    }
+  }
+}