@bridge_gpt/mcp-server 0.2.58 → 0.2.60

package/build/version.generated.js

@@ -1,4 +1,4 @@
 // AUTO-GENERATED — do not edit manually. Regenerate with: npm run build
-export const VERSION = "0.2.58";
-export const BUILD_COMMIT = "e29c3f46e4eb";
-export const LAUNCHER_ARGS = ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.58", "serve"];
+export const VERSION = "0.2.60";
+export const BUILD_COMMIT = "1920a31997d2";
+export const LAUNCHER_ARGS = ["-y", "--prefer-offline", "@bridge_gpt/mcp-server@0.2.60", "serve"];

package/docs/CONDUCTOR.md

@@ -159,18 +159,18 @@ the scheduler can catch overlaps you did not anticipate.
 > reconciler). That backstop covers declared and undeclared nodes alike — which is
 > exactly why omitting `touched_files` is safe to accept.
 
-## The conductor CI gate — `conductor-ci / gate` (BAPI-695)
+## The conductor CI gate — `epic-implementer-ci / gate` (BAPI-695)
 
 **Before driving a run you want CI-gated, wire its policy.** The reconciler's
 per-ticket `ci` gate reads **`policy_json.required_checks`** (a declared
 `RunPolicy` key) and observes those check-run conclusions at the ticket PR's
 **current head SHA**. If that list is empty, the observer short-circuits to
 `PASSED` with `{"no_required_checks": true}` and **runs no CI at all** — the loop
-merges on hand-verification only. `.github/workflows/conductor-ci.yml` publishes
-the real, always-reporting required context **`conductor-ci / gate`**; set
+merges on hand-verification only. `.github/workflows/epic-implementer-ci.yml` publishes
+the real, always-reporting required context **`epic-implementer-ci / gate`**; set
 
 ```json
-"policy_json": { "required_checks": ["conductor-ci / gate"] }
+"policy_json": { "required_checks": ["epic-implementer-ci / gate"] }
 ```
 
 on every run you want gated. The workflow existing is not enough — the context has
@@ -198,7 +198,7 @@ to be in the run policy.
 
 **Once gated, expect this behavior:**
 
-- The `ci` gate now waits for `conductor-ci / gate` on the ticket PR's current head.
+- The `ci` gate now waits for `epic-implementer-ci / gate` on the ticket PR's current head.
   A complete **red** aggregator enters the bounded `ci_fix` remediation path; a
   **missing or still-running** current-head context stays pending (never a hard
   fail).
@@ -212,11 +212,11 @@ For the exact new-run/PATCH procedure (and the **whole-object `policy_json`
 replacement** caution — GET, merge `required_checks` locally, PATCH the whole
 object), and the immutable case-sensitive matching of the context string, see the
 operator runbook, **§4a "Wire the conductor CI required check"**
-([`docs/claude/epic-conductor-v2-operator-runbook.md`](../../docs/claude/epic-conductor-v2-operator-runbook.md)).
+([`docs/claude/epic-implementer-v2-operator-runbook.md`](../../docs/claude/epic-implementer-v2-operator-runbook.md)).
 
 ## Conductor observability (opt-in via `--conductor`, BAPI-394)
 
-Conductor is **off by default** — without `--conductor` no `BAPI_CONDUCTOR_*` env,
+Conductor is **off by default** — without `--conductor` no `BAPI_EPIC_IMPLEMENTER_*` env,
 supervisor tab, or message-relay prompt is produced. With `--conductor`, a run mints
 a single conductor `run_id` and emits one canonical `run.started` event into the
 local conductor ledger (`~/.config/bridge/events.db`), attributing each worker by
@@ -224,11 +224,11 @@ local conductor ledger (`~/.config/bridge/events.db`), attributing each worker b
 the selected agent is **Claude Code**, the CLI also injects a conductor lifecycle
 hook into each created worktree's `.claude/settings.local.json` (preserving any
 existing hooks) so the spawned session streams local `run.started` / `run.stopped` /
