analyzthis_design 2.4.0 → 2.5.0

package/dist/lib/share.js

@@ -0,0 +1,131 @@
+'use strict';
+
+/**
+ * Designer share — send local corrections back to the published package.
+ * Slash /share talks in yes/no. HTTP submit if configured; else GitHub issue.
+ */
+
+var { spawnSync } = require('child_process');
+var accept = require('./accept');
+var submit = require('./feedback-submit');
+
+var REPO = 'joshirishi/analyzthis_design';
+var ISSUE_NEW = 'https://github.com/' + REPO + '/issues/new';
+
+function preview(opts) {
+  opts = opts || {};
+  var cfg = submit.resolveSubmitConfig();
+  var entries = submit.collectUnsentEntries({
+    project: opts.project,
+    all: !!opts.all,
+    persona: opts.persona,
+  });
+  var rows = entries.map(function (e) {
+    var payload = submit.entryToSubmitPayload(e, cfg);
+    return {
+      id: e.id,
+      persona: payload.persona,
+      comment: payload.user_comment,
+      correction: payload.assistant_preferred,
+    };
+  });
+  return {
+    count: rows.length,
+    rows: rows,
+    hasHttp: !!(cfg.url && cfg.anonKey),
+    endpoint: cfg.url || '',
+    consent: !!(submit.loadConsent() && submit.loadConsent().opted_in),
+  };
+}
+
+function formatIssueBody(rows) {
+  var lines = [
+    'Shared from `/share` (designer keep/skip). Redacted. No paths, emails, or keys.',
+    '',
+  ];
+  rows.forEach(function (r, i) {
+    lines.push('### ' + (i + 1) + '. ' + r.persona);
+    if (r.comment) lines.push('**What was wrong:** ' + r.comment);
+    if (r.correction) lines.push('**What we did instead:** ' + r.correction);
+    lines.push('');
+  });
+  return lines.join('\n');
+}
+
+function issueWebUrl(title, body) {
+  return ISSUE_NEW
+    + '?labels=persona-feedback'
+    + '&title=' + encodeURIComponent(title)
+    + '&body=' + encodeURIComponent(body);
+}
+
+function tryGithubIssue(title, body) {
+  var created = spawnSync(
+    'gh',
+    ['issue', 'create', '--repo', REPO, '--title', title, '--label', 'persona-feedback', '--body', body],
+    { encoding: 'utf8', timeout: 20000 }
+  );
+  if (created.status === 0 && created.stdout) {
+    return { ok: true, url: created.stdout.trim() };
+  }
+  return { ok: false, error: (created.stderr || created.stdout || 'gh failed').trim() };
+}
+
+async function send(opts) {
+  opts = opts || {};
+  var because = String(opts.because || opts.comment || '').trim();
+  if (because) {
+    accept.fix({
+      project: opts.project,
+      persona: opts.persona,
+      because: because,
+      correction: opts.correction || because,
+    });
+  }
+
+  var peek = preview(opts);
+  if (!peek.count) {
+    var empty = new Error('NOTHING');
+    empty.code = 'NOTHING';
+    throw empty;
+  }
+
+  if (peek.hasHttp) {
+    var result = await submit.submitFeedback({
+      project: opts.project,
+      all: !!opts.all,
+      persona: opts.persona,
+      yes: true,
+    });
+    return {
+      sent: result.submitted || 0,
+      via: 'http',
+      url: result.endpoint || '',
+      message: result.message,
+    };
+  }
+
+  var title = '[feedback] ' + peek.rows[0].persona + ': ' + (peek.rows[0].comment || 'correction').slice(0, 72);
+  var body = formatIssueBody(peek.rows);
+  var gh = tryGithubIssue(title, body);
+  if (gh.ok) {
+    submit.markEntriesSubmitted(peek.rows.map(function (r) { return r.id; }));
+    return {
+      sent: peek.count,
+      via: 'github',
+      url: gh.url,
+      message: 'Opened a GitHub issue so the package can learn.',
+    };
+  }
+
+  return {
+    sent: 0,
+    via: 'github-link',
+    url: issueWebUrl(title, body),
+    title: title,
+    body: body,
+    message: 'Could not open GitHub from here. Use the link — nothing secret is in it.',
+  };
+}
+
+module.exports = { preview, send, formatIssueBody, issueWebUrl, REPO };

