memento-mori-jester 0.1.96 → 0.1.97

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to Memento Mori Jester are tracked here.
 
 ## Unreleased
 
+## 0.1.97
+
+- Extended the checked support lifecycle overview so it now covers report, triage, response, closeout, prioritization, backlog record, and backlog review stages.
+- Updated `support-lifecycle.json`, `npm run support:check`, and production-readiness checks so every support outcome points at the full checked artifact chain.
+- Refreshed support docs, maintainer triage docs, production-readiness docs, roadmap, and release notes for the full lifecycle index.
+
 ## 0.1.96
 
 - Added a checked public-safe support backlog review checklist for deciding whether backlog records remain docs clarifications, fixture backlog items, rule-review candidates, or close with no action.

package/ROADMAP.md

@@ -6,6 +6,7 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
 
 ## Recently Shipped
 
+- Full checked support lifecycle overview in v0.1.97, extending the index from report, triage, response, and closeout through prioritization, backlog records, and backlog review.
 - Checked support backlog review in v0.1.96, helping maintainers revisit backlog records and keep them as docs, fixture, or rule-review work, or close them with no action when evidence goes stale.
 - 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.
@@ -87,6 +88,7 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
 
 - Collect real-world reports and fold the strongest redacted cases into more framework tuning cookbook recipes.
 - Add a small checked maintainer dashboard or report that summarizes open support backlog review states from public-safe JSON.
+- Add a compact support lifecycle diagram or generated summary once the lifecycle JSON shape has settled.
 - 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.

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. 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, then use [backlog-review.md](../examples/support/backlog-review.md) to revisit whether that artifact remains active or closes with no action.
+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 backlog review. 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, then use [backlog-review.md](../examples/support/backlog-review.md) to revisit whether that artifact remains active or closes with no action.
 
 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).
 

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, outcome prioritization guide, backlog records, backlog review checklist, maintainer triage playbook, response snippets, and closeout checklist for first response, classification, follow-up outcomes, public-safe decision records, backlog prioritization, backlog artifacts, and aging review from sanitized support reports.
+- `examples/support` provides a checked support lifecycle overview covering report, triage, response, closeout, prioritization, backlog record, and backlog review, plus the supporting outcome prioritization guide, backlog records, backlog review checklist, maintainer triage playbook, response snippets, and closeout checklist.
 - `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`.
 

package/docs/RELEASE_NOTES_v0.1.97.md

@@ -0,0 +1,58 @@
+# Memento Mori Jester v0.1.97
+
+## Summary
+
+This release updates the checked support lifecycle overview so it reflects the full public-safe support chain: report, triage, response, closeout, prioritization, backlog record, and backlog review.
+
+## What Changed
+
+- Extended `examples/support/support-lifecycle.md` to show the full seven-stage lifecycle.
+- Extended `examples/support/support-lifecycle.json` so every support outcome links to prioritization, backlog record, and backlog review artifacts.
+- Updated `scripts/check-support-triage.mjs` to validate the seven lifecycle stages and artifact references.
+- Extended production-readiness checks for the full lifecycle index.
+- Updated support docs, maintainer triage docs, production-readiness docs, roadmap, and changelog.
+
+## Public Interface
+
+- No CLI command changes.
+- No MCP tool changes.
+- No config schema changes.
+- No review rule, scoring, matching, or verdict behavior changes.
+- No GitHub Action input changes.
+- Support docs and package examples now include the full checked support lifecycle index.
+
+## 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.97 full support lifecycle overview"
+```
+
+Expected:
+
+- `support:check` verifies issue templates, feedback templates, the full support lifecycle overview, outcome prioritization guide, backlog records, backlog review checklist, 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.97` 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.
 
-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, then use [backlog-review.md](backlog-review.md) to decide whether the item stays active or closes with no action.
+Start with the checked [support lifecycle overview](support-lifecycle.md) when you need the whole path in one place: report, triage, response, closeout, prioritization, backlog record, and backlog review. 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, then use [backlog-review.md](backlog-review.md) to decide whether the item stays active or closes with no action.
 
 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). The review source is [backlog-review.json](backlog-review.json).
 

package/examples/support/support-lifecycle.json

@@ -26,6 +26,24 @@
         "artifact": "examples/support/closeout-checklist.json",
         "reference": "docs-clarification-closeout",
         "purpose": "Record whether the docs clarification shipped or is queued, then link the public-safe follow-up."
