memento-mori-jester 0.1.97 → 0.1.98

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to Memento Mori Jester are tracked here.
 
 ## Unreleased
 
+## 0.1.98
+
+- Added a compact checked support lifecycle map for scanning report, triage, response, closeout, prioritization, backlog record, and backlog review stages at a glance.
+- Added `support-lifecycle-map.json` plus `npm run support:check` and production-readiness coverage so stage order, outcome summaries, and privacy guardrails stay aligned.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and release notes for the compact lifecycle map.
+
 ## 0.1.97
 
 - Extended the checked support lifecycle overview so it now covers report, triage, response, closeout, prioritization, backlog record, and backlog review stages.

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), [outcome prioritization guide](examples/support/outcome-prioritization.md), [support backlog records](examples/support/backlog-records.md), [support backlog review](examples/support/backlog-review.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 map](examples/support/support-lifecycle-map.md), [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 backlog review](examples/support/backlog-review.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:
 
@@ -450,6 +450,7 @@ More setup examples:
 - [Consumer Quickstart Smoke](examples/consumer-quickstart)
 - [Real-World Report Gallery](examples/reports)
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
+- [Support Lifecycle Map](examples/support/support-lifecycle-map.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)
@@ -478,6 +479,7 @@ Framework CI examples:
 - [Consumer Quickstart Smoke](examples/consumer-quickstart)
 - [Real-World Report Gallery](examples/reports)
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
+- [Support Lifecycle Map](examples/support/support-lifecycle-map.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)
@@ -541,7 +543,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), [outcome prioritization guide](examples/support/outcome-prioritization.md), [support backlog records](examples/support/backlog-records.md), [support backlog review](examples/support/backlog-review.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 map](examples/support/support-lifecycle-map.md), [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 backlog review](examples/support/backlog-review.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,7 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
 
 ## Recently Shipped
 
+- Compact checked support lifecycle map in v0.1.98, giving maintainers a quick scan of report, triage, response, closeout, prioritization, backlog record, and backlog review.
 - 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.
@@ -88,7 +89,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.
+- Add a generated support lifecycle status summary if backlog review records grow beyond the compact map.
 - 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 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.
+When a report has enough public-safe detail to triage, start with the checked [support lifecycle map](../examples/support/support-lifecycle-map.md) for a quick scan of the path, or the full [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 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.
+- `examples/support` provides a compact checked support lifecycle map plus a full 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`.
 
@@ -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, record the closeout, prioritize follow-up work, create a public-safe backlog record, and review aging records for keep-or-close decisions.
+- `examples/support` shows maintainers how to scan the support lifecycle map, audit the full lifecycle overview, 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, create a public-safe backlog record, and review aging records for keep-or-close decisions.
 - `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, outcome prioritization guide, backlog records, backlog review checklist, 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 map, the support lifecycle overview, outcome prioritization guide, backlog records, backlog review checklist, 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.98.md

@@ -0,0 +1,45 @@
+# Memento Mori Jester v0.1.98
+
+## Summary
+
+This release adds a compact checked support lifecycle map so maintainers can scan the full public-safe support path without reading every support artifact first.
+
+## Changes
+
+- Added `examples/support/support-lifecycle-map.md` for the at-a-glance support chain:
+  `report -> triage -> response -> closeout -> prioritization -> backlog-record -> backlog-review`.
+- Added `examples/support/support-lifecycle-map.json` as the deterministic source for stage order, stage artifacts, outcome summaries, and privacy guardrails.
+- Extended `npm run support:check` and `npm run production:check` so the compact map stays aligned with the full lifecycle overview.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and changelog.
+
+## Public Interface Changes
+
+- No CLI, MCP, config schema, rule, scoring, GitHub Action, or release automation changes.
+- New package docs/examples only:
+  - `examples/support/support-lifecycle-map.md`
+  - `examples/support/support-lifecycle-map.json`
+
+## Release Validation
+
+```powershell
+npm.cmd test
+npm.cmd run demo:svg:check
+npm.cmd run promo:card:check
+npm.cmd run promo:check
+npm.cmd run support:check
+npm.cmd run production:check
+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.98 support lifecycle map"
+```
+
+## Post-Publish Smoke
+
+```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
+```

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: 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.
+Start with the compact checked [support lifecycle map](support-lifecycle-map.md) when you need a quick scan of the path: report, triage, response, closeout, prioritization, backlog record, and backlog review. Use the full checked [support lifecycle overview](support-lifecycle.md) when you need the outcome table in one place. The lifecycle sources are [support-lifecycle-map.json](support-lifecycle-map.json) and [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-map.json

@@ -0,0 +1,74 @@
+{
+  "title": "Support Lifecycle Map",
+  "flow": [
+    "report",
+    "triage",
+    "response",
+    "closeout",
+    "prioritization",
+    "backlog-record",
+    "backlog-review"
+  ],
+  "stages": [
+    {
+      "id": "report",
+      "artifact": "examples/reports/feedback-template.md",
+      "question": "Is the report redacted, minimal, and safe to discuss publicly?"
+    },
+    {
+      "id": "triage",
+      "artifact": "examples/support/triage-playbook.json",
+      "question": "Is this a docs example, fixture backlog item, or rule-review candidate?"
+    },
+    {
+      "id": "response",
+      "artifact": "examples/support/response-snippets.json",
+      "question": "Which public-safe reply should go back to the reporter?"
+    },
+    {
+      "id": "closeout",
+      "artifact": "examples/support/closeout-checklist.json",
+      "question": "Was the immediate support decision recorded with a safe next link?"
+    },
+    {
+      "id": "prioritization",
+      "artifact": "examples/support/outcome-prioritization.json",
+      "question": "Is the follow-up low-priority docs, medium-priority fixture work, or high-priority rule review?"
+    },
+    {
+      "id": "backlog-record",
+      "artifact": "examples/support/backlog-records.json",
+      "question": "Is there a sanitized backlog artifact with evidence and checks?"
+    },
+    {
+      "id": "backlog-review",
+      "artifact": "examples/support/backlog-review.json",
+      "question": "Does the item remain active, or should it close as closed-no-action?"
+    }
+  ],
+  "outcomes": [
+    {
+      "outcome": "docs-example",
+      "backlogRecord": "docs-clarification-backlog-record",
+      "reviewDecision": "remains-docs-clarification",
+      "fallbackReviewDecision": "closed-no-action"
+    },
+    {
+      "outcome": "fixture-backlog",
+      "backlogRecord": "fixture-backlog-record",
+      "reviewDecision": "remains-fixture-backlog",
+      "fallbackReviewDecision": "closed-no-action"
+    },
+    {
+      "outcome": "rule-review-candidate",
+      "backlogRecord": "rule-review-candidate-backlog-record",
+      "reviewDecision": "remains-rule-review-candidate",
+      "fallbackReviewDecision": "closed-no-action"
+    }
+  ],
+  "privacyGuardrail": "Route secrets, private code, private paths, customer data, full logs, unredacted SARIF, package publishing credentials, MCP data exposure, or exploitable security details through SECURITY.md instead of the public lifecycle.",
+  "requiredChecks": [
+    "npm run support:check",
+    "npm run production:check"
+  ]
+}

package/examples/support/support-lifecycle-map.md

@@ -0,0 +1,46 @@
+# Support Lifecycle Map
+
+This is the compact public-safe map for maintainers who need the whole support chain without reading every checklist first.
+
+The checked source is [support-lifecycle-map.json](support-lifecycle-map.json). Use the full [support lifecycle overview](support-lifecycle.md) when you need the outcome table and per-stage artifact references.
+
+```text
+report
+  -> triage
+  -> response
+  -> closeout
+  -> prioritization
+  -> backlog-record
+  -> backlog-review
+```
+
+## Stage Scan
+
+| Stage | Artifact | Maintainer question |
+| --- | --- | --- |
+| `report` | [feedback-template.md](../reports/feedback-template.md) | Is the report redacted, minimal, and safe to discuss publicly? |
+| `triage` | [triage-playbook.json](triage-playbook.json) | Is this a docs example, fixture backlog item, or rule-review candidate? |
+| `response` | [response-snippets.md](response-snippets.md) | Which public-safe reply should go back to the reporter? |
+| `closeout` | [closeout-checklist.md](closeout-checklist.md) | Was the immediate support decision recorded with a safe next link? |
+| `prioritization` | [outcome-prioritization.md](outcome-prioritization.md) | Is the follow-up low-priority docs, medium-priority fixture work, or high-priority rule review? |
+| `backlog-record` | [backlog-records.md](backlog-records.md) | Is there a sanitized backlog artifact with evidence and checks? |
+| `backlog-review` | [backlog-review.md](backlog-review.md) | Does the item remain active, or should it close as `closed-no-action`? |
+
+## Outcome Scan
+
+| Outcome | Backlog record | Review decision |
+| --- | --- | --- |
+| `docs-example` | `docs-clarification-backlog-record` | `remains-docs-clarification` or `closed-no-action` |
+| `fixture-backlog` | `fixture-backlog-record` | `remains-fixture-backlog` or `closed-no-action` |
+| `rule-review-candidate` | `rule-review-candidate-backlog-record` | `remains-rule-review-candidate` or `closed-no-action` |
+
+## Guardrail
+
+If the report includes secrets, private code, private paths, customer data, full logs, unredacted SARIF, package publishing credentials, MCP data exposure, or exploitable security details, stop using the public lifecycle and route through [SECURITY.md](../../SECURITY.md).
+
+Run after editing this map:
+
+```powershell
+npm run support:check
+npm run production:check
+```

package/examples/support/support-lifecycle.md

@@ -6,7 +6,7 @@ This index shows the public-safe support path at a glance:
 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), [closeout checklist](closeout-checklist.md), [outcome prioritization guide](outcome-prioritization.md), [backlog records](backlog-records.md), and [backlog review checklist](backlog-review.md).
+The compact map is [support-lifecycle-map.md](support-lifecycle-map.md), backed by [support-lifecycle-map.json](support-lifecycle-map.json). The checked source for the full outcome table 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
 

package/package.json

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

@@ -104,6 +104,8 @@ for (const path of [
   "examples/support/outcome-prioritization.json",
   "examples/support/response-snippets.md",
   "examples/support/response-snippets.json",
+  "examples/support/support-lifecycle-map.md",
+  "examples/support/support-lifecycle-map.json",
   "examples/support/support-lifecycle.md",
   "examples/support/support-lifecycle.json",
   "examples/support/triage-playbook.json",
@@ -138,6 +140,7 @@ requireText("README.md", /feedback-template\.md/, "report gallery feedback templ
 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-map\.md/, "support lifecycle map 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-review\.md/, "support backlog review link");
@@ -166,6 +169,7 @@ 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", /support lifecycle map/i, "support lifecycle map readiness");
 requireText("docs/PRODUCTION_READINESS.md", /outcome prioritization guide/i, "support outcome prioritization readiness");
 requireText("docs/PRODUCTION_READINESS.md", /backlog review/i, "support backlog review readiness");
 requireText("docs/PRODUCTION_READINESS.md", /backlog records/i, "support backlog records readiness");
@@ -195,6 +199,7 @@ requireText("docs/MAINTAINER_TRIAGE.md", /report_gallery_feedback\.yml/, "report
 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", /support-lifecycle-map\.md/, "support lifecycle map 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-review\.md/, "support backlog review link");
@@ -233,6 +238,8 @@ requireText("examples/reports/feedback-template.md", /SECURITY\.md/, "feedback t
 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", /support-lifecycle-map\.md/, "support lifecycle map link");
+requireText("examples/support/README.md", /support-lifecycle-map\.json/, "support lifecycle map JSON 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-review\.md/, "support backlog review link");
@@ -256,7 +263,19 @@ requireText("examples/support/closeout-checklist.md", /candidate-opened/, "suppo
 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/support/support-lifecycle-map.md", /Support Lifecycle Map/, "support lifecycle map heading");
+requireText("examples/support/support-lifecycle-map.md", /support-lifecycle-map\.json/, "support lifecycle map JSON link");
+requireText("examples/support/support-lifecycle-map.md", /report\s*\n\s*-> triage\s*\n\s*-> response\s*\n\s*-> closeout\s*\n\s*-> prioritization\s*\n\s*-> backlog-record\s*\n\s*-> backlog-review/, "support lifecycle map compact flow");
+requireText("examples/support/support-lifecycle-map.md", /docs-clarification-backlog-record/, "support lifecycle map docs backlog record");
+requireText("examples/support/support-lifecycle-map.md", /fixture-backlog-record/, "support lifecycle map fixture backlog record");
+requireText("examples/support/support-lifecycle-map.md", /rule-review-candidate-backlog-record/, "support lifecycle map rule-review backlog record");
+requireText("examples/support/support-lifecycle-map.md", /closed-no-action/, "support lifecycle map closed no-action decision");
+requireText("examples/support/support-lifecycle-map.md", /SECURITY\.md/, "support lifecycle map security redirect");
+requireText("examples/support/support-lifecycle-map.json", /Support Lifecycle Map/, "support lifecycle map JSON title");
+requireText("examples/support/support-lifecycle-map.json", /backlog-record/, "support lifecycle map backlog-record stage");
+requireText("examples/support/support-lifecycle-map.json", /backlog-review/, "support lifecycle map backlog-review stage");
 requireText("examples/support/support-lifecycle.md", /Support Lifecycle Overview/, "support lifecycle heading");
+requireText("examples/support/support-lifecycle.md", /support-lifecycle-map\.md/, "support lifecycle map link");
 requireText("examples/support/support-lifecycle.md", /support-lifecycle\.json/, "support lifecycle JSON link");
 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");
@@ -336,6 +355,7 @@ 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", /support-lifecycle-map\.json/, "support lifecycle map 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", /backlog-review\.json/, "support backlog review guard");

package/scripts/check-support-triage.mjs

@@ -36,6 +36,8 @@ const supportFiles = [
   "examples/support/README.md",
   "examples/support/response-snippets.md",
   "examples/support/response-snippets.json",
+  "examples/support/support-lifecycle-map.md",
+  "examples/support/support-lifecycle-map.json",
   "examples/support/support-lifecycle.md",
   "examples/support/support-lifecycle.json",
   "examples/support/triage-playbook.json",
@@ -90,7 +92,9 @@ requireText("examples/reports/README.md", /examples\/support|Maintainer Triage P
 requireText("examples/support/README.md", /Maintainer Triage Playbook/, "maintainer playbook heading");
 requireText("examples/support/README.md", /backlog-review\.md/, "support backlog review link");
 requireText("examples/support/README.md", /backlog-records\.md/, "support backlog records link");
+requireText("examples/support/README.md", /support-lifecycle-map\.md/, "support lifecycle map link");
 requireText("examples/support/README.md", /support-lifecycle\.md/, "support lifecycle overview link");
+requireText("examples/support/README.md", /support-lifecycle-map\.json/, "support lifecycle map JSON 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");
@@ -118,7 +122,22 @@ requireText("examples/support/closeout-checklist.md", /SECURITY\.md/, "closeout
 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/support-lifecycle-map.md", /Support Lifecycle Map/, "support lifecycle map heading");
+requireText("examples/support/support-lifecycle-map.md", /support-lifecycle-map\.json/, "support lifecycle map JSON link");
+requireText("examples/support/support-lifecycle-map.md", /report\s*\n\s*-> triage\s*\n\s*-> response\s*\n\s*-> closeout\s*\n\s*-> prioritization\s*\n\s*-> backlog-record\s*\n\s*-> backlog-review/, "support lifecycle compact flow");
+requireText("examples/support/support-lifecycle-map.md", /Maintainer question/, "support lifecycle map scan questions");
+requireText("examples/support/support-lifecycle-map.md", /docs-clarification-backlog-record/, "docs backlog map record");
+requireText("examples/support/support-lifecycle-map.md", /fixture-backlog-record/, "fixture backlog map record");
+requireText("examples/support/support-lifecycle-map.md", /rule-review-candidate-backlog-record/, "rule-review backlog map record");
+requireText("examples/support/support-lifecycle-map.md", /closed-no-action/, "closed no-action map review");
+requireText("examples/support/support-lifecycle-map.md", /SECURITY\.md/, "map security redirect");
+requireText("examples/support/support-lifecycle-map.md", /npm run support:check/, "support checker map command");
+requireText("examples/support/support-lifecycle-map.json", /Support Lifecycle Map/, "support lifecycle map JSON title");
+requireText("examples/support/support-lifecycle-map.json", /backlog-record/, "support lifecycle map backlog-record stage");
+requireText("examples/support/support-lifecycle-map.json", /backlog-review/, "support lifecycle map backlog-review stage");
+requireText("examples/support/support-lifecycle-map.json", /closed-no-action/, "support lifecycle map closed no-action fallback");
 requireText("examples/support/support-lifecycle.md", /Support Lifecycle Overview/, "support lifecycle heading");
+requireText("examples/support/support-lifecycle.md", /support-lifecycle-map\.md/, "support lifecycle map link");
 requireText("examples/support/support-lifecycle.md", /support-lifecycle\.json/, "support lifecycle JSON link");
 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");
@@ -200,6 +219,7 @@ requireText("examples/support/response-snippets.json", /rule-review-candidate-re
 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", /support-lifecycle-map\.md/, "support lifecycle map 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-review\.md/, "support backlog review triage link");
@@ -212,6 +232,7 @@ requireText("docs/MAINTAINER_TRIAGE.md", /rule-review-candidate/, "rule review t
 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", /support-lifecycle-map\.md/, "support lifecycle map 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-review\.md/, "support backlog review README link");
@@ -227,6 +248,7 @@ requireText("package.json", /npm run support:check/, "support checker in npm tes
 checkTriagePlaybook();
 checkResponseSnippets();
 checkCloseoutChecklist();
+checkSupportLifecycleMap();
 checkSupportLifecycle();
 checkOutcomePrioritization();
 checkBacklogRecords();
@@ -643,6 +665,106 @@ function checkSupportLifecycle() {
   }
 }
 
+function checkSupportLifecycleMap() {
+  const path = "examples/support/support-lifecycle-map.json";
+  const map = readJson(path);
+  if (!map) {
+    return;
+  }
+
+  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/outcome-prioritization.json",
+    "examples/support/backlog-records.json",
+    "examples/support/backlog-review.json"
+  ];
+  const expectedOutcomes = [
+    {
+      outcome: "docs-example",
+      backlogRecord: "docs-clarification-backlog-record",
+      reviewDecision: "remains-docs-clarification"
+    },
+    {
+      outcome: "fixture-backlog",
+      backlogRecord: "fixture-backlog-record",
+      reviewDecision: "remains-fixture-backlog"
+    },
+    {
+      outcome: "rule-review-candidate",
+      backlogRecord: "rule-review-candidate-backlog-record",
+      reviewDecision: "remains-rule-review-candidate"
+    }
+  ];
+
+  if (map.title !== "Support Lifecycle Map") {
+    failures.push(`${path}.title should be Support Lifecycle Map.`);
+  }
+
+  if (!Array.isArray(map.flow) || map.flow.join("|") !== expectedStageIds.join("|")) {
+    failures.push(`${path}.flow should contain the compact support lifecycle order.`);
+  }
+
+  if (!Array.isArray(map.stages) || map.stages.length !== expectedStageIds.length) {
+    failures.push(`${path}.stages should contain seven lifecycle stages.`);
+  } else {
+    for (const [index, stage] of map.stages.entries()) {
+      if (stage?.id !== expectedStageIds[index]) {
+        failures.push(`${path}.stages[${index}].id should be ${expectedStageIds[index]}.`);
+      }
+
+      if (stage?.artifact !== expectedArtifacts[index]) {
+        failures.push(`${path}.stages[${index}].artifact should be ${expectedArtifacts[index]}.`);
+      }
+
+      if (typeof stage?.question !== "string" || stage.question.length < 40) {
+        failures.push(`${path}.stages[${index}].question should be a useful maintainer scan question.`);
+      }
+    }
+  }
+
+  if (!Array.isArray(map.outcomes) || map.outcomes.length !== expectedOutcomes.length) {
+    failures.push(`${path}.outcomes should contain three lifecycle outcome summaries.`);
+  } else {
+    for (const [index, outcome] of map.outcomes.entries()) {
+      const expectedOutcome = expectedOutcomes[index];
+      if (outcome?.outcome !== expectedOutcome.outcome) {
+        failures.push(`${path}.outcomes[${index}].outcome should be ${expectedOutcome.outcome}.`);
+      }
+
+      if (outcome?.backlogRecord !== expectedOutcome.backlogRecord) {
+        failures.push(`${path}.outcomes[${index}].backlogRecord should be ${expectedOutcome.backlogRecord}.`);
+      }
+
+      if (outcome?.reviewDecision !== expectedOutcome.reviewDecision) {
+        failures.push(`${path}.outcomes[${index}].reviewDecision should be ${expectedOutcome.reviewDecision}.`);
+      }
+
+      if (outcome?.fallbackReviewDecision !== "closed-no-action") {
+        failures.push(`${path}.outcomes[${index}].fallbackReviewDecision should be closed-no-action.`);
+      }
+    }
+  }
+
+  if (typeof map.privacyGuardrail !== "string" || !/SECURITY\.md|secrets|private|customer data/i.test(map.privacyGuardrail)) {
+    failures.push(`${path}.privacyGuardrail should include public-safe support routing guidance.`);
+  }
+
+  const requiredChecks = ["npm run support:check", "npm run production:check"];
+  if (!Array.isArray(map.requiredChecks)) {
+    failures.push(`${path}.requiredChecks should be an array.`);
+  } else {
+    for (const check of requiredChecks) {
+      if (!map.requiredChecks.includes(check)) {
+        failures.push(`${path}.requiredChecks should include ${check}.`);
+      }
+    }
+  }
+}
+
 function checkOutcomePrioritization() {
   const path = "examples/support/outcome-prioritization.json";
   const priorities = readJson(path);