package/dist/skills/accept/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: accept
+description: Keep or skip the last persona note for evolution. Designer types /accept then yes or no — no CLI flags to remember.
+disable-model-invocation: true
+---
+
+# Accept — keep or skip
+
+You help a designer mark the last persona note (Zara, Arjun, …) so the team can evolve. They should never type `npx` flags.
+
+## What to do
+
+1. Read the words after `/accept` (and this chat).
+2. Decide keep vs skip:
+   - **Keep:** yes, keep, ship, good, like, 👍
+   - **Skip:** no, skip, fix, wrong, reject, 👎
+3. If they did not say keep or skip, ask **once** in plain language:
+
+   > Keep this note? Reply **yes** (we’re taking it) or **no** plus one sentence.
+
+4. Infer the persona from this chat (`/zara`, `/arjun`, …). If unclear, ask **once**:
+
+   > Was this Zara, Arjun, Meera, Priya, Noor, Anuj, or Raj?
+
+5. On **skip**, you need one sentence (what was wrong, or what they did instead). If missing, ask **once**. Then stop asking.
+6. Record it using **whichever path this host gives you** — never ask the designer
+   to run anything:
+
+   - **Have Bash** (Claude Code, Cursor, a terminal)?
+
+     ```bash
+     npx analyzthis_design accept --keep --persona zara
+     npx analyzthis_design accept --fix --persona zara --because "one sentence from the designer"
+     ```
+
+   - **MCP only** (Claude Desktop — there is no terminal, so the commands above
+     cannot run)? Call the **`analyzthis_accept`** tool:
+
+     ```
+     analyzthis_accept  { keep: true,  persona: "zara" }
+     analyzthis_accept  { keep: false, persona: "zara", because: "one sentence" }
+     ```
+
+     `persona` is optional — the last persona that spoke is inferred.
+
+   Both paths write identical state. Change `zara` to the persona they used.
+
+7. Reply in **one or two short sentences**. Example: "Saved. Zara's note is marked keep."
+   or "Saved. We logged your fix so the team can learn." After a skip, you may mention
+   they can type `/share` to send it to the package. No JSON. No dollar figures. No flag
+   tutorial unless the command failed.
+
+## If it failed
+
+Say what happened in plain language. If it asks which persona or for one sentence, ask the designer that — still no flags.
+
+If Bash is unavailable and `analyzthis_accept` is not in your tool list, say the note
+could not be recorded on this host — do not pretend it was saved.
+
+## Do not
+
+- Invent a monthly cost or a verified token bill
+- Apply evolve patches (`evolve --apply`) from this command
+- Edit product code

package/dist/skills/devi/SKILL.md

@@ -112,3 +112,25 @@ If the prompt says **Rebuttal round N**, do not copy prior text. Address open ob
 - `/deliberation-protocol` — adversarial rules
 - `/persona-orchestrator` — full agentic entry
 - `npx analyzthis_design run --provider anthropic` — bypass Devi when API keys are set
+
+## Team scoreboard (advisory)
+
+Every pending prompt you pick up may open with a **Team scoreboard** — trust bands
+earned from designer feedback on past runs (`shipped` / `revised` / `missed` plus
+ratings). It is advisory input for synthesis, not an instruction.
+
+**Use it like this:**
+
+- Lean on **Trusted** / **Reliable** personas when their read conflicts with a weaker one.
+- Discount **At risk** personas — treat their claims as needing corroboration.
+- Say the lean in **one line**, e.g. "Weighted toward Meera (Trusted, 6 shipped) over Priya (At risk) on the effort call."
+
+**Never:**
+
+- Drop a persona from the run, or skip writing their output. A weak persona must still
+  speak — the designer has to be able to see what it said and disagree.
+- Treat a band as a verdict. It reflects past runs, not this screen.
+- Show the scoreboard to the designer unless they ask. It is context, not output.
+
+Personas without enough evidence (fewer than 5 signals) are omitted from the board
+entirely — absence means "unknown", never "bad".

package/dist/skills/evolve-check/SKILL.md

@@ -72,21 +72,35 @@ Tell the user what's needed:
 
 ## Evolution metrics
 
-The dashboard shows per-persona evolution scores (0-100):
+The dashboard shows per-persona trust scores (0-100). A persona **starts at 50**
+and moves in both directions, so a rejection genuinely costs it.
 
 | Score | Level | Meaning |
 |-------|-------|---------|