+      },
+      {
+        "id": "prioritization",
+        "artifact": "examples/support/outcome-prioritization.json",
+        "reference": "docs-example",
+        "purpose": "Confirm the follow-up is low-priority docs clarification before opening a backlog record."
+      },
+      {
+        "id": "backlog-record",
+        "artifact": "examples/support/backlog-records.json",
+        "reference": "docs-clarification-backlog-record",
+        "purpose": "Record the public-safe docs backlog artifact and the checks needed after copy changes."
+      },
+      {
+        "id": "backlog-review",
+        "artifact": "examples/support/backlog-review.json",
+        "reference": "docs-clarification-review",
+        "purpose": "Revisit whether the docs backlog item remains active or should close with no action."
       }
     ],
     "requiredChecks": ["npm run reports:check", "npm run support:check"]
@@ -57,6 +75,24 @@
         "artifact": "examples/support/closeout-checklist.json",
         "reference": "fixture-backlog-closeout",
         "purpose": "Record that a redacted fixture backlog item exists and the rule remains unchanged."
+      },
+      {
+        "id": "prioritization",
+        "artifact": "examples/support/outcome-prioritization.json",
+        "reference": "fixture-backlog",
+        "purpose": "Confirm the follow-up is medium-priority fixture backlog before changing any matcher."
+      },
+      {
+        "id": "backlog-record",
+        "artifact": "examples/support/backlog-records.json",
+        "reference": "fixture-backlog-record",
+        "purpose": "Record the public-safe fixture backlog artifact and the expected pass or quiet-pass boundary."
+      },
+      {
+        "id": "backlog-review",
+        "artifact": "examples/support/backlog-review.json",
+        "reference": "fixture-backlog-review",
+        "purpose": "Revisit whether the fixture backlog item remains active or is already covered elsewhere."
       }
     ],
     "requiredChecks": ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"]
@@ -88,6 +124,24 @@
         "artifact": "examples/support/closeout-checklist.json",
         "reference": "rule-review-closeout",
         "purpose": "Record that a rule-review candidate was opened and fixture evidence will be compared."
+      },
+      {
+        "id": "prioritization",
+        "artifact": "examples/support/outcome-prioritization.json",
+        "reference": "rule-review-candidate",
+        "purpose": "Confirm the follow-up is high-priority rule review backed by repeated sanitized reports."
+      },
+      {
+        "id": "backlog-record",
+        "artifact": "examples/support/backlog-records.json",
+        "reference": "rule-review-candidate-backlog-record",
+        "purpose": "Record the public-safe rule-review backlog artifact and the fixture evidence to compare."
+      },
+      {
+        "id": "backlog-review",
+        "artifact": "examples/support/backlog-review.json",
+        "reference": "rule-review-candidate-review",
+        "purpose": "Revisit whether repeated evidence still warrants rule review before any behavior change."
       }
     ],
     "requiredChecks": ["npm run fixtures:report -- --markdown", "npm run support:check"]

package/examples/support/support-lifecycle.md

@@ -3,18 +3,18 @@
 This index shows the public-safe support path at a glance:
 
 ```text
-report -> triage -> response -> closeout
+report -> triage -> response -> closeout -> prioritization -> backlog-record -> backlog-review
 ```
 
-The checked source is [support-lifecycle.json](support-lifecycle.json). It ties together the [report gallery feedback template](../reports/feedback-template.md), [triage playbook](triage-playbook.json), [response snippets](response-snippets.md), and [closeout checklist](closeout-checklist.md).
+The checked source is [support-lifecycle.json](support-lifecycle.json). It ties together the [report gallery feedback template](../reports/feedback-template.md), [triage playbook](triage-playbook.json), [response snippets](response-snippets.md), [closeout checklist](closeout-checklist.md), [outcome prioritization guide](outcome-prioritization.md), [backlog records](backlog-records.md), and [backlog review checklist](backlog-review.md).
 
 ## Outcomes
 
