failproofai 1.0.4-beta.8 → 1.0.5-beta.0

package/.next/standalone/app/audit/_components/audit-poster.tsx

@@ -24,12 +24,7 @@
 import React, { forwardRef, useMemo, useState } from "react";
 import { pickArchetypeVariant, type ArchetypeKey } from "@/src/audit/archetypes";
 import { type Grade } from "@/src/audit/scoring";
-// Archetype rarity switched off — the percentages are eight hardcoded integers
-// ("Seeded with snapshot values; swap for live aggregates once that pipeline
-// lands"), and this is the ONLY surface that rendered them: baked by
-// html-to-image into the PNG people post publicly. A fabricated population
-// statistic on a shared card is a claim we cannot support.
-// import { getArchetypeRarityPct } from "@/src/audit/social-proof";
+import { getArchetypeRarityPct } from "@/src/audit/social-proof";
 import { copyOrDownloadCard, downloadCard, shareCardNative, shareCardToastMessage } from "@/lib/share-card";
 import { toast } from "@/app/components/toast";
 import { usePostHog } from "@/contexts/PostHogContext";
@@ -50,11 +45,8 @@ interface Props {
   archetypeKey: ArchetypeKey;
   /** Stable seed for variant selection (project name is the natural fit). */
   seed: string;
-  /** The score is switched off (see `src/audit/scoring.ts`). Kept as optional
-   *  props rather than removed, so restoring is un-commenting rather than
-   *  re-threading: the dashboard simply stops passing them. */
-  score?: number;
-  grade?: Grade;
+  score: number;
+  grade: Grade;
   /** Count of unenabled prescribed policies — passed to the share-text
    *  templates, not rendered on the poster itself. */
   missing: number;
@@ -71,7 +63,7 @@ export const AuditPoster = forwardRef<HTMLDivElement, Props>(function AuditPoste
     () => pickArchetypeVariant(archetypeKey, seed),
     [archetypeKey, seed],
   );
-  // const rarityPct = getArchetypeRarityPct(archetypeKey);
+  const rarityPct = getArchetypeRarityPct(archetypeKey);
   const indexLabel = String(archetype.index).padStart(2, "0");
   const auditedDate = useMemo(() => formatAuditedDate(auditedAt), [auditedAt]);
 
@@ -142,11 +134,8 @@ export const AuditPoster = forwardRef<HTMLDivElement, Props>(function AuditPoste
     }
   };
 
-  // Score switched off — the filename is keyed on the archetype instead, which
-  // is what the card now actually shows. Original:
-  //   `failproofai-${channel}-${grade.toLowerCase()}-${score}.png`
   const filenameFor = (channel: "x" | "linkedin" | "download") =>
-    `failproofai-${channel}-${archetypeKey}.png`;
+    `failproofai-${channel}-${grade.toLowerCase()}-${score}.png`;
 
   const handleShare = async (channel: "x" | "linkedin" | "download") => {
     if (busy) return;
@@ -154,11 +143,8 @@ export const AuditPoster = forwardRef<HTMLDivElement, Props>(function AuditPoste
     capture("audit_card_share_clicked", {
       channel,
       source: "poster",
-      // Score switched off — see `src/audit/scoring.ts`. Note for whoever reads
-      // the funnel: these two properties stop appearing from this release, so a
-      // dashboard keyed on them breaks rather than reading zero.
-      // score,
-      // grade,
+      score,
+      grade,
       missing_policies: missing,
     });
     try {
@@ -188,10 +174,10 @@ export const AuditPoster = forwardRef<HTMLDivElement, Props>(function AuditPoste
       }
 
       const shareCtx: ShareCtx = {
+        score,
         arch: archetype.name.toLowerCase(),
+        grade,
         missing,
-        // score,
-        // grade,
       };
       const shareText = channel === "x"
         ? pickTemplate(X_TEMPLATES, seed, shareCtx)
@@ -262,7 +248,6 @@ export const AuditPoster = forwardRef<HTMLDivElement, Props>(function AuditPoste
                 </React.Fragment>
               ))}
             </div>
-            {/* Rarity switched off — see the import above.
             {typeof rarityPct === "number" && (
               <div className="persona-rarity">
                 <span className="lbl">{"// only"}</span>{" "}
@@ -270,17 +255,13 @@ export const AuditPoster = forwardRef<HTMLDivElement, Props>(function AuditPoste
                 <span className="lbl">of agents are this archetype</span>
               </div>
             )}
-            */}
           </div>
 
-          {/* Score block — heroic number, centered in the card. Switched off;
-              see `src/audit/scoring.ts` for why. The archetype is the card's
-              headline now.
+          {/* Score block — heroic number, centered in the card */}
           <div className="poster-score">
             <span className="score-n">{score}</span>
             <span className="score-of">/100</span>
           </div>
-          */}
         </div>
 
         <footer className="poster-foot">

package/.next/standalone/app/audit/_components/come-back-better-section.tsx

@@ -21,12 +21,7 @@ import { AuthDialog, type AuthedUser } from "./auth-dialog";
 import { InviteDialog } from "./invite-dialog";
 
 interface Props {
-  /** Current audit score (0–100), forwarded into the invite email body.
-   *
-   *  Always undefined while the score is switched off (see
-   *  `src/audit/scoring.ts`) — the dashboard no longer passes it. Nothing
-   *  breaks: `/api/audit/invite` already treats it as optional and simply
-   *  leaves it out of the email body when it is not a finite number. */
+  /** Current audit score (0–100), forwarded into the invite email body. */
   score?: number;
 }
 

package/.next/standalone/app/audit/_components/empty-state.tsx

