@bridge_gpt/mcp-server 0.2.53 → 0.2.55

package/README.md

@@ -32,8 +32,7 @@ account — it will ask.
   `--api-key` or `BAPI_API_KEY` — the installer writes that store, it does not read
   it back.
 - Writes outside your project root only when you pick a host whose configuration is
-  global: OpenAI Codex (`~/.codex/config.toml`) and GitHub Copilot CLI
-  (`~/.copilot/mcp-config.json`).
+  global: OpenAI Codex (`~/.codex/config.toml`).
 
 **Prerequisites**
 
@@ -41,8 +40,8 @@ account — it will ask.
 - **A project directory** — run the command from the folder your editor opens: your
   repository root, the one containing `.git`. No `package.json` is required — SFCC
   cartridge repos, Python, Go, Rust, and other non-Node projects work the same way.
-- **An MCP-capable editor or CLI**: Claude Code, GitHub Copilot in VS Code, GitHub
-  Copilot CLI, Cursor, Windsurf, or OpenAI Codex.
+- **An MCP-capable editor or CLI**: Claude Code, GitHub Copilot in VS Code, Cursor,
+  Windsurf, or OpenAI Codex.
 - **No Bridge account needed.** The installer can create one for you from just an
   email address.
 
@@ -87,13 +86,13 @@ npx -y @bridge_gpt/mcp-server install
 a token:
 
 ```
-1. Yes, I have received a token
-2. No, I need one
+1. I need a token
+2. I already have a token
 ```
 
-- Choose **2** if you have nothing yet. It asks for your email address and a name
+- Choose **1** if you have nothing yet. It asks for your email address and a name
   for your new Bridge project, then creates both for you.
-- Choose **1** if someone gave you a token — either a Bridge API key or an invite
+- Choose **2** if someone gave you a token — either a Bridge API key or an invite
   code. Paste it at the hidden prompt; you do not have to say which kind it is,
   because the installer recognizes it. Nothing is echoed as you type.
 
