failproofai 1.0.3 → 1.0.4-beta.2

package/.next/standalone/app/audit/_components/share-templates.ts

@@ -7,20 +7,31 @@
  * appends a clipboard paste hint. Pure — no React, no DOM — so it's
  * unit-testable and shared by the client poster component.
  *
- * Each template references the score and/or archetype and ends on the
- * install-free CTA + handle. We intentionally never include a URL: a bare link
- * would make X/LinkedIn render a link-preview card and swallow the copied
- * image. The npx command is the call to action instead.
+ * ## The score is switched off (2026-09-07)
+ *
+ * Every template but one used to interpolate `${score}/100`. The score is
+ * commented out across the audit — see the header of `src/audit/scoring.ts` for
+ * why — so the copy is archetype-only. Eighteen templates lost a subordinate
+ * clause; two whose entire premise WAS the number ("my agent scored X/100,
+ * think yours can beat it?") are commented out in place rather than reworded,
+ * because there is nothing left of them once the number goes.
+ *
+ * `ShareCtx.score` is kept and still populated so restoring is re-adding the
+ * clause, not re-plumbing the type. The originals are preserved verbatim in the
+ * block at the bottom of this file.
  */
 import type { Grade } from "@/src/audit/scoring";
 
 export interface ShareCtx {
-  score: number;
   /** Lowercased archetype name, e.g. "the cowboy". */
   arch: string;
-  grade: Grade;
   /** Count of unenabled prescribed policies. */
   missing: number;
+  /** Optional ONLY because the score is switched off and nothing upstream
+   *  computes them any more. Restoring the score means making these required
+   *  again — which the compiler will then walk you through. */
+  score?: number;
+  grade?: Grade;
 }
 
 /** Call-to-action + handle per channel. No URL by design (see file header). */
@@ -33,52 +44,107 @@ const PASTE_LINE = "[ audit card copied to your clipboard — paste it into the
 
 /** Short, curiosity-forward — for X / Twitter. Ends on the npx CTA + @failproofai. */
 export const X_TEMPLATES: ((c: ShareCtx) => string)[] = [
-  ({ score, arch }) =>
-    `my agent has a personality and it's ${arch}. did not see that coming.\n\nran a failproof audit, scored ${score}/100, all local. find out what yours is → ${X_CTA}`,
-  ({ score, arch }) =>
-    `spent 30 seconds auditing my agent. learned more about it than i did all month.\n\nit's ${arch}. scored ${score}/100. → ${X_CTA}`,
-  ({ score }) =>
-    `my agent scored ${score}/100. think yours can beat it?\n\n30 sec audit, runs locally, gives you a personality too → ${X_CTA}`,
+  ({ arch }) =>
+    `my agent has a personality and it's ${arch}. did not see that coming.\n\nran a failproof audit, all local. find out what yours is → ${X_CTA}`,
+  ({ arch }) =>
+    `spent 30 seconds auditing my agent. learned more about it than i did all month.\n\nit's ${arch}. → ${X_CTA}`,
+  // Score-spined — nothing survives removing the number:
+  // ({ score }) =>
+  //   `my agent scored ${score}/100. think yours can beat it?\n\n30 sec audit, runs locally, gives you a personality too → ${X_CTA}`,
   ({ arch }) =>
     `turns out my agent is ${arch} and honestly it explains everything.\n\n→ ${X_CTA}`,
-  ({ score, arch }) =>
-    `ran a failproof audit on my agent. it reads how it actually behaves when things break, not just the happy path.\n\npersonality: ${arch}. score: ${score}/100. all local → ${X_CTA}`,
-  ({ score, arch }) =>
-    `got to know my agent today. it's ${arch} and scored ${score}/100. wow.\n\naudit yours in 30s, nothing leaves your machine → ${X_CTA}`,
-  ({ score, arch }) =>
-    `your agent has a personality. you just haven't met it.\n\ni met mine today: ${arch}, ${score}/100. → ${X_CTA}`,
-  ({ score, arch }) =>
-    `everyone talks about what their agent can build. nobody talks about how it acts when it breaks.\n\nmine's ${arch}, scored ${score}/100, all local → ${X_CTA}`,
-  ({ score, arch }) =>
-    `every agent builder should run this once.\n\n30 sec, local, gives your agent a personality and a quality score. mine: ${arch}, ${score}/100.\n\n${X_CTA}`,
-  ({ score, arch }) =>
-    `i'll go first: ${arch}, ${score}/100.\n\nwhat's your agent? 30 sec audit, no signup → ${X_CTA}`,
+  ({ arch }) =>
+    `ran a failproof audit on my agent. it reads how it actually behaves when things break, not just the happy path.\n\npersonality: ${arch}. all local → ${X_CTA}`,
+  ({ arch }) =>
+    `got to know my agent today. it's ${arch}. wow.\n\naudit yours in 30s, nothing leaves your machine → ${X_CTA}`,
+  ({ arch }) =>
+    `your agent has a personality. you just haven't met it.\n\ni met mine today: ${arch}. → ${X_CTA}`,
+  ({ arch }) =>
+    `everyone talks about what their agent can build. nobody talks about how it acts when it breaks.\n\nmine's ${arch}, all local → ${X_CTA}`,
+  ({ arch }) =>
+    `every agent builder should run this once.\n\n30 sec, local, gives your agent a personality. mine: ${arch}.\n\n${X_CTA}`,
+  ({ arch }) =>
+    `i'll go first: ${arch}.\n\nwhat's your agent? 30 sec audit, no signup → ${X_CTA}`,
 ];
 
 /** Longer, reflective — for LinkedIn. Ends on the npx CTA + @Failproof AI. */
 export const LI_TEMPLATES: ((c: ShareCtx) => string)[] = [
-  ({ score, arch }) =>
-    `I've spent more hours with my agent this month than with most people I know. Today I realized I couldn't tell you a single thing about how it actually behaves.\n\nSo I audited it. Turns out it's ${arch}, and it scored ${score}/100.\n\nThe audit reads its real history, including how it handles failures, not just the clean runs. 30 seconds, runs entirely locally.\n\nMeet yours: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `Took a personality test today. It wasn't for me — it was for my AI agent.\n\nThe result: ${arch}, with a quality score of ${score}/100.\n\nIt works by reading the agent's actual run history, so the personality comes from how it really behaves, not a vibe. Took 30 seconds and stayed local.\n\nTry it on yours: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `Everyone asks what their AI agent can build. I just found out mine has a temper.\n\nAfter watching how it reacts to a failed command, the audit called it ${arch}. It also scored its quality at ${score}/100.\n\nOddly useful to see it written down. 30 seconds, all local: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `My agent does this very specific thing every time a command fails. Today I learned there's basically a name for it.\n\nRan a quick audit and it came back ${arch}, scored ${score}/100. The whole read is based on how the agent handles things going wrong, which is where its real character shows.\n\n30 seconds, nothing leaves your machine: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `My AI agent scored ${score}/100 today. I didn't know you could even measure that.\n\nThe same audit also handed it a personality: ${arch}.\n\nIt reads the agent's real history and tells you where it's solid and where it slips. Took 30 seconds and ran fully locally: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `I'm usually the first to scroll past "audit your X" tools. This one took 30 seconds and actually told me something.\n\nMy agent is ${arch}, and it scored ${score}/100.\n\nIt reads the agent's real run history rather than asking me anything, and none of it leaves the machine: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `What is your agent's personality? I realized today that I had no answer.\n\nSo I checked. Mine is ${arch}, scored ${score}/100, with a clear read on where it shines and where it slips.\n\nIf you work with agents, run it and drop yours in the comments. 30 seconds, fully local: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `I trusted my agent a little less after this morning, and quite a bit more by the afternoon.\n\nI ran an audit on it. It showed me exactly where it's reliable and where it isn't, gave it a personality (${arch}), and scored it ${score}/100.\n\nKnowing the gaps is what made me trust it more. 30 seconds, all local: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `I almost skipped this because I assumed it would quietly ship my code off somewhere. It doesn't. Everything runs locally.\n\n30 seconds later I had my agent's personality (${arch}) and a quality score (${score}/100).\n\nIf privacy is usually what stops you from trying these, this one is different: ${LI_CTA}`,
-  ({ score, arch }) =>
-    `Found out my AI agent has a personality type. Found out it's ${arch}. Found out that explains a lot.\n\nIt scored ${score}/100 too. The audit reads how the agent handles failures, not just the runs where everything goes fine.\n\n30 seconds, runs locally: ${LI_CTA}`,
+  ({ arch }) =>
+    `I've spent more hours with my agent this month than with most people I know. Today I realized I couldn't tell you a single thing about how it actually behaves.\n\nSo I audited it. Turns out it's ${arch}.\n\nThe audit reads its real history, including how it handles failures, not just the clean runs. 30 seconds, runs entirely locally.\n\nMeet yours: ${LI_CTA}`,
+  ({ arch }) =>
+    `Took a personality test today. It wasn't for me — it was for my AI agent.\n\nThe result: ${arch}.\n\nIt works by reading the agent's actual run history, so the personality comes from how it really behaves, not a vibe. Took 30 seconds and stayed local.\n\nTry it on yours: ${LI_CTA}`,
+  ({ arch }) =>
+    `Everyone asks what their AI agent can build. I just found out mine has a temper.\n\nAfter watching how it reacts to a failed command, the audit called it ${arch}.\n\nOddly useful to see it written down. 30 seconds, all local: ${LI_CTA}`,
+  ({ arch }) =>
+    `My agent does this very specific thing every time a command fails. Today I learned there's basically a name for it.\n\nRan a quick audit and it came back ${arch}. The whole read is based on how the agent handles things going wrong, which is where its real character shows.\n\n30 seconds, nothing leaves your machine: ${LI_CTA}`,
+  // Score-spined — the opening line is the number:
+  // ({ score, arch }) =>
+  //   `My AI agent scored ${score}/100 today. I didn't know you could even measure that.\n\nThe same audit also handed it a personality: ${arch}.\n\nIt reads the agent's real history and tells you where it's solid and where it slips. Took 30 seconds and ran fully locally: ${LI_CTA}`,
+  ({ arch }) =>
+    `I'm usually the first to scroll past "audit your X" tools. This one took 30 seconds and actually told me something.\n\nMy agent is ${arch}.\n\nIt reads the agent's real run history rather than asking me anything, and none of it leaves the machine: ${LI_CTA}`,
+  ({ arch }) =>
+    `What is your agent's personality? I realized today that I had no answer.\n\nSo I checked. Mine is ${arch}, with a clear read on where it shines and where it slips.\n\nIf you work with agents, run it and drop yours in the comments. 30 seconds, fully local: ${LI_CTA}`,
+  ({ arch }) =>
+    `I trusted my agent a little less after this morning, and quite a bit more by the afternoon.\n\nI ran an audit on it. It showed me exactly where it's reliable and where it isn't, and gave it a personality: ${arch}.\n\nKnowing the gaps is what made me trust it more. 30 seconds, all local: ${LI_CTA}`,
+  ({ arch }) =>
+    `I almost skipped this because I assumed it would quietly ship my code off somewhere. It doesn't. Everything runs locally.\n\n30 seconds later I had my agent's personality: ${arch}.\n\nIf privacy is usually what stops you from trying these, this one is different: ${LI_CTA}`,
+  ({ arch }) =>
+    `Found out my AI agent has a personality type. Found out it's ${arch}. Found out that explains a lot.\n\nThe audit reads how the agent handles failures, not just the runs where everything goes fine.\n\n30 seconds, runs locally: ${LI_CTA}`,
 ];
 
+/* ---------------------------------------------------------------------------
+ * THE ORIGINAL SCORE-BEARING COPY, verbatim. To restore: put these two arrays
+ * back in place of the two above, and re-enable the score at its source (see
+ * `src/audit/scoring.ts`). Nothing else has to change — `ShareCtx` is unchanged
+ * and `score` is still populated by `audit-poster.tsx`.
+ *
+ * export const X_TEMPLATES: ((c: ShareCtx) => string)[] = [
+ *   ({ score, arch }) =>
+ *     `my agent has a personality and it's ${arch}. did not see that coming.\n\nran a failproof audit, scored ${score}/100, all local. find out what yours is → ${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `spent 30 seconds auditing my agent. learned more about it than i did all month.\n\nit's ${arch}. scored ${score}/100. → ${X_CTA}`,
+ *   ({ score }) =>
+ *     `my agent scored ${score}/100. think yours can beat it?\n\n30 sec audit, runs locally, gives you a personality too → ${X_CTA}`,
+ *   ({ arch }) =>
+ *     `turns out my agent is ${arch} and honestly it explains everything.\n\n→ ${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `ran a failproof audit on my agent. it reads how it actually behaves when things break, not just the happy path.\n\npersonality: ${arch}. score: ${score}/100. all local → ${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `got to know my agent today. it's ${arch} and scored ${score}/100. wow.\n\naudit yours in 30s, nothing leaves your machine → ${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `your agent has a personality. you just haven't met it.\n\ni met mine today: ${arch}, ${score}/100. → ${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `everyone talks about what their agent can build. nobody talks about how it acts when it breaks.\n\nmine's ${arch}, scored ${score}/100, all local → ${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `every agent builder should run this once.\n\n30 sec, local, gives your agent a personality and a quality score. mine: ${arch}, ${score}/100.\n\n${X_CTA}`,
+ *   ({ score, arch }) =>
+ *     `i'll go first: ${arch}, ${score}/100.\n\nwhat's your agent? 30 sec audit, no signup → ${X_CTA}`,
+ * ];
+ *
+ * export const LI_TEMPLATES: ((c: ShareCtx) => string)[] = [
+ *   ({ score, arch }) =>
+ *     `I've spent more hours with my agent this month than with most people I know. Today I realized I couldn't tell you a single thing about how it actually behaves.\n\nSo I audited it. Turns out it's ${arch}, and it scored ${score}/100.\n\nThe audit reads its real history, including how it handles failures, not just the clean runs. 30 seconds, runs entirely locally.\n\nMeet yours: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `Took a personality test today. It wasn't for me — it was for my AI agent.\n\nThe result: ${arch}, with a quality score of ${score}/100.\n\nIt works by reading the agent's actual run history, so the personality comes from how it really behaves, not a vibe. Took 30 seconds and stayed local.\n\nTry it on yours: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `Everyone asks what their AI agent can build. I just found out mine has a temper.\n\nAfter watching how it reacts to a failed command, the audit called it ${arch}. It also scored its quality at ${score}/100.\n\nOddly useful to see it written down. 30 seconds, all local: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `My agent does this very specific thing every time a command fails. Today I learned there's basically a name for it.\n\nRan a quick audit and it came back ${arch}, scored ${score}/100. The whole read is based on how the agent handles things going wrong, which is where its real character shows.\n\n30 seconds, nothing leaves your machine: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `My AI agent scored ${score}/100 today. I didn't know you could even measure that.\n\nThe same audit also handed it a personality: ${arch}.\n\nIt reads the agent's real history and tells you where it's solid and where it slips. Took 30 seconds and ran fully locally: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `I'm usually the first to scroll past "audit your X" tools. This one took 30 seconds and actually told me something.\n\nMy agent is ${arch}, and it scored ${score}/100.\n\nIt reads the agent's real run history rather than asking me anything, and none of it leaves the machine: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `What is your agent's personality? I realized today that I had no answer.\n\nSo I checked. Mine is ${arch}, scored ${score}/100, with a clear read on where it shines and where it slips.\n\nIf you work with agents, run it and drop yours in the comments. 30 seconds, fully local: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `I trusted my agent a little less after this morning, and quite a bit more by the afternoon.\n\nI ran an audit on it. It showed me exactly where it's reliable and where it isn't, gave it a personality (${arch}), and scored it ${score}/100.\n\nKnowing the gaps is what made me trust it more. 30 seconds, all local: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `I almost skipped this because I assumed it would quietly ship my code off somewhere. It doesn't. Everything runs locally.\n\n30 seconds later I had my agent's personality (${arch}) and a quality score (${score}/100).\n\nIf privacy is usually what stops you from trying these, this one is different: ${LI_CTA}`,
+ *   ({ score, arch }) =>
+ *     `Found out my AI agent has a personality type. Found out it's ${arch}. Found out that explains a lot.\n\nIt scored ${score}/100 too. The audit reads how the agent handles failures, not just the runs where everything goes fine.\n\n30 seconds, runs locally: ${LI_CTA}`,
+ * ];
+ * ------------------------------------------------------------------------- */
+
 /** djb2 hash — stable per seed so the template choice is deterministic. */
 function hashStr(s: string): number {
   let h = 5381;

package/.next/standalone/app/audit/audit-styles.css

@@ -496,7 +496,13 @@
 .poster-meta .of { color: var(--dim); }
 .poster-meta .poster-sep { color: var(--dim); }
 
-/* body — vertical centered stack: sigil → persona → score ─── */
+/* body — vertical centered stack: sigil → persona → score ───
+   The score block is switched off (see `src/audit/scoring.ts`), so this stack
+   currently renders two children, not three. It is a centered flex column with
+   a gap and no fixed track count, so it re-centers on its own. The
+   `.poster-score` rules below are kept, dormant, against the score coming
+   back — do not tidy them away, or restoring it means rewriting the styles
+   too. */
 .poster-body {
   display: flex;
   flex-direction: column;
@@ -555,6 +561,7 @@
 .poster-persona .persona-rarity .pct { color: var(--accent-pink); font-weight: 600; }
 
 /* score — score-n + /100, baseline-aligned and centered in the card. */
+/* Dormant while the score is switched off — see `src/audit/scoring.ts`. */
 .poster-score {
   display: flex;
   align-items: baseline;
@@ -1157,3 +1164,109 @@
 .share-card {
   max-width: 420px;
 }
+
+/* ── Leak report ─────────────────────────────────────────────────────────────
+   One block per distinct credential. Deliberately NOT a table: a table implies
+   columns worth scanning down, and the interesting comparison between two
+   leaked keys is never "which is longer" — it is what each one is and where it
+   went, which reads as a sentence.                                            */
+
+.leak-notify { margin-left: auto; }
+
+.leak-list {
+  list-style: none;
+  margin: 20px 0 0;
+  padding: 0;
+  display: flex;
+  flex-direction: column;
+  gap: 10px;
+}
+
+.leak-row {
+  border: 1px solid var(--line-2);
+  /* Hard-offset pixel shadow, never a blur — the house rule. Pink is the
+     accent that means "this one is yours to act on". */
+  box-shadow: 4px 4px 0 0 var(--line-2);
+  padding: 14px 16px;
+  display: flex;
+  flex-direction: column;
+  gap: 8px;
+  background: var(--bg);
+}
+/* A recognised prefix means a console exists and this is revocable in a
+   minute. That is a real difference in what the reader has to do, so it is the
+   one thing the row's own frame encodes. */
+.leak-row[data-attributed="true"] { box-shadow: 4px 4px 0 0 var(--accent-pink); }
+
+.leak-row-top {
+  display: flex;
+  align-items: baseline;
+  gap: 10px;
+  flex-wrap: wrap;
+}
+
+.leak-key {
+  font-family: var(--font-mono);
+  font-size: 14px;
+  color: var(--ink);
+  letter-spacing: 0.02em;
+  /* The masked value can be long; it must wrap rather than push the row wide. */
+  word-break: break-all;
+}
+
+.leak-label {
+  font-family: var(--font-mono);
+  font-size: 11px;
+  color: var(--accent-pink);
+  text-transform: lowercase;
+}
+
+.leak-name {
+  font-family: var(--font-mono);
+  font-size: 11px;
+  color: var(--ink-2);
+  border: 1px solid var(--line-2);
+  padding: 1px 5px;
+}
+
+.leak-dismiss {
+  margin-left: auto;
+  font-family: var(--font-mono);
+  font-size: 10px;
+  color: var(--dim);
+  background: none;
+  border: 1px solid var(--line-2);
+  padding: 3px 8px;
+  cursor: pointer;
+  text-transform: lowercase;
+}
+.leak-dismiss:hover:not(:disabled) { color: var(--ink); border-color: var(--ink-2); }
+.leak-dismiss:disabled { opacity: 0.4; cursor: not-allowed; }
+.leak-dismiss:focus-visible { outline: 2px solid var(--accent-pink); outline-offset: 2px; }
+
+.leak-how {
+  font-family: var(--font-mono);
+  font-size: 12px;
+  color: var(--ink-2);
+  line-height: 1.6;
+}
+.leak-verb { color: var(--ink); }
+.leak-where { color: var(--accent-green); }
+.leak-who { color: var(--ink); }
+.leak-when { color: var(--dim); }
+
+.leak-foot {
+  display: flex;
+  gap: 14px;
+  flex-wrap: wrap;
+  font-family: var(--font-mono);
+  font-size: 10px;
+  color: var(--dim);
+}
+.leak-fix { color: var(--accent-green); }
+.leak-dir { color: var(--ink-2); }
+
+@media (max-width: 640px) {
+  .leak-dismiss { margin-left: 0; }
+  .leak-foot { gap: 6px; flex-direction: column; }
+}

package/.next/standalone/fp-cloud-cli/CHANGELOG.md

@@ -3,9 +3,32 @@
 ## 0.0.1b2 — 2026-08-25
 
 Open for the next release. `0.0.1b1` published on 2026-08-24 and the `bump` job
-moved the version here automatically; nothing has landed against `0.0.1b2` yet.
-Add entries as changes merge — this section becomes the GitHub Release body when
-it ships.
+moved the version here automatically. Add entries as changes merge — this section
+becomes the GitHub Release body when it ships.
+
+### Fixes
+
+- **Typed errors keep their exit codes under typer 0.27.2.** That release moved
+  `Abort` out of its vendored `typer._click.exceptions`, and `_click_compat`
+  imported all six of its symbols under a single
+  `try: … except ImportError: from click import …`. One missing name was enough
+  to send the whole block to the fallback, binding `ClickException`,
+  `UsageError`, `BadParameter`, `Command` and `Parameter` to the pip `click`
+  distribution — which is *not* the Click Typer runs, and Typer catches only its
+  own. So every typed error escaped its handler: `fp alerts show ghost` exited
+  **1 with an empty stderr** instead of **6** with `no alert named "ghost"`, and
+  likewise for exits 2, 3, 4 and 5. Nothing warned; the CLI imported and every
+  happy path passed. The Click is now decided **once**, on whether `typer._click`
+  exists at all, and every symbol imported from that decision, so a future move
+  fails at import — a CLI that refuses to start — instead of silently flattening
+  the exit-code contract. `Abort` is resolved from `typer.Abort`, which is by
+  construction the class `typer.prompt` raises and typer's own `_main` catches on
+  every version in range. Suite verified green against typer 0.25.1, 0.27.0,
+  0.27.1 and 0.27.2 (#771)
+
+### Dependencies
+
+- typer 0.27.1 → 0.27.2, click 8.4.2 → 8.5.0, posthog 7.42.0 → 7.44.2 (#771)
 
 ## 0.0.1b1 — 2026-08-24
 

package/.next/standalone/fp-cloud-cli/fp_cli/_click_compat.py

@@ -11,9 +11,10 @@ compiles, and every happy path still passes:
   should print ``✗ …`` and exit 5 exits **1 with an empty stderr**, and the
   ``rich_format_error`` hook in ``app.py`` (reached only *after* that catch) never
   runs. Same for the ``UsageError``/``BadParameter`` we raise by hand.
-* ``Abort`` — ``typer.prompt`` raises its own Click's ``Abort`` on closed stdin, so a
-  pip-Click ``except click.Abort`` stops matching and the clean "no TTY, pass a slug"
-  usage error becomes a bare abort.
+* ``Abort`` — ``typer.prompt`` raises the ``Abort`` **typer** exports on closed stdin
+  (0.27.2 moved that class out of the vendored Click entirely), so a pip-Click
+  ``except click.Abort`` stops matching and the clean "no TTY, pass a slug" usage error
+  becomes a bare abort.
 * Options — Typer 0.26+ has no ``Option`` class in its vendored Click *at all*: every
   option in a Typer-built tree is a ``typer.core.TyperOption``, subclassing
   ``Parameter`` directly. ``isinstance(param, click.Option)`` is then quietly always
@@ -27,14 +28,36 @@ again, and that our errors are still the class Typer catches.
 
 from __future__ import annotations
 
+# `Abort` is resolved from `typer` itself rather than from either Click, because it is
+# the one symbol here that is not stably a Click class: typer 0.27.2 moved it out of the
+# vendored `typer._click.exceptions` into a plain `typer.exceptions.Abort(RuntimeError)`.
+# `typer.Abort` tracks that move — it is `click.Abort` before 0.26, the vendored class
+# through 0.27.1, the RuntimeError from 0.27.2 — and it is by construction the class
+# `typer.prompt` raises and typer's own `_main` catches, which is the only property
+# `select.py`'s `except click.Abort` needs.
+from typer import Abort as Abort
+
+# Pick the Click ONCE, on whether typer vendors one at all, then import every symbol
+# from that choice. Deciding per symbol — a single `try` around the whole vendored
+# import block, falling back to pip `click` on any ImportError — is what shipped
+# through 0.27.1 and it failed exactly as silently as this module exists to prevent:
+# 0.27.2 removing `typer._click.exceptions.Abort` made that one missing name rebind ALL
+# SIX symbols to pip Click, so every typed error escaped Typer's handler as exit 1 with
+# an empty stderr. A name that goes missing inside the chosen Click must raise here, at
+# import, where it is a CLI that refuses to start rather than one that silently stops
+# reporting errors.
 try:
-    # typer >= 0.26. pip `click` may well still be installed — it is simply not the
-    # Click in play, so binding to it here would reintroduce the whole class of bug.
-    from typer._click import ClickException, Command, Parameter
-    from typer._click.exceptions import Abort, BadParameter, UsageError
+    import typer._click as _typer_click  # typer >= 0.26 vendors its own Click
 except ImportError:  # typer < 0.26 drives the pip `click` distribution directly
+    _typer_click = None  # type: ignore[assignment]
+
+if _typer_click is not None:
+    # pip `click` may well still be installed — it is simply not the Click in play, so
+    # binding to it here would reintroduce the whole class of bug.
+    from typer._click import ClickException, Command, Parameter
+    from typer._click.exceptions import BadParameter, UsageError
+else:
     from click import (  # type: ignore[assignment]
-        Abort,
         BadParameter,
         ClickException,
         Command,

package/.next/standalone/fp-cloud-cli/fp_cli/permissions.py

@@ -26,6 +26,7 @@ ALL_PERMISSIONS: List[str] = [
     "users:delete",
     "evaluations:read",
     "evaluations:trigger",
+    "evaluations:run",
     "dashboards:read",
     "dashboards:write",
     "dashboards:delete",

package/.next/standalone/fp-cloud-cli/pyproject.toml

@@ -31,7 +31,14 @@ dependencies = [
     # through that — which is what makes both sides of the split work. Import Click from
     # there and nowhere else; `tests/test_click_compat.py` enforces it, because every way
     # this breaks is silent (typed errors collapse to exit 1 with an empty stderr, and the
-    # telemetry flag catalog empties). Suite verified against 0.25.1 and 0.27.0.
+    # telemetry flag catalog empties). Suite verified against 0.25.1, 0.27.0, 0.27.1 and
+    # 0.27.2.
+    #
+    # The split keeps moving INSIDE the vendored tree, so the shim resolves each symbol
+    # separately: 0.27.2 moved `Abort` out of `typer._click.exceptions` into
+    # `typer.exceptions`, and the one all-or-nothing `try/except ImportError` that used to
+    # wrap the vendored import sent every OTHER symbol to pip Click over that single
+    # missing name — 105 tests red, every typed error at exit 1.
     #
     # The floor is 0.13, not 0.12, because 0.12 cannot BUILD this app: the global
     # `--insecure/--secure` option in `app.py` is an `Optional[bool]` with a
@@ -39,7 +46,7 @@ dependencies = [
     # rejects with `TypeError: Secondary flag is not valid for non-boolean flag`.
     # That fires while the command tree is constructed, before any parsing, so
     # `fp --version`, `fp --help` and every subcommand die identically — an
-    # installed CLI that cannot run one command. `uv.lock` pins 0.27.1, so
+    # installed CLI that cannot run one command. `uv.lock` pins 0.27.2, so
     # neither CI nor the publish smoke test ever installed the broken part of the
     # range. Measured across 0.12.0/0.12.3/0.12.5 (all fail) and 0.13.0 upward
     # (all pass).

package/.next/standalone/fp-cloud-cli/tests/test_click_compat.py

@@ -11,6 +11,7 @@ from __future__ import annotations
 import ast
 import pathlib
 
+import pytest
 import typer
 from typer.testing import CliRunner
 
@@ -95,6 +96,59 @@ def test_error_exit_codes_are_distinct_per_class():
     assert issubclass(KeyModeUnsupportedError, _click_compat.ClickException)
 
 
+def test_every_symbol_comes_from_the_click_typer_runs():
+    """No symbol may quietly come from pip Click while Typer is running its own.
+
+    This is the alarm for a *partial* miss. `_click_compat` used to wrap the whole
+    vendored import in one `try: … except ImportError: from click import …`, so a single
+    name disappearing from `typer._click` rebound **all six** symbols to pip Click — and
+    that is not hypothetical: typer 0.27.2 moved `Abort` out of
+    `typer._click.exceptions`, and the fallback fired, and 105 tests went red at once
+    with typed errors collapsing to exit 1. Assert the provenance of each symbol
+    separately, so the next move is one failure naming one symbol.
+    """
+    typer_click = pytest.importorskip(
+        "typer._click", reason="typer < 0.26 has no vendored Click; pip click IS the right one"
+    )
+    wrong = {
+        name: obj.__module__
+        for name in ("ClickException", "UsageError", "BadParameter", "Command", "Parameter")
+        if not (obj := getattr(_click_compat, name)).__module__.startswith(typer_click.__name__)
+    }
+    assert not wrong, f"these came from pip Click, not the Click Typer runs: {wrong}"
+
+
+def test_abort_is_the_one_typer_raises():
+    """`Abort` is the exception NOT to pin to a Click — pin it to Typer.
+
+    It is `click.Abort` before typer 0.26, the vendored class through 0.27.1, and a
+    plain `typer.exceptions.Abort(RuntimeError)` from 0.27.2 on. `typer.Abort` is the
+    class `typer.prompt` raises and typer's own `_main` catches on every one of those,
+    which is the only thing `select.py`'s `except click.Abort` needs to be true.
+    """
+    assert _click_compat.Abort is typer.Abort
+
+
+def test_hand_raised_usage_errors_reach_typers_handler():
+    """The other half of the contract: `UsageError`/`BadParameter` we raise ourselves.
+
+    `test_typed_errors_reach_typers_handler` covers the `ClickException` subclasses in
+    `errors.py`; these two are raised directly through the shim (`raise
+    click.UsageError(...)`) from a dozen call sites, and bound to the wrong Click they
+    escape uncaught the same way — exit 1, empty stderr, instead of a clean exit 2.
+    """
+    for exc_class in (_click_compat.UsageError, _click_compat.BadParameter):
+        app = typer.Typer()
+
+        @app.command()
+        def boom() -> None:
+            raise exc_class("bad input")
+
+        result = CliRunner().invoke(app, [])
+        assert result.exit_code == 2, (exc_class, result.output)
+        assert "bad input" in result.output
+
+
 def test_is_option_recognises_typer_options():
     """Typer's vendored Click has no `Option` class, so `isinstance` cannot answer this.
 

package/.next/standalone/fp-cloud-cli/uv.lock

@@ -208,14 +208,11 @@ wheels = [
 
 [[package]]
 name = "click"
-version = "8.4.2"
+version = "8.5.0"
 source = { registry = "https://pypi.org/simple" }
-dependencies = [
-    { name = "colorama", marker = "sys_platform == 'win32'" },
-]
-sdist = { url = "https://files.pythonhosted.org/packages/76/d4/81420972a676e8ffea40450d8c8c92943e7218a78fe9b64359836cc9876b/click-8.4.2.tar.gz", hash = "sha256:9a6cea6e60b17ebe0a44c5cc636d94f09bd66142c1cd7d8b4cd731c4917a15f6", size = 338000, upload-time = "2026-06-24T17:45:15.148Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/c7/0e/7fa0ef50764b67090eca4114772a2abf8b6148198475e54c660b97caeee6/click-8.5.0.tar.gz", hash = "sha256:ba0d2089de75ea0310e2dde03160e6ca10009947fb95a182f9b54021bb272e34", size = 382235, upload-time = "2026-08-26T13:33:14.56Z" }
 wheels = [
-    { url = "https://files.pythonhosted.org/packages/fb/e2/79c688af8b210d232694e31e59da9f6ec747bae31c3f5946e4e9b98860d5/click-8.4.2-py3-none-any.whl", hash = "sha256:e6f9f66136c816745b9d65817da91d61d957fb16e02e4dcd0552553c5a197b76", size = 119243, upload-time = "2026-06-24T17:45:13.73Z" },
+    { url = "https://files.pythonhosted.org/packages/58/50/6c0d534c5f134586a8e1ba4e330569e32f057e33372ae556463212fb4cd3/click-8.5.0-py3-none-any.whl", hash = "sha256:255bc9599cf7748b4b1a446ccc735421bd08a2ae529a8b88597d3de5664ee360", size = 125251, upload-time = "2026-08-26T13:33:12.928Z" },
 ]
 
 [[package]]
@@ -375,7 +372,7 @@ wheels = [
 
 [[package]]
 name = "posthog"
-version = "7.42.0"
+version = "7.47.0"
 source = { registry = "https://pypi.org/simple" }
 dependencies = [
     { name = "backoff" },
@@ -383,9 +380,9 @@ dependencies = [
     { name = "requests" },
     { name = "typing-extensions" },
 ]
-sdist = { url = "https://files.pythonhosted.org/packages/79/97/32cc0a72d7896cc2d27d442c75c9d24cc77d0140be9f5e98df7f4ce98f6a/posthog-7.42.0.tar.gz", hash = "sha256:c7e9297446208d413c3071348f101f4c05e32fba4228ac0a85e9d0014c2a274e", size = 469662, upload-time = "2026-08-21T12:57:15.05Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/e4/1b/61eccf2257847def7d01ccae29f9680156cb1cd2b4f00d3e9afaabe236fa/posthog-7.47.0.tar.gz", hash = "sha256:62767af8b0808cb103da37aa3974e728467fed9527e4f201f23e718740debd30", size = 508993, upload-time = "2026-09-04T16:52:31.715Z" }
 wheels = [
-    { url = "https://files.pythonhosted.org/packages/31/f0/46e28b947a19c992ad7289931d3197358cfdf4980b33317b5e7cf9c24abe/posthog-7.42.0-py3-none-any.whl", hash = "sha256:6429c9a4145572a8f54ab00330bbfe987340025d3a464212505be814b2b0950d", size = 559119, upload-time = "2026-08-21T12:57:13.299Z" },
+    { url = "https://files.pythonhosted.org/packages/a6/28/16b9b229b9c2380211249377df5bbb4c33cb8b224b7b27ecd46c89bcedac/posthog-7.47.0-py3-none-any.whl", hash = "sha256:c87daf7830eb5ef779d0ff1ec25b5de6d316926d6bbbcde74b80e055172a0ddc", size = 601509, upload-time = "2026-09-04T16:52:29.935Z" },
 ]
 
 [[package]]
@@ -520,7 +517,7 @@ wheels = [
 
 [[package]]
 name = "typer"
-version = "0.27.1"
+version = "0.27.2"
 source = { registry = "https://pypi.org/simple" }
 dependencies = [
     { name = "annotated-doc" },
@@ -528,9 +525,9 @@ dependencies = [
     { name = "rich" },
     { name = "shellingham" },
 ]
-sdist = { url = "https://files.pythonhosted.org/packages/ae/40/4a3db7990d1f62a53182aa96eaef57aeb2886a27f90a195bc66713565d31/typer-0.27.1.tar.gz", hash = "sha256:a79bef8469a79c45498e7b814ecf8d603cc7644e9acbd9e19cac0334240b18df", size = 203994, upload-time = "2026-08-03T14:41:03.438Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/16/f7/57713ba479fd405eb76de31404b2c744c289e336b2d999511ebf51e496f7/typer-0.27.2.tar.gz", hash = "sha256:269b7eb9d3c202ca84b4bc9618cb04ebb43d3d4d1e567e4c768607232c05f945", size = 204045, upload-time = "2026-08-28T10:26:55.046Z" }
 wheels = [
-    { url = "https://files.pythonhosted.org/packages/43/89/9518bc0c3929bee36b3a4a8e3daddd6e03f92f9961c66d4983b837160543/typer-0.27.1-py3-none-any.whl", hash = "sha256:53150287edd11baeb4e4722c8e394fcdf8181c0ae89485cba8d25c778d5edd56", size = 122874, upload-time = "2026-08-03T14:41:04.391Z" },
+    { url = "https://files.pythonhosted.org/packages/dc/bf/205d0004930ede8f542fb58f601526fccf4ae7626075ca1e6c4de5d3d652/typer-0.27.2-py3-none-any.whl", hash = "sha256:b3a5fc4342d5fc8fda8fc3010b1cf117e9249aab7fae800c2eff62fd3842d97d", size = 123130, upload-time = "2026-08-28T10:26:53.752Z" },
 ]
 
 [[package]]

package/.next/standalone/lib/auth/api-server-client.ts

@@ -253,6 +253,34 @@ export interface AuditReportBody {
     last_seen?: string;
     examples: string[];
   }[];
+  /**
+   * Credentials this machine found in its own transcripts.
+   *
+   * Optional on the wire, so a CLI newer than the api-server sends a field the
+   * server ignores rather than failing the whole digest — the harmful counts
+   * are the older half of the contract and must keep arriving either way.
+   *
+   * Every field here is a mask, a label, a length or a location. There is no
+   * shape of this object that carries a secret, because the record it is built
+   * from never stores one: `recordLeaks` fingerprints at detection time and
+   * keeps only the masked rendering.
+   */
+  leaks?: {
+    id: string;
+    display: string;
+    label: string;
+    length: number;
+    attributed: boolean;
+    name: string | null;
+    confidence: string;
+    first_seen: string;
+    last_seen: string;
+    occurrences: number;
+    cli: string;
+    project: string;
+    mechanism: string;
+    direction: "input" | "result";
+  }[];
 }
 
 export interface AuditReportResult {