@synap-core/cli 1.10.0 → 1.12.2

package/dist/commands/bridge-setup.d.ts

@@ -18,9 +18,13 @@
  * Hidden on purpose: this is a dogfood/dev convenience, not a first-class
  * surface. Not shown in `synap --help`.
  *
+ * The bridge lands data POD-WIDE by default. An OPTIONAL project scope can be
+ * picked interactively (or via --project-id); --workspace-id remains an
+ * advanced/legacy escape hatch to pin a single workspace, never prompted.
+ *
  * Usage:
  *   synap bridge-setup --client-id <discord-app-id> [--bridge-dir <path>]
- *     [--pod <profile-name>] [--workspace-id <uuid>]
+ *     [--pod <profile-name>] [--workspace-id <uuid>] [--project-id <uuid>]
  *     [--proactive-channel <discord-channel-id>] [--enable-react]
  *     [--pod-url <url>] [--api-key <key>]
  */
@@ -34,13 +38,22 @@ export interface BridgeSetupOpts {
     apiKey?: string;
     bridgeDir?: string;
     clientId?: string;
+    /** Advanced/legacy escape hatch — pins the bridge to one workspace instead of pod-wide. */
     workspaceId?: string;
+    /** Scopes the bridge to one project (peer lens to workspace). Skips the project prompt. */
+    projectId?: string;
     proactiveChannel?: string;
     enableReact?: boolean;
     /** Discord bot token — provisioned INTO the pod vault (not a loose env var). */
     botToken?: string;
     /** Discord server (guild) id — written to the bridge .env. */
     guildId?: string;
+    /**
+     * Re-ask every question and re-provision from scratch, ignoring what a
+     * previous run already configured (pod choice, project pin, agent template,
+     * governance, the vaulted bot token). Without it a re-run REUSES all of that.
+     */
+    reconfigure?: boolean;
 }
 export declare function bridgeSetup(opts: BridgeSetupOpts): Promise<void>;
 /**