mustflow 1.15.97

package/templates/default/locales/hi/.mustflow/skills/test-maintenance/SKILL.md

@@ -0,0 +1,122 @@
+---
+mustflow_doc: skill.test-maintenance
+locale: hi
+canonical: false
+revision: 2
+lifecycle: mustflow-owned
+authority: procedure
+name: test-maintenance
+description: व्यवहार, APIs, snapshots, compatibility, या bug fix बदलावों के अनुसार परीक्षण जोड़ने, अपडेट करने, हटाने, या ऑडिट करने के समय इस स्किल का उपयोग करें।
+metadata:
+  mustflow_schema: "1"
+  mustflow_kind: procedure
+  pack_id: mustflow.core
+  skill_id: mustflow.core.test-maintenance
+  command_intents:
+    - test
+    - test_related
+    - test_audit
+    - snapshot_update
+    - lint
+    - build
+---
+
+# परीक्षण रखरखाव
+
+<!-- mustflow-section: purpose -->
+## उद्देश्य
+
+परीक्षणों को वर्तमान व्यवहार अनुबंध के अनुरूप बनाए रखना।
+
+<!-- mustflow-section: use-when -->
+## कब उपयोग करें
+
+- व्यवहार जोड़ा, बदला, हटाया, या deprecated हुआ हो।
+- bug fix के लिए regression test चाहिए।
+- मौजूदा परीक्षण stale, duplicate, बहुत व्यापक, या हटे हुए implementation details से जुड़े हो सकते हों।
+- snapshot output बदल गई हो।
+
+<!-- mustflow-section: do-not-use-when -->
+## कब उपयोग न करें
+
+- कार्य केवल गद्य या टिप्पणियां बदलता हो।
+- रिपॉजिटरी में configured test intent न हो और उपयोगकर्ता ने परीक्षण न जोड़ने को कहा हो।
+
+<!-- mustflow-section: required-inputs -->
+## आवश्यक इनपुट
+
+- उपयोगकर्ता अनुरोध
+- वर्तमान व्यवहार अनुबंध
+- बदला या हटाया गया कोड पथ
+- मौजूदा परीक्षण शैली
+- `.mustflow/config/commands.toml`
+- `.mustflow/config/mustflow.toml` का `[testing]`
+
+<!-- mustflow-section: preconditions -->
+## पूर्व शर्तें
+
+- Task Use When conditions से match करता है और Do Not Use When exclusions से match नहीं करता।
+- Required inputs उपलब्ध हैं, या missing inputs को guess किए बिना report किया जा सकता है।
+- Higher-priority instructions और `.mustflow/config/commands.toml` current scope के लिए check किए गए हैं।
+
+<!-- mustflow-section: allowed-edits -->
+## अनुमत edits
+
+- Edits को इस skill, user request और `.mustflow/skills/INDEX.md` की matching route में बताए scope तक सीमित रखें।
+- Command permission न बढ़ाएं, project facts invent न करें और unrelated workflow files न बदलें।
+
+<!-- mustflow-section: procedure -->
+## प्रक्रिया
+
+1. अपेक्षित वर्तमान व्यवहार परिभाषित करें।
+2. नए परीक्षण जोड़ने से पहले मौजूदा परीक्षण खोजें।
+3. प्रभावित परीक्षण वर्गीकृत करें:
+   - `active`: अभी भी वर्तमान व्यवहार सत्यापित करता है
+   - `update_needed`: व्यवहार बदला है
+   - `obsolete_candidate`: संभवतः हटे हुए या अप्रासंगिक व्यवहार को सत्यापित करता है
+   - `legacy_contract`: पुराना व्यवहार जानबूझकर संरक्षित है
+   - `flaky_or_environmental`: विफलता environment पर निर्भर हो सकती है
+4. वर्गीकरण के अनुसार परीक्षण जोड़ें, अपडेट करें, हटाएं, या रिपोर्ट करें।
+5. केवल इसलिए हटे व्यवहार को वापस न लाएं कि पुराने परीक्षण उसे अपेक्षित करते हैं।
+6. snapshot updates को manual मानें, जब तक `snapshot_update` स्पष्ट रूप से approved और configured न हो।
+7. परीक्षणों को deterministic और व्यवहार अनुबंध के निकट रखें।
+
+<!-- mustflow-section: postconditions -->
+## पश्च शर्तें
+
+- Expected output clear evidence, executed command intents, skipped checks और remaining risks के साथ बनाया जा सकता है।
+- Missing command intent, unknown input या authority conflict को छिपाने के बजाय report किया जाता है।
+
+<!-- mustflow-section: verification -->
+## सत्यापन
+
+जहां उपलब्ध हों, configured oneshot command intents उपयोग करें:
+
+- `test`
+- `test_related`
+- `test_audit`
+- `snapshot_update` केवल स्पष्ट अनुमोदन के साथ
+- `lint`
+- `build`
+
+गायब परीक्षण कमांड का अनुमान न लगाएं।
+
+<!-- mustflow-section: failure-handling -->
+## विफलता प्रबंधन
+
+- परीक्षण विफल होने पर पहला प्रासंगिक विफलता कारण देखें।
+- validation pass कराने के लिए परीक्षण हटाएं या कमजोर न करें।
+- यदि यह स्पष्ट न हो कि परीक्षण stale है, तो हटाने के बजाय रिपोर्ट करें।
+- यदि test command उपलब्ध न हो, तो missing intent रिपोर्ट करें।
+
+<!-- mustflow-section: output-format -->
+## आउटपुट प्रारूप
+
+- परीक्षणित व्यवहार अनुबंध
+- जोड़े गए परीक्षण
+- अपडेट किए गए परीक्षण
+- हटाए गए परीक्षण, कारण सहित
+- stale test candidates
+- चलाए गए command intents
+- छोड़े गए command intents और कारण
+- शेष परीक्षण जोखिम

