@nebulr-group/bridge-cli 0.6.6 → 0.6.7

package/dist/commands/check.command.d.ts

@@ -5,6 +5,7 @@ export declare function checkGates(root: string): {
     scanned: number;
     findings: GateFinding[];
 };
+export declare const SUCCESS_MESSAGE_REMINDER: string;
 export declare function formatGateReport(scanned: number, findings: GateFinding[]): string;
 export declare function registerCheckCommands(program: Command): void;
 //# sourceMappingURL=check.command.d.ts.map

package/dist/commands/check.command.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"check.command.d.ts","sourceRoot":"","sources":["../../src/commands/check.command.ts"],"names":[],"mappings":"AAWA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAIpC,OAAO,EAKL,KAAK,WAAW,EACjB,MAAM,kBAAkB,CAAC;AAE1B,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,CAoBzD;AAED,wBAAgB,UAAU,CAAC,IAAI,EAAE,MAAM,GAAG;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,WAAW,EAAE,CAAA;CAAE,CAIrF;AAUD,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,EAAE,QAAQ,EAAE,WAAW,EAAE,GAAG,MAAM,CAwBjF;AAED,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAqB5D"}
+{"version":3,"file":"check.command.d.ts","sourceRoot":"","sources":["../../src/commands/check.command.ts"],"names":[],"mappings":"AAWA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAIpC,OAAO,EAKL,KAAK,WAAW,EACjB,MAAM,kBAAkB,CAAC;AAE1B,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,CAoBzD;AAED,wBAAgB,UAAU,CAAC,IAAI,EAAE,MAAM,GAAG;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,WAAW,EAAE,CAAA;CAAE,CAIrF;AAeD,eAAO,MAAM,wBAAwB,QAEoI,CAAC;AAE1K,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,EAAE,QAAQ,EAAE,WAAW,EAAE,GAAG,MAAM,CAwBjF;AAED,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAqB5D"}

package/dist/commands/check.command.js

@@ -48,9 +48,16 @@ const KIND_LABEL = {
     'plan-name': 'plan-name check',
     'removed-api': 'removed API',
 };
