@bridge_gpt/mcp-server 0.2.42 → 0.2.43
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +321 -182
- package/build/agents.generated.js +2 -2
- package/build/claude-review-workflow.js +510 -45
- package/build/commands.generated.js +4 -3
- package/build/conduct-epic/cli.js +195 -0
- package/build/conductor/bridge-api-client.js +121 -0
- package/build/conductor/cli.js +63 -0
- package/build/conductor/recovery-cli.js +313 -0
- package/build/conductor/recovery-operations.js +219 -0
- package/build/conductor-bin.js +9 -5
- package/build/docs.generated.js +2 -1
- package/build/doctor.js +13 -3
- package/build/drive-epic.js +375 -0
- package/build/executor/http-client.js +71 -3
- package/build/executor/job-errors.js +9 -0
- package/build/executor/job-runner.js +50 -3
- package/build/executor/observation.js +105 -13
- package/build/executor/runner.js +219 -0
- package/build/executor/worker-finalization.js +233 -56
- package/build/executor/worktree.js +8 -1
- package/build/index.js +2156 -98
- package/build/install-bridge.js +23 -9
- package/build/pipelines.generated.js +304 -14
- package/build/plane/cli.js +73 -7
- package/build/plane/defaults.js +14 -4
- package/build/plane/manifest.js +90 -0
- package/build/plane/preflight.js +19 -0
- package/build/plane/shutdown.js +71 -3
- package/build/readme.generated.js +1 -1
- package/build/run-unit-tests-launcher.js +75 -5
- package/build/setup-epic.js +82 -8
- package/build/version.generated.js +2 -1
- package/build/worktree-core.js +31 -17
- package/package.json +1 -1
- package/pipelines/greenfield-setup.json +286 -0
package/build/install-bridge.js
CHANGED
|
@@ -206,7 +206,10 @@ export function buildPrewarmCommandPreview() {
|
|
|
206
206
|
}
|
|
207
207
|
/**
|
|
208
208
|
* The natural-language prompt handed to the spawned agent session. It is
|
|
209
|
-
* CONFIGURE-ONLY: it derives and applies configuration,
|
|
209
|
+
* CONFIGURE-ONLY: it derives and applies configuration (or, on the greenfield
|
|
210
|
+
* path BAPI-855 added, delegates that work wholesale to the packaged
|
|
211
|
+
* `greenfield-setup` recipe — this prompt describes the handoff in one sentence
|
|
212
|
+
* and deliberately embeds no recipe orchestration of its own), presents the concise
|
|
210
213
|
* capability report — the availability-framed 'Available now' / 'Needs setup'
|
|
211
214
|
* pair the server authors (BAPI-719), rendered verbatim with zero local
|
|
212
215
|
* curation — and closes with the server-provided `next_step.command`
|
|
@@ -220,11 +223,16 @@ export function buildPrewarmCommandPreview() {
|
|
|
220
223
|
*/
|
|
221
224
|
export const INSTALL_BRIDGE_AGENT_PROMPT = "Execute the /install-bridge command in the install-spawn context (tell the command it is running " +
|
|
222
225
|
"in the install-spawn context so it SKIPS its Stage 8, Stage 9, and Stage 10 offers). " +
|
|
223
|
-
"The command
|
|
224
|
-
"
|
|
225
|
-
"
|
|
226
|
-
"
|
|
227
|
-
"
|
|
226
|
+
"The command owns its own Stage 2 decision and evaluates it in a fixed order from the install " +
|
|
227
|
+
"manifest — do NOT force an outcome. `configured == true` is JOIN MODE; otherwise a manifest whose " +
|
|
228
|
+
"`greenfield_setup_path` field is already set is GREENFIELD REPORT-ONLY; otherwise the command's " +
|
|
229
|
+
"Stage 2b classifies the repository as greenfield or established. In JOIN MODE and in GREENFIELD " +
|
|
230
|
+
"REPORT-ONLY the command must NOT derive, approve, apply, or offer any configuration and applies " +
|
|
231
|
+
"zero fields for any caller; the closing interaction is the welcome plus the concise capability " +
|
|
232
|
+
"report. An established classification runs the ordinary fresh-configuration flow unchanged. " +
|
|
233
|
+
"A greenfield classification hands off to the packaged `greenfield-setup` recipe — the command " +
|
|
234
|
+
"fetches it with get_pipeline_recipe and completes every returned step in THIS same session, then " +
|
|
235
|
+
"resumes /install-bridge reporting from the recipe's own read-after-write manifest. " +
|
|
228
236
|
"Complete the command's concise capability report: the single 'What Bridge " +
|
|
229
237
|
"can help with' section, rendered exactly as the server's concise_tool_capabilities field gives it. " +
|
|
230
238
|
"That field is exactly two availability sections in server order — 'Available now' first, then " +
|
|
@@ -259,8 +267,10 @@ export const INSTALL_BRIDGE_AGENT_PROMPT = "Execute the /install-bridge command
|
|
|
259
267
|
"funnel with no visibility from this session, so say nothing about it at all. " +
|
|
260
268
|
"Close with the server's own next step, which you must read at runtime rather than assume. Inspect " +
|
|
261
269
|
"the `next_step` object on the manifest response the flow already used: on the fresh-configuration " +
|
|
262
|
-
"path that is the Stage 7 post-apply read-after-write manifest
|
|
263
|
-
"
|
|
270
|
+
"path that is the Stage 7 post-apply read-after-write manifest; after a greenfield handoff it is " +
|
|
271
|
+
"the read-after-write manifest the greenfield-setup recipe returned; and in JOIN MODE and " +
|
|
272
|
+
"GREENFIELD REPORT-ONLY it is the Stage 2 manifest (neither performs a read-after-write). Look at " +
|
|
273
|
+
"`next_step.command`: when it is a " +
|
|
264
274
|
"NON-EMPTY string, recommend exactly that command, verbatim, in inline code — do not rename it or " +
|
|
265
275
|
"substitute a command you happen to know. When it is an empty string, make NO next-command " +
|
|
266
276
|
"recommendation at all and say nothing in its place: no heading, no placeholder, no 'nothing to " +
|
|
@@ -278,7 +288,11 @@ export const INSTALL_BRIDGE_AGENT_PROMPT = "Execute the /install-bridge command
|
|
|
278
288
|
"the apply_install_manifest call " +
|
|
279
289
|
"applied (e.g. 'Applied 8 of 9 derived fields') — if 0 fields were applied, say so loudly and " +
|
|
280
290
|
"explain what is still pending. In JOIN MODE there is no apply — state instead that the project " +
|
|
281
|
-
"was already configured and zero changes were made, without a fabricated applied count."
|
|
291
|
+
"was already configured and zero changes were made, without a fabricated applied count. The two " +
|
|
292
|
+
"greenfield paths report the same way: GREENFIELD REPORT-ONLY states that greenfield setup was " +
|
|
293
|
+
"already completed and that zero changes were made, and a completed greenfield handoff states " +
|
|
294
|
+
"which setup path the recipe recorded — the recipe made the only apply, so neither path invents an " +
|
|
295
|
+
"applied count or apply buckets of its own.";
|
|
282
296
|
/** Default base URL when `BAPI_BASE_URL` is unset (mirrors index.ts). */
|
|
283
297
|
export const DEFAULT_BAPI_BASE_URL = "https://bridgegpt-api.com";
|
|
284
298
|
/**
|