[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EHARK33CZCDG4ANE09NDAM":3,"skill-same:01M7EHARK33CZCDG4ANE09NDAM":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7EHARK33CZCDG4ANE09NDAM","verify-demistify",null,"Use when checking a declared Demistify built runtime or Markdown CLI, including choices\u002Fcomments, navigation, Markdown\u002Fdiagrams or small-parts behavior, or maintaining this project's verification recipe. Not for product repairs or delivery acceptance.","ShravanSunder\u002Fsunstack-tools","ShravanSunder","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5294949?v=4","01M7EHAJQY0H013BR4QAEVHEJF","Shravan Sunder","01M7EHAJRFJNY38NQBBVDDH999",0,"MIT","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: verify-demistify\ndescription: Use when checking a declared Demistify built runtime or Markdown CLI, including choices\u002Fcomments, navigation, Markdown\u002Fdiagrams or small-parts behavior, or maintaining this project's verification recipe. Not for product repairs or delivery acceptance.\n---\n\n# Verify Demistify\n\nVerify `packages\u002Fdemistify` through its plain-HTML consumer, `apps\u002Fdemistify-poc`. Keep the real built library, Markdown files, native custom elements, diagram renderer and browser layout in the path. CLI checking and embedding prove different claims from browser behavior.\n\n**Operable for the existing focused headless browser and CLI routes below.** The choices\u002Fcomments journey remains a draft wherever its declared-target observations are incomplete; distinguish applicable feature\u002Fboundary assertions, component integration and native host observations. Broader journey variants remain explicitly unobserved. Record the actual target and coverage in the task's evidence\u002Ftrace; a working recipe is not product acceptance or proof of cold-runner skill application.\n\n## Target and contract\n\nRead the [owner task list](..\u002F..\u002F..\u002Fdocs\u002Fwip\u002Fdemystify\u002F2026-10-16-fixes-todo.md), [project instructions](..\u002F..\u002F..\u002FAGENTS.md) and [handoff](..\u002F..\u002F..\u002Fdocs\u002Fwip\u002Fdemystify\u002F2026-10-14-demistify-handoff.md). Their outcomes and the current commission are the oracle. Sidebar\u002Fsource inspection retains rendered main content. Fullscreen may temporarily move live content, but Close\u002FEscape must restore the same nodes and state.\n\nRecord the declared commit, permitted dirty-state exceptions, build location\u002Freceipt, fixture URL, browser\u002Fclient, viewport and process\u002Fbrowser ownership. Compare `git status --short`, `git branch --show-current` and `git rev-parse HEAD` with that declaration. Moving source supports preparation, not delivery observation. Stop affected observations if the target changes.\n\nPublic-safe fixtures need no account\u002Fbackend. Existing dependencies are a prerequisite; this recipe grants no installation, browser control or execution beyond the current commission.\n\nThe small-parts and fresh-Luna journeys below describe native coverage for the adopted 22 October 2026 small-parts contract (U1–U4\u002FR1–R7). Require its exact source revisions, matching candidate guidance and frozen complete build from the commission. The permanent small-parts fixture and browser test exist in the repository. Their automated assertions and the native fixture, literal-example and fresh-author observations need their own target-bound evidence.\n\n## Frozen built-library launch and health\n\nFrom the monorepo root, with Node 26+, pnpm 12 and the installed Chromium matching the checkout's Playwright dependency, run the existing repository harness after execution is authorized:\n\n```sh\npnpm test:browser\n```\n\nFor an explicitly scoped compact-headings correction, run only its permanent case:\n\n```sh\npnpm --filter @sunstack\u002Fdemistify-poc exec vitest run --config vitest.browser.config.ts tests\u002Fbrowser\u002Fdocument.browser.test.ts -t 'compact headings menu'\n```\n\nReport selected tests separately from name-filtered skips and uncollected files. A focused pass is not a full-suite pass.\n\nThe root\u002Fpackage scripts route this to `vitest run --config vitest.browser.config.ts`. The existing Vitest Playwright provider launches isolated headless Chromium; no desktop tab is used. With no `PLAYWRIGHT_BROWSERS_PATH` override, use the matching installed default executable. Before launch, resolve its path through the PoC's installed dependency and confirm it exists:\n\n```sh\nnode --input-type=module -e 'import {createRequire} from \"node:module\"; import {resolve} from \"node:path\"; import {existsSync} from \"node:fs\"; const requireFromPoc=createRequire(resolve(\"apps\u002Fdemistify-poc\u002Fpackage.json\")); const executable=requireFromPoc(\"playwright\").chromium.executablePath(); const exists=existsSync(executable); console.log(JSON.stringify({executable,exists,browserPathOverride:process.env.PLAYWRIGHT_BROWSERS_PATH??null},null,2)); process.exitCode=exists?0:1;'\n```\n\nRetain the actual executable\u002Foverride receipt. An explicit cache is valid only when selected by the commission and this same check confirms its executable exists; preserve that override for the run. A missing executable is a setup gap: never install, change caches or fall back silently. Its Vite plugin (`tests\u002Fbrowser\u002Fbuilt-fixtures.ts`) snapshots the complete `packages\u002Fdemistify\u002Fdist`, the authored fixtures and the built consumer page `apps\u002Fdemistify-poc\u002Fdist\u002Fexperiments\u002Fhtml-islands-content-surfaces-live.html`, rewrites that page's asset links to the snapshot library, then serves those bytes from a fresh loopback port. The declared target therefore needs both outputs of one root `pnpm build` from the same source: a library-only build fails the whole suite at startup, and a stale PoC build silently serves an older page. Record that page's SHA-256 beside the library hashes. `DEMISTIFY_BROWSER_ASSETS` optionally selects a declared complete library copy and replaces library bytes only; the consumer page still comes from `apps\u002Fdemistify-poc\u002Fdist`. Record any override. Installations require a separate grant. See the [harness README](..\u002F..\u002F..\u002Fapps\u002Fdemistify-poc\u002Ftests\u002Fbrowser\u002FREADME.md) for harness behavior; its installation example grants no install and does not select this run's cache.\n\nKeep stdout\u002Fstderr, exit code, printed snapshot directory and API URL. Compare the snapshot's library hashes with the declared library, and the built page's hash with the declared build. Vite writes generated config\u002Fcache files under `node_modules\u002F.vite-temp`; if sandbox permissions prevent launch, preserve that startup failure and request the exact access for the same command. It is not a product test failure. Never rebuild a frozen target.\n\n**Readiness\u002Fhealth:** `openFixture` polls for the real document, upgraded navigation controls and stylesheet, then awaits fonts. Each behavior test waits for its actual heading\u002Ftable\u002FSVG or inspection result. These checks, together with snapshot identity, establish a usable real target; a listening port alone does not. Preserve failed assertions and request\u002Fbrowser errors emitted by the suite. Successful tests do not establish a comprehensive console\u002Fnetwork audit.\n\nFor separately authorized PoC preview work, root `pnpm build` refreshes the library and copied static host; `pnpm --filter @sunstack\u002Fdemistify-poc preview --port 4174` serves it on loopback. This is a distinct delivery path from the harness snapshot. The owner desktop surface needs its own release. Do not run these commands during a source\u002Fbuild freeze.\n\n## Drive and reuse\n\nInspect the finished browser configuration and assertions before reuse. The separate `apps\u002Fdemistify-poc\u002Fvitest.config.ts` uses Node; the package `test` command is not browser evidence. The Implementer owns product tests. Report the current selected browser cases from the actual run and read their assertion limits at source; historical case counts in a journey are not the current suite inventory.\n\nFor direct UI observation, use host computer-use\u002FChrome on one released surface with sole control. Use ordinary links, tabs, buttons, wheel and pointer input. Read-only DOM geometry corroborates visible outcomes. Internal setters, synthetic events and mocked rendering\u002Ffetch do not establish user interaction. An adopted component-integration case may call an existing action to decide its lifecycle boundary; label that result separately from native input, as the choices\u002Fcomments reference requires for controls behind a phone modal. Do not introduce a separate Playwright driver.\n\nInspect a passing journey's target, fixtures, interactions, assertions and result before reuse. Reuse applicable evidence. Add direct observation for a missing interaction, changed dependency or specific unresolved doubt; independence does not require repeating equivalent proof.\n\n## Journeys\n\nRead [journey instructions and source map](references\u002Fjourneys.md) for the selected scope.\n\nIF the claim includes choices or comments, load `references\u002Fchoices-comments.md` and return the declared target, selected O1\u002FO2 cases, deciding observations with evidence paths, and every unobserved case\u002Fgap. Use that return in the evidence\u002Flimits report below; selecting cases without observing them is not coverage.\n\nIF the claim covers shared story\u002Fsection\u002FMap composition, read [the show-me-work journey](references\u002Fshow-me-work.md). The product fixture and permanent browser cases exist; require the declared frozen target and account for each applicable O1\u002FO2\u002FO3\u002FO5 case. The permanent harness entrypoint is `node apps\u002Fdemistify-poc\u002Fscripts\u002Fverify-story-map.ts`; run it from the monorepo root on an authorized matching build. The supplementary native-host journey remains a draft where its cases are unobserved.\n\n| Journey                          | Deciding observation                                                                                                                                                                                                                                                        |\n| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Prepared call-stack reader       | [Built-fixture journey](references\u002Fdocument-browsers.md): call selection\u002Fkeyboard, visible owner-body links, partial inputs, Comments\u002Fsource revision and inspection; `node apps\u002Fdemistify-poc\u002Fscripts\u002Fverify-design-documents.ts` selects the existing built-fixture cases |\n| Shared story\u002Fsection\u002FMap         | Native story content, scoped folds\u002Fcounts, Map\u002FComments and layout against the adopted S3 target; `verify-story-map.ts` runs the permanent built-fixture and M shortcut cases; direct native-host and missing surfaces need case-specific evidence                          |\n| Presentations\u002Fpages\u002Ffragments    | Cold and same-page links reveal the correct presentation\u002Ftab; selected-only content and grouped navigation remain useful                                                                                                                                                    |\n| Markdown\u002FMermaid\u002Fsource          | Referenced text and real SVG render; source text\u002Freference stay exact while main content stays rendered                                                                                                                                                                     |\n| Diagram layout\u002Finspection        | Local scrolling reaches both ends without page overflow, displacement, lost controls or arrow\u002Fnode drift; fullscreen restores state                                                                                                                                         |\n| Tree labels                      | Multiline, inline-code and loose-paragraph labels wrap beneath text with the icon on the first line                                                                                                                                                                         |\n| Visual gestures                  | Cmd+wheel anchors zoom at the pointer; Cmd+drag pans; normal scroll, buttons, reset and restoration remain usable                                                                                                                                                           |\n| CLI checking\u002Fembedding           | Local sources check\u002Fembed and missing sources fail; transformation stays distinct from runtime\u002Foffline proof                                                                                                                                                                |\n| CLI package-manager delivery     | [Cache delivery journey](references\u002Fcli-delivery.md): exercise staged guide, actual package-manager selection and cache evidence; hosted publication remains separate                                                                                                       |\n| Small parts in cells\u002Fprose\u002FTrace | Exact numeric states, stable phase slots, both themes and desktop\u002F390px containment; permanent `review-ui\u002Fsmall-parts.html` and `tests\u002Fbrowser\u002Fsmall-parts.browser.test.ts` exist in the existing harness                                                                   |\n| Frozen fresh-Luna artifact       | Supported native action capture establishes the loaded candidate copies; matching CLI and the actual frozen HTML establish only the named case's factual\u002Fcomposition behavior                                                                                               |\n| Choices and comments             | Native cards\u002Ftable\u002Finline details, exact identified feedback, same-revision reload and actual Copy\u002FExport; shared panels, reconnect and read-only-copy isolation through the existing frozen harness plus assigned native observations                                      |\n\nThe representative pass uses the complete existing suite: real frame launch\u002Freadiness, navigation selection and cold fragment cases, external\u002Fembedded rendered text\u002FSVG, exact-source inspection with original heading\u002Ftable retained, Close, then automatic teardown. Cases use fresh frames rather than sharing one continuous user session. A pass covers only the assertions actually exercised.\n\n## Evidence, ownership and cleanup\n\nUse a separate run directory under ignored `tmp\u002Fverification\u002Fdemistify\u002F`. Record target\u002Fbuild\u002Fresource and fixture\u002Fsource identities, route, viewport, actions, before\u002Fafter observations, actual rectangles\u002Fscroll offsets, screenshots, console\u002Fnetwork failures, CLI output and exit codes. Report test pass\u002Ffail\u002Fskip counts only from actual runs; preserve failures alongside later success. Keep captured content public-safe.\n\nFor each journey report **supported**, **unsupported** or **unknown**, evidence paths and undriven entry points. Source checks, suites, browser behavior, file-protocol operation, hosting and release are separate claims. Name missing sensitivity if a known failure has not shown the observation can reject it. Measure actual geometry instead of copying production formulas. Hidden overflow that clips content fails even when document width looks contained.\n\nThe Verifier owns this recipe and assigned apparatus. Product failures\u002Ftest gaps go to the Implementer; unsettled expectations\u002Ftargets go to the Lead. Run history belongs in the authorized trace\u002Fevidence. This recipe grants no product\u002Ftest edits, public uploads, release or acceptance authority.\n\nThe non-watch Vitest command exits and tears down its server\u002Fbrowser. Confirm the recorded API port has no listener; preserve\u002Freopen evidence afterward. Keep the immutable temp snapshot if it is still needed as input evidence. Stop only a hung process\u002Fsession this run started, by recorded identity. Leave shared instances\u002Ftabs and others' files alone. Directory removal needs explicit repository permission.\n\nReport the exact build and exercised scope on every use. Other journey variants stay unknown until adequate applicable evidence exists. Embedding\u002FHTTP rendering alone does not establish offline\u002Ffile viewing. Normal main-diagram scroll input, precise pointer anchoring, drawer resize and narrow-navigation interactions beyond the scoped 390px hover\u002Fclick\u002FRecovery case need separate proof.\n","# Verify Demistify\n\nVerify `packages\u002Fdemistify` through its plain-HTML consumer, `apps\u002Fdemistify-poc`. Keep the real built library, Markdown files, native custom elements, diagram renderer and browser layout in the path. CLI checking and embedding prove different claims from browser behavior.\n\n**Operable for the existing focused headless browser and CLI routes below.** The choices\u002Fcomments journey remains a draft wherever its declared-target observations are incomplete; distinguish applicable feature\u002Fboundary assertions, component integration and native host observations. Broader journey variants remain explicitly unobserved. Record the actual target and coverage in the task's evidence\u002Ftrace; a working recipe is not product acceptance or proof of cold-runner skill application.\n\n## Target and contract\n\nRead the [owner task list](..\u002F..\u002F..\u002Fdocs\u002Fwip\u002Fdemystify\u002F2026-10-16-fixes-todo.md), [project instructions](..\u002F..\u002F..\u002FAGENTS.md) and [handoff](..\u002F..\u002F..\u002Fdocs\u002Fwip\u002Fdemystify\u002F2026-10-14-demistify-handoff.md). Their outcomes and the current commission are the oracle. Sidebar\u002Fsource inspection retains rendered main content. Fullscreen may temporarily move live content, but Close\u002FEscape must restore the same nodes and state.\n\nRecord the declared commit, permitted dirty-state exceptions, build location\u002Freceipt, fixture URL, browser\u002Fclient, viewport and process\u002Fbrowser ownership. Compare `git status --short`, `git branch --show-current` and `git rev-parse HEAD` with that declaration. Moving source supports preparation, not delivery observation. Stop affected observations if the target changes.\n\nPublic-safe fixtures need no account\u002Fbackend. Existing dependencies are a prerequisite; this recipe grants no installation, browser control or execution beyond the current commission.\n\nThe small-parts and fresh-Luna journeys below describe native coverage for the adopted 22 October 2026 small-parts contract (U1–U4\u002FR1–R7). Require its exact source revisions, matching candidate guidance and frozen complete build from the commission. The permanent small-parts fixture and browser test exist in the repository. Their automated assertions and the native fixture, literal-example and fresh-author observations need their own target-bound evidence.\n\n## Frozen built-library launch and health\n\nFrom the monorepo root, with Node 26+, pnpm 12 and the installed Chromium matching the checkout's Playwright dependency, run the existing repository harness after execution is authorized:\n\n```sh\npnpm test:browser\n```\n\nFor an explicitly scoped compact-headings correction, run only its permanent case:\n\n```sh\npnpm --filter @sunstack\u002Fdemistify-poc exec vitest run --config vitest.browser.config.ts tests\u002Fbrowser\u002Fdocument.browser.test.ts -t 'compact headings menu'\n```\n\nReport selected tests separately from name-filtered skips and uncollected files. A focused pass is not a full-suite pass.\n\nThe root\u002Fpackage scripts route this to `vitest run --config vitest.browser.config.ts`. The existing Vitest Playwright provider launches isolated headless Chromium; no desktop tab is used. With no `PLAYWRIGHT_BROWSERS_PATH` override, use the matching installed default executable. Before launch, resolve its path through the PoC's installed dependency and confirm it exists:\n\n```sh\nnode --input-type=module -e 'import {createRequire} from \"node:module\"; import {resolve} from \"node:path\"; import {existsSync} from \"node:fs\"; const requireFromPoc=createRequire(resolve(\"apps\u002Fdemistify-poc\u002Fpackage.json\")); const executable=requireFromPoc(\"playwright\").chromium.executablePath(); const exists=existsSync(executable); console.log(JSON.stringify({executable,exists,browserPathOverride:process.env.PLAYWRIGHT_BROWSERS_PATH??null},null,2)); process.exitCode=exists?0:1;'\n```\n\nRetain the actual executable\u002Foverride receipt. An explicit cache is valid only when selected by the commission and this same check confirms its executable exists; preserve that override for the run. A missing executable is a setup gap: never install, change caches or fall back silently. Its Vite plugin (`tests\u002Fbrowser\u002Fbuilt-fixtures.ts`) snapshots the complete `packages\u002Fdemistify\u002Fdist`, the authored fixtures and the built consumer page `apps\u002Fdemistify-poc\u002Fdist\u002Fexperiments\u002Fhtml-islands-content-surfaces-live.html`, rewrites that page's asset links to the snapshot library, then serves those bytes from a fresh loopback port. The declared target therefore needs both outputs of one root `pnpm build` from the same source: a library-only build fails the whole suite at startup, and a stale PoC build silently serves an older page. Record that page's SHA-256 beside the library hashes. `DEMISTIFY_BROWSER_ASSETS` optionally selects a declared complete library copy and replaces library bytes only; the consumer page still comes from `apps\u002Fdemistify-poc\u002Fdist`. Record any override. Installations require a separate grant. See the [harness README](..\u002F..\u002F..\u002Fapps\u002Fdemistify-poc\u002Ftests\u002Fbrowser\u002FREADME.md) for harness behavior; its installation example grants no install and does not select this run's cache.\n\nKeep stdout\u002Fstderr, exit code, printed snapshot directory and API URL. Compare the snapshot's library hashes with the declared library, and the built page's hash with the declared build. Vite writes generated config\u002Fcache files under `node_modules\u002F.vite-temp`; if sandbox permissions prevent launch, preserve that startup failure and request the exact access for the same command. It is not a product test failure. Never rebuild a frozen target.\n\n**Readiness\u002Fhealth:** `openFixture` polls for the real document, upgraded navigation controls and stylesheet, then awaits fonts. Each behavior test waits for its actual heading\u002Ftable\u002FSVG or inspection result. These checks, together with snapshot identity, establish a usable real target; a listening port alone does not. Preserve failed assertions and request\u002Fbrowser errors emitted by the suite. Successful tests do not establish a comprehensive console\u002Fnetwork audit.\n\nFor separately authorized PoC preview work, root `pnpm build` refreshes the library and copied static host; `pnpm --filter @sunstack\u002Fdemistify-poc preview --port 4174` serves it on loopback. This is a distinct delivery path from the harness snapshot. The owner desktop surface needs its own release. Do not run these commands during a source\u002Fbuild freeze.\n\n## Drive and reuse\n\nInspect the finished browser configuration and assertions before reuse. The separate `apps\u002Fdemistify-poc\u002Fvitest.config.ts` uses Node; the package `test` command is not browser evidence. The Implementer owns product tests. Report the current selected browser cases from the actual run and read their assertion limits at source; historical case counts in a journey are not the current suite inventory.\n\nFor direct UI observation, use host computer-use\u002FChrome on one released surface with sole control. Use ordinary links, tabs, buttons, wheel and pointer input. Read-only DOM geometry corroborates visible outcomes. Internal setters, synthetic events and mocked rendering\u002Ffetch do not establish user interaction. An adopted component-integration case may call an existing action to decide its lifecycle boundary; label that result separately from native input, as the choices\u002Fcomments reference requires for controls behind a phone modal. Do not introduce a separate Playwright driver.\n\nInspect a passing journey's target, fixtures, interactions, assertions and result before reuse. Reuse applicable evidence. Add direct observation for a missing interaction, changed dependency or specific unresolved doubt; independence does not require repeating equivalent proof.\n\n## Journeys\n\nRead [journey instructions and source map](references\u002Fjourneys.md) for the selected scope.\n\nIF the claim includes choices or comments, load `references\u002Fchoices-comments.md` and return the declared target, selected O1\u002FO2 cases, deciding observations with evidence paths, and every unobserved case\u002Fgap. Use that return in the evidence\u002Flimits report below; selecting cases without observing them is not coverage.\n\nIF the claim covers shared story\u002Fsection\u002FMap composition, read [the show-me-work journey](references\u002Fshow-me-work.md). The product fixture and permanent browser cases exist; require the declared frozen target and account for each applicable O1\u002FO2\u002FO3\u002FO5 case. The permanent harness entrypoint is `node apps\u002Fdemistify-poc\u002Fscripts\u002Fverify-story-map.ts`; run it from the monorepo root on an authorized matching build. The supplementary native-host journey remains a draft where its cases are unobserved.\n\n| Journey                          | Deciding observation                                                                                                                                                                                                                                                        |\n| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Prepared call-stack reader       | [Built-fixture journey](references\u002Fdocument-browsers.md): call selection\u002Fkeyboard, visible owner-body links, partial inputs, Comments\u002Fsource revision and inspection; `node apps\u002Fdemistify-poc\u002Fscripts\u002Fverify-design-documents.ts` selects the existing built-fixture cases |\n| Shared story\u002Fsection\u002FMap         | Native story content, scoped folds\u002Fcounts, Map\u002FComments and layout against the adopted S3 target; `verify-story-map.ts` runs the permanent built-fixture and M shortcut cases; direct native-host and missing surfaces need case-specific evidence                          |\n| Presentations\u002Fpages\u002Ffragments    | Cold and same-page links reveal the correct presentation\u002Ftab; selected-only content and grouped navigation remain useful                                                                                                                                                    |\n| Markdown\u002FMermaid\u002Fsource          | Referenced text and real SVG render; source text\u002Freference stay exact while main content stays rendered                                                                                                                                                                     |\n| Diagram layout\u002Finspection        | Local scrolling reaches both ends without page overflow, displacement, lost controls or arrow\u002Fnode drift; fullscreen restores state                                                                                                                                         |\n| Tree labels                      | Multiline, inline-code and loose-paragraph labels wrap beneath text with the icon on the first line                                                                                                                                                                         |\n| Visual gestures                  | Cmd+wheel anchors zoom at the pointer; Cmd+drag pans; normal scroll, buttons, reset and restoration remain usable                                                                                                                                                           |\n| CLI checking\u002Fembedding           | Local sources check\u002Fembed and missing sources fail; transformation stays distinct from runtime\u002Foffline proof                                                                                                                                                                |\n| CLI package-manager delivery     | [Cache delivery journey](references\u002Fcli-delivery.md): exercise staged guide, actual package-manager selection and cache evidence; hosted publication remains separate                                                                                                       |\n| Small parts in cells\u002Fprose\u002FTrace | Exact numeric states, stable phase slots, both themes and desktop\u002F390px containment; permanent `review-ui\u002Fsmall-parts.html` and `tests\u002Fbrowser\u002Fsmall-parts.browser.test.ts` exist in the existing harness                                                                   |\n| Frozen fresh-Luna artifact       | Supported native action capture establishes the loaded candidate copies; matching CLI and the actual frozen HTML establish only the named case's factual\u002Fcomposition behavior                                                                                               |\n| Choices and comments             | Native cards\u002Ftable\u002Finline details, exact identified feedback, same-revision reload and actual Copy\u002FExport; shared panels, reconnect and read-only-copy isolation through the existing frozen harness plus assigned native observations                                      |\n\nThe representative pass uses the complete existing suite: real frame launch\u002Freadiness, navigation selection and cold fragment cases, external\u002Fembedded rendered text\u002FSVG, exact-source inspection with original heading\u002Ftable retained, Close, then automatic teardown. Cases use fresh frames rather than sharing one continuous user session. A pass covers only the assertions actually exercised.\n\n## Evidence, ownership and cleanup\n\nUse a separate run directory under ignored `tmp\u002Fverification\u002Fdemistify\u002F`. Record target\u002Fbuild\u002Fresource and fixture\u002Fsource identities, route, viewport, actions, before\u002Fafter observations, actual rectangles\u002Fscroll offsets, screenshots, console\u002Fnetwork failures, CLI output and exit codes. Report test pass\u002Ffail\u002Fskip counts only from actual runs; preserve failures alongside later success. Keep captured content public-safe.\n\nFor each journey report **supported**, **unsupported** or **unknown**, evidence paths and undriven entry points. Source checks, suites, browser behavior, file-protocol operation, hosting and release are separate claims. Name missing sensitivity if a known failure has not shown the observation can reject it. Measure actual geometry instead of copying production formulas. Hidden overflow that clips content fails even when document width looks contained.\n\nThe Verifier owns this recipe and assigned apparatus. Product failures\u002Ftest gaps go to the Implementer; unsettled expectations\u002Ftargets go to the Lead. Run history belongs in the authorized trace\u002Fevidence. This recipe grants no product\u002Ftest edits, public uploads, release or acceptance authority.\n\nThe non-watch Vitest command exits and tears down its server\u002Fbrowser. Confirm the recorded API port has no listener; preserve\u002Freopen evidence afterward. Keep the immutable temp snapshot if it is still needed as input evidence. Stop only a hung process\u002Fsession this run started, by recorded identity. Leave shared instances\u002Ftabs and others' files alone. Directory removal needs explicit repository permission.\n\nReport the exact build and exercised scope on every use. Other journey variants stay unknown until adequate applicable evidence exists. Embedding\u002FHTTP rendering alone does not establish offline\u002Ffile viewing. Normal main-diagram scroll input, precise pointer anchoring, drawer resize and narrow-navigation interactions beyond the scoped 390px hover\u002Fclick\u002FRecovery case need separate proof.\n",{"name":5,"description":7},"main","dd78d12c5562758ae581f1dedccb0e09d2290154",".agents\u002Fskills\u002Fverify-demistify","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools","https:\u002F\u002Fgithub.com\u002FShravanSunder","💻 Staff AI Engineer @ Relay Financial;   \r\n🪙 Exploring AI Agents","2026-11-15 01:43:51",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ShravanSunder\u002Fsunstack-tools --skill verify-demistify",{"tool":37,"command":38},"bunx","bunx skills add ShravanSunder\u002Fsunstack-tools --skill verify-demistify",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ShravanSunder\u002Fsunstack-tools --skill verify-demistify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fchoices-comments.md","REFERENCE","参考文档",23767,"https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002Freferences\u002Fchoices-comments.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcli-delivery.md",2918,"https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002Freferences\u002Fcli-delivery.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fdocument-browsers.md",6429,"https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002Freferences\u002Fdocument-browsers.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fjourneys.md",27921,"https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002Freferences\u002Fjourneys.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fshow-me-work.md",12565,"https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-demistify\u002Freferences\u002Fshow-me-work.md",[68,74,81,87,94,101],{"skillNo":69,"name":70,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7EHCT4EWN4EWJ6SSY7E4B6E","smoke-fixture","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002Fscripts\u002Frelease\u002Fsmoke-fixture\u002Fskill.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7EHCQJWP7TNVKV4S1BR3QYA","demistify-explainer","Use when writing, editing, or checking Demistify markup: component syntax, attributes, nesting, layouts, Markdown\u002FMermaid islands, and data references.","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002Fpackages\u002Fdemistify\u002Fskill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EHCNB60T960ND6G9P0R5EE","examples","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002Fdocs\u002Fspecs\u002F2026-10-12-rust-rule-engine\u002Fexamples\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7EHCF5QKTPPAD5XWP1WTCVR","verification-design","Use when planning how a design project's requirements will be proven: for each requirement, the reference, the target and `verify-\u003Capp>` journey, a passing condition a wrong build fails, reused real-path tests and what stays unverified, after Program Design or when that plan is missing or stale. Not for observing or challenging a delivered claim (practices-verification), building journeys (practices-verification-maintenance), or regression tests.","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002Fcrates\u002Fsunstack\u002Ftests\u002Ffixtures\u002Frulebook-lint\u002Fskills\u002Fverification-design\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EHCB34APZ6K02GXFCGRZGC","practices-retrospective","Use when asked for a blameless retrospective, a look back, or lessons from a finished or bounded session or delivery: what helped, what hindered, what to preserve, or why an owner or review correction keeps recurring across sessions. Not for re-anchoring a shared model in the current conversation, diagnosing a current failure, collecting evidence alone, choosing which skills to create or merge, or maintaining a verification skill.","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002Fcrates\u002Fsunstack\u002Ftests\u002Ffixtures\u002Frulebook-lint\u002Fskills\u002Fpractices-retrospective\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7EHC6QJ3GXRZWGXHAKD03CH","practices-research","Use when a task needs source gathering, prior-art research, current docs or web evidence, or memory, session-log, or saved-reader research before design, planning, review, or discussion can continue. Not for extracting unwritten owner meaning.","https:\u002F\u002Fgithub.com\u002FShravanSunder\u002Fsunstack-tools\u002Fblob\u002Fmain\u002Fcrates\u002Fsunstack\u002Ftests\u002Ffixtures\u002Frulebook-lint\u002Fskills\u002Fpractices-research\u002FSKILL.md",[],[]]