+// TBP-952 — the gate check is the last command of every integration, in every
+// run we looked at, and agents read its output through `tail -N`. The success
+// message was an instruction near the end of a long guide read at the start,
+// and agents dropped it by the time they finished. So the passing line itself
+// says what comes next. One line, so no `tail` cuts it off.
+export const SUCCESS_MESSAGE_REMINDER = "If you just finished adding Bridge sign-in, flags, plans or plan limits for the developer, your reply starts with Bridge's success message: " +
+    '`npx @nebulr-group/bridge-cli guide integration-success` (MCP: get_integration_guide topic integration-success) has it and says which one to show and how to fill it.';
 export function formatGateReport(scanned, findings) {
     if (findings.length === 0) {
-        return `bridge check gates: ${scanned} files checked, no direct role, privilege, plan or plan-feature checks. Every gate goes through a flag.\n`;
+        return `bridge check gates: ${scanned} files checked, no direct role, privilege, plan or plan-feature checks. Every gate goes through a flag. ${SUCCESS_MESSAGE_REMINDER}\n`;
     }
     const lines = [
         `bridge check gates: ${findings.length} direct check${findings.length === 1 ? '' : 's'} in ${scanned} files.`,

package/dist/commands/check.command.js.map

@@ -1 +1 @@
-{"version":3,"file":"check.command.js","sourceRoot":"","sources":["../../src/commands/check.command.ts"],"names":[],"mappings":"AAAA,4EAA4E;AAC5E,EAAE;AACF,6EAA6E;AAC7E,+EAA+E;AAC/E,gFAAgF;AAChF,+EAA+E;AAC/E,8EAA8E;AAC9E,wEAAwE;AACxE,EAAE;AACF,2EAA2E;AAG3E,OAAO,EAAE,WAAW,EAAE,YAAY,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAC9D,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpD,OAAO,EAAE,WAAW,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AACxE,OAAO,EACL,qBAAqB,EACrB,YAAY,EACZ,gBAAgB,EAChB,eAAe,GAEhB,MAAM,kBAAkB,CAAC;AAE1B,MAAM,UAAU,kBAAkB,CAAC,IAAY;IAC7C,MAAM,GAAG,GAAa,EAAE,CAAC;IACzB,MAAM,IAAI,GAAG,CAAC,GAAW,EAAE,EAAE;QAC3B,KAAK,MAAM,IAAI,IAAI,WAAW,CAAC,GAAG,CAAC,EAAE,CAAC;YACpC,MAAM,IAAI,GAAG,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;YAC7B,IAAI,IAAI,CAAC;YACT,IAAI,CAAC;gBACH,IAAI,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC;YACxB,CAAC;YAAC,MAAM,CAAC;gBACP,SAAS;YACX,CAAC;YACD,IAAI,IAAI,CAAC,WAAW,EAAE,EAAE,CAAC;gBACvB,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC;oBAAE,IAAI,CAAC,IAAI,CAAC,CAAC;YACnE,CAAC;iBAAM,IAAI,eAAe,CAAC,IAAI,CAAC,EAAE,CAAC;gBACjC,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YACjB,CAAC;QACH,CAAC;IACH,CAAC,CAAC;IACF,IAAI,CAAC,IAAI,CAAC,CAAC;IACX,OAAO,GAAG,CAAC,IAAI,EAAE,CAAC;AACpB,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAY;IACrC,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,MAAM,QAAQ,GAAG,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,gBAAgB,CAAC,YAAY,CAAC,IAAI,EAAE,OAAO,CAAC,EAAE,QAAQ,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC,CAAC,CAAC;IAC9G,OAAO,EAAE,OAAO,EAAE,KAAK,CAAC,MAAM,EAAE,QAAQ,EAAE,CAAC;AAC7C,CAAC;AAED,MAAM,UAAU,GAAwC;IACtD,IAAI,EAAE,YAAY;IAClB,SAAS,EAAE,iBAAiB;IAC5B,cAAc,EAAE,oBAAoB;IACpC,WAAW,EAAE,iBAAiB;IAC9B,aAAa,EAAE,aAAa;CAC7B,CAAC;AAEF,MAAM,UAAU,gBAAgB,CAAC,OAAe,EAAE,QAAuB;IACvE,IAAI,QAAQ,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,uBAAuB,OAAO,2GAA2G,CAAC;IACnJ,CAAC;IACD,MAAM,KAAK,GAAG;QACZ,uBAAuB,QAAQ,CAAC,MAAM,gBAAgB,QAAQ,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,OAAO,OAAO,SAAS;QAC7G,EAAE;QACF,+FAA+F;QAC/F,yGAAyG;QACzG,0FAA0F;QAC1F,EAAE;KACH,CAAC;IACF,KAAK,MAAM,CAAC,IAAI,QAAQ,EAAE,CAAC;QACzB,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,IAAI,IAAI,CAAC,CAAC,IAAI,KAAK,UAAU,CAAC,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QACzD,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC;QAC5B,KAAK,CAAC,IAAI,CAAC,gBAAgB,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC;QACxC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACjB,CAAC;IACD,KAAK,CAAC,IAAI,CACR,wIAAwI,EACxI,sHAAsH,EACtH,QAAQ,qBAAqB,qDAAqD,CACnF,CAAC;IACF,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC;AACjC,CAAC;AAED,MAAM,UAAU,qBAAqB,CAAC,OAAgB;IACpD,MAAM,KAAK,GAAG,OAAO,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC,WAAW,CAAC,8DAA8D,CAAC,CAAC;IAEnH,KAAK;SACF,OAAO,CAAC,OAAO,CAAC;SAChB,WAAW,CACV,wIAAwI,CACzI;SACA,MAAM,CAAC,cAAc,EAAE,yCAAyC,EAAE,OAAO,CAAC,GAAG,EAAE,CAAC;SAChF,MAAM,CAAC,QAAQ,EAAE,4BAA4B,CAAC;SAC9C,MAAM,CAAC,CAAC,IAAqC,EAAE,EAAE;QAChD,IAAI,CAAC;YACH,MAAM,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;YAC/B,MAAM,EAAE,OAAO,EAAE,QAAQ,EAAE,GAAG,UAAU,CAAC,IAAI,CAAC,CAAC;YAC/C,IAAI,IAAI,CAAC,IAAI;gBAAE,aAAa,CAAC,EAAE,OAAO,EAAE,QAAQ,EAAE,CAAC,CAAC;;gBAC/C,YAAY,CAAC,gBAAgB,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC,CAAC;YACvD,IAAI,QAAQ,CAAC,MAAM,GAAG,CAAC;gBAAE,OAAO,CAAC,QAAQ,GAAG,CAAC,CAAC;QAChD,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,WAAW,CAAC,KAAK,CAAC,CAAC;QACrB,CAAC;IACH,CAAC,CAAC,CAAC;AACP,CAAC"}
+{"version":3,"file":"check.command.js","sourceRoot":"","sources":["../../src/commands/check.command.ts"],"names":[],"mappings":"AAAA,4EAA4E;AAC5E,EAAE;AACF,6EAA6E;AAC7E,+EAA+E;AAC/E,gFAAgF;AAChF,+EAA+E;AAC/E,8EAA8E;AAC9E,wEAAwE;AACxE,EAAE;AACF,2EAA2E;AAG3E,OAAO,EAAE,WAAW,EAAE,YAAY,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAC9D,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpD,OAAO,EAAE,WAAW,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AACxE,OAAO,EACL,qBAAqB,EACrB,YAAY,EACZ,gBAAgB,EAChB,eAAe,GAEhB,MAAM,kBAAkB,CAAC;AAE1B,MAAM,UAAU,kBAAkB,CAAC,IAAY;IAC7C,MAAM,GAAG,GAAa,EAAE,CAAC;IACzB,MAAM,IAAI,GAAG,CAAC,GAAW,EAAE,EAAE;QAC3B,KAAK,MAAM,IAAI,IAAI,WAAW,CAAC,GAAG,CAAC,EAAE,CAAC;YACpC,MAAM,IAAI,GAAG,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;YAC7B,IAAI,IAAI,CAAC;YACT,IAAI,CAAC;gBACH,IAAI,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC;YACxB,CAAC;YAAC,MAAM,CAAC;gBACP,SAAS;YACX,CAAC;YACD,IAAI,IAAI,CAAC,WAAW,EAAE,EAAE,CAAC;gBACvB,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC;oBAAE,IAAI,CAAC,IAAI,CAAC,CAAC;YACnE,CAAC;iBAAM,IAAI,eAAe,CAAC,IAAI,CAAC,EAAE,CAAC;gBACjC,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YACjB,CAAC;QACH,CAAC;IACH,CAAC,CAAC;IACF,IAAI,CAAC,IAAI,CAAC,CAAC;IACX,OAAO,GAAG,CAAC,IAAI,EAAE,CAAC;AACpB,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAY;IACrC,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,MAAM,QAAQ,GAAG,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,gBAAgB,CAAC,YAAY,CAAC,IAAI,EAAE,OAAO,CAAC,EAAE,QAAQ,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC,CAAC,CAAC;IAC9G,OAAO,EAAE,OAAO,EAAE,KAAK,CAAC,MAAM,EAAE,QAAQ,EAAE,CAAC;AAC7C,CAAC;AAED,MAAM,UAAU,GAAwC;IACtD,IAAI,EAAE,YAAY;IAClB,SAAS,EAAE,iBAAiB;IAC5B,cAAc,EAAE,oBAAoB;IACpC,WAAW,EAAE,iBAAiB;IAC9B,aAAa,EAAE,aAAa;CAC7B,CAAC;AAEF,8EAA8E;AAC9E,8EAA8E;AAC9E,6EAA6E;AAC7E,8EAA8E;AAC9E,4DAA4D;AAC5D,MAAM,CAAC,MAAM,wBAAwB,GACnC,8IAA8I;IAC9I,uKAAuK,CAAC;AAE1K,MAAM,UAAU,gBAAgB,CAAC,OAAe,EAAE,QAAuB;IACvE,IAAI,QAAQ,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,uBAAuB,OAAO,2GAA2G,wBAAwB,IAAI,CAAC;IAC/K,CAAC;IACD,MAAM,KAAK,GAAG;QACZ,uBAAuB,QAAQ,CAAC,MAAM,gBAAgB,QAAQ,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,OAAO,OAAO,SAAS;QAC7G,EAAE;QACF,+FAA+F;QAC/F,yGAAyG;QACzG,0FAA0F;QAC1F,EAAE;KACH,CAAC;IACF,KAAK,MAAM,CAAC,IAAI,QAAQ,EAAE,CAAC;QACzB,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,IAAI,IAAI,CAAC,CAAC,IAAI,KAAK,UAAU,CAAC,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QACzD,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC;QAC5B,KAAK,CAAC,IAAI,CAAC,gBAAgB,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC;QACxC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACjB,CAAC;IACD,KAAK,CAAC,IAAI,CACR,wIAAwI,EACxI,sHAAsH,EACtH,QAAQ,qBAAqB,qDAAqD,CACnF,CAAC;IACF,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC;AACjC,CAAC;AAED,MAAM,UAAU,qBAAqB,CAAC,OAAgB;IACpD,MAAM,KAAK,GAAG,OAAO,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC,WAAW,CAAC,8DAA8D,CAAC,CAAC;IAEnH,KAAK;SACF,OAAO,CAAC,OAAO,CAAC;SAChB,WAAW,CACV,wIAAwI,CACzI;SACA,MAAM,CAAC,cAAc,EAAE,yCAAyC,EAAE,OAAO,CAAC,GAAG,EAAE,CAAC;SAChF,MAAM,CAAC,QAAQ,EAAE,4BAA4B,CAAC;SAC9C,MAAM,CAAC,CAAC,IAAqC,EAAE,EAAE;QAChD,IAAI,CAAC;YACH,MAAM,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;YAC/B,MAAM,EAAE,OAAO,EAAE,QAAQ,EAAE,GAAG,UAAU,CAAC,IAAI,CAAC,CAAC;YAC/C,IAAI,IAAI,CAAC,IAAI;gBAAE,aAAa,CAAC,EAAE,OAAO,EAAE,QAAQ,EAAE,CAAC,CAAC;;gBAC/C,YAAY,CAAC,gBAAgB,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC,CAAC;YACvD,IAAI,QAAQ,CAAC,MAAM,GAAG,CAAC;gBAAE,OAAO,CAAC,QAAQ,GAAG,CAAC,CAAC;QAChD,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,WAAW,CAAC,KAAK,CAAC,CAAC;QACrB,CAAC;IACH,CAAC,CAAC,CAAC;AACP,CAAC"}

package/dist/prompts/auth-master-integration-prompt.md

@@ -44,7 +44,7 @@ Run `bridge auth login` and wait for it to print "Logged in as <email>". Once it
    ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝
 
   ──────────────────────────────────────────────
-   Congratulations — [project-name] now has superpowers.
+   Congratulations! [project-name] now has superpowers.
    ...
     ✅  You know who's calling
         [token-description]
@@ -53,6 +53,11 @@ Run `bridge auth login` and wait for it to print "Logged in as <email>". Once it
     Here is what I actually did:
     [what-i-actually-did]
 
+    Bridge's footprint in your code:
+    [footprint]
+
+    [see-every-change]
+
     And here is what I changed:
     [what-i-changed]
   ──────────────────────────────────────────────
@@ -63,6 +68,8 @@ As you work through the steps below, track the following so you have it ready:
 - **`[token-description]`** — the identifiers the developer uses to access the authenticated user in their framework (e.g. stores for Svelte, hooks for React, decorators for NestJS)
 - **`[what-i-actually-did]`** — high-level outcomes: what works now that didn't before
 - **`[what-i-changed]`** — every package installed, file created or modified, and URL configured, with exact values
+- **`[footprint]`** — as you make each edit, note its file and its changes (one import, one wrapper, one guard, one env var…), whether the file is new, and whether you modified any of the developer's existing code. Count from this record, never estimate it afterwards
+- **`[see-every-change]`** — the git state of each project, recorded in Step 1 before your first edit
 
 ## Step 1 — Discover projects
 
@@ -96,6 +103,8 @@ Scan the current directory and its immediate subdirectories for `package.json` f
    - Package manager
    - Existing auth (if any)
 
+6. **Note the git state, before you edit anything.** Run `git status` in each project and record one of: clean; uncommitted changes already there (note which files); not a git repo, or no commits yet. The success message uses it to tell the developer how to see your changes. Never run `git init`, `git add`, `git stash` or `git commit`, and do not ask the developer about git.
+
 ## Step 1b — Check if Bridge is already integrated
 
 If Step 1 detected a Bridge plugin (`@nebulr-group/bridge-<framework>`) in `dependencies`, the integration may already be partially or fully complete. Don't guess from the dependency alone — audit the wiring.
@@ -228,7 +237,7 @@ If anything fails, including the gate check, diagnose and fix before moving on.
 
 ## Step 6b — Tell the developer what they just got
 
-Fetch the success message template (MCP: `get_integration_guide` topic `integration-success`; CLI: `bridge guide integration-success`), then output it personalised for this project.
+Fetch the success message guide (MCP: `get_integration_guide` topic `integration-success`; CLI: `npx @nebulr-group/bridge-cli guide integration-success`) and output its MESSAGE 1 (sign-in), personalised for this project. Do this even when the gate check's line is the last thing you read: it reminds you of this step.
 
 **Substitutions (always apply):**
 
@@ -238,7 +247,7 @@ Fetch the success message template (MCP: `get_integration_guide` topic `integrat
 
 **Personalisation rules:**
 
-- Fill in every `[placeholder]` using the substitution guide at the bottom of the template. For `[what-i-actually-did]` and `[what-i-changed]`, draw from what you actually observed and changed during Steps 1–6 — the examples in the guide are illustrative only. Strip the `AGENT SUBSTITUTION GUIDE` section before outputting — it must never be shown to the developer.
+- Fill in every `[placeholder]` using the substitution guide at the bottom of the template. For `[what-i-actually-did]`, `[footprint]` and `[what-i-changed]`, draw from what you actually observed and changed during Steps 1–6; the examples in the guide are illustrative only. Count the footprint from your record of each edit and pick `[see-every-change]` from the git state you noted in Step 1, as the guide's counting rules say. Output MESSAGE 1 only: never the `WHICH MESSAGE TO SHOW` part, the MESSAGE headings or the `AGENT SUBSTITUTION GUIDE`.
 - If both a frontend and a backend were integrated, group the bottom two sections by project rather than merging them into a flat list.
 - **DO NOT write any text before the banner.** The very first character of your response must be the first character of the ASCII art. No "Perfect!", no "Here's your success message:", no transition sentence, no acknowledgement — nothing. Start with the `█` character. If you find yourself typing an intro, stop and delete it.
 - **If the build is broken** or auth doesn't actually work end-to-end, prepend a single "Heads up:" line before the banner. Never bury bad news under it.

package/dist/prompts/billing/master.md

@@ -51,6 +51,8 @@ Scan the current directory and its immediate subdirectories for `package.json` f
 
 5. **Existing billing system?** — look for `stripe`, `@stripe/*`, `paddle-*`, `lemon-squeezy`, `chargebee`. Flag any found.
 
+6. **Note the git state, before you edit anything.** Run `git status` in each project and record one of: clean; uncommitted changes already there (note which files); not a git repo, or no commits yet. The success message uses it to tell the developer how to see your changes. Never run `git init`, `git add`, `git stash` or `git commit`, and do not ask the developer about git. From your first edit on, keep a record of each change (its file, what it is, whether the file is new): the success message counts its footprint from that record.
+
 ## Step 1b — Audit existing billing wiring
 
 If Step 1 found billing already partially or fully set up, audit it before doing anything:
@@ -271,44 +273,10 @@ If anything fails, diagnose and fix before moving on.
 
 ## Step 6 — Tell the developer what they just got
 
-**Do not skip this step.** Output the banner below, personalised. The very first character of your response must be `█` — no intro sentence, no "Here's your summary:", nothing before it. If something is broken, prepend a single "Heads up:" line before the `█`.
-
-```
-   ██████╗ ██████╗ ██╗██████╗  ██████╗ ███████╗
-   ██╔══██╗██╔══██╗██║██╔══██╗██╔════╝ ██╔════╝
-   ██████╔╝██████╔╝██║██║  ██║██║  ███╗█████╗
-   ██╔══██╗██╔══██╗██║██║  ██║██║   ██║██╔══╝
-   ██████╔╝██║  ██║██║██████╔╝╚██████╔╝███████╗
-   ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝
-
-  ──────────────────────────────────────────────
-   Billing is live in [project-name].
-
-    ✅  Plans — [plan-names]
-    ✅  Subscription page — [subscription-route]
-    ✅  Paywall — [paywall-summary]
-    ✅  Lifecycle notices — auto-render on trial / payment failure / cancel
-    ✅  Quotas and entitlements — [quota-summary]
-  ──────────────────────────────────────────────
-    Here is what I actually did:
-    [what-i-actually-did]
-
-    And here is what I changed:
-    [what-i-changed]
-  ──────────────────────────────────────────────
-    Plan selection is required by default. To let users into the app without
-    picking a plan first, disable the paywall:
-      bridge app update --payments-auto-redirect false
-  ──────────────────────────────────────────────
-```
+**Do not skip this step.** Fetch the integration success guide (MCP: `get_integration_guide` topic `integration-success`; CLI: `npx @nebulr-group/bridge-cli guide integration-success`) and output its MESSAGE 2 (plans, billing or plan limits), personalised. The very first character of your response must be `█`: no intro sentence, no "Here's your summary:", nothing before it. If something is broken, prepend a single "Heads up:" line before the `█`.
 
-Fill every `[placeholder]` with real values from the integration:
-- `[project-name]` — folder name and/or `package.json` name
-- `[plan-names]` — the plan keys (e.g. `free`, `premium`)
-- `[subscription-route]` — where the subscription page is served (SvelteKit default `/subscription`)
-- `[paywall-summary]` — e.g. "new users sent to `/subscription/plan` to pick a plan" (or "off — `paymentsAutoRedirect false`")
-- `[quota-summary]` — metric keys, limits and kind, and the backend handlers that enforce them, or "none"
-- `[what-i-actually-did]` / `[what-i-changed]` — every file created or modified, every command run
+- Fill every `[placeholder]` by the guide's substitution rules: the plan keys, the subscription route, the paywall, the plan limits and where each is enforced. Count `[footprint]` from your record of each edit, never estimate; pick `[see-every-change]` from the git state you noted in Step 1; give each line of `[what-i-changed]` its size in changes. Plans, prices and Stripe settings made through the CLI or MCP are app settings, not code
+- Output MESSAGE 2 only: never the `WHICH MESSAGE TO SHOW` part, the MESSAGE headings or the substitution guide
 
 ## Step 7 — Offer follow-on tracks
 

package/dist/prompts/flags/master.md

@@ -33,37 +33,15 @@ If the user is using flags **without Bridge Auth** (bring-your-own identity), th
 
 ---
 
-**At the end of this integration you will output a success message:**
-
-```
-   ██████╗ ██████╗ ██╗██████╗  ██████╗ ███████╗
-   ██╔══██╗██╔══██╗██║██╔══██╗██╔════╝ ██╔════╝
-   ██████╔╝██████╔╝██║██║  ██║██║  ███╗█████╗
-   ██╔══██╗██╔══██╗██║██║  ██║██║   ██║██╔══╝
-   ██████╔╝██║  ██║██║██████╔╝╚██████╔╝███████╗
-   ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝
-
-  ──────────────────────────────────────────────
-   Feature flags are live in [project-name].
-
-    ✅  Flags read from the bulk-evaluate endpoint at boot
-    ✅  Eval context wired: [identity-source]
-    ✅  Telemetry batching enabled
-    ✅  Realtime updates enabled (optional)
-  ──────────────────────────────────────────────
-    Here is what I actually did:
-    [what-i-actually-did]
-
-    And here is what I changed:
-    [what-i-changed]
-  ──────────────────────────────────────────────
-```
+**At the end of this integration you will output a success message:** MESSAGE 3 (feature flags) in the integration success guide (MCP: `get_integration_guide` topic `integration-success`; CLI: `npx @nebulr-group/bridge-cli guide integration-success`). It opens with the Bridge banner, says what now works, then what you did, Bridge's footprint in the code and every change.
 
 Track as you work:
 - **`[project-name]`** — folder name and/or `package.json` name for each project
 - **`[identity-source]`** — how `identity` flows in (Bridge Auth `user.id`, your own session, anonymous bucket ID, etc.)
 - **`[what-i-actually-did]`** — high-level outcomes
 - **`[what-i-changed]`** — every package installed, file modified, env var set
+- **`[footprint]`** — as you make each edit, note its file and its changes (one import, one hook call, one decorator, one env var…), whether the file is new, and whether you modified any of the developer's existing code
+- **`[see-every-change]`** — the git state of each project, recorded in Step 1 before your first edit
 
 ## Mental model (1-minute version)
 
@@ -105,6 +83,8 @@ Scan the current directory and its immediate subdirectories for `package.json` f
 
 5. **Record** for each project: path, type (frontend/backend), framework, package manager, existing flag system (if any).
 
+6. **Note the git state, before you edit anything.** Run `git status` in each project and record one of: clean; uncommitted changes already there (note which files); not a git repo, or no commits yet. The success message uses it to tell the developer how to see your changes. Never run `git init`, `git add`, `git stash` or `git commit`, and do not ask the developer about git.
+
 ## Step 2 — Present findings and confirm
 
 ```
@@ -203,12 +183,12 @@ If anything fails, diagnose and fix before moving on.
 
 ## Step 6 — Tell the developer what they just got
 
-Output the success message at the top of this prompt, personalised for what you actually did. Same rules as the auth master:
+**Do not skip this step.** Fetch the integration success guide (MCP: `get_integration_guide` topic `integration-success`; CLI: `npx @nebulr-group/bridge-cli guide integration-success`) and output its MESSAGE 3 (feature flags), personalised for what you actually did:
 
-- Fill every `[placeholder]` with real values
-- Strip any agent-only notes
+- Fill every `[placeholder]` by the guide's substitution rules. Count `[footprint]` from your record of each edit, never estimate; pick `[see-every-change]` from the git state you noted in Step 1; give each line of `[what-i-changed]` its size in changes
+- Output MESSAGE 3 only: never the `WHICH MESSAGE TO SHOW` part, the MESSAGE headings or the substitution guide
 - Group by project if both frontend and backend were integrated
-- **Do not** write any text before the banner — start with the `█` character
+- **Do not** write any text before the banner: start with the `█` character
 - If a build is broken or flag reads return defaults forever, prepend a single "Heads up:" line before the banner
 
 After delivering the message, the flags integration is complete.

package/dist/prompts/integration-success.md

@@ -1,3 +1,21 @@
+WHICH MESSAGE TO SHOW (for you: never output this part)
+
+Show one message, picked by what this request added, then stop:
+  - Sign-in (Bridge auth)                            → MESSAGE 1
+  - Plans, billing or plan limits                    → MESSAGE 2
+  - Feature flags                                    → MESSAGE 3
+Several in one request: show the first that applies, in that order, and
+list the rest under what-i-actually-did.
+
+The very first character of your reply is the first `█` of the banner: no
+sentence before it. If the build is broken or the feature does not work end
+to end, put a single "Heads up:" line before the banner; never bury bad news
+under it. Fill every [placeholder] by the AGENT SUBSTITUTION GUIDE at the
+bottom. Output the chosen message only: not this part, not the MESSAGE
+headings, not the guide.
+
+===== MESSAGE 1: sign-in =====
+
    ██████╗ ██████╗ ██╗██████╗  ██████╗ ███████╗
    ██╔══██╗██╔══██╗██║██╔══██╗██╔════╝ ██╔════╝
    ██████╔╝██████╔╝██║██║  ██║██║  ███╗█████╗
@@ -6,26 +24,26 @@
    ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝
 
   ──────────────────────────────────────────────
-   Congratulations — [project-name] now has superpowers.
+   Congratulations! [project-name] now has superpowers.
 
     ✅  Authentication
-        UI for users to signup and login. Enable more
-        alternatives from the control center.
+        Sign-in and signup pages for your users. Turn on
+        more ways to sign in from the Control Center.
 
     ✅  Locked by default
-        Every route protected. Unauth'd users
-        bounce to login automatically.
+        Every route protected. Signed-out users
+        go to the sign-in page automatically.
 
     ✅  Multi-tenant ready
         Teams · Orgs · Workspaces · RBAC
-        Tenant context flows through every request.
+        Workspace context flows through every request.
 
     ✅  You know who's calling
         [token-description]
-        One token. Every auth alternative covered.
+        One token. Every way to sign in covered.
 
   ──────────────────────────────────────────────
-    The control center gives you even more powers.
+    The Control Center gives you even more powers.
 
       ›  Billing            Stripe plans & subscriptions    →  bridge guide [framework] billing
       ›  Feature flags      Per-user, per-plan toggles      →  bridge guide flags
@@ -40,31 +58,104 @@
 
     [what-i-actually-did]
 
+    Bridge's footprint in your code:
+
+    [footprint]
+
+    [see-every-change]
+
     And here is what I changed:
 
     [what-i-changed]
   ──────────────────────────────────────────────
 
+===== MESSAGE 2: plans, billing or plan limits =====
+
+   ██████╗ ██████╗ ██╗██████╗  ██████╗ ███████╗
+   ██╔══██╗██╔══██╗██║██╔══██╗██╔════╝ ██╔════╝
+   ██████╔╝██████╔╝██║██║  ██║██║  ███╗█████╗
+   ██╔══██╗██╔══██╗██║██║  ██║██║   ██║██╔══╝
+   ██████╔╝██║  ██║██║██████╔╝╚██████╔╝███████╗
+   ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝
+
+  ──────────────────────────────────────────────
+   Billing is live in [project-name].
+
+    ✅  Plans: [plan-names]
+    ✅  Subscription page: [subscription-route]
+    ✅  Paywall: [paywall-summary]
+    ✅  Lifecycle notices: auto-render on trial / payment failure / cancel
+    ✅  Quotas and entitlements: [quota-summary]
+  ──────────────────────────────────────────────
+    Here is what I actually did:
+    [what-i-actually-did]
+
+    Bridge's footprint in your code:
+    [footprint]
+
+    [see-every-change]
+
+    And here is what I changed:
+    [what-i-changed]
+  ──────────────────────────────────────────────
+    Plan selection is required by default. To let users into the app without
+    picking a plan first, disable the paywall:
+      bridge app update --payments-auto-redirect false
+  ──────────────────────────────────────────────
+
+===== MESSAGE 3: feature flags =====
+
+   ██████╗ ██████╗ ██╗██████╗  ██████╗ ███████╗
+   ██╔══██╗██╔══██╗██║██╔══██╗██╔════╝ ██╔════╝
+   ██████╔╝██████╔╝██║██║  ██║██║  ███╗█████╗
+   ██╔══██╗██╔══██╗██║██║  ██║██║   ██║██╔══╝
+   ██████╔╝██║  ██║██║██████╔╝╚██████╔╝███████╗
+   ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝
+
+  ──────────────────────────────────────────────
+   Feature flags are live in [project-name].
+
+    ✅  Flags read from the bulk-evaluate endpoint at boot
+    ✅  Eval context wired: [identity-source]
+    ✅  Telemetry batching enabled
+    ✅  Realtime updates enabled (optional)
+  ──────────────────────────────────────────────
+    Here is what I actually did:
+    [what-i-actually-did]
+
+    Bridge's footprint in your code:
+    [footprint]
+
+    [see-every-change]
+
+    And here is what I changed:
+    [what-i-changed]
+  ──────────────────────────────────────────────
+
 ---
 AGENT SUBSTITUTION GUIDE (strip this section before outputting)
 
+No em dashes (—) anywhere in the text you output. Use a colon, a comma or a
+period instead. In prose say "sign in" and "signup" (not "login"),
+"Control Center", "workspace" (not "tenant") and "app" (not "application").
+
 PLACEHOLDER: project-name
   Pick the most human-readable name available. Prefer in this order:
-    1. The folder name (e.g. "my-saas-app") — often more meaningful than the package name
+    1. The folder name (e.g. "my-saas-app"), often more meaningful than the package name
     2. The `name` field in package.json if it's descriptive
   If both frontend and backend were integrated, combine them:
     "my-saas-app + my-saas-api" or just the shared root folder name if obvious.
 
 PLACEHOLDER: framework
-  In the "control center" next-steps lines, replace `[framework]` with the
+  In the Control Center next-steps lines, replace `[framework]` with the
   framework slug used by `bridge guide` (`svelte`, `react`, `nextjs`, `angular`,
   `nestjs`, `express`). Use the frontend framework when both frontend and
-  backend were integrated. Leave `bridge guide flags` unchanged — that command
+  backend were integrated. Leave `bridge guide flags` unchanged: that command
   auto-detects the framework from `package.json`.
 
 PLACEHOLDER: token-description
-  One short line — the key identifiers the developer uses to access the
-  authenticated user in their specific framework. No explanation.
+  One short line: the key identifiers the developer uses to access the
+  signed-in user in their specific framework. No explanation.
   Examples:
     Svelte:  profileStore · isAuthenticated · tokenStore
     React:   useProfile() · useIsAuthenticated() · useToken()
@@ -75,32 +166,138 @@ PLACEHOLDER: token-description
 
 PLACEHOLDER: what-i-actually-did
   3–5 bullet lines drawn from what actually happened in this session.
-  High-level outcomes in plain English — not file names.
+  High-level outcomes in plain English, not file names.
   If both frontend and backend were integrated, group under headings:
 
     Frontend (my-saas-app):
-    ✅  Auth UI live — signup, login, password reset
+    ✅  Sign-in pages live: signup, sign in, password reset
     ✅  All routes protected by default
 
     Backend (my-saas-api):
     ✅  All endpoints require a verified JWT
-    ✅  Authenticated user available on every request
+    ✅  Signed-in user available on every request
+
+PLACEHOLDER: plan-names (MESSAGE 2)
+  The plan keys, e.g. `free`, `pro`.
+
+PLACEHOLDER: subscription-route (MESSAGE 2)
+  Where the subscription page is served (default `/subscription`).
+
+PLACEHOLDER: paywall-summary (MESSAGE 2)
+  e.g. "new users sent to `/subscription/plan` to pick a plan", or
+  "off: `paymentsAutoRedirect false`". When the paywall is off, drop the
+  closing "Plan selection is required by default" block.
+
+PLACEHOLDER: quota-summary (MESSAGE 2)
+  Metric keys, limits and kind (hard or billed per extra use), and where each
+  is enforced (the backend handler, or the frontend report), or "none".
+  Plans, prices and Stripe settings made through the CLI or MCP are app
+  settings, not code.
+
+PLACEHOLDER: identity-source (MESSAGE 3)
+  How `identity` reaches the flags: Bridge Auth `user.id`, the app's own
+  session, an anonymous bucket ID.
+
+HOW TO COUNT THE FOOTPRINT (used by footprint, see-every-change, what-i-changed)
+  - Count only the changes YOU made in this session, from your own record of
+    each edit. Never estimate, and never count from `git diff` alone: the tree
+    may hold the developer's own work, and `git diff` does not show new
+    (untracked) files at all.
+  - The unit is a CHANGE, not a line. One change is one logical unit: an
+    import, a wrapper, a guard, a hook call, a handler or a button with its
+    handler, a component placed, an env var, a dependency, a config entry, a
+    route, a decorator or a module registration. An 8-line handler is one
+    change; a 3-name import statement is one import.
+  - "Imports or config" = imports, env vars, dependencies and config entries.
+  - Source files = the code files you created or modified. Env files,
+    package.json and lockfiles are config: they appear as env vars and
+    dependencies, not as source files. Stylesheets are styling, never code.
+  - New files are part of the footprint: count each one as touched and as new.
+  - Bridge app settings you changed through the CLI or MCP (callback URL,
+    allowed origins, redirect URIs, plans, flags) are listed in what-i-changed
+    but are NOT code changes and are not counted.
+  - Nothing changed this session (Bridge was already fully integrated): the
+    footprint is the single line "Nothing changed this session: Bridge was
+    already wired in." Drop see-every-change, and what-i-changed lists only
+    the Bridge app settings you changed, or "Nothing to change."
+
+PLACEHOLDER: footprint
+  Two to four short lines, in this order:
+
+  1. Size, one line:
+       3 source files touched, 1 new · 11 changes, 7 of them imports or config
+     Leave out ", 1 new" when no file is new. Use "1 source file" in the
+     singular. Frontend and backend both integrated: one line per side,
+     headed like the other sections:
+       Frontend (my-saas-app): 3 source files touched, 1 new · 8 changes, 5 of them imports or config
+       Backend (my-saas-api): 1 source file touched · 4 changes, 3 of them imports or config
+
+  2. Existing logic, one line. Only when it is TRUE that you added code and
+     changed none of the developer's existing statements, write:
+       None of your existing logic changed: only additions, plus <body> wrapped.
+     naming the one wrapping you did (`<body>`, the app, the root layout), or
+     ending at "only additions." when you wrapped nothing. If you modified or
+     removed any of their code, say what instead, plainly:
+       2 of your lines changed: the old login check in app/page.tsx, now a Bridge guard.
+
+  3. Styling, one or two lines, kept apart from code. Count CSS in lines.
+     Only `--bridge-*` tokens mapped to the app's colors:
+       Styling: 16 lines map Bridge to your colors.
+     Tokens plus more styling to match the app:
+       Styling is optional: 16 lines map Bridge to your colors, and 46 more
+       copy your app's borders and shadows.
+     No styling: leave the styling line out.
+
+PLACEHOLDER: see-every-change
+  One line (two at most), chosen from the `git status` you ran in each project
+  BEFORE your first edit. Never run `git init`, `git add` or `git commit` for
+  the developer, and do not ask them about git.
+  - Git repo, clean before you started, no new files:
+      See every change: git diff
+  - Git repo, clean before you started, you created files (`git diff` does
+    not show new files; `git status` lists them):
+      See every change: git status, then git diff
+  - Git repo, the developer already had uncommitted changes: point only at
+    the files you touched, and name new files on their own line:
+      See every change: git diff -- app/layout.tsx app/page.tsx
+      New files: app/auth/[...bridge]/page.tsx
+    If one of those files already had the developer's own uncommitted edits,
+    add "(also shows your earlier edits)" after the command.
+  - Not a git repo, or a repo with no commits yet:
+      Tip: commit before your next integration and git diff shows the whole footprint.
+  Frontend and backend in separate repos in different states: one line per
+  side, starting "Frontend:" / "Backend:". Files ignored by git (often
+  `.env.local`) never show in git; they are listed in what-i-changed anyway.
 
 PLACEHOLDER: what-i-changed
-  The nitty-gritty. One line per actual change, drawn from what you did in this
-  session. Real package names, real file paths, real URLs, real values. Omit
-  anything that was skipped.
+  The nitty-gritty. One line per file (or per small group of config files),
+  drawn from what you did in this session. Real file paths, real package
+  names, real URLs, real values. Omit anything that was skipped.
+  End each line with its size in changes, in parentheses, lined up in one
+  column where the width allows:
+    - the changes in that file, using the units above: (1 import, 1 wrapper)
+    - a file you created starts with "new: ": (new: 1 import, 1 component)
+    - a stylesheet: (styling only)
+    - a Bridge app setting: (app setting, not code)
+  The sizes must add up to the totals in the footprint.
+  Example (Next.js):
+
+    ✅  app/layout.tsx: <BridgeProvider> around the app       (1 import, 1 wrapper)
+    ✅  app/auth/[...bridge]/page.tsx: every sign-in page      (new: 1 import, 1 component)
+    ✅  app/page.tsx: studio needs sign-in, Sign out button    (2 imports, 1 guard, 1 button)
+    ✅  .env.local, package.json                               (2 env vars, 1 dependency)
+    ✅  app/globals.css                                        (styling only)
+    ✅  Bridge app: http://localhost:3000 as callback + origin (app setting, not code)
+
   If both frontend and backend were integrated, group under headings:
 
     Frontend (my-saas-app):
-    ✅  @nebulr-group/bridge-svelte installed
-    ✅  src/routes/+layout.ts — export const load = bridgeBootstrap({ rules })
-    ✅  src/routes/+layout.svelte — app wrapped in <BridgeBootstrap>
-    ✅  src/routes/auth/[...bridge]/+page.svelte — <BridgeAuthRoutes /> serves every sign-in page
-    ✅  .env configured with VITE_BRIDGE_APP_ID=abc123
-    ✅  Bridge app configured for http://localhost:5175
+    ✅  src/routes/+layout.ts: bridgeBootstrap({ rules }) as the load      (1 import, 1 hook call)
+    ✅  src/routes/+layout.svelte: app wrapped in <BridgeBootstrap>         (1 import, 1 wrapper)
+    ✅  src/routes/auth/[...bridge]/+page.svelte: every sign-in page        (new: 1 import, 1 component)
+    ✅  .env, package.json: VITE_BRIDGE_APP_ID=abc123, bridge-svelte        (1 env var, 1 dependency)
+    ✅  Bridge app: http://localhost:5175 as callback + origin              (app setting, not code)
 
     Backend (my-saas-api):
-    ✅  @nebulr-group/bridge-nestjs installed
-    ✅  AppModule — BridgeModule.forRoot({ guard: { global: true } }), every route needs a signed-in user
-    ✅  .env configured with BRIDGE_APP_ID=abc123
+    ✅  src/app.module.ts: BridgeModule.forRoot({ guard: { global: true } }) (1 import, 1 module registration)
+    ✅  .env, package.json: BRIDGE_APP_ID=abc123, bridge-nestjs             (1 env var, 1 dependency)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nebulr-group/bridge-cli",
-  "version": "0.6.6",
+  "version": "0.6.7",
   "description": "The Bridge CLI: set up and manage sign-in, roles, plans, feature flags and API tokens from your terminal or AI coding agent.",
   "author": "Nebulr Group",
   "license": "MIT",