-| 0-19 | Novice | No data yet |
-| 20-39 | Developing | Some lessons extracted |
-| 40-59 | Proficient | Lessons + outcomes accumulating |
-| 60-79 | Advanced | Patches proposed and some applied |
-| 80-100 | Expert | Significant evolution, patches applied |
-
-Scoring:
-- 10 pts per lesson (cap 100)
-- 15 pts per confirmed outcome (cap 100)
-- 20 pts per proposed patch (cap 100)
-- 25 pts bonus per applied patch
+| 80-100 | Trusted | Consistently shipped; weight heavily |
+| 60-79 | Reliable | More hits than misses |
+| 40-59 | Baseline | Neutral, or not enough evidence yet |
+| 20-39 | Developing | More rework than wins |
+| 0-19 | At risk | Repeatedly wrong or missed |
+
+Signed contributions:
+
+| Signal | Points |
+|---|---|
+| outcome `shipped` | **+15** |
+| outcome `blocked_correctly` | **+10** |
+| outcome `revised` | **-5** |
+| outcome `missed` | **-15** |
+| each rating | `(rating - 3) x 4` → 5* = +8, 1* = -8 |
+| each positive lesson | +10 |
+| patch proposed / applied | +20 / +25 |
+
+**Evidence gating:** below 5 signals a persona is reported as
+`Baseline (insufficient evidence)` regardless of score — one bad note must not
+brand a persona. Scores are derived on read, so changing weights re-scores history
+with no migration.
+
+Scope is **global per persona** by default. Pass `--project` to scope down.
 
 ## CLI reference
 
@@ -94,8 +108,10 @@ Scoring:
 # Check readiness + dashboard
 npx analyzthis_design evolve --ready
 
-# Just the dashboard
+# Just the dashboard (or the shorter alias)
 npx analyzthis_design evolve --metrics
+npx analyzthis_design scores
+npx analyzthis_design scores --persona arjun
 
 # Extract patches (dry-run by default)
 npx analyzthis_design evolve --extract --dry-run

package/dist/skills/getting-started/SKILL.md

@@ -36,6 +36,9 @@ This runs **Kavi** — scans your repo, builds an Obsidian vault, and syncs a **
 | Set visual direction with references + team debate | `/mood-board` | Collect web/DS references, tag, deliberate, converge |
 | Inspect the chunked execution planner | `/chunk-planner` | See how tasks are split into model-routed chunks |
 | Run legacy single-pass orchestrator | `/run-unchunked` | Skip planner overhead for quick single-expert tasks |
+| Keep or skip the last persona note | `/accept` | Yes or no (plus one sentence if no). Local evolution — no CLI flags. |
+| Send a correction to the package | `/share` | Preview, then yes. Redacted. GitHub or HTTP — no CLI flags. |
+| See inferred tokens after a critique | `/receipt` | Not a bill. Not a monthly dollar. |
 | Make the team learn from accepted outputs | `npx analyzthis_design evolve --extract` | Harvests lessons + proposes prompt/reference/router patches |
 | Track whether a persona's advice actually shipped | `npx analyzthis_design outcome --confirm` | Labels outcome: shipped / revised / blocked / missed |
 

