mesa-ai-cto 0.0.1 → 0.2.0

package/LICENSE

@@ -1,155 +1,155 @@
-THE AI CTO — PROPRIETARY LICENSE
-
-Copyright (c) 2026 Mesa Startup Lab. All rights reserved.
-
-Created by Gaurav Madan and the Mesa Startup Lab team.
-
---------------------------------------------------------------------------------
-1. DEFINITIONS
---------------------------------------------------------------------------------
-
-"The Kit" means this repository and everything in it: the module execution guides,
-the concept cards, the checklists, the kit manifests, the AGENTS.md and
-INITIALIZE.md templates, the prompts, the pitch deck, the scripts, and any
-software published from it including the `mesa-ai-cto` command-line tool.
-
-"Licensor" means Mesa Startup Lab, the owner of the Kit.
-
-"You" means the individual or organisation granted a licence under these terms.
-
-"Your Products" means software You build for Yourself or for Your clients using
-the Kit.
-
-"Generated Code" means source code, configuration and other files produced by an
-AI agent, by You, or by the `mesa-ai-cto` tool while following the Kit.
-
---------------------------------------------------------------------------------
-2. WHAT YOU MAY DO
---------------------------------------------------------------------------------
-
-Subject to Section 3, You are granted a non-exclusive, non-transferable,
-worldwide licence to:
-
-  a. USE the Kit to design, build, test, deploy and operate Your Products,
-     including for commercial purposes and including work delivered to clients.
-
-  b. OWN the Generated Code outright. Nothing in this licence claims any right
-     over the code You or Your agent produce by following the Kit. You may
-     license, sell, open-source or keep that code entirely as You choose, with
-     no obligation to attribute the Kit.
-
-  c. COPY the guides, checklists, prompts and templates into Your own private
-     repositories, and modify them there, for use on Your Products.
-
-  d. SHARE the Kit within Your organisation, with employees and contractors
-     working on Your Products, provided they are bound by these terms.
-
---------------------------------------------------------------------------------
-3. WHAT YOU MAY NOT DO
---------------------------------------------------------------------------------
-
-You may not, without prior written permission from the Licensor:
-
-  a. REDISTRIBUTE, resell, rent, lease, sublicense or otherwise make the Kit, or
-     any substantial part of it, available to anyone outside Your organisation.
-
-  b. PUBLISH the Kit, or any substantial part of it, publicly — including in a
-     public repository, a website, a book, a course, or a video series.
-
-  c. OFFER a product or service that is substantially the Kit, or that is derived
-     from it and competes with it, whether paid or free.
-
-  d. USE the Kit, or any substantial part of it, as training data for a machine
-     learning model, or to generate a derivative work intended for distribution.
-
-  e. REMOVE or obscure any copyright, attribution or licence notice in the Kit.
-
-For clarity: Section 3 restricts redistribution of *the Kit*. It places no
-restriction whatsoever on Your Products or on Generated Code, which are Yours
-under Section 2(b).
-
---------------------------------------------------------------------------------
-4. NO WARRANTY
---------------------------------------------------------------------------------
-
-THE KIT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
-INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
-PARTICULAR PURPOSE, AND NONINFRINGEMENT.
-
-The Kit contains security guidance, checklists and architectural
-recommendations. These are offered in good faith and are not a substitute for a
-professional security audit, legal advice, or compliance review appropriate to
-Your jurisdiction and industry. Software versions, provider behaviour and
-security best practice all change; each guide states the versions and the date it
-was last verified, and You are responsible for confirming that guidance is still
-current before relying on it.
-
-Following the Kit does not guarantee that Your Products are secure, correct,
-compliant, or fit for any purpose. You remain solely responsible for what You
-build, deploy and operate.
-
---------------------------------------------------------------------------------
-5. LIMITATION OF LIABILITY
---------------------------------------------------------------------------------
-
-IN NO EVENT SHALL THE LICENSOR OR ITS AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
-OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE KIT OR THE USE OR OTHER DEALINGS IN THE
-KIT — including without limitation any loss of data, loss of profit, business
-interruption, security incident, or third-party claim arising from software built
-using the Kit.
-
---------------------------------------------------------------------------------
-6. TERMINATION
---------------------------------------------------------------------------------
-
-This licence terminates automatically if You breach Section 3. On termination You
-must stop using the Kit and delete Your copies of it. Your Products and Generated
-Code created before termination are unaffected and remain Yours.
-
---------------------------------------------------------------------------------
-7. GOVERNING LAW
---------------------------------------------------------------------------------
-
-This licence is governed by the laws of India, and the courts of India shall have
-exclusive jurisdiction over any dispute arising from it.
-
---------------------------------------------------------------------------------
-8. CONTACT
---------------------------------------------------------------------------------
-
-For permissions beyond the scope of this licence — redistribution, resale,
-white-labelling, training use, or an enterprise arrangement — contact Mesa Startup
-Lab.
-
-================================================================================
-NOTICE — PROVENANCE
-================================================================================
-
-The Kit is not theory. Its architectural patterns, its security checklists and
-its traps are generalised from Mesa LMS, a production platform built and operated
-by Mesa Startup Lab: four user roles with scoped permissions, roughly forty
-backend modules, around fifty frontend feature slices, PostgreSQL, object
-storage, transactional email, web push, a progressive web app and an LLM module.
-
-Specifically:
-
-  * The response envelope, the error hierarchy, the boot-time environment
-    validation, the guard chain and the request logging format are generalised
-    from that codebase.
-
-  * The security checklists are derived from a review of it. Findings carry
-    identifiers (SEC-01 … SEC-20) so a rule in a checklist can be traced to the
-    incident or pattern that produced it. That review is included at
-    docs/specs/2026-08-19-mesa-security-review.md.
-
-  * The "How Mesa LMS does it" boxes in the concept cards point at real files in
-    that codebase, not at illustrative examples.
-
-Mesa LMS itself is separate proprietary software and is not licensed by this
-document. No right to Mesa LMS, its source code, its data, or any of its
-trademarks is granted here. The Kit is stack-generic: nothing in it requires You
-to use the same stack, the same providers, or the same conventions.
-
-"The AI CTO", "Mesa Startup Lab", "Mesa School of Business" and "Mesa LMS" are
-marks of Mesa Startup Lab.
+THE AI CTO — PROPRIETARY LICENSE
+
+Copyright (c) 2026 Mesa Startup Lab. All rights reserved.
+
+Created by Gaurav Madan and the Mesa Startup Lab team.
+
+--------------------------------------------------------------------------------
+1. DEFINITIONS
+--------------------------------------------------------------------------------
+
+"The Kit" means this repository and everything in it: the module execution guides,
+the concept cards, the checklists, the kit manifests, the AGENTS.md and
+INITIALIZE.md templates, the prompts, the pitch deck, the scripts, and any
+software published from it including the `mesa-ai-cto` command-line tool.
+
+"Licensor" means Mesa Startup Lab, the owner of the Kit.
+
+"You" means the individual or organisation granted a licence under these terms.
+
+"Your Products" means software You build for Yourself or for Your clients using
+the Kit.
+
+"Generated Code" means source code, configuration and other files produced by an
+AI agent, by You, or by the `mesa-ai-cto` tool while following the Kit.
+
+--------------------------------------------------------------------------------
+2. WHAT YOU MAY DO
+--------------------------------------------------------------------------------
+
+Subject to Section 3, You are granted a non-exclusive, non-transferable,
+worldwide licence to:
+
+  a. USE the Kit to design, build, test, deploy and operate Your Products,
+     including for commercial purposes and including work delivered to clients.
+
+  b. OWN the Generated Code outright. Nothing in this licence claims any right
+     over the code You or Your agent produce by following the Kit. You may
+     license, sell, open-source or keep that code entirely as You choose, with
+     no obligation to attribute the Kit.
+
+  c. COPY the guides, checklists, prompts and templates into Your own private
+     repositories, and modify them there, for use on Your Products.
+
+  d. SHARE the Kit within Your organisation, with employees and contractors
+     working on Your Products, provided they are bound by these terms.
+
+--------------------------------------------------------------------------------
+3. WHAT YOU MAY NOT DO
+--------------------------------------------------------------------------------
+
+You may not, without prior written permission from the Licensor:
+
+  a. REDISTRIBUTE, resell, rent, lease, sublicense or otherwise make the Kit, or
+     any substantial part of it, available to anyone outside Your organisation.
+
+  b. PUBLISH the Kit, or any substantial part of it, publicly — including in a
+     public repository, a website, a book, a course, or a video series.
+
+  c. OFFER a product or service that is substantially the Kit, or that is derived
+     from it and competes with it, whether paid or free.
+
+  d. USE the Kit, or any substantial part of it, as training data for a machine
+     learning model, or to generate a derivative work intended for distribution.
+
+  e. REMOVE or obscure any copyright, attribution or licence notice in the Kit.
+
+For clarity: Section 3 restricts redistribution of *the Kit*. It places no
+restriction whatsoever on Your Products or on Generated Code, which are Yours
+under Section 2(b).
+
+--------------------------------------------------------------------------------
+4. NO WARRANTY
+--------------------------------------------------------------------------------
+
+THE KIT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+PARTICULAR PURPOSE, AND NONINFRINGEMENT.
+
+The Kit contains security guidance, checklists and architectural
+recommendations. These are offered in good faith and are not a substitute for a
+professional security audit, legal advice, or compliance review appropriate to
+Your jurisdiction and industry. Software versions, provider behaviour and
+security best practice all change; each guide states the versions and the date it
+was last verified, and You are responsible for confirming that guidance is still
+current before relying on it.
+
+Following the Kit does not guarantee that Your Products are secure, correct,
+compliant, or fit for any purpose. You remain solely responsible for what You
+build, deploy and operate.
+
+--------------------------------------------------------------------------------
+5. LIMITATION OF LIABILITY
+--------------------------------------------------------------------------------
+
+IN NO EVENT SHALL THE LICENSOR OR ITS AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
+OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE KIT OR THE USE OR OTHER DEALINGS IN THE
+KIT — including without limitation any loss of data, loss of profit, business
+interruption, security incident, or third-party claim arising from software built
+using the Kit.
+
+--------------------------------------------------------------------------------
+6. TERMINATION
+--------------------------------------------------------------------------------
+
+This licence terminates automatically if You breach Section 3. On termination You
+must stop using the Kit and delete Your copies of it. Your Products and Generated
+Code created before termination are unaffected and remain Yours.
+
+--------------------------------------------------------------------------------
+7. GOVERNING LAW
+--------------------------------------------------------------------------------
+
+This licence is governed by the laws of India, and the courts of India shall have
+exclusive jurisdiction over any dispute arising from it.
+
+--------------------------------------------------------------------------------
+8. CONTACT
+--------------------------------------------------------------------------------
+
+For permissions beyond the scope of this licence — redistribution, resale,
+white-labelling, training use, or an enterprise arrangement — contact Mesa Startup
+Lab.
+
+================================================================================
+NOTICE — PROVENANCE
+================================================================================
+
+The Kit is not theory. Its architectural patterns, its security checklists and
+its traps are generalised from Mesa LMS, a production platform built and operated
+by Mesa Startup Lab: four user roles with scoped permissions, roughly forty
+backend modules, around fifty frontend feature slices, PostgreSQL, object
+storage, transactional email, web push, a progressive web app and an LLM module.
+
+Specifically:
+
+  * The response envelope, the error hierarchy, the boot-time environment
+    validation, the guard chain and the request logging format are generalised
+    from that codebase.
+
+  * The security checklists are derived from a review of it. Findings carry
+    identifiers (SEC-01 … SEC-20) so a rule in a checklist can be traced to the
+    incident or pattern that produced it. That review is included at
+    docs/specs/2026-08-19-mesa-security-review.md.
+
+  * The "How Mesa LMS does it" boxes in the concept cards point at real files in
+    that codebase, not at illustrative examples.
+
+Mesa LMS itself is separate proprietary software and is not licensed by this
+document. No right to Mesa LMS, its source code, its data, or any of its
+trademarks is granted here. The Kit is stack-generic: nothing in it requires You
+to use the same stack, the same providers, or the same conventions.
+
+"The AI CTO", "Mesa Startup Lab", "Mesa School of Business" and "Mesa LMS" are
+marks of Mesa Startup Lab.

