memento-mori-jester 0.1.99 → 0.1.100

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to Memento Mori Jester are tracked here.
 
 ## Unreleased
 
+## 0.1.100
+
+- Added a checked synthetic filled support lifecycle worksheet example showing one `docs-example` report through report, triage, response, closeout, prioritization, backlog record, and backlog review.
+- Added `support-lifecycle-filled-example.json` plus `npm run support:check` and production-readiness coverage so the completed example stays public-safe, deterministic, and aligned with the blank worksheet.
+- Updated README, maintainer triage docs, support examples, production-readiness docs, roadmap, and release notes for the filled worksheet example.
+
 ## 0.1.99
 
 - Added a checked public-safe support lifecycle worksheet for reviewing one report across 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 map](examples/support/support-lifecycle-map.md), [support lifecycle worksheet](examples/support/support-lifecycle-worksheet.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.
+Maintainers can use the checked [support lifecycle map](examples/support/support-lifecycle-map.md), [support lifecycle worksheet](examples/support/support-lifecycle-worksheet.md), synthetic [filled worksheet example](examples/support/support-lifecycle-filled-example.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:
 
@@ -452,6 +452,7 @@ More setup examples:
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
 - [Support Lifecycle Map](examples/support/support-lifecycle-map.md)
 - [Support Lifecycle Worksheet](examples/support/support-lifecycle-worksheet.md)
+- [Filled Support Lifecycle Worksheet Example](examples/support/support-lifecycle-filled-example.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)
@@ -482,6 +483,7 @@ Framework CI examples:
 - [Report Gallery Feedback Template](examples/reports/feedback-template.md)
 - [Support Lifecycle Map](examples/support/support-lifecycle-map.md)
 - [Support Lifecycle Worksheet](examples/support/support-lifecycle-worksheet.md)
+- [Filled Support Lifecycle Worksheet Example](examples/support/support-lifecycle-filled-example.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)
@@ -545,7 +547,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 map](examples/support/support-lifecycle-map.md), [support lifecycle worksheet](examples/support/support-lifecycle-worksheet.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 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 worksheet](examples/support/support-lifecycle-worksheet.md), [filled worksheet example](examples/support/support-lifecycle-filled-example.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
 
+- Checked filled support lifecycle worksheet example in v0.1.100, showing a synthetic `docs-example` report through report, triage, response, closeout, prioritization, backlog record, and backlog review.
 - Checked support lifecycle worksheet in v0.1.99, turning the compact map into an active-review checklist with stage checks, record fields, and stop conditions.
 - 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.
@@ -91,7 +92,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 generated support lifecycle status summary if backlog review records grow beyond the compact map.
-- Add a checked anonymized example of a completed lifecycle worksheet once support reports accumulate.
+- Add synthetic filled worksheet examples for `fixture-backlog` and `rule-review-candidate` if maintainers need more public-safe training cases.
 - 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 map](../examples/support/support-lifecycle-map.md) for a quick scan of the path, then use the checked [support lifecycle worksheet](../examples/support/support-lifecycle-worksheet.md) to record each stage during active review. Use 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.
+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, then use the checked [support lifecycle worksheet](../examples/support/support-lifecycle-worksheet.md) to record each stage during active review. Use the synthetic [filled lifecycle worksheet example](../examples/support/support-lifecycle-filled-example.md) when you need to compare a real public-safe report against one completed `docs-example` path. Use 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 compact checked support lifecycle map, an active-review worksheet, and 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.
+- `examples/support` provides a compact checked support lifecycle map, an active-review worksheet, a synthetic filled worksheet example, and 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 scan the support lifecycle map, use the support lifecycle worksheet during active review, 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.
+- `examples/support` shows maintainers how to scan the support lifecycle map, use the support lifecycle worksheet during active review, compare against a synthetic filled worksheet example, 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 map, support lifecycle worksheet, 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, support lifecycle worksheet, filled worksheet example, 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.100.md

@@ -0,0 +1,45 @@
+# Memento Mori Jester v0.1.100
+
+## Summary
+
+This release adds a checked synthetic filled support lifecycle worksheet example so maintainers can see one public-safe `docs-example` report move through the whole support chain.
+
+## Changes
+
+- Added `examples/support/support-lifecycle-filled-example.md` with a completed synthetic support case for:
+  `report -> triage -> response -> closeout -> prioritization -> backlog-record -> backlog-review`.
+- Added `examples/support/support-lifecycle-filled-example.json` as the deterministic source for the filled example fields, stage checks, privacy review notes, required checks, and synthetic guardrail.
+- Extended `npm run support:check` and `npm run production:check` so the filled example stays aligned with the support lifecycle worksheet, map, and 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-filled-example.md`
+  - `examples/support/support-lifecycle-filled-example.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.100 filled support lifecycle worksheet"
+```
+
+## 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 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 checked [support lifecycle worksheet](support-lifecycle-worksheet.md) during an active review so every stage has concrete checks and record fields. 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), [support-lifecycle-worksheet.json](support-lifecycle-worksheet.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.
+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 checked [support lifecycle worksheet](support-lifecycle-worksheet.md) during an active review so every stage has concrete checks and record fields, and compare against the synthetic [filled worksheet example](support-lifecycle-filled-example.md) when you need to see one completed `docs-example` path. 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), [support-lifecycle-worksheet.json](support-lifecycle-worksheet.json), [support-lifecycle-filled-example.json](support-lifecycle-filled-example.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-filled-example.json

@@ -0,0 +1,160 @@
+{
+  "title": "Filled Support Lifecycle Worksheet Example",
+  "sourceWorksheet": "examples/support/support-lifecycle-worksheet.json",
+  "synthetic": true,
+  "caseId": "synthetic-report-gallery-docs-example",
+  "outcome": "docs-example",
+  "flow": [
+    "report",
+    "triage",
+    "response",
+    "closeout",
+    "prioritization",
+    "backlog-record",
+    "backlog-review"
+  ],
+  "stages": [
+    {
+      "id": "report",
+      "artifact": "examples/reports/feedback-template.md",
+      "fields": {
+        "sourceIssue": "<public-issue-url>",
+        "packageVersion": "0.1.100",
+        "sanitizedSummary": "A reporter says the checked destructive-command-summary gallery item is useful but unclear about whether the block is expected.",
+        "safeToDiscussPublicly": true
+      },
+      "checks": [
+        "Confirmed the report references the checked destructive-command-summary gallery item instead of a private repository command.",
+        "Confirmed the report includes only a sanitized command summary and redacted doctor --json fragments.",
+        "Confirmed there are no secrets, private code, private paths, customer data, full logs, unredacted SARIF, or exploitable details."
+      ],
+      "privacyReview": [
+        "The issue link is a placeholder rather than a real user report.",
+        "The command is a public demo command already used in docs.",
+        "Security-sensitive details would be redirected to SECURITY.md."
+      ]
+    },
+    {
+      "id": "triage",
+      "artifact": "examples/support/triage-playbook.json",
+      "fields": {
+        "selectedOutcome": "docs-example",
+        "ruleIdOrReportId": "destructive-command-summary",
+        "whyOutcomeFits": "The block is expected behavior for destructive git history changes, but the report-gallery wording can be clearer."
+      },
+      "checks": [
+        "Reproduced the checked report-gallery summary with the published command shape.",
+        "Compared the output to the existing report-gallery expected fragments.",
+        "Chose docs-example because no rule behavior, fixture boundary, or scoring change is needed."
+      ],
+      "privacyReview": [
+        "The reproduction uses only the public demo command.",
+        "The triage note does not include private repository output.",
+        "No secret material or exploit detail is needed to classify the report."
+      ]
+    },
+    {
+      "id": "response",
+      "artifact": "examples/support/response-snippets.json",
+      "fields": {
+        "snippetId": "docs-example-response",
+        "nextCommand": "npx -y memento-mori-jester@latest summary --kind command \"git reset --hard\"",
+        "publicSafeFollowUpLink": "<docs-follow-up-url>"
+      },
+      "checks": [
+        "Used the checked docs-example response snippet rather than writing a one-off reply.",
+        "Asked only for redacted diagnostics if local output still differs from the gallery.",
+        "Gave the reporter one command to compare with the checked report."
+      ],
+      "privacyReview": [
+        "The response asks for redacted diagnostics only.",
+        "The follow-up link is a placeholder until a public docs issue or pull request exists.",
+        "Any credential exposure, private code, or command execution concern belongs in SECURITY.md."
+      ]
+    },
+    {
+      "id": "closeout",
+      "artifact": "examples/support/closeout-checklist.json",
+      "fields": {
+        "closeoutId": "docs-clarification-closeout",
+        "decisionStatus": "shipped-or-queued",
+        "followUpLinkPlaceholder": "<docs-pr-url-or-issue>"
+      },
+      "checks": [
+        "Recorded that the immediate support decision is a docs clarification.",
+        "Linked only a placeholder public follow-up artifact.",
+        "Kept rule behavior, matching, scoring, and CLI policy unchanged."
+      ],
+      "privacyReview": [
+        "The closeout can be explained using only public docs and report-gallery context.",
+        "No private code or user-specific terminal output is required.",
+        "Security-sensitive follow-up is explicitly out of scope for the public closeout."
+      ]
+    },
+    {
+      "id": "prioritization",
+      "artifact": "examples/support/outcome-prioritization.json",
+      "fields": {
+        "priority": "low",
+        "minimumEvidence": "Nearest checked report, observed output, and no rule behavior change.",
+        "notEnoughEvidenceGuardrail": "Do not open fixture or rule-review work from a docs-only confusion report."
+      },
+      "checks": [
+        "Used the outcome prioritization guide for the docs-example path.",
+        "Confirmed the minimum evidence threshold is met by the existing checked gallery item.",
+        "Confirmed there is enough public-safe evidence to queue a docs clarification."
+      ],
+      "privacyReview": [
+        "The priority does not depend on private reports.",
+        "The evidence is already public and synthetic.",
+        "No secrets, private paths, or full logs are needed."
+      ]
+    },
+    {
+      "id": "backlog-record",
+      "artifact": "examples/support/backlog-records.json",
+      "fields": {
+        "backlogRecordId": "docs-clarification-backlog-record",
+        "backlogType": "docs clarification",
+        "nextAction": "Update the report-gallery wording so the destructive command summary clearly says the block is expected and shows the next comparison command.",
+        "requiredChecks": ["npm run reports:check", "npm run support:check"]
+      },
+      "checks": [
+        "Created a public-safe backlog record from the closeout and prioritization decision.",
+        "Included a public title, public summary, next action, and required checks.",
+        "Verified the backlog item does not ask for rule behavior changes."
+      ],
+      "privacyReview": [
+        "The backlog item references only checked docs and placeholder links.",
+        "The public summary is redacted and synthetic.",
+        "Any real private report detail would be removed before publishing."
+      ]
+    },
+    {
+      "id": "backlog-review",
+      "artifact": "examples/support/backlog-review.json",
+      "fields": {
+        "reviewDecision": "remains-docs-clarification",
+        "reviewCadence": "next monthly support review",
+        "nextAction": "Keep the docs clarification open until the gallery wording or docs example lands.",
+        "checksRun": ["npm run reports:check", "npm run support:check"]
+      },
+      "checks": [
+        "Revisited whether the item still belongs in the docs clarification lane.",
+        "Confirmed the report has not become a fixture backlog or rule-review candidate.",
+        "Confirmed the current public checks still pass before keeping it active."
+      ],
+      "privacyReview": [
+        "The review does not include private user names, repositories, paths, or logs.",
+        "The review can close as closed-no-action later if evidence becomes stale or duplicated.",
+        "Security-sensitive evidence would be removed from the public lifecycle and routed through SECURITY.md."
+      ]
+    }
+  ],
+  "requiredChecks": [
+    "npm run reports:check",
+    "npm run support:check",
+    "npm run production:check"
+  ],
+  "privacyGuardrail": "This filled worksheet is synthetic. Do not add secrets, private code, private paths, customer data, full logs, unredacted SARIF, package publishing credentials, MCP data exposure, or exploitable security details; route those through SECURITY.md."
+}

package/examples/support/support-lifecycle-filled-example.md

@@ -0,0 +1,146 @@
+# Filled Support Lifecycle Worksheet Example
+
+This is a synthetic, public-safe example of one completed support lifecycle worksheet. It demonstrates how a report-gallery surprise can move through report, triage, response, closeout, prioritization, backlog record, and backlog review without exposing user data, private repository paths, secrets, or full logs.
+
+The checked source is [support-lifecycle-filled-example.json](support-lifecycle-filled-example.json). Use it with the blank [support lifecycle worksheet](support-lifecycle-worksheet.md), compact [support lifecycle map](support-lifecycle-map.md), and full [support lifecycle overview](support-lifecycle.md).
+
+Case ID: `synthetic-report-gallery-docs-example`
+
+Selected outcome: `docs-example`
+
+## Report
+
+- Source issue: `<public-issue-url>`
+- Package version: `0.1.100`
+- Sanitized summary: A reporter says the checked report-gallery example for `summary --kind command "git reset --hard"` is useful, but they cannot tell whether the block is expected or whether their local setup is misconfigured.
+- Safe to discuss publicly: `true`
+
+Checks completed:
+
+- Confirmed the report references the checked `destructive-command-summary` gallery item instead of a private repository command.
+- Confirmed the report includes only a sanitized command summary and redacted `doctor --json` fragments.
+- Confirmed there are no secrets, private code, private paths, customer data, full logs, unredacted SARIF, or exploitable details.
+
+Privacy review:
+
+- The issue link is a placeholder, not a real user report.
+- The command is a public demo command already used in docs.
+- Security-sensitive details would be redirected to [SECURITY.md](../../SECURITY.md).
+
+## Triage
+
+- Selected outcome: `docs-example`
+- Rule id or report id: `destructive-command-summary`
+- Why the outcome fits: The block is expected behavior for destructive git history changes, but the report-gallery wording can be clearer about why the example is intentionally blocked.
+
+Checks completed:
+
+- Reproduced the checked report-gallery summary with the published command shape.
+- Compared the output to the existing report-gallery expected fragments.
+- Chose `docs-example` because no rule behavior, fixture boundary, or scoring change is needed.
+
+Privacy review:
+
+- The reproduction uses only the public demo command.
+- The triage note does not include private repository output.
+- No secret material or exploit detail is needed to classify the report.
+
+## Response
+
+- Snippet id: `docs-example-response`
+- Next command: `npx -y memento-mori-jester@latest summary --kind command "git reset --hard"`
+- Public-safe follow-up link: `<docs-follow-up-url>`
+
+Checks completed:
+
+- Used the checked docs-example response snippet rather than writing a one-off reply.
+- Asked only for redacted diagnostics if local output still differs from the gallery.
+- Gave the reporter one command to compare with the checked report.
+
+Privacy review:
+
+- The response asks for redacted diagnostics only.
+- The follow-up link is a placeholder until a public docs issue or pull request exists.
+- Any credential exposure, private code, or command execution concern belongs in [SECURITY.md](../../SECURITY.md).
+
+## Closeout
+
+- Closeout id: `docs-clarification-closeout`
+- Decision status: `shipped-or-queued`
+- Follow-up link placeholder: `<docs-pr-url-or-issue>`
+
+Checks completed:
+
+- Recorded that the immediate support decision is a docs clarification.
+- Linked only a placeholder public follow-up artifact.
+- Kept rule behavior, matching, scoring, and CLI policy unchanged.
+
+Privacy review:
+
+- The closeout can be explained using only public docs and report-gallery context.
+- No private code or user-specific terminal output is required.
+- Security-sensitive follow-up is explicitly out of scope for the public closeout.
+
+## Prioritization
+
+- Priority: `low`
+- Minimum evidence: Nearest checked report, observed output, and no rule behavior change.
+- Not enough evidence guardrail: Do not open fixture or rule-review work from a docs-only confusion report.
+
+Checks completed:
+
+- Used the outcome prioritization guide for the `docs-example` path.
+- Confirmed the minimum evidence threshold is met by the existing checked gallery item.
+- Confirmed there is enough public-safe evidence to queue a docs clarification.
+
+Privacy review:
+
+- The priority does not depend on private reports.
+- The evidence is already public and synthetic.
+- No secrets, private paths, or full logs are needed.
+
+## Backlog Record
+
+- Backlog record id: `docs-clarification-backlog-record`
+- Backlog type: `docs clarification`
+- Next action: Update the report-gallery wording so the destructive command summary clearly says the block is expected and shows the next comparison command.
+- Required checks: `npm run reports:check`, `npm run support:check`
+
+Checks completed:
+
+- Created a public-safe backlog record from the closeout and prioritization decision.
+- Included a public title, public summary, next action, and required checks.
+- Verified the backlog item does not ask for rule behavior changes.
+
+Privacy review:
+
+- The backlog item references only checked docs and placeholder links.
+- The public summary is redacted and synthetic.
+- Any real private report detail would be removed before publishing.
+
+## Backlog Review
+
+- Review decision: `remains-docs-clarification`
+- Review cadence: next monthly support review
+- Next action: Keep the docs clarification open until the gallery wording or docs example lands.
+- Checks run: `npm run reports:check`, `npm run support:check`
+
+Checks completed:
+
+- Revisited whether the item still belongs in the docs clarification lane.
+- Confirmed the report has not become a fixture backlog or rule-review candidate.
+- Confirmed the current public checks still pass before keeping it active.
+
+Privacy review:
+
+- The review does not include private user names, repositories, paths, or logs.
+- The review can close as `closed-no-action` later if evidence becomes stale or duplicated.
+- Security-sensitive evidence would be removed from the public lifecycle and routed through [SECURITY.md](../../SECURITY.md).
+
+## Required Checks
+
+```powershell
+npm run reports:check
+npm run support:check
+npm run production:check
+```

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

@@ -2,7 +2,7 @@
 
 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 [support lifecycle worksheet](support-lifecycle-worksheet.md) during an active review, and use the full [support lifecycle overview](support-lifecycle.md) when you need the outcome table and per-stage artifact references.
+The checked source is [support-lifecycle-map.json](support-lifecycle-map.json). Use the [support lifecycle worksheet](support-lifecycle-worksheet.md) during an active review, compare against the synthetic [filled worksheet example](support-lifecycle-filled-example.md), and use the full [support lifecycle overview](support-lifecycle.md) when you need the outcome table and per-stage artifact references.
 
 ```text
 report

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

@@ -2,7 +2,7 @@
 
 Use this public-safe worksheet while reviewing one support report. It turns the [support lifecycle map](support-lifecycle-map.md) into a stage-by-stage checklist.
 
-The checked source is [support-lifecycle-worksheet.json](support-lifecycle-worksheet.json). Use [support-lifecycle.md](support-lifecycle.md) for the outcome table after the worksheet identifies the right path.
+The checked source is [support-lifecycle-worksheet.json](support-lifecycle-worksheet.json). Use [support-lifecycle-filled-example.md](support-lifecycle-filled-example.md) for a synthetic completed example, and use [support-lifecycle.md](support-lifecycle.md) for the outcome table after the worksheet identifies the right path.
 
 ## Report
 

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 compact map is [support-lifecycle-map.md](support-lifecycle-map.md), backed by [support-lifecycle-map.json](support-lifecycle-map.json). The active review worksheet is [support-lifecycle-worksheet.md](support-lifecycle-worksheet.md), backed by [support-lifecycle-worksheet.json](support-lifecycle-worksheet.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).
+The compact map is [support-lifecycle-map.md](support-lifecycle-map.md), backed by [support-lifecycle-map.json](support-lifecycle-map.json). The active review worksheet is [support-lifecycle-worksheet.md](support-lifecycle-worksheet.md), backed by [support-lifecycle-worksheet.json](support-lifecycle-worksheet.json), with a synthetic completed example in [support-lifecycle-filled-example.md](support-lifecycle-filled-example.md) and [support-lifecycle-filled-example.json](support-lifecycle-filled-example.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.99",
+  "version": "0.1.100",
   "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

@@ -108,6 +108,8 @@ for (const path of [
   "examples/support/support-lifecycle-map.json",
   "examples/support/support-lifecycle-worksheet.md",
   "examples/support/support-lifecycle-worksheet.json",
+  "examples/support/support-lifecycle-filled-example.md",
+  "examples/support/support-lifecycle-filled-example.json",
   "examples/support/support-lifecycle.md",
   "examples/support/support-lifecycle.json",
   "examples/support/triage-playbook.json",
@@ -144,6 +146,7 @@ requireText("README.md", /response-snippets\.md/, "support response snippets lin
 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-worksheet\.md/, "support lifecycle worksheet link");
+requireText("README.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -174,6 +177,7 @@ requireText("docs/PRODUCTION_READINESS.md", /closeout checklist/i, "support clos
 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", /support lifecycle worksheet/i, "support lifecycle worksheet readiness");
+requireText("docs/PRODUCTION_READINESS.md", /filled worksheet example/i, "filled lifecycle worksheet example 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");
@@ -205,6 +209,7 @@ requireText("docs/MAINTAINER_TRIAGE.md", /response-snippets\.md/, "support respo
 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-worksheet\.md/, "support lifecycle worksheet link");
+requireText("docs/MAINTAINER_TRIAGE.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -247,6 +252,8 @@ requireText("examples/support/README.md", /support-lifecycle-map\.md/, "support
 requireText("examples/support/README.md", /support-lifecycle-map\.json/, "support lifecycle map JSON link");
 requireText("examples/support/README.md", /support-lifecycle-worksheet\.md/, "support lifecycle worksheet link");
 requireText("examples/support/README.md", /support-lifecycle-worksheet\.json/, "support lifecycle worksheet JSON link");
+requireText("examples/support/README.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example link");
+requireText("examples/support/README.md", /support-lifecycle-filled-example\.json/, "filled lifecycle worksheet example 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");
@@ -273,6 +280,7 @@ requireText("examples/support/closeout-checklist.json", /rule-review-closeout/,
 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", /support-lifecycle-worksheet\.md/, "support lifecycle worksheet link");
+requireText("examples/support/support-lifecycle-map.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -284,6 +292,7 @@ requireText("examples/support/support-lifecycle-map.json", /backlog-record/, "su
 requireText("examples/support/support-lifecycle-map.json", /backlog-review/, "support lifecycle map backlog-review stage");
 requireText("examples/support/support-lifecycle-worksheet.md", /Support Lifecycle Worksheet/, "support lifecycle worksheet heading");
 requireText("examples/support/support-lifecycle-worksheet.md", /support-lifecycle-worksheet\.json/, "support lifecycle worksheet JSON link");
+requireText("examples/support/support-lifecycle-worksheet.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example link");
 requireText("examples/support/support-lifecycle-worksheet.md", /support lifecycle map/, "support lifecycle worksheet map link");
 requireText("examples/support/support-lifecycle-worksheet.md", /## Report/, "support lifecycle worksheet report stage");
 requireText("examples/support/support-lifecycle-worksheet.md", /## Backlog Review/, "support lifecycle worksheet backlog review stage");
@@ -292,9 +301,20 @@ requireText("examples/support/support-lifecycle-worksheet.md", /SECURITY\.md/, "
 requireText("examples/support/support-lifecycle-worksheet.json", /Support Lifecycle Worksheet/, "support lifecycle worksheet JSON title");
 requireText("examples/support/support-lifecycle-worksheet.json", /support-lifecycle-map\.json/, "support lifecycle worksheet source map");
 requireText("examples/support/support-lifecycle-worksheet.json", /closed-no-action/, "support lifecycle worksheet closed no-action outcome");
+requireText("examples/support/support-lifecycle-filled-example.md", /Filled Support Lifecycle Worksheet Example/, "filled lifecycle worksheet example heading");
+requireText("examples/support/support-lifecycle-filled-example.md", /support-lifecycle-filled-example\.json/, "filled lifecycle worksheet example JSON link");
+requireText("examples/support/support-lifecycle-filled-example.md", /synthetic-report-gallery-docs-example/, "filled lifecycle worksheet example synthetic case");
+requireText("examples/support/support-lifecycle-filled-example.md", /docs-clarification-backlog-record/, "filled lifecycle worksheet docs backlog record");
+requireText("examples/support/support-lifecycle-filled-example.md", /remains-docs-clarification/, "filled lifecycle worksheet docs review decision");
+requireText("examples/support/support-lifecycle-filled-example.md", /SECURITY\.md/, "filled lifecycle worksheet security redirect");
+requireText("examples/support/support-lifecycle-filled-example.json", /Filled Support Lifecycle Worksheet Example/, "filled lifecycle worksheet example JSON title");
+requireText("examples/support/support-lifecycle-filled-example.json", /support-lifecycle-worksheet\.json/, "filled lifecycle worksheet source worksheet");
+requireText("examples/support/support-lifecycle-filled-example.json", /synthetic-report-gallery-docs-example/, "filled lifecycle worksheet synthetic case");
+requireText("examples/support/support-lifecycle-filled-example.json", /npm run production:check/, "filled lifecycle worksheet production check");
 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-worksheet\.md/, "support lifecycle worksheet link");
+requireText("examples/support/support-lifecycle.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -376,6 +396,7 @@ requireText("scripts/check-support-triage.mjs", /closeout-checklist\.json/, "sup
 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", /support-lifecycle-worksheet\.json/, "support lifecycle worksheet guard");
+requireText("scripts/check-support-triage.mjs", /support-lifecycle-filled-example\.json/, "filled lifecycle worksheet example 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

@@ -40,6 +40,8 @@ const supportFiles = [
   "examples/support/support-lifecycle-map.json",
   "examples/support/support-lifecycle-worksheet.md",
   "examples/support/support-lifecycle-worksheet.json",
+  "examples/support/support-lifecycle-filled-example.md",
+  "examples/support/support-lifecycle-filled-example.json",
   "examples/support/support-lifecycle.md",
   "examples/support/support-lifecycle.json",
   "examples/support/triage-playbook.json",
@@ -96,9 +98,11 @@ requireText("examples/support/README.md", /backlog-review\.md/, "support backlog
 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-worksheet\.md/, "support lifecycle worksheet link");
+requireText("examples/support/README.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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", /support-lifecycle-worksheet\.json/, "support lifecycle worksheet JSON link");
+requireText("examples/support/README.md", /support-lifecycle-filled-example\.json/, "filled lifecycle worksheet example 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");
@@ -129,6 +133,7 @@ requireText("examples/support/closeout-checklist.json", /rule-review-closeout/,
 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", /support-lifecycle-worksheet\.md/, "support lifecycle worksheet link");
+requireText("examples/support/support-lifecycle-map.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -143,6 +148,7 @@ requireText("examples/support/support-lifecycle-map.json", /backlog-review/, "su
 requireText("examples/support/support-lifecycle-map.json", /closed-no-action/, "support lifecycle map closed no-action fallback");
 requireText("examples/support/support-lifecycle-worksheet.md", /Support Lifecycle Worksheet/, "support lifecycle worksheet heading");
 requireText("examples/support/support-lifecycle-worksheet.md", /support-lifecycle-worksheet\.json/, "support lifecycle worksheet JSON link");
+requireText("examples/support/support-lifecycle-worksheet.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example link");
 requireText("examples/support/support-lifecycle-worksheet.md", /support lifecycle map/, "support lifecycle worksheet map link");
 requireText("examples/support/support-lifecycle-worksheet.md", /## Report/, "worksheet report stage");
 requireText("examples/support/support-lifecycle-worksheet.md", /## Triage/, "worksheet triage stage");
@@ -159,10 +165,32 @@ requireText("examples/support/support-lifecycle-worksheet.json", /Support Lifecy
 requireText("examples/support/support-lifecycle-worksheet.json", /support-lifecycle-map\.json/, "worksheet source map");
 requireText("examples/support/support-lifecycle-worksheet.json", /docs-example/, "worksheet docs outcome");
 requireText("examples/support/support-lifecycle-worksheet.json", /closed-no-action/, "worksheet closed no-action outcome");
+requireText("examples/support/support-lifecycle-filled-example.md", /Filled Support Lifecycle Worksheet Example/, "filled lifecycle worksheet heading");
+requireText("examples/support/support-lifecycle-filled-example.md", /support-lifecycle-filled-example\.json/, "filled lifecycle worksheet JSON link");
+requireText("examples/support/support-lifecycle-filled-example.md", /support-lifecycle-worksheet\.md/, "source worksheet link");
+requireText("examples/support/support-lifecycle-filled-example.md", /synthetic-report-gallery-docs-example/, "synthetic filled worksheet case id");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Report/, "filled worksheet report stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Triage/, "filled worksheet triage stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Response/, "filled worksheet response stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Closeout/, "filled worksheet closeout stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Prioritization/, "filled worksheet prioritization stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Backlog Record/, "filled worksheet backlog record stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /## Backlog Review/, "filled worksheet backlog review stage");
+requireText("examples/support/support-lifecycle-filled-example.md", /docs-clarification-backlog-record/, "filled worksheet docs backlog record");
+requireText("examples/support/support-lifecycle-filled-example.md", /remains-docs-clarification/, "filled worksheet docs review decision");
+requireText("examples/support/support-lifecycle-filled-example.md", /npm run support:check/, "filled worksheet support check");
+requireText("examples/support/support-lifecycle-filled-example.md", /SECURITY\.md/, "filled worksheet security redirect");
+requireText("examples/support/support-lifecycle-filled-example.json", /Filled Support Lifecycle Worksheet Example/, "filled lifecycle worksheet JSON title");
+requireText("examples/support/support-lifecycle-filled-example.json", /support-lifecycle-worksheet\.json/, "filled worksheet source worksheet");
+requireText("examples/support/support-lifecycle-filled-example.json", /synthetic-report-gallery-docs-example/, "filled worksheet synthetic case id");
+requireText("examples/support/support-lifecycle-filled-example.json", /docs-example/, "filled worksheet docs outcome");
+requireText("examples/support/support-lifecycle-filled-example.json", /remains-docs-clarification/, "filled worksheet review decision");
 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-worksheet\.md/, "support lifecycle worksheet link");
 requireText("examples/support/support-lifecycle.md", /support-lifecycle-worksheet\.json/, "support lifecycle worksheet JSON link");
+requireText("examples/support/support-lifecycle.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example link");
+requireText("examples/support/support-lifecycle.md", /support-lifecycle-filled-example\.json/, "filled lifecycle worksheet example JSON 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");
@@ -246,6 +274,7 @@ requireText("docs/MAINTAINER_TRIAGE.md", /report_gallery_feedback\.yml/, "report
 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-worksheet\.md/, "support lifecycle worksheet triage link");
+requireText("docs/MAINTAINER_TRIAGE.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -260,6 +289,7 @@ requireText("docs/PRODUCTION_READINESS.md", /support:check/, "support checker re
 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-worksheet\.md/, "support lifecycle worksheet README link");
+requireText("README.md", /support-lifecycle-filled-example\.md/, "filled lifecycle worksheet example 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");
@@ -276,6 +306,7 @@ checkTriagePlaybook();
 checkResponseSnippets();
 checkCloseoutChecklist();
 checkSupportLifecycleWorksheet();
+checkSupportLifecycleFilledExample();
 checkSupportLifecycleMap();
 checkSupportLifecycle();
 checkOutcomePrioritization();
@@ -876,6 +907,101 @@ function checkSupportLifecycleWorksheet() {
   }
 }
 
+function checkSupportLifecycleFilledExample() {
+  const path = "examples/support/support-lifecycle-filled-example.json";
+  const example = readJson(path);
+  if (!example) {
+    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 requiredChecks = ["npm run reports:check", "npm run support:check", "npm run production:check"];
+
+  if (example.title !== "Filled Support Lifecycle Worksheet Example") {
+    failures.push(`${path}.title should be Filled Support Lifecycle Worksheet Example.`);
+  }
+
+  if (example.sourceWorksheet !== "examples/support/support-lifecycle-worksheet.json") {
+    failures.push(`${path}.sourceWorksheet should point at examples/support/support-lifecycle-worksheet.json.`);
+  }
+
+  if (example.synthetic !== true) {
+    failures.push(`${path}.synthetic should be true.`);
+  }
+
+  if (example.caseId !== "synthetic-report-gallery-docs-example") {
+    failures.push(`${path}.caseId should be synthetic-report-gallery-docs-example.`);
+  }
+
+  if (example.outcome !== "docs-example") {
+    failures.push(`${path}.outcome should be docs-example.`);
+  }
+
+  if (!Array.isArray(example.flow) || example.flow.join("|") !== expectedStageIds.join("|")) {
+    failures.push(`${path}.flow should contain the support lifecycle order.`);
+  }
+
+  if (!Array.isArray(example.stages) || example.stages.length !== expectedStageIds.length) {
+    failures.push(`${path}.stages should contain seven completed lifecycle stages.`);
+  } else {
+    for (const [index, stage] of example.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 (!stage?.fields || typeof stage.fields !== "object" || Array.isArray(stage.fields) || Object.keys(stage.fields).length < 3) {
+        failures.push(`${path}.stages[${index}].fields should record at least three completed fields.`);
+      }
+
+      if (!Array.isArray(stage?.checks) || stage.checks.length !== 3) {
+        failures.push(`${path}.stages[${index}].checks should contain exactly three completed checks.`);
+      } else {
+        for (const [itemIndex, item] of stage.checks.entries()) {
+          if (typeof item !== "string" || item.length < 35) {
+            failures.push(`${path}.stages[${index}].checks[${itemIndex}] should be a useful completed check.`);
+          }
+        }
+      }
+
+      if (!Array.isArray(stage?.privacyReview) || stage.privacyReview.length !== 3) {
+        failures.push(`${path}.stages[${index}].privacyReview should contain exactly three privacy review notes.`);
+      } else {
+        const privacyText = stage.privacyReview.join("\n");
+        if (!/synthetic|placeholder|redacted|private|secret|SECURITY\.md|public/i.test(privacyText)) {
+          failures.push(`${path}.stages[${index}].privacyReview should include public-safe or security routing guidance.`);
+        }
+      }
+    }
+  }
+
+  if (!Array.isArray(example.requiredChecks)) {
+    failures.push(`${path}.requiredChecks should be an array.`);
+  } else {
+    for (const check of requiredChecks) {
+      if (!example.requiredChecks.includes(check)) {
+        failures.push(`${path}.requiredChecks should include ${check}.`);
+      }
+    }
+  }
+
+  if (typeof example.privacyGuardrail !== "string" || !/synthetic|secrets|private|customer data|SECURITY\.md|exploitable/i.test(example.privacyGuardrail)) {
+    failures.push(`${path}.privacyGuardrail should include synthetic, public-safe support guidance.`);
+  }
+}
+
 function checkOutcomePrioritization() {
   const path = "examples/support/outcome-prioritization.json";
   const priorities = readJson(path);