@@ -120,8 +119,8 @@ include a host the installer can launch, the run has to be on an interactive
 terminal, and you have to accept the consent prompt (*"Bridge can configure and set
 up this project for you automatically. Open a `<tool>` session to do that now?
 (Y/n)"*). Claude Code is the only selection that launches on its own. A
-Cursor-only, Copilot, Copilot CLI, Codex, or Windsurf selection, a non-interactive
-run, or a declined prompt all print the command to continue by hand instead. Pass
+Cursor-only, Copilot, Codex, or Windsurf selection, a non-interactive run, or a
+declined prompt all print the command to continue by hand instead. Pass
 `--agent claude` or `--agent cursor-agent` to override the decision outright.
 
 **7. Follow the next step the session shows you, if it shows one.** The installer
@@ -143,7 +142,7 @@ Want to see what would happen without changing anything? Add `--dry-run`.
 
 | Path | What it is | Commit it? |
 |---|---|---|
-| `.claude/commands/`, `.cursor/commands/` | The slash commands your editor runs | Yes |
+| `.claude/commands/`, `.cursor/commands/`, `.github/prompts/`, `.github/skills/` | The generated workflow commands for supported agent hosts | Yes |
 | `.claude/agents/` and editor equivalents | Agent definitions used by those commands | Yes |
 | `.bridge/config` | Your project manifest — the repository name and which MCP targets to provision. Deliberately secret-free | Yes |
 | `.bridge/pipelines/`, `.bridge/instructions/` | Editable pipeline definitions | Yes |
@@ -173,8 +172,8 @@ Cursor's agent instead of Claude Code.
 
 **Selecting Windsurf prints instructions instead of writing config.** Windsurf's
 global `mcp_config.json` is never modified automatically; the installer reports the
-entry for you to paste yourself. Codex and Copilot CLI *are* written automatically,
-even though their files are global too.
+entry for you to paste yourself. Codex *is* written automatically, even though its
+file is global too.
 
 **Your key is stored for the tools that read the store.** The MCP server and the
 shell-spawned tooling (`start-tickets` and its model routing) resolve it from
@@ -261,7 +260,7 @@ Creates a brand-new Bridge project for that address and your first admin key in
 command. No account, no key, and no invite needed beforehand. The address labels
 your new workspace and may receive a setup message; delivery is best-effort, so
 nothing waits on it. The email is visible as you type (it is not a secret) and is
-never written to a log. This is the same route as answering **2** at the prompt.
+never written to a log. This is the same route as answering **1** at the prompt.
 
 **You were sent an invite code.**
 
@@ -300,7 +299,7 @@ created or spent.
 | `--invite [code]` | Redeem an invite code. Omit the value for the hidden prompt (recommended) |
 | `--api-key <key>` | Use an existing Bridge API key |
 | `--repo <name>` | Name the registered repository instead of resolving or asking for it |
-| `--tools <list>` | Configure specific MCP hosts without the picker. Accepted IDs are exactly `claude-code`, `cursor`, `copilot-vscode`, `copilot-cli`, `codex`, and `windsurf` (e.g. `claude-code,cursor`); any other value is a parse error |
+| `--tools <list>` | Configure specific MCP hosts without the picker. Accepted IDs are exactly `claude-code`, `cursor`, `copilot-vscode`, `codex`, and `windsurf` (e.g. `claude-code,cursor`); any other value is a parse error |
 | `--agent claude\|cursor-agent` | Which agent to open for the final configuration step. **No default** — without this flag the agent is derived from the hosts you selected, and an explicit value always wins, including for a host you did not select |
 | `--dry-run` | Preview every step without writing, contacting Bridge, resolving or prompting for a credential, or opening anything. Genuinely inert: it returns before the project-root prompt, before the repository is resolved, and before any tool-selection prompt, so a value it cannot know locally (an unresolved repository name, an unselected tool) is shown as **not yet known** rather than guessed |
 | `--force` | Overwrite an existing stored key without asking |
@@ -352,7 +351,7 @@ later boot.
   "mcpServers": {
     "bridge": {
       "command": "npx",
-      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.53", "serve"],
+      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.55", "serve"],
       "env": {
         "BAPI_BASE_URL": "https://bridgegpt-api.com",
         "BAPI_REPO_NAME": "your-repo",
@@ -366,7 +365,7 @@ later boot.
 </details>
 
 <details>
-<summary><strong>VS Code / Copilot (.vscode/mcp.json)</strong></summary>
+<summary><strong>GitHub Copilot (.vscode/mcp.json)</strong></summary>
 
 ```json
 {
@@ -374,7 +373,7 @@ later boot.
     "bridge": {
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.53", "serve"],
+      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.55", "serve"],
       "env": {
         "BAPI_BASE_URL": "https://bridgegpt-api.com",
         "BAPI_REPO_NAME": "your-repo",
@@ -396,33 +395,7 @@ later boot.
     "bridge": {
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.53", "serve"],
-      "env": {
-        "BAPI_BASE_URL": "https://bridgegpt-api.com",
-        "BAPI_REPO_NAME": "your-repo",
-        "BAPI_API_KEY": "your-api-key",
-        "BAPI_DOCS_DIR": "docs/tmp"
-      }
-    }
-  }
-}
-```
-</details>
-
-<details>
-<summary><strong>GitHub Copilot CLI (~/.copilot/mcp-config.json)</strong></summary>
-
-Copilot CLI reads a single global file. The installer writes this one for you when
-you select `copilot-cli`; the shape below is what it produces.
-
-```json
-{
-  "mcpServers": {
-    "bridge": {
-      "type": "local",
-      "command": "npx",
-      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.53", "serve"],
-      "tools": ["*"],
+      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.55", "serve"],
       "env": {
         "BAPI_BASE_URL": "https://bridgegpt-api.com",
         "BAPI_REPO_NAME": "your-repo",
@@ -445,7 +418,7 @@ Windsurf only supports global MCP configuration.
   "mcpServers": {
     "bridge": {
       "command": "npx",
-      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.53", "serve"],
+      "args": ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.55", "serve"],
       "env": {
         "BAPI_BASE_URL": "https://bridgegpt-api.com",
         "BAPI_REPO_NAME": "your-repo",
@@ -464,7 +437,7 @@ Windsurf only supports global MCP configuration.
 ```toml
 [mcp_servers.bridge]
 command = "npx"
-args = ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.53", "serve"]
+args = ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.55", "serve"]
 
 [mcp_servers.bridge.env]
 BAPI_BASE_URL = "https://bridgegpt-api.com"
@@ -802,7 +775,16 @@ Repository and ticket housekeeping commands, beyond the tiers above. Implementat
 | `/parse-repository` | Queue a background job to index the repository for Bridge AI agents |
 | `/scan-tickets` | Sync recently-updated Jira tickets and backfill workflow timestamps |
 
-> Commands are designed for Claude Code. Other editors may support slash commands differently — check your editor's documentation for how to invoke prompt files.
+> **GitHub Copilot modes.** On VS Code's Local agent, Bridge provisions one
+> `.github/prompts/<command>.prompt.md` prompt per packaged command, including
+> `/explore-ticket`. On VS Code Agent Host, prompt files are not loaded, so the
+> installer provisions the same canonical command as a project skill at
+> `.github/skills/<command>/SKILL.md`; invoke that skill by its slash-command
+> name. Bridge does not claim Copilot CLI or cloud-agent workflow support from
+> this scaffold alone. If either artifact is not discovered, use VS Code's Chat
+> Customizations diagnostics, confirm the workspace is trusted, and invoke the
+> workflow manually with its full instructions rather than assuming the slash
+> command is available.
 
 ### Extra Capabilities
 
@@ -1090,12 +1072,54 @@ all, because an unknown owner is not the same as a not-ready one. No branch,
 including every error path, ever offers you two paths.
 
 `drive-epic` owns no branch behavior of its own — it forwards `--feature-branch
-<name>` and `--into-base` verbatim to `setup-epic`, which decides the strategy (see
-below). With neither flag, a multi-ticket epic runs on `epic/<KEY>`.
+<name>`, `--into-base`, and `--attended` verbatim to `setup-epic`, which decides
+the strategy and the posture (see below). With none of them, a multi-ticket epic
+runs on `epic/<KEY>`, unattended.
+
+**The composed bring-up is two-phase (BAPI-1102).** With `--plan-file` on a
+repository whose readiness is missing only the runtime facts, one invocation runs,
+in order: the **control plane** (Bridge API server + reconciler, each gated on its
+own readiness), then `setup-epic` to create and approve the run, then **executor
+lanes scoped to that run** with `--epic-run-id <run>`, then the **dead-man
+observer** last, then the ready banner. The order is forced: an executor lane must
+carry an explicit claim scope, and the run it is scoped to does not exist until the
+server is up and `setup-epic` has run.
+
+A composed plane serves **exactly one** run; start a second plane for a second
+epic. If `setup-epic` fails, the control plane is left running and **no executor
+lane is spawned**. If the lanes fail to become ready, the control plane and the
+committed run are both left intact and the observer is not started — nothing is
+rolled back, because a local process that failed to start says nothing about
+whether the run is valid.
+
+"Plane ready" reports **processes**, not dispatchability: if the run cuts an epic
+branch, the reconciler holds ticket dispatch until that branch's index scope
+finishes preparing.
 
 Two conductors is a transitional state. When one is eliminated, `drive-epic` is
 the only thing that changes.
 
+### `plane up` — claim scope is required
+
+`plane up` starts the runtime on its own, and every executor lane it starts needs
+an explicit claim scope:
+
+```
+npx -y @bridge_gpt/mcp-server plane up --epic-run-id <run-id>   # repeatable
+npx -y @bridge_gpt/mcp-server plane up --repo-wide              # or repository-wide
+```
+
+The two are mutually exclusive. Asked to start lanes with neither, `plane up`
+**refuses before spawning anything**, in the executor's own words. That is not a
+new restriction — an executor started with no claim scope has refused to start
+since BAPI-1026 — it is that refusal moved to where it is actionable, instead of
+surfacing as a member crash and a full plane rollback.
+
+`plane status` reports the lifecycle phase (control plane starting/ready, lanes
+starting/ready, observer active, plane ready) and the epic run the plane is bound
+to. `plane down` handles every intermediate phase: it stops the bound run first,
+then signals the recorded process group.
+
 ### `setup-epic`
 
 Bootstraps an Epic Conductor v2 run in one command — creates the epic run, stores the plan DAG, and approves it:
@@ -1118,21 +1142,56 @@ branch, matching plain `start-tickets`.
 > name, or to force a branch for a single-node plan. Passing both is a parse error,
 > refused before any file read, credential resolution, or network call.
 
+**A run that selects an epic branch is created UNATTENDED (BAPI-1102).** Its
+`policy_json` carries `posture: "unattended"` and `v2_auto_merge_enabled: true`, so
+child PRs merge into the epic branch without parking for a human at every gate. The
+**integration PR into the repository base branch stays human-gated.** The run's CI
+gate is stamped **server-side at first approval** — from your repository's declared
+default, or, when it declares none, as an explicit recorded `no_ci_gate` mode.
+
+> **Behavior change (BAPI-1102).** Pass `--attended` to restore the previous
+> composition: `base_branch` plus an explicitly requested `--review-policy`, with no
+> posture and no auto-merge authorization. `--into-base`, single-node plans, and
+> branch-silent invocations are **unchanged** — they send no `policy_json` at all,
+> byte for byte as before. A `--policy-file` still supersedes composition entirely;
+> combining `--attended` with a file that declares `posture: "unattended"` is a named
+> refusal rather than a silent winner.
+
+An unattended run has two one-time **repository** prerequisites — consent
+(`unattended_epic_implementer_allowed`) and a verified notify webhook default — plus
+confirmed default-branch review/CI workflows. Each is refused by name **before any
+run row is created** (`target_not_allowed`, `webhook_unverified`,
+`repository_readiness_unconfirmed`), and `drive-epic` readiness and `doctor` both
+list them with their current state. `notify.local_sink` does not satisfy the webhook
+prerequisite.
+
+> **Rollout note.** The client-side default and the server-side admission,
+> stamping, and readiness changes must be released as **one compatible unit**. The
+> new default's shape (`v2_auto_merge_enabled: true` with no `required_checks`) is
+> exactly what the create route refused before BAPI-1102, so shipping the client
+> half alone would 422 every unattended run at `POST /jira/epic-runs/runs`.
+> Deploying only the server half is safe and inert: it narrows two refusals and adds
+> a first-approval stamp, and **rewrites no existing run**. No database migration and
+> no new environment variable is introduced — `config_projects.unattended_epic_implementer_allowed`
+> and `epic_supervisor_setup.done_gate_config` already exist and are read as-is.
+
 Once the plan is approved, the **server-side reconciler** picks the run up within ~30s. To execute claimed jobs on your machine, run `executor`:
 
 ```
 npx -y @bridge_gpt/mcp-server executor --repo <name>
 ```
 
-### `conduct-epic`
+### `implement-epic`
 
 The deterministic half of the `/conduct-epic` loop: it owns the epic branch, a
 versioned local checkpoint, a per-epic lock, and the read-only probes the loop
 decides on. It never creates or mutates an `epic_run` — that is the server-side
 v2 reconciler's job, and `init` refuses to start when one is already active.
+This is EPIC-LEVEL orchestration, distinct from the ticket-level
+`implement-ticket` command.
 
 ```
-npx -y @bridge_gpt/mcp-server conduct-epic <verb> [flags]
+npx -y @bridge_gpt/mcp-server implement-epic <verb> [flags]
 ```
 
 **Verbs**
@@ -1198,9 +1257,9 @@ appear in a command argument, in stdout/stderr, or in a journal line.
 
 ### Conductor (epic & multi-agent orchestration)
 
-Conductor is an **opt-in, off-by-default** layer for epic supervision, inter-agent messaging, done-gate evaluation, local git-hook event producers, and conditional auto-merge. Its full reference — the v2 architecture (server-side reconciler + local executor), `setup-epic`, `conductor install-git-hooks`, the supervisor `done_gate_config` / `auto_merge_enabled` settings, and the observability stream — lives in **[CONDUCTOR.md](./docs/CONDUCTOR.md)**.
+Conductor is an **opt-in, off-by-default** layer for epic supervision, inter-agent messaging, done-gate evaluation, local git-hook event producers, and conditional auto-merge. Its full reference — the v2 architecture (server-side reconciler + local executor), `setup-epic`, `epic-implementer install-git-hooks`, the supervisor `done_gate_config` / `auto_merge_enabled` settings, and the observability stream — lives in **[CONDUCTOR.md](./docs/CONDUCTOR.md)**. (The event-ledger CLI was renamed from `conductor` to `epic-implementer`; the retained `conductor` bin name is now a fixed migration pointer.)
 
-> The v1 `conductor epic-tick` command is **frozen** — it throws on every invocation. There is nothing to schedule locally, and `conductor doctor` flags any epic-tick schedule left over from an earlier release so you can cancel it.
+> The v1 `epic-implementer epic-tick` command is **frozen** — it throws on every invocation. There is nothing to schedule locally, and `epic-implementer doctor` flags any epic-tick schedule left over from an earlier release so you can cancel it.
 
 ## Custom Pipelines
 
@@ -1487,17 +1546,18 @@ The full surface, for when you need the complete enumeration. Day-to-day, use [U
 
 ### MCP tools
 
-The authoritative tool catalog covers **73 tools** (enumerated below). What's actually registered in a session depends on `BRIDGE_MCP_PROFILE`: the default `core` profile loads a trimmed subset, and the conductor/pipeline-authoring/SFCC tools are added only under their respective profiles (see [Environment Variables](#environment-variables)). Async AI tools follow a request/get pattern: call the `request_*` tool to kick off generation, then the matching `get_*` tool to retrieve the result (or pass `wait_for_result: true` to poll automatically).
+The authoritative tool catalog covers **75 tools** (enumerated below). What's actually registered in a session depends on `BRIDGE_MCP_PROFILE`: the default `core` profile loads a trimmed subset, and the conductor/pipeline-authoring/SFCC tools are added only under their respective profiles (see [Environment Variables](#environment-variables)). Async AI tools follow a request/get pattern: call the `request_*` tool to kick off generation, then the matching `get_*` tool to retrieve the result (or pass `wait_for_result: true` to poll automatically).
 
 - **Connectivity & identity** — `ping` (its JSON also carries `docs_dir`, `role`, and `customer_type`)
 - **Team & access** — `invite_member` (admin-only; mints a scoped access key for a teammate on an already-configured project — the plaintext key is shown exactly once)
 - **Jira tickets** — `get_tickets`, `get_ticket`, `create_ticket`, `update_ticket_description`, `add_comment`, `get_comments`
 - **Attachments** — `attachment` (operations: `upload`, `download`, `list`)
 - **AI generation (request/get)** — `request_plan_generation`/`get_plan`, `create_doc`/`get_doc` (design docs by `doc_type`: tdd/architecture/fsd/prd, where `architecture` is an alias of `tdd`), `request_ticket_review` (writes both `get_clarifying_questions` and `get_ticket_critique`), `request_reimplement_context`/`get_reimplement_context`, `request_council`/`get_council`, `request_deep_research`/`get_deep_research`
+- **Bounded waits** — `wait_for_ticket_review`, `wait_for_ci_checks`. Each call waits at most 240 s and returns `state: "ready" | "pending" | "error"`; `pending` is a normal, resumable result you call again on, never a failure. They exist so an agent can wait without a foreground `sleep` and without binding a long server-side operation to the 900 s MCP client deadline. `wait_for_ci_checks` reports only that checks are **terminal** — deciding pass or fail stays with the caller.
 - **Other AI** — `second_opinion`, `generate_image`, `generate_decision_page`, `visual_diff` (deterministic pixel diff of a rendered URL vs a design comp)
 - **Ticket lifecycle** — `track_ticket`, `update_ticket_state`, `get_ticket_state`, `get_ticket_state_tree` (live repo-wide lifecycle + dependency tree; read-only, no mutation parameter)
 - **Jira status** — `update_jira_status` (pass `status: "auto"` to resolve the configured post-PR status server-side)
-- **Repository & CI** — `parse_repository` (`action`: `start`, `status`), `regenerate_directory_map`, `create_pull_request`, `merge_pull_request`, `resolve_ci_checks`, `poll_ci_checks`
+- **Repository & CI** — `parse_repository` (`action`: `start`, `status`), `regenerate_directory_map`, `create_pull_request`, `merge_pull_request`, `resolve_ci_checks`, `poll_ci_checks`, `wait_for_ci_checks` (the last two are hidden until `ci_check_config` resolves, and share one visibility gate)
 - **Pipelines & automation** — `get_pipeline_recipe` (returns a fully resolved recipe the agent executes step-by-step)
 - **Config** — `get_project_standards`, `config_field` (operations: `get`, `update`, `list`)
 

package/build/agent-guidance.generated.js

@@ -0,0 +1,3 @@
+// AUTO-GENERATED — do not edit manually. Regenerate with: npm run build
+// This file is produced by scripts/bundle-agent-guidance.js from mcp_server/agent-guidance.md
+export const AGENT_GUIDANCE = "### Get Project Standards (`get_project_standards`)\n\n**When to use it:** (Implementation | Refinement) Before writing or reviewing code, so the agent applies this project's recorded coding standards instead of generic defaults.\n\n**How to use it:** Call the `get_project_standards` MCP tool directly — it takes no required input and returns the project's recorded standards text.\n\n### Second Opinion (`second_opinion`)\n\n**When to use it:** (Architecture | Refinement | Implementation) Any time you want a quick sanity check on a plan, draft, or decision from a fresh perspective.\n\n**How to use it:** Ask your agent — \"Get a second opinion from Gemini on whether the BAPI-123 plan's migration step is safe to run against production.\"\n\n### Council (`request_council`)\n\n**When to use it:** (Architecture | Refinement) Early, when you want a spread of approaches — technical for how to build it, design for how it should look, discovery for what still needs figuring out before a real ticket exists, general for a quick brief-driven pass before the repository is indexed.\n\n**How to use it:** `/council <question>`\n\n### Review Ticket (`request_ticket_review`)\n\n**When to use it:** (Refinement) Right after a ticket is drafted, before anyone starts building — to surface gaps and tighten it.\n\n**How to use it:** `/review-tickets BAPI-123` (command only — \"review\" as free text is easily mistaken for a freehand agent review). A single key reviews inline in the current session — no terminal tab, no worktree. For several tickets at once, `/review-tickets BAPI-123 BAPI-456` opens one terminal tab per ticket and reviews them in parallel with no worktrees; every review flag applies, and `--review KEY=auto,rounds=N` sets per-ticket overrides.";

package/build/agent-launchers/claude-executor-adapter.js

@@ -345,6 +345,9 @@ export function createClaudeExecutorAdapter(spec, deps = {}) {
             if (input.workerBranch !== undefined) {
                 envOptions.workerBranch = input.workerBranch;
             }
+            if (input.declaredTouchedFiles !== undefined) {
+                envOptions.declaredTouchedFiles = input.declaredTouchedFiles;
+            }
             return {
                 executable: spec.command,
                 argv: buildClaudeArgv(input.prompt, input.modelAlias, input.mcpConfigPath, input.posture),

package/build/agent-launchers/claude.js

@@ -3,7 +3,7 @@
  *
  * Resolves the `claude` binary against the *explicitly supplied PATH* (not the
  * ambient process default) and builds the launched-run invocation by delegating
- * to the shared `renderScheduledPrompt` renderer (no hard-coded `/full-automation`
+ * to the shared `renderScheduledPrompt` renderer (no hard-coded per-command
  * prompt). It emits `{ exe, args: ["-p", prompt] }`. Claude Code has no
  * working-directory flag, so the cwd is always set by the launching unit — this
  * adapter must never add a working-directory argument to the invocation.
@@ -41,8 +41,8 @@ export async function resolveCommandOnPath(command, envPath, deps) {
     return pathApi.normalize(candidate);
 }
 /**
- * Backward-compatibility shim for callers that quoted an idea-file path for a
- * `/full-automation` prompt. Generalized prompt-token quoting now lives in
+ * Backward-compatibility shim for callers that quoted an idea-file path for the
+ * pre-rename automation prompt. Generalized prompt-token quoting now lives in
  * `quotePromptToken`; this preserves the original quote semantics (always wrap in
  * double quotes, escape embedded quotes) for any remaining path callers.
  */

package/build/agent-launchers/prompt.js

@@ -32,15 +32,14 @@ function schemaSupportsAutoFlag(schema) {
  * the normalized `input.args`, plus (only where the command can parse them)
  * `--scheduled-at <ISO>` and `--auto`.
  *
- * `--scheduled-at` is appended for `full-automation` (legacy) and `epic-tick`
- * (BAPI-418), both of whose parsers accept it as a first-class argument. Every
- * other command rejects unrecognized flags and halts (e.g. `start-tickets` stops
- * on any unsupported flag), and the shared late-fire gate already embeds the
- * scheduled time — so injecting `--scheduled-at` into their argv would break an
- * otherwise launchable command for no benefit.
+ * `--scheduled-at` is appended for `epic-tick` (BAPI-418), whose parser accepts
+ * it as a first-class argument. Every other command rejects unrecognized flags
+ * and halts (e.g. `start-tickets` stops on any unsupported flag), and the shared
+ * late-fire gate already embeds the scheduled time — so injecting `--scheduled-at`
+ * into their argv would break an otherwise launchable command for no benefit.
  *
  * `--auto` is appended when auto-approve is set AND the command supports it (its
- * schema declares a boolean `--auto` flag, or it is `full-automation` / `epic-tick`).
+ * schema declares a boolean `--auto` flag, or it is `epic-tick`).
  * It is never duplicated if already present in `input.args`.
  *
  * This is the SINGLE source of the delegated argv: both the rendered target
@@ -54,12 +53,10 @@ function buildAugmentedArgs(input) {
     // epic-tick already accepts --scheduled-at (parseEpicTickArgs, cli.ts) so it
     // receives the scheduled time as a structured arg for the late-fire decision,
     // not just via the embedded gate text.
-    if (input.commandName === "full-automation" || input.commandName === "epic-tick") {
+    if (input.commandName === "epic-tick") {
         args.push("--scheduled-at", input.runAtIso);
     }
-    const supportsAuto = schemaSupportsAutoFlag(input.schema) ||
-        input.commandName === "full-automation" ||
-        input.commandName === "epic-tick";
+    const supportsAuto = schemaSupportsAutoFlag(input.schema) || input.commandName === "epic-tick";
     const alreadyHasAuto = input.args.includes("--auto");
     if (input.autoApprove && supportsAuto && !alreadyHasAuto) {
         args.push("--auto");

package/build/agent-notes.js

@@ -0,0 +1,178 @@
+/**
+ * Marker-scoped, opt-in cross-platform agent notes writer (BAPI-1207).
+ *
+ * Creates or refreshes a Bridge-owned region inside a consumer project's
+ * `AGENTS.md` (shared by Cursor, Copilot VS Code, Codex, and Claude Code) and,
+ * for Claude Code specifically, a pointer region inside `CLAUDE.md` — so a
+ * Claude-only selection never leaves a dangling `@AGENTS.md` reference. Every
+ * other byte in either file — content a person wrote by hand outside the
+ * marker pair — is preserved exactly.
+ *
+ * This module performs I/O only through the injected `readFile`/`writeFile`/
+ * `mkdir` seams, mirroring the rest of the install-flow dependency-injection
+ * convention (see `InstallBridgeDeps` in `install-bridge.ts`), and does no
+ * platform detection, credential handling, `.gitignore` mutation, or scaffold
+ * bookkeeping of its own — those stay the caller's responsibility.
+ */
+import path from "path";
+/** The runtime marker pair this module owns inside a target notes file. */
+export const BRIDGE_MCP_GUIDANCE_BEGIN_MARKER = "<!-- BEGIN BRIDGE MCP GUIDANCE -->";
+export const BRIDGE_MCP_GUIDANCE_END_MARKER = "<!-- END BRIDGE MCP GUIDANCE -->";
+/** Platforms whose shared notes file is AGENTS.md. Claude Code also gets CLAUDE.md. */
+const AGENTS_MD_PLATFORMS = new Set([
+    "cursor",
+    "copilot-vscode",
+    "codex",
+    "claude-code",
+]);
+/**
+ * Pure projection from a selected-platform set to the physical notes files
+ * that selection implies. Never touches the filesystem or re-detects
+ * platforms — the caller supplies the already-selected set.
+ */
+export function resolveAgentNotesTargets(selectedPlatforms) {
+    const targets = new Set();
+    const unsupported = new Set();
+    for (const platform of selectedPlatforms) {
+        if (platform === "windsurf") {
+            unsupported.add(platform);
+            continue;
+        }
+        if (AGENTS_MD_PLATFORMS.has(platform)) {
+            targets.add("AGENTS.md");
+        }
+        // Claude Code additionally gets a CLAUDE.md pointer — never a substitute
+        // for AGENTS.md, since @AGENTS.md would otherwise dangle.
+        if (platform === "claude-code") {
+            targets.add("CLAUDE.md");
+        }
+    }
+    const ordered = [];
+    if (targets.has("AGENTS.md"))
+        ordered.push("AGENTS.md");
+    if (targets.has("CLAUDE.md"))
+        ordered.push("CLAUDE.md");
+    return { targets: ordered, unsupportedPlatforms: [...unsupported] };
+}
+/** The one-line pointer note CLAUDE.md's owned region carries (BAPI-1207). */
+const CLAUDE_NOTES_POINTER_NOTE = "Bridge MCP usage guidance is maintained in AGENTS.md — see the section above.";
+function buildClaudeOwnedBody() {
+    return `@AGENTS.md\n\n${CLAUDE_NOTES_POINTER_NOTE}`;
+}
+function countOccurrences(text, marker) {
+    return text.split(marker).length - 1;
+}
+/**
+ * Locate the existing owned region in *text*, or classify why it cannot be
+ * located safely. A malformed topology (a missing half, a duplicate, reversed
+ * order, or a marker not on its own line) is reported rather than repaired —
+ * this module never appends a second region next to one it cannot parse.
+ */
+function scanMarkers(text) {
+    const beginCount = countOccurrences(text, BRIDGE_MCP_GUIDANCE_BEGIN_MARKER);
+    const endCount = countOccurrences(text, BRIDGE_MCP_GUIDANCE_END_MARKER);
+    if (beginCount === 0 && endCount === 0)
+        return { kind: "absent" };
+    if (beginCount === 0 || endCount === 0) {
+        return { kind: "malformed", reason: "missing half of the marker pair" };
+    }
+    if (beginCount > 1)
+        return { kind: "malformed", reason: "duplicate BEGIN marker" };
+    if (endCount > 1)
+        return { kind: "malformed", reason: "duplicate END marker" };
+    const beginIndex = text.indexOf(BRIDGE_MCP_GUIDANCE_BEGIN_MARKER);
+    const endIndex = text.indexOf(BRIDGE_MCP_GUIDANCE_END_MARKER);
+    if (endIndex < beginIndex)
+        return { kind: "malformed", reason: "markers are reversed" };
+    const afterBegin = beginIndex + BRIDGE_MCP_GUIDANCE_BEGIN_MARKER.length;
+    if (text[afterBegin] !== "\n") {
+        return { kind: "malformed", reason: "BEGIN marker is not on its own line" };
+    }
+    const contentStart = afterBegin + 1;
+    const lineStart = text.lastIndexOf("\n", endIndex - 1) + 1;
+    if (text.slice(lineStart, endIndex).trim().length > 0) {
+        return { kind: "malformed", reason: "END marker is not on its own line" };
+    }
+    return { kind: "present", contentStart, contentEnd: endIndex };
+}
+/** Replace only the bytes between valid existing markers; preserve everything else. */
+function replaceRegion(text, contentStart, contentEnd, ownedBody) {
+    const normalized = ownedBody.trim() + "\n";
+    return text.slice(0, contentStart) + normalized + text.slice(contentEnd);
+}
+/**
+ * Append one fresh owned region at EOF, using the minimal separator needed
+ * for a clean markdown boundary. The existing prefix is never normalized —
+ * only the amount of new whitespace inserted before the region varies.
+ */
+function appendRegion(existingText, ownedBody) {
+    const region = `${BRIDGE_MCP_GUIDANCE_BEGIN_MARKER}\n${ownedBody.trim()}\n${BRIDGE_MCP_GUIDANCE_END_MARKER}\n`;
+    if (existingText.length === 0)
+        return region;
+    if (existingText.endsWith("\n\n"))
+        return existingText + region;
+    if (existingText.endsWith("\n"))
+        return existingText + "\n" + region;
+    return existingText + "\n\n" + region;
+}
+function isEnoent(err) {
+    return (typeof err === "object" &&
+        err !== null &&
+        "code" in err &&
+        err.code === "ENOENT");
+}
+async function writeOneTarget(target, options) {
+    const filePath = path.join(options.cwd, target);
+    let existing;
+    try {
+        existing = await options.readFile(filePath);
+    }
+    catch (err) {
+        if (isEnoent(err)) {
+            existing = "";
+        }
+        else {
+            return { target, status: "failed", reason: "could not read the existing file" };
+        }
+    }
+    const ownedBody = target === "AGENTS.md" ? options.guidance : buildClaudeOwnedBody();
+    const scan = scanMarkers(existing);
+    let merged;
+    if (scan.kind === "malformed") {
+        return {
+            target,
+            status: "failed",
+            reason: `existing marker region is malformed (${scan.reason})`,
+        };
+    }
+    else if (scan.kind === "present") {
+        merged = replaceRegion(existing, scan.contentStart, scan.contentEnd, ownedBody);
+    }
+    else {
+        merged = appendRegion(existing, ownedBody);
+    }
+    if (merged === existing) {
+        return { target, status: "skipped", reason: "content already up to date" };
+    }
+    try {
+        await options.mkdir(path.dirname(filePath), { recursive: true });
+        await options.writeFile(filePath, merged, { encoding: "utf-8" });
+    }
+    catch {
+        return { target, status: "failed", reason: "could not write the file" };
+    }
+    return { target, status: "written" };
+}
+/**
+ * Create or refresh the Bridge-owned notes region in every target the
+ * selected platforms resolve to. Each target is handled independently — a
+ * failure on one never rolls back or blocks a write already made to another.
+ */
+export async function writeAgentNotes(options) {
+    const { targets, unsupportedPlatforms } = resolveAgentNotesTargets(options.selectedPlatforms);
+    const files = [];
+    for (const target of targets) {
+        files.push(await writeOneTarget(target, options));
+    }
+    return { files, unsupportedPlatforms };
+}

package/build/agent-registry.js

@@ -44,8 +44,11 @@ export const AGENT_REGISTRY = {
         supportsModelOverride: true,
         modelFlag: "--model",
         // Claude family aliases float to the latest release and never drift, so they
-        // can be validated against a static allowlist.
-        tierModels: { cheap: "haiku", basic: "sonnet", premium: "opus" },
+        // can be validated against a static allowlist. The `cheap` tier deliberately
+        // maps to `sonnet` (not `haiku`): even the lowest-difficulty tickets route to
+        // sonnet. `haiku` stays in the allowlist so a per-repo
+        // `difficulty_model_tier_overrides` may still opt back into it.
+        tierModels: { cheap: "sonnet", basic: "sonnet", premium: "opus" },
         staticModelAliasAllowlist: ["haiku", "sonnet", "opus"],
         // BAPI-781: the reference executor adapter. `managedCarriers` is EMPTY and
         // `passthroughs` names only the operator's own OAuth variable — Bridge