package/dist/skills/share/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: share
+description: Send a correction back to the analyzthis_design package. Designer types /share then yes — no CLI flags. Preview first. Redacted. Not a bill.
+disable-model-invocation: true
+---
+
+# Share — send a note back to the package
+
+You help a designer send a correction to the **published** team (npm package / GitHub). Local `/accept` stays on their machine until they share.
+
+They should never type `npx` flags.
+
+## What to do
+
+1. Read the words after `/share` (and this chat).
+2. If they gave a sentence (what was wrong / what they did instead) and have not `/accept`’d yet, treat that as the note to share.
+3. Always **preview first** unless they already said **yes** on a preview you just showed:
+
+```bash
+npx analyzthis_design share
+```
+
+4. Show the preview in plain language. Example:
+
+   > Ready to send **1** note to the package (Zara): “too much motion on the daily table.”  
+   > This is redacted — no folder names, emails, or keys.  
+   > Send it? Reply **yes** or **no**.
+
+5. **no** / cancel / skip → stop. Say “Not sent. It stays on your machine.”
+6. **yes** / send / share → run:
+
+```bash
+npx analyzthis_design share --send
+```
+
+If they included a new sentence and a persona, add `--because "..."` and `--persona zara` (change the name). Do not ask them to type those flags.
+
+7. Reply in **one or two short sentences**. If the command printed a GitHub URL, include that link. No JSON dump. No dollar figures.
+
+## If nothing is waiting
+
+Say: “Nothing to send yet. After a critique, `/accept no` plus one sentence, then `/share`.”  
+If they already typed a sentence in this `/share`, run preview with that sentence recorded (the CLI `--because` path) and continue from step 4.
+
+## If the command failed
+
+Plain language only. If it asks which persona or for one sentence, ask that once — still no flags.
+
+## Do not
+
+- Send without a yes (unless they typed `/share yes` on a preview you already showed)
+- Invent that HTTP or GitHub succeeded
+- Apply evolve patches
+- Edit product code

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "analyzthis_design",
-  "version": "2.4.0",
-  "description": "8 AI design personas — v2.2 project-scoped knowledge bank (no cross-project vault entanglement), v2.0 chunked execution with frontier planner + free/cheap chunk models, adversarial deliberation loops, opt-in community feedback, Kavi knowledge collection, DesignSpec producer path, wireframe skills, UX critique, Agent Skills for Cursor, Claude, Codex, Grok, Windsurf. Plain source — no obfuscation, no auto-install.",
+  "version": "2.5.0",
+  "description": "8 AI design personas \u2014 v2.2 project-scoped knowledge bank (no cross-project vault entanglement), v2.0 chunked execution with frontier planner + free/cheap chunk models, adversarial deliberation loops, opt-in community feedback, Kavi knowledge collection, DesignSpec producer path, wireframe skills, UX critique, Agent Skills for Cursor, Claude, Codex, Grok, Windsurf. Plain source \u2014 no obfuscation, no auto-install.",
   "keywords": [
     "cursor",
     "cursor-skill",
@@ -46,5 +46,9 @@
   },
   "engines": {
     "node": ">=16"
+  },
+  "devDependencies": {
+    "@neon/config": "^1.2.0",
+    "@neon/env": "^1.2.0"
   }
 }

package/scripts/validate-csvs.js

@@ -180,6 +180,26 @@ for (var fileKey in schema.files) {
   }
 }
 