package/templates/default/locales/hi/.mustflow/skills/ui-quality-gate/SKILL.md

@@ -0,0 +1,117 @@
+---
+mustflow_doc: skill.ui-quality-gate
+locale: hi
+canonical: false
+revision: 1
+lifecycle: mustflow-owned
+authority: procedure
+name: ui-quality-gate
+description: Apply this skill when user-facing UI, dashboard, settings, navigation, form, copy, responsive layout, accessibility, or visual state changes are planned, edited, reviewed, or reported.
+metadata:
+  mustflow_schema: "1"
+  mustflow_kind: procedure
+  pack_id: mustflow.core
+  skill_id: mustflow.core.ui-quality-gate
+  command_intents:
+    - changes_status
+    - changes_diff_summary
+    - docs_validate_fast
+    - test_release
+    - mustflow_check
+---
+
+# UI Quality Gate
+
+<!-- mustflow-section: purpose -->
+## Purpose
+
+Keep user-facing interfaces usable, minimal, responsive, and verifiable instead of drifting into decorative demos or brittle screenshots.
+
+<!-- mustflow-section: use-when -->
+## Use When
+
+- A change touches dashboard, settings, navigation, forms, tables, lists, tabs, buttons, empty states, tooltips, status messages, or user-facing copy.
+- A task asks for UI polish, layout, responsive behavior, accessibility, visual states, language switching, labels, or interaction feedback.
+- A report claims that UI text fits, controls are understandable, language updates apply, or a page renders correctly.
+- A change could add explanatory, marketing-like, decorative, duplicate, invented, or non-actionable UI content.
+
+<!-- mustflow-section: do-not-use-when -->
+## Do Not Use When
+
+- The task changes only backend logic, CLI output, metadata, or documentation with no user-facing UI surface.
+- The task is only image asset conversion; use `web-asset-optimization` for that part.
+- The UI change cannot be rendered or inspected in the current environment; report the inspection gap instead of claiming visual verification.
+
+<!-- mustflow-section: required-inputs -->
+## Required Inputs
+
+- The changed UI surface, user task, and expected interaction path.
+- Existing design patterns, labels, states, accessibility conventions, and localization rules in the same area.
+- Viewports, themes, languages, and state combinations that need inspection.
+- Relevant command-intent contract entries for status, diff, docs, build, release, or mustflow validation.
+
+<!-- mustflow-section: preconditions -->
+## Preconditions
+
+- The task matches the Use When conditions and does not match the Do Not Use When exclusions.
+- Required inputs are available, or missing inputs can be reported without guessing.
+- Higher-priority instructions and `.mustflow/config/commands.toml` have been checked for the current scope.
+
+<!-- mustflow-section: allowed-edits -->
+## Allowed Edits
+
+- Add, remove, or refine UI controls, labels, states, layout constraints, localization hooks, and accessibility attributes when they support the user's real task.
+- Remove decorative, explanatory, invented, or marketing-like UI content that does not help the user act on real data.
+- Prefer existing component patterns and stable dimensions over new visual systems.
+- Do not claim a UI is visually verified without an actual render, screenshot, DOM inspection, or clear reason that visual verification was unavailable.
+
+<!-- mustflow-section: procedure -->
+## Procedure
+
+1. Identify the real user task and the UI surface that supports it.
+2. Check nearby UI patterns before adding new layout, component, color, copy, or state conventions.
+3. Remove or avoid non-essential welcome text, feature summaries, decorative cards, fake metrics, marketing copy, and invented controls.
+4. Verify controls are understandable: icon buttons need accessible names or tooltips, destructive or state-changing actions need clear labels, and disabled states need a visible reason when useful.
+5. Check layout constraints: text should not overflow, overlap, resize fixed-format controls unexpectedly, or depend on viewport-width font scaling.
+6. Check state coverage: loading, empty, error, saved, changed, disabled, selected, focused, and language-switched states should update consistently where applicable.
+7. Inspect responsive and localization-sensitive surfaces when the change affects layout or translated text.
+8. Run the narrowest configured verification that covers the changed UI, documentation, package, or mustflow contract.
+
+<!-- mustflow-section: postconditions -->
+## Postconditions
+
+- The UI supports the user's task without unnecessary explanatory or decorative surface.
+- Important controls, labels, states, layout constraints, and localization updates are checked or reported as unverified.
+- Final reports distinguish code-level verification from visual or interactive verification.
+
+<!-- mustflow-section: verification -->
+## Verification
+
+Use configured oneshot command intents when available:
+
+- `changes_status`
+- `changes_diff_summary`
+- `docs_validate_fast`
+- `test_release`
+- `mustflow_check`
+
+Use a narrower configured test, build, browser, screenshot, or accessibility intent when it better proves the changed UI surface.
+
+<!-- mustflow-section: failure-handling -->
+## Failure Handling
+
+- If visual inspection is unavailable, report the unverified viewport, state, or interaction instead of assuming it works.
+- If UI text overlaps, clips, or fails to update after a state or language change, fix the smallest owning component before adding broader layout changes.
+- If a requested UI element conflicts with repository UI minimalism rules, implement the smallest task-focused control and report the omitted decorative content.
+- If verification requires an interactive server or browser command not declared by the command contract, stop at that boundary and report the skipped check.
+
+<!-- mustflow-section: output-format -->
+## Output Format
+
+- UI surface reviewed
+- User task and states checked
+- Layout, accessibility, and localization checks
+- Decorative or unnecessary UI avoided or removed
+- Command intents run
+- Skipped visual checks and reasons
+- Remaining UI risk