-`agent.notification` (and, with `BAPI_CONDUCTOR_ENABLE_PRE_TOOL_USE=1`,
+`agent.notification` (and, with `BAPI_EPIC_IMPLEMENTER_ENABLE_PRE_TOOL_USE=1`,
 `tool.intent`) events. Per-worker conductor identity is passed only via secret-free
 environment scoped to that one terminal/tab/session — no credentials are ever placed
 in the env, hook command, or run metadata. Override the gate/supervisor labels with
-`BAPI_CONDUCTOR_GATE_NAME` / `BAPI_CONDUCTOR_SUPERVISOR_MODE`. Inspect the stream
+`BAPI_EPIC_IMPLEMENTER_GATE_NAME` / `BAPI_EPIC_IMPLEMENTER_SUPERVISOR_MODE`. Inspect the stream
 with `epic-implementer doctor`. Observability is best-effort: a conductor failure never
 blocks or aborts a spawn, and `--dry-run` performs no conductor side effects.
 (Epic dispatch always enables conductor internally, independent of this flag.)
@@ -238,6 +238,57 @@ When `--conductor` is set, the spawn boundary also injects
 supervisor MCP tools (a plain `start-tickets` run stays on the default `core`
 profile). See [README → Environment Variables](../README.md#environment-variables).
 
+### Environment-variable names and the legacy-name refusal (BAPI-1190)
+
+Every Epic Implementer environment variable uses the `BAPI_EPIC_IMPLEMENTER_`
+prefix, and the worker Node path is `EPIC_IMPLEMENTER_NODE_PATH`. These replaced
+the old Conductor names by a plain token swap: `CONDUCTOR` became
+`EPIC_IMPLEMENTER` and the rest of the name stayed the same. For example, the old
+run-id variable is now `BAPI_EPIC_IMPLEMENTER_RUN_ID`. There are no aliases and no
+dual reads.
+
+**Old names are refused, not ignored.** If any variable with the old
+`BAPI_CONDUCTOR_` prefix, or the old `CONDUCTOR_NODE_PATH`, is set, these entry
+points refuse to start:
+
+| Entry point | On an old name |
+|---|---|
+| MCP server (bare startup) and every `npx @bridge_gpt/mcp-server <subcommand>` | stderr diagnostic, exit `1`, before any spawn, network call, ledger open, or file write |
+| `epic-implementer` bin | stderr diagnostic, exit `1`, before argv reaches the CLI |
+| `epic-implementer-claude-hook` bin | same stderr diagnostic, **exit `0`**, no ledger event |
+
+The hook is the one exception to the non-zero exit. A hook must never block the
+Claude tool loop, so it stays loud but exits `0`. The two removed `conductor`
+stub bins are not guarded; they already fail with a fixed migration message.
+
+The diagnostic lists **every** offending key, sorted, in one message. Each line
+gives the exact successor, a "retired — remove it" note (the old MCP shadowing
+override), or, for an unknown old name, the generic advice: rename the prefix if
+it is still a current setting, otherwise remove it. It prints **key names only,
+never values**, because these variables can hold secrets. Old names copied from
+frozen records (`docs/BAPI-*.md`, run notes) are refused the same way. Stale
+names usually live in shell profiles, hand-edited executor service units, or CI
+environment configuration.
+
+**Version skew.** A worker environment injected by an **older** published package
+still carries the old names. A **newer** TypeScript process started inside it (for
+example the MCP server launched through `mcp-invoke`) will refuse to start. This
+is intended: it is the loud outcome, not a silent half-configured worker.
+
+- **Remedy:** re-spawn the worker so the launcher and the process it starts run
+  the same package version.
+- **If that does not fix it:** send the MCP package owner the launcher version,
+  the process version, and the offending **key names only** — never their values.
+
+The executor's worker-environment filter rejects both whole prefixes and both
+node-path spellings, so an old ambient name never reaches a worker it spawns.
+
+**No Python guard.** No production Python reads these variables, so they are
+inert there, and no broad Python `BAPI_*` guard is added. They are refused when
+inherited by a TypeScript child or MCP process. The Python dead-man variables
+(`CONDUCTOR_DEAD_MAN_ONLY`, `CONDUCTOR_DEADMAN_*`) are a separate exact-name
+contract owned by BAPI-1231.
+
 ## `epic-implementer install-git-hooks` (BAPI-395)
 
 Installs local git hooks that opportunistically emit conductor git/PR/CI events into
@@ -373,10 +424,10 @@ supervisor remain the authority; this change only stops the worker's own ledger
 from failing.
 
 **The invariant.** Worker-facing ledger operations run through `conductor-bin.js`
-executed **under the captured conductor Node** (`CONDUCTOR_NODE_PATH`). **The worker
+executed **under the captured conductor Node** (`EPIC_IMPLEMENTER_NODE_PATH`). **The worker
 Node must never load `better-sqlite3`.** Dispatch captures the conductor process's
-own Node executable and threads it to each worker as `CONDUCTOR_NODE_PATH`, paired
-with `BAPI_CONDUCTOR_CLI_FILE` (the packaged `conductor-bin.js` path). The
+own Node executable and threads it to each worker as `EPIC_IMPLEMENTER_NODE_PATH`, paired
+with `BAPI_EPIC_IMPLEMENTER_CLI_FILE` (the packaged `conductor-bin.js` path). The
 worker-side boundary (`src/conductor/worker-ledger-cli.ts`) shells out with a fixed
 **list argv** via `execFile` (never `shell: true`, never a command string) and
 passes event JSON over **stdin** (`--data-json-stdin`), so raw payloads/secrets
@@ -384,14 +435,14 @@ never enter the process argument list. Conductor-**owned** processes (the CLI,
 supervisor, and epic runtimes) keep calling `store.ts` directly — they legitimately
 own the native load.
 
-**Fail loud, never fall back.** A missing/invalid `CONDUCTOR_NODE_PATH` or absent
-`BAPI_CONDUCTOR_CLI_FILE` raises the typed `ConductorLedgerSubprocessRuntimeError`,
+**Fail loud, never fall back.** A missing/invalid `EPIC_IMPLEMENTER_NODE_PATH` or absent
+`BAPI_EPIC_IMPLEMENTER_CLI_FILE` raises the typed `ConductorLedgerSubprocessRuntimeError`,
 surfaced to callers as the `LEDGER_SUBPROCESS_RUNTIME_UNAVAILABLE` (503) envelope
 with a fixed, path-free, secret-free `details: { env_var, reason }` bag
 (`reason ∈ missing | invalid | cli_missing | spawn_failed | malformed_stdout`). The
 boundary **never** falls back to the worker's `process.execPath` — doing so would
 re-introduce the native load into the worker Node, the exact failure this removes.
-`CONDUCTOR_NODE_PATH` is **non-secret operational metadata**: it is inherited from
+`EPIC_IMPLEMENTER_NODE_PATH` is **non-secret operational metadata**: it is inherited from
 the worker shell env injected at the spawn boundary and is **not** persisted into
 `.mcp.json`, which stays intentionally env-free.
 
@@ -411,7 +462,7 @@ BAPI-527 adds three independent reliability guarantees. Each is a protective
 default; none changes the interactive (non-conductor) `start-tickets` contract.
 
 1. **Ledger operations are isolated from the worker path.** Worker-facing ledger
-   operations run in a subprocess under `CONDUCTOR_NODE_PATH` (details above), so a
+   operations run in a subprocess under `EPIC_IMPLEMENTER_NODE_PATH` (details above), so a
    Node ABI mismatch degrades a worker convenience, never the whole session.
 
 2. **Dispatch does not alter your branch.** Unattended/epic dispatch is
@@ -422,9 +473,9 @@ default; none changes the interactive (non-conductor) `start-tickets` contract.
    guard** additionally refuses dispatch (or, with an explicit override, warns
    loudly) when the conductor's base repo path equals the operator's live
    dev-server checkout:
-   - `BAPI_CONDUCTOR_LIVE_SOURCE_PATH` — the operator's live dev-server checkout
+   - `BAPI_EPIC_IMPLEMENTER_LIVE_SOURCE_PATH` — the operator's live dev-server checkout
      path to protect.
-   - `BAPI_CONDUCTOR_ALLOW_LIVE_SOURCE_DISPATCH` — truthy (`1`/`true`/`yes`/`on`)
+   - `BAPI_EPIC_IMPLEMENTER_ALLOW_LIVE_SOURCE_DISPATCH` — truthy (`1`/`true`/`yes`/`on`)
      override that downgrades a collision from fatal to a loud warning.
    The read-only `doctor` command surfaces the guard state
    (`not-configured` / `safe` / `collision`) without mutating anything.

package/docs/install/mcp-tool-integrations.md

@@ -118,6 +118,7 @@ scope for local v1):
 | `get_comments` | Jira (only) **[BLOCK]** |
 | `add_comment` | Jira (only) **[BLOCK]** |
 | `attachment` (upload/download/list) | Jira (only) **[BLOCK]** |
+| `publish_reviewed_attachment` | Jira (only) **[BLOCK]** |
 
 ### AI ticket-artifact generators — ticket backend + VCS + code index
 
@@ -323,7 +324,7 @@ wanting both selects `sfcc,sfcc-write` (or `full`).
 | Integration | BLOCK without it | DEGRADE without it |
 |---|---|---|
 | **Ticket backend** (jira mode) | `create_ticket`, `get_ticket(s)`, `update_ticket_description`, `update_jira_status`, and every AI generator (they read the ticket) | — |
-| **Jira (only)** | `get_comments`, `add_comment`, `attachment`, `estimate_epic` | — |
+| **Jira (only)** | `get_comments`, `add_comment`, `attachment`, `publish_reviewed_attachment`, `estimate_epic` | — |
 | **Version control (VCS)** | `create_pull_request`, `merge_pull_request`, `resolve_ci_checks`, `poll_ci_checks`, `wait_for_ci_checks`, `fresh_base`, `parse_repository`, `regenerate_directory_map`; **Tier-3** `request_plan_generation`/`get_plan`, `request_reimplement_context`/`get_reimplement_context`, `create_doc`(tdd/architecture) | **Tier-4** `request_ticket_review`, `create_doc`(prd/fsd), `clarify_task` |
 | **Code index** (succeeded parse) | Tier-3 plan/reimplement/`create_doc`(tdd/architecture); `request_council` in `technical`/`discovery` modes | Tier-4 review/prd/fsd, `clarify_task` |
 | **SFCC OCAPI** | `check_permissions` + every gated SFCC read and write tool | — |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bridge_gpt/mcp-server",
-  "version": "0.2.58",
+  "version": "0.2.60",
   "description": "Bridge API MCP server — exposes Jira endpoints as MCP tools for Claude Code agents",
   "license": "MIT",
   "type": "module",
@@ -26,7 +26,7 @@
   "//test": "The `test` script delegates to the bounded launcher (scripts/run-unit-tests.js → src/run-unit-tests-launcher.ts, BAPI-683), which discovers build/*.test.js at runtime and spawns them in size-bounded batches so the argv never exceeds Windows' ~8191-char command-line limit. Two determinism rules from the pre-launcher script are preserved INSIDE the launcher: (1) multi-file batches run WITHOUT --test-force-exit, because that flag makes node:test exit before aggregating per-subprocess summaries and the tally becomes nondeterministic (failures still surface and still set exit 1, but the count cannot be trusted as a completeness signal); (2) build/secret-safety.test.js leaks a handle that holds the event loop ~60s after its tests finish (they run in ~147ms), so the launcher quarantines it into its own single-file --test-force-exit invocation (FORCE_EXIT_QUARANTINE in src/run-unit-tests-launcher.ts) where the tally stays exact. Do NOT add --test-force-exit to batched invocations, and do NOT remove the quarantine, until the underlying handle leak is fixed.",
   "//version": "BAPI-930: fired by `npm version <level>` AFTER npm rewrites package.json's version field, so the bumped version and the repinned README land in the SAME commit. A bump performed by hand-editing package.json instead of running `npm version` bypasses this hook entirely and must repin manually via `node scripts/sync-readme-host-examples.js` — the `--check` wired into `build` below is the backstop that catches that case.",
   "scripts": {
-    "build": "node scripts/bundle-version.js && node scripts/sync-readme-host-examples.js --check && node scripts/validate-packaged-command-references.js && node scripts/bundle-readme.js && node scripts/bundle-pipelines.js && node scripts/bundle-commands.js && node scripts/bundle-agents.js && node scripts/bundle-docs.js && node scripts/bundle-agent-guidance.js && tsc && node scripts/sync-agent-mirrors.js && node scripts/bundle-esbuild.js",
+    "build": "node scripts/bundle-version.js && node scripts/sync-readme-host-examples.js --check && node scripts/validate-packaged-command-references.js && node scripts/bundle-readme.js && node scripts/bundle-pipelines.js && node scripts/bundle-commands.js && node scripts/bundle-agents.js && node scripts/bundle-docs.js && node scripts/bundle-agent-guidance.js && tsc && node scripts/sync-readme-merge-workflow.js --check && node scripts/sync-agent-mirrors.js && node scripts/bundle-esbuild.js",
     "version": "node scripts/sync-readme-host-examples.js --write && git add -- README.md package.json package-lock.json && git commit -m \"chore(mcp-server): release $npm_package_version\" && git tag \"mcp-server/v$npm_package_version\"",
     "check:version-generated": "node scripts/bundle-version.js && node scripts/check-version-generated.js",
     "assert:release-identity": "node scripts/assert-release-identity.js",
@@ -47,11 +47,11 @@
     "zod": "^4.4.3"
   },
   "optionalDependencies": {
-    "better-sqlite3": "^12.11.1",
+    "better-sqlite3": "^13.0.3",
     "playwright": "^1.51.1"
   },
   "devDependencies": {
-    "@types/better-sqlite3": "^7.6.12",
+    "@types/better-sqlite3": "^9.6.0",
     "@types/node": "^26.0.1",
     "@types/pngjs": "^6.0.5",
     "esbuild": "^0.28.1",

package/pipelines/implement-ticket.json

@@ -18,7 +18,7 @@
         "save_locally": true,
         "provider": "{provider}"
       },
-      "description": "Submit implementation-plan generation without waiting through an MCP client deadline. Re-entry-safe: the backend reuses a fresh existing plan (reused: true, no new run). force is reserved for deliberate regeneration; this step never sets it. On a dropped connection or other ambiguous submission outcome, use get_plan to inspect the existing run — never reissue this step automatically."
+      "description": "Submit implementation-plan generation without waiting through an MCP client deadline. The next step keeps polling get_plan through normal pending windows without an operator decision, including in auto mode. Re-entry-safe: the backend reuses a fresh existing plan (reused: true, no new run). force is reserved for deliberate regeneration; this step never sets it. On a dropped connection or other ambiguous submission outcome, use get_plan to inspect the existing run — never reissue this step automatically."
     },
     {
       "type": "agent_task",

package/pipelines/plan-epic.json

@@ -47,8 +47,8 @@
     },
     {
       "type": "agent_task",
-      "instruction_file": "assess-conductor-eligibility.md",
-      "description": "Assessing conductor eligibility"
+      "instruction_file": "assess-epic-implementer-eligibility.md",
+      "description": "Assessing Epic Implementer eligibility"
     },
     {
       "type": "agent_task",