package/README.md

@@ -1,34 +1,114 @@
-# mesa-ai-cto
-
-Scaffolds a production-grade project from a plan produced by [The AI CTO](https://github.com/Mesa-School).
-
-> **Not yet released.** `0.0.1` is a placeholder and does not scaffold anything.
-> The working client ships as `0.1.0`.
-
-## What it will do
-
-You describe your business to the AI CTO. It produces a plan — the tier, the stack, the
-modules, and what to build first. The plan gives you one command:
-
-```bash
-npx mesa-ai-cto my-app --tier1 --token=mesa_i_…
-```
-
-That command checks your machine, installs the right codebase, writes your plan and the
-module guides alongside it, installs dependencies, and leaves you with something running
-on localhost.
-
-```
-my-app/
-├── src/
-├── docs/          module guides and checklists
-├── plan.md        what you are building, and in what order
-└── mesa.json
-```
-
-## Licence
-
-Proprietary. See [LICENSE](LICENSE).
-
-The guides, checklists and boilerplate are **not** contained in this package. They are
-delivered only to a holder of a valid install token.
+# mesa-ai-cto
+
+Check your machine, then scaffold a production-grade project from a plan produced by
+[The AI CTO](https://github.com/Mesa-School).
+
+## `doctor`
+
+```bash
+npx mesa-ai-cto doctor
+```
+
+```
+  Runtime
+    ✓ Node.js           v22.18.0
+    ✓ npm               10.9.3
+  Git
+    ✓ git               git version 2.50.0
+    ✓ user.name         Gaurav Madan
+    ✗ user.email        not set
+  Editor
+    ✓ VS Code           detected
+    ✗ `code` on PATH    not on PATH
+  GitHub
+    ✓ GitHub CLI        github.com
+  Vercel
+    ✗ Vercel CLI        not installed
+
+  Fix this before you start:
+    git config --global user.email "you@example.com"
+
+  Not needed yet, but you will want:
+    In VS Code: Command Palette → "Shell Command: Install 'code' command in PATH"
+    npm install -g vercel
+
+  Not ready yet — see above.
+```
+
+Blocking problems are listed apart from ones you will only need later, because "one thing
+to fix" sitting above "ready to build" does not answer the only question this command
+exists to answer.
+
+**Three results, not two.** A tool can be *missing*, *installed but not working*, or
+*impossible to reach right now* — a `gh auth status` that times out on hotel wifi has not
+told us your account is broken. Each leads to different advice, so each is reported
+differently, and a result we could not determine never fails the run.
+
+### For coding agents
+
+`doctor` is designed to be run by Claude Code, Codex or any agent driving a founder's
+setup — so it does not just say what is wrong, it says what to do about it, on this
+operating system, and whether the agent may do it unattended.
+
+```bash
+npx mesa-ai-cto doctor --json
+```
+
+JSON goes to stdout and nothing else does, so it pipes cleanly. Human output goes to
+stderr. Exit codes: `0` ready, `1` a required check failed, `2` a usage error.
+
+**Read `nextActions`.** It is the failures only, already ordered with blocking ones first,
+so an agent that repairs one item and re-runs has removed the reason the build could not
+start.
+
+```json
+{
+  "ok": false,
+  "nextActions": [
+    { "id": "git.installed", "blocking": true, "autoRunnable": true,
+      "command": "winget install --id Git.Git -e --accept-package-agreements" },
+
+    { "id": "git.email", "blocking": true, "autoRunnable": false, "needsInput": true,
+      "commandTemplate": "git config --global user.email \"<user.email>\"" },
+
+    { "id": "editor.code", "blocking": false, "autoRunnable": false,
+      "manual": "Open VS Code, press the Command Palette shortcut, and run \"Shell Command: Install 'code' command in PATH\"" }
+  ]
+}
+```
+
+The loop:
+
+1. Run `doctor --json`. If `ok` is true, stop.
+2. For each entry in `nextActions` where `autoRunnable` is **true** — run `command`.
+3. Where `needsInput` is true — **ask the founder for the value**, then run
+   `commandTemplate` with the placeholder replaced. Do not invent one: a repository whose
+   history says `you@example.com` is worse than one with no commits, and rewriting author
+   history later is painful.
+4. Where only `manual` is present — relay it and wait. There is no command; guessing one
+   (symlinking `code` by hand, for instance) creates something the next update overwrites.
+5. Re-run `doctor --json`. Repeat at most a few times, then report what is left.
+
+Only act on entries where `blocking` is true if the goal is to get building. The rest are
+needed for deploying later and can wait.
+
+**Platform.** Commands are chosen for the machine `doctor` ran on — `brew` on macOS,
+`winget` on Windows. On Linux, where package managers differ too much between
+distributions to guess safely, there is no `command`: the entry carries a `url` instead,
+and guessing `apt` would be wrong often enough to matter.
+
+## Coming next
+
+```bash
+npx mesa-ai-cto <name> --tier<N> --token=<t>   scaffold a project
+npx mesa-ai-cto add <module>                    add a module guide
+```
+
+You get that command, with its token, from your plan in the AI CTO dashboard.
+
+## Licence
+
+Proprietary. See [LICENSE](LICENSE).
+
+The guides, checklists and boilerplate are **not** contained in this package. They are
+delivered only to a holder of a valid install token.

package/bin/mesa-ai-cto.mjs

@@ -1,50 +1,9 @@
-#!/usr/bin/env node
-/**
- * Placeholder release.
- *
- * This exists so the name is held by the product that will use it — the dashboard already
- * renders `npx mesa-ai-cto …` in every plan it produces, and a command that resolves to
- * somebody else's package is worse than one that resolves to nothing.
- *
- * It also proves the publish pipeline while nothing is at stake. A version number can never
- * be reused and a package cannot meaningfully be unpublished after 72 hours, so the first
- * real release should not be the first release.
- *
- * Replaced by the real client in 0.1.0. See docs/specs/2026-08-22-cli-install-design.md.
- */
-
-const args = process.argv.slice(2);
-const wants = (...flags) => args.some((a) => flags.includes(a));
-
-// `--version` and `--help` are questions this build can answer honestly, so they succeed.
-if (wants("-v", "--version")) {
-  process.stdout.write("0.0.1\n");
-  process.exit(0);
-}
-
-const HELP = `
-  mesa-ai-cto — scaffold a project from your AI CTO plan
-
-  Not yet released. This version is a placeholder and does not scaffold anything.
-
-  When it ships:
-    npx mesa-ai-cto <name> --tier<N> --token=<t>   scaffold a project
-    npx mesa-ai-cto doctor                          check your machine
-    npx mesa-ai-cto add <module>                    add a module guide
-
-  You get the command, with its token, from your plan in the AI CTO dashboard.
-`;
-
-if (wants("-h", "--help") || args.length === 0) {
-  process.stdout.write(`${HELP}\n`);
-  // No arguments is a request for help, and help was given.
-  process.exit(0);
-}
-
-// Anything else is somebody — or some agent — asking this to do real work. It cannot, and
-// exiting 0 would report success for a project that was never created.
-process.stderr.write(
-  "\n  mesa-ai-cto is not yet released — this is a placeholder version.\n" +
-    "  Nothing has been created. Run with --help for what is coming.\n\n",
-);
-process.exit(1);
+#!/usr/bin/env node
+/**
+ * The bin entry is a shim so the published package has one job here: hand control to the
+ * compiled CLI and turn its return value into an exit code. Keeping `process.exit` out of
+ * `src/` is what makes every command testable.
+ */
+import { runCli } from "../dist/cli.js";
+
+process.exitCode = await runCli(process.argv.slice(2));

package/dist/checks/cloud.js

@@ -0,0 +1,73 @@
+import { perPlatform } from "./types.js";
+/**
+ * Neither of these is required to reach localhost. They ship now so a founder sees what is
+ * coming in the next milestone without being blocked on it today.
+ *
+ * Neither probes a permission by using it: nothing is created to find out whether creating
+ * is allowed. `gh auth status` reports what the token can already do; the real operation
+ * reports the real failure when it runs.
+ */
+function authCheck(args) {
+    return {
+        id: args.id,
+        group: args.group,
+        label: args.label,
+        required: false,
+        timeoutMs: 5000,
+        run: async ({ exec, present, platform }) => {
+            if (!(await present(args.cmd))) {
+                return {
+                    state: "fail",
+                    detail: "not installed",
+                    fix: args.installFix,
+                    remedy: args.installRemedy(platform),
+                };
+            }
+            const out = await exec(args.cmd, args.probe, { timeoutMs: 5000 });
+            if (out.kind === "ok") {
+                // `gh auth status` prints its useful line to stderr, not stdout.
+                const line = (out.stdout || out.stderr).split("\n").find((l) => l.trim().length > 0);
+                return { state: "pass", detail: (line ?? "authenticated").trim() };
+            }
+            // A network call that did not answer has told us nothing about the account.
+            if (out.kind === "timeout")
+                return { state: "unknown", detail: "no response — offline?" };
+            if (out.kind === "error")
+                return { state: "unknown", detail: out.code };
+            return {
+                state: "fail",
+                detail: "not authenticated",
+                fix: args.loginFix,
+                // Runnable, but it opens a browser and waits for a person. An agent should run it
+                // and then tell the founder to finish in the browser, not assume it completed.
+                remedy: { manual: `${args.loginFix} — this opens a browser and needs you to sign in` },
+            };
+        },
+    };
+}
+export const ghAuth = authCheck({
+    id: "github.auth",
+    group: "GitHub",
+    label: "GitHub CLI",
+    cmd: "gh",
+    probe: ["auth", "status"],
+    installFix: "Install the GitHub CLI from cli.github.com",
+    installRemedy: (platform) => perPlatform(platform, {
+        darwin: "brew install gh",
+        win32: "winget install --id GitHub.cli -e --accept-package-agreements",
+        manual: "Install the GitHub CLI",
+        url: "https://cli.github.com",
+    }),
+    loginFix: "gh auth login",
+});
+export const vercelAuth = authCheck({
+    id: "vercel.auth",
+    group: "Vercel",
+    label: "Vercel CLI",
+    cmd: "vercel",
+    probe: ["whoami"],
+    installFix: "npm install -g vercel",
+    // The only one that is genuinely identical everywhere, because it is an npm package.
+    installRemedy: () => ({ command: "npm install -g vercel" }),
+    loginFix: "vercel login",
+});

package/dist/checks/editor.js

@@ -0,0 +1,45 @@
+/**
+ * Installed and on the PATH are different facts.
+ *
+ * A founder who has VS Code open while being told to install VS Code stops trusting the
+ * tool. The fix names the command palette entry, because that is what actually resolves it.
+ */
+export const codeOnPath = {
+    id: "editor.code",
+    group: "Editor",
+    label: "`code` on PATH",
+    // Not required: nothing about reaching localhost needs the shell command.
+    required: false,
+    timeoutMs: 3000,
+    run: async ({ present }) => {
+        if (await present("code"))
+            return { state: "pass", detail: "available" };
+        return {
+            state: "fail",
+            detail: "not on PATH",
+            fix: 'In VS Code: Command Palette → "Shell Command: Install \'code\' command in PATH"',
+            // No command exists — this is a GUI action inside the editor. Saying so plainly
+            // stops an agent inventing a symlink into /usr/local/bin that the next VS Code
+            // update will overwrite.
+            remedy: {
+                manual: 'Open VS Code, press the Command Palette shortcut, and run "Shell Command: Install \'code\' command in PATH"',
+            },
+        };
+    },
+};
+export const vscodePresent = {
+    id: "editor.vscode",
+    group: "Editor",
+    label: "VS Code",
+    required: false,
+    timeoutMs: 3000,
+    run: async ({ present }) => (await present("code"))
+        ? { state: "pass", detail: "detected" }
+        : {
+            state: "unknown",
+            // Absence of the shell command is not absence of the editor, and there is no
+            // portable way to see an installed GUI application. Reporting "not installed"
+            // here would be a guess, and a wrong one for most people who hit it.
+            detail: "could not detect without the `code` command",
+        },
+};