-| Outcome | Report | Triage | Response | Closeout |
-| --- | --- | --- | --- | --- |
-| `docs-example` | `report-gallery-feedback` | `gallery-expected-block-docs` | `docs-example-response` | `docs-clarification-closeout` |
-| `fixture-backlog` | `false-positive` | `false-positive-fixture-backlog` | `fixture-backlog-response` | `fixture-backlog-closeout` |
-| `rule-review-candidate` | `false-positive` | `repeated-risky-domain-rule-review` | `rule-review-candidate-response` | `rule-review-closeout` |
+| Outcome | Report | Triage | Response | Closeout | Prioritization | Backlog Record | Backlog Review |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| `docs-example` | `report-gallery-feedback` | `gallery-expected-block-docs` | `docs-example-response` | `docs-clarification-closeout` | `docs-example` | `docs-clarification-backlog-record` | `docs-clarification-review` |
+| `fixture-backlog` | `false-positive` | `false-positive-fixture-backlog` | `fixture-backlog-response` | `fixture-backlog-closeout` | `fixture-backlog` | `fixture-backlog-record` | `fixture-backlog-review` |
+| `rule-review-candidate` | `false-positive` | `repeated-risky-domain-rule-review` | `rule-review-candidate-response` | `rule-review-closeout` | `rule-review-candidate` | `rule-review-candidate-backlog-record` | `rule-review-candidate-review` |
 
 ## Audit Checklist
 
@@ -24,6 +24,9 @@ For each public support issue, confirm:
 - the triage outcome is one of `docs-example`, `fixture-backlog`, or `rule-review-candidate`,
 - the response snippet matches the chosen outcome,
 - the closeout record says whether the docs clarification shipped or queued, fixture backlog was created, or rule-review candidate was opened,
+- the prioritization record says whether follow-up is low-priority docs, medium-priority fixture backlog, or high-priority rule review,
+- the backlog record captures the public-safe follow-up artifact without changing rule behavior first,
+- the backlog review keeps the item active as docs, fixture, or rule-review work only while evidence still holds, otherwise it closes as `closed-no-action`,
 - no secrets, private code, private paths, customer data, full logs, unredacted SARIF, or exploitable security details appear in the public record.
 
 ## Checks

package/package.json

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