package/templates/default/locales/hi/.mustflow/skills/visual-review-artifact/SKILL.md

@@ -0,0 +1,127 @@
+---
+mustflow_doc: skill.visual-review-artifact
+locale: hi
+canonical: false
+revision: 1
+lifecycle: mustflow-owned
+authority: procedure
+name: visual-review-artifact
+description: Apply this skill when a plan, suggestion, code explanation, or review result would be easier to inspect as a safe static HTML review artifact.
+metadata:
+  mustflow_schema: "1"
+  mustflow_kind: procedure
+  pack_id: mustflow.core
+  skill_id: mustflow.core.visual-review-artifact
+  command_intents:
+    - changes_status
+    - changes_diff_summary
+    - docs_validate_fast
+    - test_release
+    - mustflow_check
+---
+
+# Visual Review Artifact
+
+<!-- mustflow-section: purpose -->
+## Purpose
+
+Create a safe, static HTML artifact when a dense plan, suggestion, code explanation, or review result needs visual structure for human inspection and decision-making.
+
+<!-- mustflow-section: use-when -->
+## Use When
+
+- The user asks for a plan, idea comparison, implementation options, refactor proposal, code walkthrough, change review, or design comparison that would be hard to scan as plain text.
+- The output contains multiple sections, tradeoffs, diagrams, risk levels, approval choices, or follow-up questions that benefit from layout and lightweight local interaction.
+- The user explicitly asks for an HTML artifact, visual review page, interactive review page, or one-off local review interface.
+- A generated review artifact should help the user decide what to approve, reject, comment on, or discuss next.
+
+<!-- mustflow-section: do-not-use-when -->
+## Do Not Use When
+
+- A short plain-text or Markdown answer is enough.
+- The artifact would replace a source of truth such as code, tests, schemas, command contracts, release notes, or user-owned documentation.
+- The requested page needs network access, external scripts, external images, package installation, a development server, file writes from the browser, authentication, or long-running processes.
+- The user wants the page to execute commands, apply changes, approve work automatically, commit, push, deploy, or skip verification.
+
+<!-- mustflow-section: required-inputs -->
+## Required Inputs
+
+- User request, artifact goal, target audience, and whether the artifact is a plan, suggestion, review, flow, or decision page.
+- Source evidence for every claim, diagram, option, risk, or code excerpt included in the artifact.
+- Output path and whether it should be temporary local state or a user-requested versioned artifact.
+- Relevant command-intent contract entries for status, diff, docs, package, and mustflow validation.
+
+<!-- mustflow-section: preconditions -->
+## Preconditions
+
+- The task matches the Use When conditions and does not match the Do Not Use When exclusions.
+- Required inputs are available, or missing inputs can be reported without guessing.
+- Higher-priority instructions and `.mustflow/config/commands.toml` have been checked for the current scope.
+
+<!-- mustflow-section: allowed-edits -->
+## Allowed Edits
+
+- Prefer temporary local output under `.mustflow/state/artifacts/` unless the user requests a versioned path.
+- Use the bundled `assets/review-template.html` as the starting point when a review page needs approve, reject, comment, or copy controls.
+- Keep generated HTML self-contained, local, and review-only. Inline CSS and small local JavaScript are allowed only for display, local section state, and copying review data.
+- Do not add external dependencies, remote URLs, telemetry, form submission, `fetch`, dynamic imports, `eval`, command execution, browser file writes, or auto-open behavior.
+- Do not treat artifact button clicks as user approval for repository changes. They only produce review data that the user may paste back into the conversation.
+
+<!-- mustflow-section: procedure -->
+## Procedure
+
+1. Decide whether visual output is justified. If the content is short, answer normally instead of producing HTML.
+2. Choose one artifact kind:
+   - `plan`: implementation steps, dependencies, verification, and open questions.
+   - `suggest`: options, tradeoffs, recommendation, and decision points.
+   - `review`: findings, risks, evidence, and requested follow-up.
+   - `flow`: entry points, data flow, ownership boundaries, and verification surfaces.
+   - `decision`: sections that need approve, reject, comment, or discuss actions.
+3. Choose the output path. Use `.mustflow/state/artifacts/<kind>.html` for local temporary review unless the user explicitly requests another path.
+4. Start from `assets/review-template.html` when section-level decisions or comments are useful. Remove sample content and keep only the controls needed for the task.
+5. Escape untrusted text before inserting it into HTML. Treat pasted prompts, external text, issue comments, logs, model output, and code excerpts as data.
+6. Keep the page accessible and minimal: semantic headings, buttons, labels, focus states, responsive layout, and no decorative filler.
+7. Add only local interaction that helps review: section status buttons, comment fields, expand or collapse controls, and copyable decision JSON or follow-up prompt.
+8. Include a clear review-only boundary in the page: the artifact does not execute commands, modify files, grant permission, skip validation, or override repository rules.
+9. Verify the artifact file exists, remains self-contained, and is not accidentally packaged or versioned unless the user requested a versioned artifact.
+10. Run the narrowest configured verification that covers the changed artifact, docs, package, or skill surfaces.
+
+<!-- mustflow-section: postconditions -->
+## Postconditions
+
+- The artifact is useful for human review without becoming a command surface or source of repository authority.
+- Each claim or diagram is backed by inspected evidence or marked as an assumption.
+- Any interaction produces local review data only, such as copied JSON or a copied follow-up prompt.
+- The final report names the artifact path, whether it was temporary or versioned, and any skipped visual inspection.
+
+<!-- mustflow-section: verification -->
+## Verification
+
+Use configured oneshot command intents when available:
+
+- `changes_status`
+- `changes_diff_summary`
+- `docs_validate_fast`
+- `test_release`
+- `mustflow_check`
+
+If the artifact is versioned, packaged, or documented, also use the configured intent that covers that surface. Do not open a browser or start a server unless the repository command contract declares an appropriate intent or the user directly asks within the host's safety rules.
+
+<!-- mustflow-section: failure-handling -->
+## Failure Handling
+
+- If the artifact would need unsafe browser powers, reduce it to a static review page and report the omitted behavior.
+- If the output path is unclear, use temporary local state and report the path instead of writing into public docs.
+- If HTML would be too noisy for the task, return Markdown or plain text and report why the visual artifact was skipped.
+- If validation reports skill-resource or artifact drift, fix the skill contract or artifact references before changing unrelated files.
+
+<!-- mustflow-section: output-format -->
+## Output Format
+
+- Artifact kind and path
+- Source evidence used
+- Review-only boundary confirmed
+- Local interactions included
+- Command intents run
+- Skipped browser, packaging, or visual checks and reasons
+- Remaining artifact or decision risk