@@ -74,10 +74,7 @@ export function EmptyState({ mode, running, onStarted, onCompleted }: Props) {
           <p className="empty-sub">
             we&apos;ll walk every transcript across your installed CLIs — Claude Code,
             Codex, Copilot, Cursor, OpenCode, Pi — and count every wasteful
-            {/* Was "a tier, a score, and a punch-list" — the tier was never
-                rendered and the score is switched off, so this promised two
-                things the page did not show. */}
-            or risky action. you&apos;ll get a leak report and a scan summary.
+            or risky action. you&apos;ll get a tier, a score, and a punch-list.
           </p>
 
           <div className="empty-actions">

package/.next/standalone/app/audit/_components/how-to-improve-section.tsx

@@ -12,18 +12,13 @@
  */
 import { useMemo, useState } from "react";
 import type { AuditResult } from "@/src/audit/types";
-// Score switched off — see `src/audit/scoring.ts`.
-// import { type Grade, tierName } from "@/src/audit/scoring";
-import type { Grade } from "@/src/audit/scoring";
+import { type Grade, tierName } from "@/src/audit/scoring";
 import { usePostHog } from "@/contexts/PostHogContext";
 
 interface Props {
   result: AuditResult;
-  /** The projection is switched off — see `src/audit/scoring.ts`. Optional
-   *  rather than removed so restoring it is un-commenting the two lines in
-   *  `audit-dashboard.tsx` and the sub-heading below. */
-  projected?: number;
-  projectedGrade?: Grade;
+  projected: number;
+  projectedGrade: Grade;
 }
 
 const DETECTOR_TO_PRIMARY_POLICY: Record<string, string> = {
@@ -104,7 +99,7 @@ function bulkInstall(fixes: FixRow[]): string {
   return `failproofai policies --install ${fixes.map((f) => f.name).join(" ")}`;
 }
 
-export function HowToImproveSection({ result }: Props) {
+export function HowToImproveSection({ result, projected, projectedGrade }: Props) {
   const { capture } = usePostHog();
   const fixes = useMemo(() => buildFixes(result), [result]);
   const installAllCmd = useMemo(() => bulkInstall(fixes), [fixes]);
@@ -141,18 +136,9 @@ export function HowToImproveSection({ result }: Props) {
         </button>
       </div>
       <h2 className="audit-sec-title">install or configure</h2>
-      {/* The projected-score clause is switched off. It was also the one place
-          the product promised a number it could not deliver: `deriveScore`
-          never read `enabledInConfig`, so taking this prescription and
-          re-running returned the SAME score with the projection gone. What
-          replaces it is the thing that was always true — one command, enforced
-          on every tool call. Original:
+      <div className="audit-sec-sub">
         enable all {fixes.length === 1 ? "one" : fixes.length} → projected{" "}
         <strong>{projected}</strong> · {tierName(projectedGrade).toLowerCase()}
-      */}
-      <div className="audit-sec-sub">
-        enable all {fixes.length === 1 ? "one" : fixes.length} → one command,
-        enforced on every tool call
       </div>
 
       <div className="fix-list">

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

@@ -7,31 +7,20 @@
  * appends a clipboard paste hint. Pure — no React, no DOM — so it's
  * unit-testable and shared by the client poster component.
  *
- * ## 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.
+ * 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.
  */
 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). */
@@ -44,107 +33,52 @@ 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)[] = [
-  ({ 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}`,
+  ({ 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}`,
-  ({ 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}`,
+  ({ 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}`,
 ];
 
 /** Longer, reflective — for LinkedIn. Ends on the npx CTA + @Failproof AI. */
 export const LI_TEMPLATES: ((c: ShareCtx) => string)[] = [
-  ({ 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}`,
+  ({ 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}`,
 ];
 
-/* ---------------------------------------------------------------------------
- * 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,13 +496,7 @@
 .poster-meta .of { color: var(--dim); }
 .poster-meta .poster-sep { color: var(--dim); }
 
-/* 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. */
+/* body — vertical centered stack: sigil → persona → score ─── */
 .poster-body {
   display: flex;
   flex-direction: column;
@@ -561,7 +555,6 @@
 .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;
@@ -1164,127 +1157,3 @@
 .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; }
-}
-
-/* The re-scan control in the scan header. Sits at the end of the eyebrow row so
-   it reads as an action on that section rather than a page-level nav item. */
-.scan-rerun {
-  margin-left: auto;
-  font-family: var(--font-mono);
-  font-size: 10.5px;
-  letter-spacing: 0.1em;
-  text-transform: lowercase;
-  color: var(--ink-2);
-  background: none;
-  border: 1px solid var(--line-2);
-  padding: 4px 10px;
-  cursor: pointer;
-}
-.scan-rerun:hover:not(:disabled) { color: var(--ink); border-color: var(--accent-pink); }
-.scan-rerun:disabled { opacity: 0.5; cursor: not-allowed; }
-.scan-rerun:focus-visible { outline: 2px solid var(--accent-pink); outline-offset: 2px; }

package/.next/standalone/app/settings/page.tsx

@@ -30,7 +30,7 @@ export const dynamic = "force-dynamic";
 export default async function SettingsPage() {
   // Same gate the audit, policies and projects pages carry. It was dropped in
   // the rewrite, and this is the page that least deserves to lose it: it shows
-  // the address credential alerts go to and can sign the machine out, on a dashboard an
+  // the address digests go to and can sign the machine out, on a dashboard an
   // operator may deliberately be exposing beyond localhost.
   const disabled = (process.env.FAILPROOFAI_DISABLE_PAGES ?? "")
     .split(",").map((s) => s.trim()).filter(Boolean);