@nebulr-group/bridge-cli 0.6.6 → 1.0.0-alpha.0

package/dist/commands/guide.command.js

@@ -1,655 +0,0 @@
-import { readFile } from 'node:fs/promises';
-import { readFileSync } from 'node:fs';
-import { join } from 'node:path';
-import { commandsDir } from './runtime-dir.js';
-import { outputSuccess, outputPrompt, outputError } from '../output.js';
-import { AUTH_MASTER_PROMPT_FILENAME, AUTH_MASTER_PROMPT_URL, pluginGuideUrl } from '../prompt-urls.js';
-import { DECISION_DOMAINS, fetchDecisionGuide, registerJourneyCommands, unknownGuideMessage, } from './journeys.js';
-/**
- * Locate the directory containing this module on disk so the bundled prompts
- * (shipped at `dist/prompts/`) can be read relative to it. The `import.meta`
- * resolution is isolated in `runtime-dir.ts` (and stubbed for jest) — see that
- * file for the dual-runtime rationale.
- *
- * The previous in-line `new Function('return import.meta.url')()` trick could
- * never work: a Function-constructor body runs in global *script* scope where
- * `import.meta` is a SyntaxError, so it threw even under ESM and silently fell
- * through to a `process.cwd()`-based branch — which only resolved correctly by
- * accident when the CWD happened to be the package root.
- */
-function thisDir() {
-    return commandsDir;
-}
-const GUIDE_REPOS = {
-    react: 'bridge-react/main',
-    svelte: 'bridge-svelte/main',
-    angular: 'bridge-angular/main',
-    nextjs: 'bridge-nextjs/main',
-    express: 'bridge-express/main',
-    nestjs: 'bridge-nestjs/main',
-};
-/**
- * Which per-framework guides exist, from `prompts/guide-coverage.json`.
- *
- * That file is the one copy (TBP-706): this command lists it, and the Bridge
- * MCP server reads the same file from GitHub for its "no such guide" answers.
- * Before it, the CLI, the MCP server and the auth master prompt gave three
- * different answers, and the CLI's was the most out of date.
- */
-export function loadGuideCoverage() {
-    const here = thisDir();
-    const candidates = [
-        join(here, '..', 'prompts', 'guide-coverage.json'),
-        join(here, '..', '..', 'prompts', 'guide-coverage.json'),
-    ];
-    for (const path of candidates) {
-        try {
-            const { aliases, frameworks, topics } = JSON.parse(readFileSync(path, 'utf-8'));
-            return { aliases, frameworks, topics: topics ?? {} };
-        }
-        catch {
-            /* try next */
-        }
-    }
-    throw new Error(`guide-coverage.json not found. Tried: ${candidates.join(', ')}`);
-}
-const FLAGS_FRAMEWORKS = ['svelte', 'react', 'nextjs', 'angular', 'nestjs', 'express'];
-const BILLING_FRAMEWORKS = ['svelte', 'react', 'nextjs', 'angular', 'nestjs', 'express'];
-/**
- * Per-framework prompts are the responsibility of each plugin repo
- * (`bridge-<framework>/mcp/feature-flags-prompt.md` and `mcp/billing-prompt.md`).
- * Bridge-cli only bundles the generic master orchestrators
- * (`prompts/flags/master.md`, `prompts/billing/master.md`) — never per-framework
- * copies, which would diverge from the plugin's source of truth.
- *
- * Both alias sets are now exhaustive: every framework routes through fetchGuide
- * to its plugin repo's mcp/ folder. If the plugin repo doesn't have the file
- * yet, the user gets a clear "HTTP 404 — file may not exist yet in the plugin
- * repo" error pointing them at the right destination.
- */
-const FLAGS_ALIAS_FRAMEWORKS = new Set(FLAGS_FRAMEWORKS);
-const BILLING_ALIAS_FRAMEWORKS = new Set(BILLING_FRAMEWORKS);
-function guideFilename(feature) {
-    if (!feature)
-        return 'integration-prompt.md';
-    return `${feature}-prompt.md`;
-}
-const guideCache = new Map();
-const CACHE_TTL_MS = 5 * 60 * 1000; // 5 minutes
-export function registerGuideCommands(program) {
-    const guide = program.command('guide')
-        .description('Integration guides — run with no arguments for the master integration prompt')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            // TBP-712: `bridge guide <anything unknown>` used to fall through to
-            // here and print the master as if the lookup had worked. Name what
-            // exists instead.
-            const [unknown] = command.args;
-            if (unknown) {
-                throw Object.assign(new Error(unknownGuideMessage(unknown, Object.keys(GUIDE_REPOS))), {
-                    code: 'GUIDE_NOT_FOUND',
-                });
-            }
-            // No login here: reading a guide needs no session, and the commands
-            // the guide goes on to run ask for one themselves (TBP-706).
-            const guide = await fetchMasterPrompt();
-            if (opts.json)
-                outputSuccess({ guide });
-            else
-                outputPrompt(guide);
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    const technologies = [...Object.keys(GUIDE_REPOS), 'custom'];
-    guide.command('list')
-        .description('List available integration guides and feature guides')
-        .action(() => {
-        const { aliases, frameworks, topics } = loadGuideCoverage();
-        outputSuccess({ technologies, features: frameworks, aliases, topics });
-    });
-    // TBP-206 — `bridge guide flags [--framework <name>]`
-    guide.command('flags')
-        .description('Feature Flags 2.0 integration prompt (use --framework for per-framework guide)')
-        .option('--framework <name>', `Framework: ${FLAGS_FRAMEWORKS.join(' | ')} (auto-detected from package.json when omitted)`)
-        .option('--cwd <path>', 'Project dir used for framework detection', process.cwd())
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            // Always return the master when no --framework flag is given.
-            // The master orchestrates discovery then calls bridge guide flags --framework <name> in Step 4.
-            const content = opts.framework
-                ? await fetchGuide(await resolveFlagsFramework(opts.framework, opts.cwd ?? process.cwd()) ?? opts.framework, 'feature-flags')
-                : await fetchFlagsMasterPrompt();
-            if (opts.json) {
-                outputSuccess({
-                    feature: 'flags',
-                    framework: opts.framework ?? 'generic',
-                    guide: content,
-                });
-            }
-            else {
-                outputPrompt(content);
-            }
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    // Billing 2.0 — `bridge guide billing [--framework <name>]`. Mirrors the
-    // flags command shape. Auto-detects from package.json when --framework is
-    // omitted; falls back to `prompts/billing/master.md` when detection fails.
-    guide.command('billing')
-        .description('Billing 2.0 integration prompt (use --framework for per-framework guide)')
-        .option('--framework <name>', `Framework: ${BILLING_FRAMEWORKS.join(' | ')} (auto-detected from package.json when omitted)`)
-        .option('--cwd <path>', 'Project dir used for framework detection', process.cwd())
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            // Always return the master when no --framework flag is given.
-            // The master orchestrates discovery, pricing-model elicitation, and
-            // calls `bridge guide billing --framework <name>` itself in Step 4.
-            const content = opts.framework
-                ? await fetchGuide(await resolveBillingFramework(opts.framework, opts.cwd ?? process.cwd()) ?? opts.framework, 'billing')
-                : await fetchBillingMasterPrompt();
-            if (opts.json) {
-                outputSuccess({
-                    feature: 'billing',
-                    framework: opts.framework ?? 'generic',
-                    guide: content,
-                });
-            }
-            else {
-                outputPrompt(content);
-            }
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    for (const tech of Object.keys(GUIDE_REPOS)) {
-        guide.command(tech)
-            .argument('[feature]', 'Feature guide — `bridge guide list` shows which exist per framework')
-            .description(`Integration guide for ${tech}`)
-            .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-            .action(async (feature, _opts, command) => {
-            try {
-                const opts = command.optsWithGlobals();
-                // `flags` is a synonym for `feature-flags`. Both routes — `bridge
-                // guide flags --framework <name>` and `bridge guide <name> flags` —
-                // resolve to the same plugin-repo source of truth at
-                // `bridge-<name>/mcp/feature-flags-prompt.md`. `billing` follows the
-                // same pattern. There is no per-framework bundled fallback by design.
-                let content;
-                let resolvedFeature = feature ?? 'default';
-                if (feature === 'flags' && FLAGS_FRAMEWORKS.includes(tech)) {
-                    content = await fetchGuide(tech, 'feature-flags');
-                    resolvedFeature = 'flags';
-                }
-                else if (feature === 'billing' && BILLING_FRAMEWORKS.includes(tech)) {
-                    content = await fetchGuide(tech, 'billing');
-                    resolvedFeature = 'billing';
-                }
-                else {
-                    content = await fetchGuide(tech, feature);
-                    if (!feature) {
-                        const preface = authModesPreface(tech, loadGuideCoverage().frameworks);
-                        if (preface)
-                            content = `${preface}\n\n${content}`;
-                    }
-                }
-                if (opts.json) {
-                    outputSuccess({ technology: tech, feature: resolvedFeature, guide: content });
-                }
-                else {
-                    outputPrompt(content);
-                }
-            }
-            catch (err) {
-                outputError(err);
-            }
-        });
-    }
-    // TBP-712 — the seven journeys by name, composed like the MCP prompts.
-    registerJourneyCommands(guide, {
-        decision: fetchDecisionGuide,
-        master: (m) => m === 'auth' ? fetchMasterPrompt() : m === 'flags' ? fetchFlagsMasterPrompt() : fetchBillingMasterPrompt(),
-        frameworkGuide: (tech, feature) => fetchGuide(tech, feature),
-        coverage: () => loadGuideCoverage().frameworks,
-    }, resolveFlagsFramework);
-    guide.command('custom')
-        .description('Universal integration guide for any technology using REST API + JWKS')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action((_opts, command) => {
-        const opts = command.optsWithGlobals();
-        if (opts.json)
-            outputSuccess({ technology: 'custom', guide: CUSTOM_GUIDE });
-        else
-            outputPrompt(CUSTOM_GUIDE);
-    });
-    // TBP-705 — the mechanisms every guide builds on: the server decides, a POST
-    // increments the limit, counter vs gauge, the three UI levels, the four
-    // customisation rungs, self-reported usage. The MCP server serves the same
-    // file (bridge-cli/main/bridge-cli/prompts/mechanisms.md) as
-    // `get_integration_guide topic=mechanisms`.
-    guide.command('mechanisms')
-        .description('How Bridge works: limits, counter vs gauge, UI levels, customisation rungs')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            const content = await fetchMechanismsGuide();
-            if (opts.json)
-                outputSuccess({ topic: 'mechanisms', guide: content });
-            else
-                outputPrompt(content);
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    // TBP-540 — the level-1 map: what Bridge does, one short paragraph per
-    // area, for an agent to relay as is. The MCP server serves the same file.
-    guide.command('orientation')
-        .description('What Bridge does: a short map to relay to a developer, with where to go next')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            const content = await fetchOrientationGuide();
-            if (opts.json)
-                outputSuccess({ topic: 'orientation', guide: content });
-            else
-                outputPrompt(content);
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    // TBP-705 — how roles, plans, limits and flags fit together: the one rule
-    // every decision guide and the orientation point to. The MCP server serves
-    // the same file (bridge-cli/main/bridge-cli/prompts/fit-together.md).
-    guide.command('fit-together')
-        .description('How roles, plans, limits and flags fit together: the rule every decision guide builds on')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            const content = await fetchFitTogetherGuide();
-            if (opts.json)
-                outputSuccess({ topic: 'fit-together', guide: content });
-            else
-                outputPrompt(content);
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    // TBP-540 — each decision guide on its own. Five of the seven also open a
-    // journey (`bridge guide add-login` …); `roles` and `look-and-feel` open
-    // none, so without this command the CLI could not reach them.
-    guide.command('decision')
-        .argument('<domain>', `One of: ${DECISION_DOMAINS.join(', ')}`)
-        .description('A decision guide: the questions to ask the developer and the defaults to apply')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (domain, _opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            if (!DECISION_DOMAINS.includes(domain)) {
-                throw Object.assign(new Error(`No decision guide named '${domain}'. Decision guides: ${DECISION_DOMAINS.join(', ')}.`), { code: 'GUIDE_NOT_FOUND' });
-            }
-            const content = await fetchDecisionGuide(domain);
-            if (!content) {
-                throw Object.assign(new Error(`The '${domain}' decision guide could not be read.`), { code: 'GUIDE_NOT_FOUND' });
-            }
-            if (opts.json)
-                outputSuccess({ domain, guide: content });
-            else
-                outputPrompt(content);
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-    guide.command('integration-success')
-        .description('Integration success message template — output at the end of a completed integration')
-        .option('--json', 'Emit a JSON envelope instead of the raw markdown prompt')
-        .action(async (_opts, command) => {
-        try {
-            const opts = command.optsWithGlobals();
-            const content = await fetchIntegrationSuccess();
-            if (opts.json)
-                outputSuccess({ guide: content });
-            else
-                outputPrompt(content);
-        }
-        catch (err) {
-            outputError(err);
-        }
-    });
-}
-/**
- * TBP-540 (folds TBP-599) — `bridge guide <framework>` prints the HOSTED
- * sign-in guide, and used to say nothing about the other mode. A developer who
- * wanted in-app forms never learned `bridge guide svelte sdk-auth` existed,
- * hand-wrote a login form against `/auth/login` (a 404) and shipped it. So a
- * framework that has an SDK-auth guide opens by naming both modes; one that
- * has none (the backends) is unchanged.
- *
- * TBP-807 — the per-framework guide now sets up in-app (SDK) sign-in itself,
- * so there is no mode to pick; the preface only points at the guide for the
- * sign-in pages and their design.
- */
-export function authModesPreface(tech, coverage) {
-    if (!coverage[tech]?.includes('sdk-auth'))
-        return null;
-    return [
-        `> **The sign-in pages, matching the app's design:** \`bridge guide ${tech} sdk-auth\`. The SDK handles password, magic link, passkeys, SSO, two-factor and workspace choice inside the app's own layout.`,
-        '>',
-        '> Never write a login form or call Bridge auth endpoints by hand: the SDK does it, and a guessed endpoint fails as a silent 404.',
-    ].join('\n');
-}
-/** The per-framework guides that exist for `tech`, or null when the list cannot be read. */
-function guidesFor(tech) {
-    try {
-        return loadGuideCoverage().frameworks[tech] ?? null;
-    }
-    catch {
-        return null;
-    }
-}
-export const MECHANISMS_PROMPT_FILENAME = 'mechanisms.md';
-export const ORIENTATION_PROMPT_FILENAME = 'orientation.md';
-export const FIT_TOGETHER_PROMPT_FILENAME = 'fit-together.md';
-/** The mechanisms page, bundled with the CLI (`BRIDGE_GUIDE_LOCAL_DIR` wins in development). */
-export async function fetchMechanismsGuide() {
-    return fetchBundledPage(MECHANISMS_PROMPT_FILENAME, 'mechanisms guide');
-}
-/** The orientation map, bundled with the CLI (`BRIDGE_GUIDE_LOCAL_DIR` wins in development). */
-export async function fetchOrientationGuide() {
-    return fetchBundledPage(ORIENTATION_PROMPT_FILENAME, 'orientation guide');
-}
-/** How roles, plans, limits and flags fit together, bundled with the CLI (`BRIDGE_GUIDE_LOCAL_DIR` wins in development). */
-export async function fetchFitTogetherGuide() {
-    return fetchBundledPage(FIT_TOGETHER_PROMPT_FILENAME, 'fit-together guide');
-}
-async function fetchBundledPage(filename, label) {
-    const localDir = process.env.BRIDGE_GUIDE_LOCAL_DIR;
-    if (localDir) {
-        try {
-            return await readFile(join(localDir, 'bridge-cli', 'bridge-cli', 'prompts', filename), 'utf-8');
-        }
-        catch {
-            /* fall through to bundled */
-        }
-    }
-    const here = thisDir();
-    const candidates = [
-        join(here, '..', 'prompts', filename),
-        join(here, '..', '..', 'prompts', filename),
-    ];
-    for (const path of candidates) {
-        try {
-            return await readFile(path, 'utf-8');
-        }
-        catch {
-            /* try next */
-        }
-    }
-    throw new Error(`${label} not found. Tried: ${candidates.join(', ')}`);
-}
-async function fetchIntegrationSuccess() {
-    const here = thisDir();
-    const candidates = [
-        join(here, '..', 'prompts', 'integration-success.md'),
-        join(here, '..', '..', 'prompts', 'integration-success.md'),
-    ];
-    for (const path of candidates) {
-        try {
-            return await readFile(path, 'utf-8');
-        }
-        catch {
-            /* try next */
-        }
-    }
-    throw new Error(`integration-success prompt not found. Tried: ${candidates.join(', ')}`);
-}
-/**
- * Detect framework from package.json so `bridge guide flags` can be called
- * bare. Same heuristic order as `bridge flag init`.
- */
-export async function resolveFlagsFramework(override, cwd) {
-    if (override) {
-        if (!FLAGS_FRAMEWORKS.includes(override)) {
-            throw new Error(`Unknown --framework: ${override}. Must be one of ${FLAGS_FRAMEWORKS.join(', ')}.`);
-        }
-        return override;
-    }
-    try {
-        const raw = await readFile(join(cwd, 'package.json'), 'utf-8');
-        const pkg = JSON.parse(raw);
-        const deps = { ...(pkg.dependencies ?? {}), ...(pkg.devDependencies ?? {}) };
-        if ('next' in deps)
-            return 'nextjs';
-        if ('@sveltejs/kit' in deps || 'svelte' in deps)
-            return 'svelte';
-        if ('@nestjs/core' in deps)
-            return 'nestjs';
-        if ('@angular/core' in deps)
-            return 'angular';
-        if ('react' in deps)
-            return 'react';
-        if ('express' in deps)
-            return 'express';
-    }
-    catch {
-        /* no package.json — fall through */
-    }
-    return undefined;
-}
-/**
- * Bridge-cli only bundles the generic master orchestrators. Per-framework
- * prompts always come from the plugin repos' mcp/ folder via `fetchGuide`.
- */
-export async function fetchFlagsMasterPrompt() {
-    return fetchBundledMaster('flags');
-}
-export async function fetchBillingMasterPrompt() {
-    return fetchBundledMaster('billing');
-}
-async function fetchBundledMaster(feature) {
-    const filename = 'master.md';
-    // Local override for development (same env var as the rest of the guides).
-    const localDir = process.env.BRIDGE_GUIDE_LOCAL_DIR;
-    if (localDir) {
-        const localPath = join(localDir, 'bridge-cli', 'bridge-cli', 'prompts', feature, filename);
-        try {
-            return await readFile(localPath, 'utf-8');
-        }
-        catch {
-            /* fall through to bundled */
-        }
-    }
-    // Two possible runtime locations:
-    //   - Built CLI: dist/commands/guide.command.js → ../prompts/<feature>/master.md
-    //   - Jest (ts-jest, run from src/): src/commands/guide.command.ts → ../../prompts/<feature>/master.md
-    const here = thisDir();
-    const candidates = [
-        join(here, '..', 'prompts', feature, filename),
-        join(here, '..', '..', 'prompts', feature, filename),
-    ];
-    for (const path of candidates) {
-        try {
-            return await readFile(path, 'utf-8');
-        }
-        catch {
-            /* try next */
-        }
-    }
-    const label = feature === 'flags' ? 'Flags' : 'Billing';
-    throw new Error(`${label} master prompt not found. Tried: ${candidates.join(', ')}`);
-}
-/**
- * Detect framework for Billing 2.0. Mirrors resolveFlagsFramework — same
- * package.json heuristic order, validated against BILLING_FRAMEWORKS.
- */
-export async function resolveBillingFramework(override, cwd) {
-    if (override) {
-        if (!BILLING_FRAMEWORKS.includes(override)) {
-            throw new Error(`Unknown --framework: ${override}. Must be one of ${BILLING_FRAMEWORKS.join(', ')}.`);
-        }
-        return override;
-    }
-    try {
-        const raw = await readFile(join(cwd, 'package.json'), 'utf-8');
-        const pkg = JSON.parse(raw);
-        const deps = { ...(pkg.dependencies ?? {}), ...(pkg.devDependencies ?? {}) };
-        if ('next' in deps)
-            return 'nextjs';
-        if ('@sveltejs/kit' in deps || 'svelte' in deps)
-            return 'svelte';
-        if ('@nestjs/core' in deps)
-            return 'nestjs';
-        if ('@angular/core' in deps)
-            return 'angular';
-        if ('react' in deps)
-            return 'react';
-        if ('express' in deps)
-            return 'express';
-    }
-    catch {
-        /* no package.json — fall through */
-    }
-    return undefined;
-}
-async function fetchGuide(tech, feature) {
-    const cacheKey = feature ? `${tech}:${feature}` : tech;
-    const cached = guideCache.get(cacheKey);
-    if (cached && Date.now() - cached.fetchedAt < CACHE_TTL_MS) {
-        return cached.content;
-    }
-    const repoPrefix = GUIDE_REPOS[tech];
-    if (!repoPrefix)
-        throw new Error(`Unknown technology: ${tech}`);
-    const filename = guideFilename(feature);
-    // Local override for development: reads from filesystem before hitting GitHub
-    const localDir = process.env.BRIDGE_GUIDE_LOCAL_DIR;
-    if (localDir) {
-        const localPath = join(localDir, `bridge-${tech}`, 'mcp', filename);
-        try {
-            const content = await readFile(localPath, 'utf-8');
-            guideCache.set(cacheKey, { content, fetchedAt: Date.now() });
-            return content;
-        }
-        catch {
-            // Local file not found — fall through to remote fetch
-        }
-    }
-    const url = pluginGuideUrl(repoPrefix, filename);
-    const response = await fetch(url);
-    if (!response.ok) {
-        const label = feature ? `${tech}/${feature}` : tech;
-        // TBP-540 — a failed lookup names what does exist, so the next try is right.
-        const available = response.status === 404 ? guidesFor(tech) : null;
-        throw Object.assign(new Error(`Guide not available for ${label} (HTTP ${response.status}). ` +
-            (available
-                ? `Guides for ${tech}: ${available.join(', ')} (\`bridge guide ${tech} <guide>\`; \`bridge guide list\` shows every framework).`
-                : 'The prompt file may not exist yet in the plugin repo.')), response.status === 404 ? { code: 'GUIDE_NOT_FOUND' } : {});
-    }
-    const content = await response.text();
-    guideCache.set(cacheKey, { content, fetchedAt: Date.now() });
-    return content;
-}
-async function fetchMasterPrompt() {
-    const filename = AUTH_MASTER_PROMPT_FILENAME;
-    // Local override for development
-    const localDir = process.env.BRIDGE_GUIDE_LOCAL_DIR;
-    if (localDir) {
-        const localPath = join(localDir, 'bridge-cli', 'bridge-cli', 'prompts', filename);
-        try {
-            return await readFile(localPath, 'utf-8');
-        }
-        catch { /* fall through */ }
-    }
-    // Resolved-on-disk fallback (when the CLI runs from its own checkout).
-    const here = thisDir();
-    const candidates = [
-        join(here, '..', 'prompts', filename),
-        join(here, '..', '..', 'prompts', filename),
-    ];
-    for (const path of candidates) {
-        try {
-            return await readFile(path, 'utf-8');
-        }
-        catch {
-            /* try next */
-        }
-    }
-    // Remote fetch
-    const response = await fetch(AUTH_MASTER_PROMPT_URL);
-    if (!response.ok) {
-        throw new Error(`Auth master integration prompt not available (HTTP ${response.status})`);
-    }
-    return response.text();
-}
-const CUSTOM_GUIDE = `# Universal Bridge Integration Guide
-
-This guide covers integrating Bridge into any language/framework using the REST API directly.
-
-## 1. Authentication — JWKS-based JWT Verification
-
-Bridge issues JWTs signed with PS256. Verify them using your app's JWKS endpoint:
-
-\`\`\`
-GET https://api.thebridge.dev/v1/account/app/.well-known/jwks.json
-\`\`\`
-
-Use a JWT library in your language that supports JWKS auto-refresh:
-- Node.js: \`jose\`
-- Python: \`PyJWKClient\` from \`PyJWT\`
-- Go: \`github.com/lestrrat-go/jwx\`
-- Java: \`com.nimbusds:nimbus-jose-jwt\`
-- Ruby: \`jwt\` gem
-
-## 2. Token Structure
-
-The access token contains:
-- \`sub\` — User ID
-- \`tid\` — Tenant ID
-- \`role\` — User's role
-- \`privileges\` — Array of privilege strings
-- \`plan\` — Tenant's plan key
-
-## 3. Feature Flags
-
-Evaluate flags server-side for a signed-in user (the Bridge evaluates; you get values).
-This is not the endpoint the SDKs load flag rules from — that one returns the rules
-for local evaluation, and the SDKs call it for you:
-\`\`\`
-POST https://api.thebridge.dev/cloud-views/flags/bulkEvaluate/{appId}
-Authorization: Bearer <user-access-token>
-\`\`\`
-
-## 4. User/Tenant Management
-
-Use the Bridge REST API with an API token:
-\`\`\`
-GET https://api.thebridge.dev/v1/account/tenant
-x-api-key: <your-api-token>
-\`\`\`
-
-## 5. Webhooks
-
-Configure a webhook URL in your app settings to receive events:
-- User created/updated/deleted
-- Tenant created/updated
-- Subscription changes
-
-See the Bridge API documentation for the full webhook payload format.
-`;
-//# sourceMappingURL=guide.command.js.map