analyzthis_design 2.4.0 → 2.5.0

package/HOW-TO-USE.md

@@ -313,21 +313,39 @@ Each persona reads the session state, so you do not need to repeat the task.
 
 ## 8. After the run — accept, reject, evolve
 
-### Mark an output accepted
+### Designer path (remember this)
 
-```bash
-npx analyzthis_design session accept --persona arjun
+In chat, after `/zara` or any persona:
+
+```
+/accept yes
+```
+
+or
+
+```
+/accept no — too much motion on the daily table
 ```
 
-### Reject with correction
+No terminal flags. `/accept` writes keep or skip for **local** evolution.
+
+To send a correction to the published package:
+
+```
+/share
+```
+
+Then **yes** if the preview looks right. Redacted — no folder names, emails, or keys.
+
+### CLI (same thing, if you prefer the terminal)
 
 ```bash
-npx analyzthis_design session accept --persona arjun --reject \
-  --comment "Invented tokens not in our DS" \
-  --correction "Use --color-primary and spacing-4 from tokens.css" \
-  --rating 2 --tags invented_tokens,missed_ds
+npx analyzthis_design accept --keep --persona arjun
+npx analyzthis_design accept --fix --persona arjun --because "Invented tokens — use tokens.css"
 ```
 
+The older `session accept` / `feedback record` flags still work.
+
 ### Make the team learn
 
 ```bash

package/README.md

@@ -4,6 +4,43 @@ A set of AI design personas and a task-first evaluation framework that plugs int
 
 Install once. Run structured UX critiques, multi-phase ideation, and task-grounded screen reviews — directly inside your AI chat. **No external LLM API keys required** for CLI orchestrator runs: **`/devi`** voices each persona from your host IDE (Cursor, Claude, etc.).
 
+## v2.5.0 — personas earn or lose trust
+
+Marking a note now moves a score. Previously a rejection *raised* a persona's score by
+15 — `accept.fix()` recorded `outcome: 'revised'` and scoring counted outcomes without
+reading their value. Punishment was a reward. Fixed.
+
+- **Signed, rate-based scoring.** A persona starts at 50 and moves both ways:
+  `shipped` +15, `blocked_correctly` +10, `revised` −5, `missed` −15, plus
+  `(rating − 3) x 4` per rating. Scored as a **rate per signal**, not a running total,
+  so early wins can never make a persona immune to later failures.
+- **Evidence gating.** Under 5 signals a persona reads `Baseline (insufficient
+  evidence)`. One bad note does not brand anyone.
+- **Bands:** At risk · Developing · Baseline · Reliable · Trusted.
+- **Devi gets a scoreboard** in every pending prompt and weights its synthesis,
+  saying the lean in one line. Advisory only — **no persona is ever dropped from a run.**
+- **Feedback works with no terminal.** New `analyzthis_accept` MCP tool in the
+  **lite** catalog, so Claude Desktop can record keep/skip. Same shared core as the
+  CLI — both transports write identical state.
+- **The persona asks.** Every note ends with one host-neutral line: *"Was this right?
+  Say yes, or no plus one sentence."* The designer answers in plain language; the
+  agent picks the transport. No flags, ever.
+- **Lessons learn from rejections too**, tagged `polarity`, and de-duplicated so
+  re-marking a note cannot inflate a score.
+
+```bash
+npx analyzthis_design scores                  # the whole team
+npx analyzthis_design scores --persona arjun  # one persona, with the breakdown
+```
+
+Scores are derived on read — changing the weights re-scores history with no migration.
+
+## v2.4.1 — `/accept` and `/share` (designer keep / skip / send)
+
+After `/zara` (or any persona), type `/accept yes` or `/accept no` plus one sentence. No CLI flags. Writes keep or skip for **local** evolution. Slash-only notes still count.
+
+To send a correction to the **published** package: `/share` (preview) then `/share yes`. Redacted. Uses the HTTP endpoint if configured; otherwise a GitHub issue on joshirishi/analyzthis_design.
+
 ## v2.4.0 — Claude-path efficiency (1 Sep 2026)
 
 Same SHIP / REVISE / BLOCK. Fewer tokens on Claude Code and Claude Desktop. Not Caveman-speak. Not a proxy.