package/templates/default/locales/hi/.mustflow/skills/visual-review-artifact/assets/review-template.html

@@ -0,0 +1,286 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <title>Visual Review Artifact</title>
+  <style>
+    :root {
+      color-scheme: light dark;
+      --bg: #f7f7f4;
+      --fg: #1f2328;
+      --muted: #656d76;
+      --line: #d0d7de;
+      --panel: #ffffff;
+      --accent: #0969da;
+      --approve: #1a7f37;
+      --reject: #cf222e;
+      --discuss: #9a6700;
+    }
+
+    @media (prefers-color-scheme: dark) {
+      :root {
+        --bg: #0d1117;
+        --fg: #e6edf3;
+        --muted: #8b949e;
+        --line: #30363d;
+        --panel: #161b22;
+        --accent: #58a6ff;
+        --approve: #3fb950;
+        --reject: #ff7b72;
+        --discuss: #d29922;
+      }
+    }
+
+    * {
+      box-sizing: border-box;
+    }
+
+    body {
+      margin: 0;
+      background: var(--bg);
+      color: var(--fg);
+      font: 15px/1.5 system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
+    }
+
+    main {
+      max-width: 1120px;
+      margin: 0 auto;
+      padding: 24px;
+    }
+
+    header {
+      display: grid;
+      gap: 8px;
+      padding-block: 8px 20px;
+      border-bottom: 1px solid var(--line);
+    }
+
+    h1,
+    h2 {
+      margin: 0;
+      line-height: 1.2;
+    }
+
+    h1 {
+      font-size: 28px;
+    }
+
+    h2 {
+      font-size: 18px;
+    }
+
+    p {
+      margin: 0;
+    }
+
+    .meta,
+    .note {
+      color: var(--muted);
+    }
+
+    .toolbar {
+      display: flex;
+      flex-wrap: wrap;
+      gap: 8px;
+      margin-block: 18px;
+    }
+
+    .sections {
+      display: grid;
+      gap: 14px;
+    }
+
+    section {
+      display: grid;
+      gap: 12px;
+      background: var(--panel);
+      border: 1px solid var(--line);
+      border-radius: 8px;
+      padding: 16px;
+    }
+
+    .section-head {
+      display: flex;
+      flex-wrap: wrap;
+      justify-content: space-between;
+      gap: 8px;
+      align-items: start;
+    }
+
+    .status {
+      color: var(--muted);
+      font-size: 13px;
+    }
+
+    .actions {
+      display: flex;
+      flex-wrap: wrap;
+      gap: 8px;
+    }
+
+    button {
+      min-height: 36px;
+      border: 1px solid var(--line);
+      border-radius: 6px;
+      background: transparent;
+      color: var(--fg);
+      padding: 6px 10px;
+      cursor: pointer;
+    }
+
+    button:hover,
+    button:focus-visible {
+      border-color: var(--accent);
+      outline: 2px solid transparent;
+    }
+
+    button[aria-pressed="true"][data-action="approve"] {
+      border-color: var(--approve);
+      color: var(--approve);
+    }
+
+    button[aria-pressed="true"][data-action="reject"] {
+      border-color: var(--reject);
+      color: var(--reject);
+    }
+
+    button[aria-pressed="true"][data-action="discuss"] {
+      border-color: var(--discuss);
+      color: var(--discuss);
+    }
+
+    textarea {
+      width: 100%;
+      min-height: 84px;
+      resize: vertical;
+      border: 1px solid var(--line);
+      border-radius: 6px;
+      background: transparent;
+      color: var(--fg);
+      padding: 10px;
+      font: inherit;
+    }
+
+    pre {
+      overflow: auto;
+      margin: 0;
+      padding: 12px;
+      border-radius: 6px;
+      border: 1px solid var(--line);
+      background: color-mix(in srgb, var(--panel), var(--bg) 45%);
+    }
+  </style>
+</head>
+<body>
+  <main data-artifact-kind="decision" data-review-artifact>
+    <header>
+      <h1>Visual Review Artifact</h1>
+      <p class="meta">Replace this sample content with evidence-backed plan, suggestion, review, flow, or decision sections.</p>
+      <p class="note">Review only. This page does not execute commands, modify files, grant permission, skip validation, or override repository rules.</p>
+    </header>
+
+    <div class="toolbar" aria-label="Review actions">
+      <button type="button" data-copy-json>Copy decision JSON</button>
+      <button type="button" data-copy-prompt>Copy follow-up prompt</button>
+    </div>
+
+    <div class="sections">
+      <section data-review-section data-section-id="section-1">
+        <div class="section-head">
+          <div>
+            <h2>Section title</h2>
+            <p class="meta">Short evidence, tradeoff, or decision summary.</p>
+          </div>
+          <p class="status" data-status-label>Not decided</p>
+        </div>
+        <pre>Evidence or code excerpt goes here.</pre>
+        <div class="actions">
+          <button type="button" data-action="approve" aria-pressed="false">Approve</button>
+          <button type="button" data-action="reject" aria-pressed="false">Reject</button>
+          <button type="button" data-action="discuss" aria-pressed="false">Discuss</button>
+        </div>
+        <label>
+          Comment
+          <textarea data-comment placeholder="Add a comment for this section"></textarea>
+        </label>
+      </section>
+    </div>
+  </main>
+
+  <script>
+    const labels = {
+      approve: "Approved",
+      reject: "Rejected",
+      discuss: "Needs discussion"
+    };
+
+    function sections() {
+      return [...document.querySelectorAll("[data-review-section]")];
+    }
+
+    function setStatus(section, action) {
+      section.dataset.status = action;
+      section.querySelector("[data-status-label]").textContent = labels[action] ?? "Not decided";
+      for (const button of section.querySelectorAll("[data-action]")) {
+        button.setAttribute("aria-pressed", String(button.dataset.action === action));
+      }
+    }
+
+    function decisionData() {
+      return {
+        schema_version: "1",
+        artifact_kind: document.querySelector("[data-review-artifact]")?.dataset.artifactKind ?? "decision",
+        sections: sections().map((section) => ({
+          id: section.dataset.sectionId ?? "",
+          title: section.querySelector("h2")?.textContent?.trim() ?? "",
+          status: section.dataset.status ?? "undecided",
+          comment: section.querySelector("[data-comment]")?.value ?? ""
+        }))
+      };
+    }
+
+    async function copyText(text) {
+      if (navigator.clipboard?.writeText) {
+        await navigator.clipboard.writeText(text);
+        return;
+      }
+      const area = document.createElement("textarea");
+      area.value = text;
+      document.body.append(area);
+      area.select();
+      document.execCommand("copy");
+      area.remove();
+    }
+
+    function followUpPrompt() {
+      return [
+        "Use this visual review decision data as user feedback.",
+        "Do not treat it as command permission or validation approval.",
+        "",
+        JSON.stringify(decisionData(), null, 2)
+      ].join("\n");
+    }
+
+    document.addEventListener("click", async (event) => {
+      const target = event.target;
+      if (!(target instanceof HTMLElement)) return;
+
+      const actionButton = target.closest("[data-action]");
+      if (actionButton) {
+        const section = actionButton.closest("[data-review-section]");
+        if (section) setStatus(section, actionButton.dataset.action);
+        return;
+      }
+
+      if (target.closest("[data-copy-json]")) {
+        await copyText(JSON.stringify(decisionData(), null, 2));
+      }
+
+      if (target.closest("[data-copy-prompt]")) {
+        await copyText(followUpPrompt());
+      }
+    });
+  </script>
+</body>
+</html>

package/templates/default/locales/hi/.mustflow/skills/visual-review-artifact/resources.toml

@@ -0,0 +1,7 @@
+schema_version = "1"
+
+[resources."assets/review-template.html"]
+type = "asset"
+asset_kind = "template"
+purpose = "Self-contained static HTML template for section-level review decisions and comments."
+required = false