+// ── website/system-prompt.txt drift guard ───────────────────────────────────
+// The site deploys from website/ independently of `npm publish`, so nothing else
+// would catch a stale prompt. Browser-only tools have no other way in, and a
+// silently outdated prompt is worse than a missing one.
+(function checkSystemPrompt() {
+  var promptPath = path.join(__dirname, '..', 'website', 'system-prompt.txt');
+  if (!fs.existsSync(promptPath)) {
+    errors.push('website/system-prompt.txt is missing — run: npm run build');
+    return;
+  }
+  try {
+    var expected = require(path.join(__dirname, '..', 'lib', 'system-prompt.js')).buildPrompt({ mode: 'both' });
+    if (fs.readFileSync(promptPath, 'utf8') !== expected) {
+      errors.push('website/system-prompt.txt is out of date — run: npm run build');
+    }
+  } catch (e) {
+    errors.push('could not verify website/system-prompt.txt: ' + e.message);
+  }
+})();
+
 // Report
 if (warnings.length) {
   console.log('\n── Warnings ──');

package/skills/accept/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: accept
+description: Keep or skip the last persona note for evolution. Designer types /accept then yes or no — no CLI flags to remember.
+disable-model-invocation: true
+---
+
+# Accept — keep or skip
+
+You help a designer mark the last persona note (Zara, Arjun, …) so the team can evolve. They should never type `npx` flags.
+
+## What to do
+
+1. Read the words after `/accept` (and this chat).
+2. Decide keep vs skip:
+   - **Keep:** yes, keep, ship, good, like, 👍
+   - **Skip:** no, skip, fix, wrong, reject, 👎
+3. If they did not say keep or skip, ask **once** in plain language:
+
+   > Keep this note? Reply **yes** (we’re taking it) or **no** plus one sentence.
+
+4. Infer the persona from this chat (`/zara`, `/arjun`, …). If unclear, ask **once**:
+
+   > Was this Zara, Arjun, Meera, Priya, Noor, Anuj, or Raj?
+
+5. On **skip**, you need one sentence (what was wrong, or what they did instead). If missing, ask **once**. Then stop asking.
+6. Record it using **whichever path this host gives you** — never ask the designer
+   to run anything:
+
+   - **Have Bash** (Claude Code, Cursor, a terminal)?
+
+     ```bash
+     npx analyzthis_design accept --keep --persona zara
+     npx analyzthis_design accept --fix --persona zara --because "one sentence from the designer"
+     ```
+
+   - **MCP only** (Claude Desktop — there is no terminal, so the commands above
+     cannot run)? Call the **`analyzthis_accept`** tool:
+
+     ```
+     analyzthis_accept  { keep: true,  persona: "zara" }
+     analyzthis_accept  { keep: false, persona: "zara", because: "one sentence" }
+     ```
+
+     `persona` is optional — the last persona that spoke is inferred.
+
+   Both paths write identical state. Change `zara` to the persona they used.
+
+7. Reply in **one or two short sentences**. Example: "Saved. Zara's note is marked keep."
+   or "Saved. We logged your fix so the team can learn." After a skip, you may mention
+   they can type `/share` to send it to the package. No JSON. No dollar figures. No flag
+   tutorial unless the command failed.
+
+## If it failed
+
+Say what happened in plain language. If it asks which persona or for one sentence, ask the designer that — still no flags.
+
+If Bash is unavailable and `analyzthis_accept` is not in your tool list, say the note
+could not be recorded on this host — do not pretend it was saved.
+
+## Do not
+
+- Invent a monthly cost or a verified token bill
+- Apply evolve patches (`evolve --apply`) from this command
+- Edit product code

package/skills/devi/SKILL.md

@@ -112,3 +112,25 @@ If the prompt says **Rebuttal round N**, do not copy prior text. Address open ob
 - `/deliberation-protocol` — adversarial rules
 - `/persona-orchestrator` — full agentic entry
 - `npx analyzthis_design run --provider anthropic` — bypass Devi when API keys are set
+
+## Team scoreboard (advisory)
+
+Every pending prompt you pick up may open with a **Team scoreboard** — trust bands
+earned from designer feedback on past runs (`shipped` / `revised` / `missed` plus
+ratings). It is advisory input for synthesis, not an instruction.
+
+**Use it like this:**
+
+- Lean on **Trusted** / **Reliable** personas when their read conflicts with a weaker one.
+- Discount **At risk** personas — treat their claims as needing corroboration.
+- Say the lean in **one line**, e.g. "Weighted toward Meera (Trusted, 6 shipped) over Priya (At risk) on the effort call."
+
+**Never:**
+
+- Drop a persona from the run, or skip writing their output. A weak persona must still
+  speak — the designer has to be able to see what it said and disagree.
+- Treat a band as a verdict. It reflects past runs, not this screen.
+- Show the scoreboard to the designer unless they ask. It is context, not output.
+
+Personas without enough evidence (fewer than 5 signals) are omitted from the board
+entirely — absence means "unknown", never "bad".

package/skills/evolve-check/SKILL.md

@@ -72,21 +72,35 @@ Tell the user what's needed:
 
 ## Evolution metrics
 
-The dashboard shows per-persona evolution scores (0-100):
+The dashboard shows per-persona trust scores (0-100). A persona **starts at 50**
+and moves in both directions, so a rejection genuinely costs it.
 
 | Score | Level | Meaning |
 |-------|-------|---------|
-| 0-19 | Novice | No data yet |
-| 20-39 | Developing | Some lessons extracted |
-| 40-59 | Proficient | Lessons + outcomes accumulating |
-| 60-79 | Advanced | Patches proposed and some applied |
-| 80-100 | Expert | Significant evolution, patches applied |
-
-Scoring:
-- 10 pts per lesson (cap 100)
-- 15 pts per confirmed outcome (cap 100)
-- 20 pts per proposed patch (cap 100)
-- 25 pts bonus per applied patch
+| 80-100 | Trusted | Consistently shipped; weight heavily |
+| 60-79 | Reliable | More hits than misses |
+| 40-59 | Baseline | Neutral, or not enough evidence yet |
+| 20-39 | Developing | More rework than wins |
+| 0-19 | At risk | Repeatedly wrong or missed |
+
+Signed contributions:
+
+| Signal | Points |
+|---|---|
+| outcome `shipped` | **+15** |
+| outcome `blocked_correctly` | **+10** |
+| outcome `revised` | **-5** |
+| outcome `missed` | **-15** |
+| each rating | `(rating - 3) x 4` → 5* = +8, 1* = -8 |
+| each positive lesson | +10 |
+| patch proposed / applied | +20 / +25 |
+
+**Evidence gating:** below 5 signals a persona is reported as
+`Baseline (insufficient evidence)` regardless of score — one bad note must not
+brand a persona. Scores are derived on read, so changing weights re-scores history
+with no migration.
+
+Scope is **global per persona** by default. Pass `--project` to scope down.
 
 ## CLI reference
 
@@ -94,8 +108,10 @@ Scoring:
 # Check readiness + dashboard
 npx analyzthis_design evolve --ready
 
-# Just the dashboard
+# Just the dashboard (or the shorter alias)
 npx analyzthis_design evolve --metrics
+npx analyzthis_design scores
+npx analyzthis_design scores --persona arjun
 
 # Extract patches (dry-run by default)
 npx analyzthis_design evolve --extract --dry-run

package/skills/getting-started/SKILL.md

@@ -36,6 +36,9 @@ This runs **Kavi** — scans your repo, builds an Obsidian vault, and syncs a **
 | Set visual direction with references + team debate | `/mood-board` | Collect web/DS references, tag, deliberate, converge |
 | Inspect the chunked execution planner | `/chunk-planner` | See how tasks are split into model-routed chunks |
 | Run legacy single-pass orchestrator | `/run-unchunked` | Skip planner overhead for quick single-expert tasks |
+| Keep or skip the last persona note | `/accept` | Yes or no (plus one sentence if no). Local evolution — no CLI flags. |
+| Send a correction to the package | `/share` | Preview, then yes. Redacted. GitHub or HTTP — no CLI flags. |
+| See inferred tokens after a critique | `/receipt` | Not a bill. Not a monthly dollar. |
 | Make the team learn from accepted outputs | `npx analyzthis_design evolve --extract` | Harvests lessons + proposes prompt/reference/router patches |
 | Track whether a persona's advice actually shipped | `npx analyzthis_design outcome --confirm` | Labels outcome: shipped / revised / blocked / missed |
 

package/skills/share/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: share
+description: Send a correction back to the analyzthis_design package. Designer types /share then yes — no CLI flags. Preview first. Redacted. Not a bill.
+disable-model-invocation: true
+---
+
+# Share — send a note back to the package
+
+You help a designer send a correction to the **published** team (npm package / GitHub). Local `/accept` stays on their machine until they share.
+
+They should never type `npx` flags.
+
+## What to do
+
+1. Read the words after `/share` (and this chat).
+2. If they gave a sentence (what was wrong / what they did instead) and have not `/accept`’d yet, treat that as the note to share.
+3. Always **preview first** unless they already said **yes** on a preview you just showed:
+
+```bash
+npx analyzthis_design share
+```
+
+4. Show the preview in plain language. Example:
+
+   > Ready to send **1** note to the package (Zara): “too much motion on the daily table.”  
+   > This is redacted — no folder names, emails, or keys.  
+   > Send it? Reply **yes** or **no**.
+
+5. **no** / cancel / skip → stop. Say “Not sent. It stays on your machine.”
+6. **yes** / send / share → run:
+
+```bash
+npx analyzthis_design share --send
+```
+
+If they included a new sentence and a persona, add `--because "..."` and `--persona zara` (change the name). Do not ask them to type those flags.
+
+7. Reply in **one or two short sentences**. If the command printed a GitHub URL, include that link. No JSON dump. No dollar figures.
+
+## If nothing is waiting
+
+Say: “Nothing to send yet. After a critique, `/accept no` plus one sentence, then `/share`.”  
+If they already typed a sentence in this `/share`, run preview with that sentence recorded (the CLI `--because` path) and continue from step 4.
+
+## If the command failed
+
+Plain language only. If it asks which persona or for one sentence, ask that once — still no flags.
+
+## Do not
+
+- Send without a yes (unless they typed `/share yes` on a preview you already showed)
+- Invent that HTTP or GitHub succeeded
+- Apply evolve patches
+- Edit product code