@@ -48,7 +85,7 @@ Pass `--global` to opt into the legacy merged behavior (read `config.sources` an
 
 Use `npx analyzthis_design run-unchunked` for the legacy single-pass orchestrator.
 
-**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.4.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
+**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.5.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
 
 ---
 
@@ -74,7 +111,7 @@ npx analyzthis_design run-unchunked --task "Review invoice approval screen" --pr
 
 > **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design install --target <ide>` (or `npx analyzthis_design --target <ide>`).
 >
-> **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. For Lovable, v0, Bolt, Replit, ChatGPT: run `npx analyzthis_design mcp --configure <tool>` for a config snippet.
+> **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. **Browser-only tools (Lovable, v0, Bolt, Replit, ChatGPT) cannot use MCP here** — our server speaks stdio, and a cloud-hosted tool cannot spawn a process on your machine. Paste the team in instead: `npx analyzthis_design system-prompt --mode both`, or copy it with one click from [the tool picker](https://analyzthis-lab.vercel.app/design#install-lovable). Note the paste path gives you the personas but no `/accept`, lessons, or trust scores — those need local state.
 
 ### Install by target IDE
 
@@ -149,6 +186,9 @@ Invoke critique personas for targeted, already-grounded questions. For **wirefra
 | `/knowledge-bank` | Auto-populated from your connected vault (or from Kavi collect). All personas read this first. |
 | `/design-reference` | CSV reference data (colors, typography, UX guidelines, stacks, …) |
 | `/collect-knowledge` | Alias for `/kavi` |
+| `/accept` | Keep or skip the last persona note (yes / no). Local evolution — no CLI flags. |
+| `/share` | Send a correction to the package (preview, then yes). Redacted. |
+| `/receipt` | Inferred token receipt for this project. Not a bill. |
 
 ---
 
@@ -742,6 +782,10 @@ npx analyzthis_design status
 
 # Session (agentic)
 npx analyzthis_design session init|show|reset [--project id] [--all]
+npx analyzthis_design accept --keep [--persona zara]          # designer keep (slash: /accept yes)
+npx analyzthis_design accept --fix --because "one sentence"   # designer skip (slash: /accept no)
+npx analyzthis_design share                                   # preview notes for the package
+npx analyzthis_design share --send                            # send (slash: /share yes)
 npx analyzthis_design session accept --persona <id> [--reject] [--comment "..."] [--correction "..."] [--rating 1-5] [--tags a,b]
 
 # Persona feedback (v1.16)
@@ -880,7 +924,7 @@ skills/
 |---------|-------------|
 | **MCP server** | `npx analyzthis_design mcp` starts a local MCP server exposing 19 tools — all 8 individual personas + 6 combination passes + 5 utilities. Any MCP-compatible client can discover and call them. |
 | **Auto-configure MCP** | `npx analyzthis_design mcp --configure cursor` (or `claude`, `windsurf`) writes the MCP config automatically. `--target all` now auto-configures MCP during install. |
-| **Universal IDE support** | Cursor, Claude Desktop, Windsurf auto-configured. Lovable, v0, Bolt, Replit, ChatGPT: run `mcp --configure <tool>` for a copy-paste config snippet. |
+| **Universal IDE support** | Cursor, Claude Code, Claude Desktop, Windsurf auto-configured via MCP. Lovable, v0, Bolt, Replit, ChatGPT install nothing — paste `system-prompt` output into the tool's instructions. |
 | **MCP lite + full** | Default: router (`analyzthis_design`) + retrieve + session + receipt. Full 19 named tools behind `--catalog full`. |
 | **System prompt fallback** | `analyzthis_system_prompt` tool generates a consolidated prompt for tools that don't support MCP yet |
 
@@ -945,7 +989,7 @@ skills/
 
 ## Marketing site
 
-The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). Copy now names two doors: lab products for people who already use Cursor or Claude, and custom teams that arrive in a firm’s existing tools. The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
+The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). The home page keeps the packet story and offers three paths: designers (`design.html`), Dev/PMs (three jobs + workspace warning), and firm owners (map one workflow). The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
 
 - Live: [https://analyzthis-lab.vercel.app](https://analyzthis-lab.vercel.app)
 - Design team deep-dive: [https://analyzthis-lab.vercel.app/design](https://analyzthis-lab.vercel.app/design) (`website/design.html`)

package/agents/cards/anuj.md

@@ -26,3 +26,16 @@ Full Concept B text wireframe (hierarchy check, primary action, nav level, visib
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/arjun.md

@@ -27,3 +27,16 @@ Full UX Critique + Visual Design Audit blocks with per-dimension reasons — see
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/devi.md

@@ -13,3 +13,25 @@ run --task "..."  →  pending/001-arjun.json  →  /devi  →  responses/001-ar
 ```
 
 See `skills/devi/SKILL.md` for the full protocol.
+
+## 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/agents/cards/kavi.md

@@ -24,3 +24,16 @@ Next: run /persona-orchestrator or any critique persona — they read this bank
 ```
 
 Consult `skills/kavi/SKILL.md` for the host workflow. Prefer running `npx analyzthis_design collect` over re-scanning files in chat. Invoke as **`/kavi`** (alias: `/collect-knowledge`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/meera.md

@@ -25,3 +25,16 @@ Full Business Impact block (metric impact, hierarchy check, segment, GTM lever,
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/noor.md

@@ -26,3 +26,16 @@ Full Concept A text wireframe (hierarchy, primary action, nav level, visible-on-
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/priya.md

@@ -25,3 +25,16 @@ Full Feasibility Analysis block (score, blockers, ranked risks, effort, simpler
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/raj.md

@@ -27,3 +27,16 @@ What [losing agent] gives up: [named]
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/agents/cards/zara.md

@@ -28,3 +28,16 @@ Full Delight Pass block (surface, moment, type, specific addition, why-this-one,
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/HOW-TO-USE.md

@@ -313,21 +313,39 @@ Each persona reads the session state, so you do not need to repeat the task.
 
 ## 8. After the run — accept, reject, evolve
 
-### Mark an output accepted
+### Designer path (remember this)
 
-```bash
-npx analyzthis_design session accept --persona arjun
+In chat, after `/zara` or any persona:
+
+```
+/accept yes
+```
+
+or
+
+```
+/accept no — too much motion on the daily table
 ```
 
-### Reject with correction
+No terminal flags. `/accept` writes keep or skip for **local** evolution.
+
+To send a correction to the published package:
+
+```
+/share
+```
+
+Then **yes** if the preview looks right. Redacted — no folder names, emails, or keys.
+
+### CLI (same thing, if you prefer the terminal)
 
 ```bash
-npx analyzthis_design session accept --persona arjun --reject \
-  --comment "Invented tokens not in our DS" \
-  --correction "Use --color-primary and spacing-4 from tokens.css" \
-  --rating 2 --tags invented_tokens,missed_ds
+npx analyzthis_design accept --keep --persona arjun
+npx analyzthis_design accept --fix --persona arjun --because "Invented tokens — use tokens.css"
 ```
 
+The older `session accept` / `feedback record` flags still work.
+
 ### Make the team learn
 
 ```bash

package/dist/README.md

@@ -4,6 +4,43 @@ A set of AI design personas and a task-first evaluation framework that plugs int
 
 Install once. Run structured UX critiques, multi-phase ideation, and task-grounded screen reviews — directly inside your AI chat. **No external LLM API keys required** for CLI orchestrator runs: **`/devi`** voices each persona from your host IDE (Cursor, Claude, etc.).
 
+## v2.5.0 — personas earn or lose trust
+
+Marking a note now moves a score. Previously a rejection *raised* a persona's score by
+15 — `accept.fix()` recorded `outcome: 'revised'` and scoring counted outcomes without
+reading their value. Punishment was a reward. Fixed.
+
+- **Signed, rate-based scoring.** A persona starts at 50 and moves both ways:
+  `shipped` +15, `blocked_correctly` +10, `revised` −5, `missed` −15, plus
+  `(rating − 3) x 4` per rating. Scored as a **rate per signal**, not a running total,
+  so early wins can never make a persona immune to later failures.
+- **Evidence gating.** Under 5 signals a persona reads `Baseline (insufficient
+  evidence)`. One bad note does not brand anyone.
+- **Bands:** At risk · Developing · Baseline · Reliable · Trusted.
+- **Devi gets a scoreboard** in every pending prompt and weights its synthesis,
+  saying the lean in one line. Advisory only — **no persona is ever dropped from a run.**
+- **Feedback works with no terminal.** New `analyzthis_accept` MCP tool in the
+  **lite** catalog, so Claude Desktop can record keep/skip. Same shared core as the
+  CLI — both transports write identical state.
+- **The persona asks.** Every note ends with one host-neutral line: *"Was this right?
+  Say yes, or no plus one sentence."* The designer answers in plain language; the
+  agent picks the transport. No flags, ever.
+- **Lessons learn from rejections too**, tagged `polarity`, and de-duplicated so
+  re-marking a note cannot inflate a score.
+
+```bash
+npx analyzthis_design scores                  # the whole team
+npx analyzthis_design scores --persona arjun  # one persona, with the breakdown
+```
+
+Scores are derived on read — changing the weights re-scores history with no migration.
+
+## v2.4.1 — `/accept` and `/share` (designer keep / skip / send)
+
+After `/zara` (or any persona), type `/accept yes` or `/accept no` plus one sentence. No CLI flags. Writes keep or skip for **local** evolution. Slash-only notes still count.
+
+To send a correction to the **published** package: `/share` (preview) then `/share yes`. Redacted. Uses the HTTP endpoint if configured; otherwise a GitHub issue on joshirishi/analyzthis_design.
+
 ## v2.4.0 — Claude-path efficiency (1 Sep 2026)
 
 Same SHIP / REVISE / BLOCK. Fewer tokens on Claude Code and Claude Desktop. Not Caveman-speak. Not a proxy.
@@ -48,7 +85,7 @@ Pass `--global` to opt into the legacy merged behavior (read `config.sources` an
 
 Use `npx analyzthis_design run-unchunked` for the legacy single-pass orchestrator.
 
-**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.4.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
+**npm:** [analyzthis_design](https://www.npmjs.com/package/analyzthis_design) · **Current version:** 2.5.0 · **Step-by-step guide:** [HOW-TO-USE.md](./HOW-TO-USE.md)
 
 ---
 
@@ -74,7 +111,7 @@ npx analyzthis_design run-unchunked --task "Review invoice approval screen" --pr
 
 > **Security:** This package publishes **plain source** — no obfuscation, no minification, no dynamic require. Every file in `dist/` is readable and auditable. The `postinstall` script only prints a welcome message; it does **not** write to any AI-agent directories. Skill installation requires an explicit `npx analyzthis_design install --target <ide>` (or `npx analyzthis_design --target <ide>`).
 >
-> **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. For Lovable, v0, Bolt, Replit, ChatGPT: run `npx analyzthis_design mcp --configure <tool>` for a config snippet.
+> **MCP (universal):** `npx analyzthis_design mcp` starts a local MCP server. Default catalog is **lite** (router + retrieve + session + receipt). Full 19 named tools: `ANALYZTHIS_MCP_CATALOG=full` or `mcp --catalog full`. Auto-configures for Cursor, Claude Desktop, **Claude Code**, and Windsurf during install. **Browser-only tools (Lovable, v0, Bolt, Replit, ChatGPT) cannot use MCP here** — our server speaks stdio, and a cloud-hosted tool cannot spawn a process on your machine. Paste the team in instead: `npx analyzthis_design system-prompt --mode both`, or copy it with one click from [the tool picker](https://analyzthis-lab.vercel.app/design#install-lovable). Note the paste path gives you the personas but no `/accept`, lessons, or trust scores — those need local state.
 
 ### Install by target IDE
 
@@ -149,6 +186,9 @@ Invoke critique personas for targeted, already-grounded questions. For **wirefra
 | `/knowledge-bank` | Auto-populated from your connected vault (or from Kavi collect). All personas read this first. |
 | `/design-reference` | CSV reference data (colors, typography, UX guidelines, stacks, …) |
 | `/collect-knowledge` | Alias for `/kavi` |
+| `/accept` | Keep or skip the last persona note (yes / no). Local evolution — no CLI flags. |
+| `/share` | Send a correction to the package (preview, then yes). Redacted. |
+| `/receipt` | Inferred token receipt for this project. Not a bill. |
 
 ---
 
@@ -742,6 +782,10 @@ npx analyzthis_design status
 
 # Session (agentic)
 npx analyzthis_design session init|show|reset [--project id] [--all]
+npx analyzthis_design accept --keep [--persona zara]          # designer keep (slash: /accept yes)
+npx analyzthis_design accept --fix --because "one sentence"   # designer skip (slash: /accept no)
+npx analyzthis_design share                                   # preview notes for the package
+npx analyzthis_design share --send                            # send (slash: /share yes)
 npx analyzthis_design session accept --persona <id> [--reject] [--comment "..."] [--correction "..."] [--rating 1-5] [--tags a,b]
 
 # Persona feedback (v1.16)
@@ -880,7 +924,7 @@ skills/
 |---------|-------------|
 | **MCP server** | `npx analyzthis_design mcp` starts a local MCP server exposing 19 tools — all 8 individual personas + 6 combination passes + 5 utilities. Any MCP-compatible client can discover and call them. |
 | **Auto-configure MCP** | `npx analyzthis_design mcp --configure cursor` (or `claude`, `windsurf`) writes the MCP config automatically. `--target all` now auto-configures MCP during install. |
-| **Universal IDE support** | Cursor, Claude Desktop, Windsurf auto-configured. Lovable, v0, Bolt, Replit, ChatGPT: run `mcp --configure <tool>` for a copy-paste config snippet. |
+| **Universal IDE support** | Cursor, Claude Code, Claude Desktop, Windsurf auto-configured via MCP. Lovable, v0, Bolt, Replit, ChatGPT install nothing — paste `system-prompt` output into the tool's instructions. |
 | **MCP lite + full** | Default: router (`analyzthis_design`) + retrieve + session + receipt. Full 19 named tools behind `--catalog full`. |
 | **System prompt fallback** | `analyzthis_system_prompt` tool generates a consolidated prompt for tools that don't support MCP yet |
 
@@ -945,7 +989,7 @@ skills/
 
 ## Marketing site
 
-The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). Copy now names two doors: lab products for people who already use Cursor or Claude, and custom teams that arrive in a firm’s existing tools. The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
+The public lab site lives in `website/` and is deployed on Vercel as **analyzthis-lab** (site only — not the npm package). The home page keeps the packet story and offers three paths: designers (`design.html`), Dev/PMs (three jobs + workspace warning), and firm owners (map one workflow). The Vercel project root is `website/` with no build step — do not set Output Directory to `public`.
 
 - Live: [https://analyzthis-lab.vercel.app](https://analyzthis-lab.vercel.app)
 - Design team deep-dive: [https://analyzthis-lab.vercel.app/design](https://analyzthis-lab.vercel.app/design) (`website/design.html`)

package/dist/agents/cards/anuj.md

@@ -26,3 +26,16 @@ Full Concept B text wireframe (hierarchy check, primary action, nav level, visib
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/arjun.md

@@ -27,3 +27,16 @@ Full UX Critique + Visual Design Audit blocks with per-dimension reasons — see
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/devi.md

@@ -13,3 +13,25 @@ run --task "..."  →  pending/001-arjun.json  →  /devi  →  responses/001-ar
 ```
 
 See `skills/devi/SKILL.md` for the full protocol.
+
+## 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/agents/cards/kavi.md

@@ -24,3 +24,16 @@ Next: run /persona-orchestrator or any critique persona — they read this bank
 ```
 
 Consult `skills/kavi/SKILL.md` for the host workflow. Prefer running `npx analyzthis_design collect` over re-scanning files in chat. Invoke as **`/kavi`** (alias: `/collect-knowledge`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/meera.md

@@ -25,3 +25,16 @@ Full Business Impact block (metric impact, hierarchy check, segment, GTM lever,
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/noor.md

@@ -26,3 +26,16 @@ Full Concept A text wireframe (hierarchy, primary action, nav level, visible-on-
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/priya.md

@@ -25,3 +25,16 @@ Full Feasibility Analysis block (score, blockers, ranked risks, effort, simpler
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/raj.md

@@ -27,3 +27,16 @@ What [losing agent] gives up: [named]
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.

package/dist/agents/cards/zara.md

@@ -28,3 +28,16 @@ Full Delight Pass block (surface, moment, type, specific addition, why-this-one,
 **Review mode (rounds 0–N-1):** Critique prior output with grounded objections. Default `accepts_prior: false`. Include deliberation JSON block.
 
 **Produce mode (final round):** Full output schema after consensus or Raj. See `deliberation-protocol` in your host skills dir (e.g. `~/.claude/skills/deliberation-protocol/SKILL.md` or `~/.claude/commands/deliberation-protocol.md`).
+
+## Closing line (always)
+
+End every reply with this line, exactly:
+
+```
+—
+Was this right? Say yes, or no plus one sentence. I'll record it.
+```
+
+If the designer answers, record it with whatever path you have — Bash
+(`npx analyzthis_design accept …`) or the `analyzthis_accept` MCP tool. Never ask
+them to type a command, and never mention flags.