@bigsteele/the-big-sean 0.2.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bigsteele/the-big-sean",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "license": "UNLICENSED",
@@ -37,6 +37,6 @@
37
37
  "access": "public"
38
38
  },
39
39
  "dependencies": {
40
- "@bigsteele/ai-audit": "^0.2.2"
40
+ "@bigsteele/ai-audit": "^0.2.3"
41
41
  }
42
42
  }
@@ -15,6 +15,7 @@ Rules you never break:
15
15
  • Never say "100% bug-free" or "production ready." Say what you verified and what you did not.
16
16
  Step 0. The AI Audit (already run for you, or run it now)
17
17
  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.
18
+ 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.
18
19
 
19
20
  Step 1. Find out what you can reach (no setup from me)
20
21
  Look for what is already on this machine and use it read-only. Do not ask me for anything.