@bigsteele/the-big-sean 0.2.0 → 0.2.2

package/README.md

@@ -65,7 +65,8 @@ says what it verified and what it did not.
 
 Every report card ends the same way: send it in at **bigsteele.com/scan** and get a written
 read of the three fixes that come first, in order. No call required to get it, and no pitch
-inside it. If the read turns into a build, it is the first mile of that engagement.
+inside it. If the read turns into a build, it is the first mile of that engagement. The read is
+free; the live Scan Analysis call is $497, booked from the same page.
 
 ## The name
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bigsteele/the-big-sean",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "The Big Sean: the Launch Report Card, by Big Steele and LaSean Pickens. Runs the Big Steele AI Audit, drops a 140-check launch-readiness and autonomy audit protocol into a repo for Claude Code to run, names the deliverable after the app, and independently re-computes any report's math from its grade.json so the number on the card can be proven, not trusted.",
   "type": "module",
   "license": "UNLICENSED",
@@ -37,6 +37,6 @@
     "access": "public"
   },
   "dependencies": {
-    "@bigsteele/ai-audit": "^0.2.2"
+    "@bigsteele/ai-audit": "^0.2.3"
   }
 }

package/prompt/THE-BIG-SEAN.md

@@ -15,6 +15,7 @@ Rules you never break:
 	•	Never say "100% bug-free" or "production ready." Say what you verified and what you did not.
 Step 0. The AI Audit (already run for you, or run it now)
 If .planning/launch-audit/ai-audit-<app>.md and ai-audit-<app>.json exist, big-sean ran the Big Steele AI Audit before handing you this protocol. Read both. They are evidence, cited like any other: use their findings for the checks about surfaces, model calls, tools, loops, reach, and failure visibility in Part B, and cite the file and the criterion. If they are missing, run `npx @bigsteele/ai-audit --repo . --out .planning/launch-audit` yourself (it is read-only, writes only those two files, and never opens an env file), then read them. The AI Audit's score, grade, and level go on the summary card as the AI readiness line. It replaces no check: an agent-runnable architecture still has to pass every gate.
+The AI Audit is deterministic: it reads files and counts patterns, and it can miss an agent surface that lives outside the main app (Deno edge functions, workers, a separate service, a hand-written MCP server with no SDK). Never accept its zeros on faith. If it reports zero or near zero for the MCP server, tool definitions, or memory between runs, go read supabase/functions, workers, api, and any folder named mcp, tools, agents, or intelligence yourself before grading. Where you find a surface the scanner missed, grade the capability as present with your own evidence, and record a separate finding: the surface is not discoverable (no SDK declaration, no server card or mcp.json, no mention in README, AGENTS.md, or llms.txt). Claude, Cursor, and ChatGPT discover software the way the scanner did. An agent surface a scanner cannot find is one an agent cannot find either, and that is the real finding, not the zero.
 
 Step 1. Find out what you can reach (no setup from me)
 Look for what is already on this machine and use it read-only. Do not ask me for anything.
@@ -343,6 +344,8 @@ Big Steele and LaSean Pickens wrote this standard because they build what it gra
 **bigsteele.com/scan** Upload this file. You get a written read back. No call required to get it, and no pitch inside it.
 
 If the read turns into a build, it is the first mile of that engagement. The path to 100 above is the plan; the read tells you where to start.
+
+The written read is free. If you want it walked through live, the Scan Analysis call is $497, booked at the same page.
 Minimums, or the report is not done: every one of the one hundred forty checks has a written test and at least one evidence entry or an UNKNOWN reason; every table and every route appears in the inventories; the findings list contains every FAIL and every UNKNOWN as its own row. If the app is large, the report is long. That is correct.
 Make the HTML readable by a non-engineer at the top and complete for an engineer underneath: a score dial, category cards with color by band, filters by category and severity and status, expandable evidence, and a button that downloads grade.json. Put the summary card from Step 7 at the very top of the page so the first screen answers the question.
 Step 7. Hand it to me