@@ -258,13 +258,18 @@ requireText("examples/support/closeout-checklist.json", /fixture-backlog-closeou
 requireText("examples/support/closeout-checklist.json", /rule-review-closeout/, "support rule-review closeout record");
 requireText("examples/support/support-lifecycle.md", /Support Lifecycle Overview/, "support lifecycle heading");
 requireText("examples/support/support-lifecycle.md", /support-lifecycle\.json/, "support lifecycle JSON link");
-requireText("examples/support/support-lifecycle.md", /report -> triage -> response -> closeout/, "support lifecycle flow");
+requireText("examples/support/support-lifecycle.md", /report -> triage -> response -> closeout -> prioritization -> backlog-record -> backlog-review/, "support lifecycle flow");
 requireText("examples/support/support-lifecycle.md", /docs-example/, "support lifecycle docs outcome");
 requireText("examples/support/support-lifecycle.md", /fixture-backlog/, "support lifecycle fixture outcome");
 requireText("examples/support/support-lifecycle.md", /rule-review-candidate/, "support lifecycle rule-review outcome");
+requireText("examples/support/support-lifecycle.md", /backlog records/, "support lifecycle backlog records stage");
+requireText("examples/support/support-lifecycle.md", /backlog review checklist/, "support lifecycle backlog review stage");
 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/support-lifecycle.json", /outcome-prioritization\.json/, "support lifecycle prioritization artifact");
+requireText("examples/support/support-lifecycle.json", /backlog-records\.json/, "support lifecycle backlog records artifact");
+requireText("examples/support/support-lifecycle.json", /backlog-review\.json/, "support lifecycle backlog review artifact");
 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");

package/scripts/check-support-triage.mjs

@@ -120,19 +120,26 @@ requireText("examples/support/closeout-checklist.json", /fixture-backlog-closeou
 requireText("examples/support/closeout-checklist.json", /rule-review-closeout/, "rule-review closeout record");
 requireText("examples/support/support-lifecycle.md", /Support Lifecycle Overview/, "support lifecycle heading");
 requireText("examples/support/support-lifecycle.md", /support-lifecycle\.json/, "support lifecycle JSON link");
-requireText("examples/support/support-lifecycle.md", /report -> triage -> response -> closeout/, "support lifecycle flow");
+requireText("examples/support/support-lifecycle.md", /report -> triage -> response -> closeout -> prioritization -> backlog-record -> backlog-review/, "support lifecycle flow");
 requireText("examples/support/support-lifecycle.md", /report gallery feedback template/, "report feedback lifecycle link");
 requireText("examples/support/support-lifecycle.md", /triage playbook/, "triage lifecycle link");
 requireText("examples/support/support-lifecycle.md", /response snippets/, "response lifecycle link");
 requireText("examples/support/support-lifecycle.md", /closeout checklist/, "closeout lifecycle link");
+requireText("examples/support/support-lifecycle.md", /outcome prioritization guide/, "prioritization lifecycle link");
+requireText("examples/support/support-lifecycle.md", /backlog records/, "backlog records lifecycle link");
+requireText("examples/support/support-lifecycle.md", /backlog review checklist/, "backlog review lifecycle link");
 requireText("examples/support/support-lifecycle.md", /docs-example/, "docs lifecycle outcome");
 requireText("examples/support/support-lifecycle.md", /fixture-backlog/, "fixture lifecycle outcome");
 requireText("examples/support/support-lifecycle.md", /rule-review-candidate/, "rule-review lifecycle outcome");
+requireText("examples/support/support-lifecycle.md", /closed-no-action/, "closed no-action lifecycle review");
 requireText("examples/support/support-lifecycle.md", /doctor --json/, "doctor JSON lifecycle prompt");
 requireText("examples/support/support-lifecycle.md", /SECURITY\.md/, "lifecycle security redirect");
 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/support-lifecycle.json", /outcome-prioritization\.json/, "lifecycle prioritization artifact");
+requireText("examples/support/support-lifecycle.json", /backlog-records\.json/, "lifecycle backlog records artifact");
+requireText("examples/support/support-lifecycle.json", /backlog-review\.json/, "lifecycle backlog review artifact");
 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");
@@ -534,26 +541,53 @@ function checkSupportLifecycle() {
   const expected = [
     {
       outcome: "docs-example",
-      stageReferences: ["report-gallery-feedback", "gallery-expected-block-docs", "docs-example-response", "docs-clarification-closeout"],
+      stageReferences: [
+        "report-gallery-feedback",
+        "gallery-expected-block-docs",
+        "docs-example-response",
+        "docs-clarification-closeout",
+        "docs-example",
+        "docs-clarification-backlog-record",
+        "docs-clarification-review"
+      ],
       checks: ["npm run reports:check", "npm run support:check"]
     },
     {
       outcome: "fixture-backlog",
-      stageReferences: ["false-positive", "false-positive-fixture-backlog", "fixture-backlog-response", "fixture-backlog-closeout"],
+      stageReferences: [
+        "false-positive",
+        "false-positive-fixture-backlog",
+        "fixture-backlog-response",
+        "fixture-backlog-closeout",
+        "fixture-backlog",
+        "fixture-backlog-record",
+        "fixture-backlog-review"
+      ],
       checks: ["npm run fixtures:check", "npm run fixtures:report", "npm run support:check"]
     },
     {
       outcome: "rule-review-candidate",
-      stageReferences: ["false-positive", "repeated-risky-domain-rule-review", "rule-review-candidate-response", "rule-review-closeout"],
+      stageReferences: [
+        "false-positive",
+        "repeated-risky-domain-rule-review",
+        "rule-review-candidate-response",
+        "rule-review-closeout",
+        "rule-review-candidate",
+        "rule-review-candidate-backlog-record",
+        "rule-review-candidate-review"
+      ],
       checks: ["npm run fixtures:report -- --markdown", "npm run support:check"]
     }
   ];
-  const expectedStageIds = ["report", "triage", "response", "closeout"];
+  const expectedStageIds = ["report", "triage", "response", "closeout", "prioritization", "backlog-record", "backlog-review"];
   const expectedArtifacts = [
     "examples/reports/feedback-template.md",
     "examples/support/triage-playbook.json",
     "examples/support/response-snippets.json",
-    "examples/support/closeout-checklist.json"
+    "examples/support/closeout-checklist.json",
+    "examples/support/outcome-prioritization.json",
+    "examples/support/backlog-records.json",
+    "examples/support/backlog-review.json"
   ];
   const seenOutcomes = new Set();
 
@@ -573,8 +607,8 @@ function checkSupportLifecycle() {
       failures.push(`${entry.outcome}.title should explain the lifecycle outcome.`);
     }
 
-    if (!Array.isArray(entry.stages) || entry.stages.length !== 4) {
-      failures.push(`${entry.outcome}.stages should contain report, triage, response, and closeout.`);
+    if (!Array.isArray(entry.stages) || entry.stages.length !== 7) {
+      failures.push(`${entry.outcome}.stages should contain report, triage, response, closeout, prioritization, backlog-record, and backlog-review.`);
       continue;
     }