@bridge_gpt/mcp-server 0.2.53 → 0.2.55

package/build/plane/types.js

@@ -43,8 +43,17 @@
  * but it makes the failure legible ("schema version is not supported" instead
  * of what reads like a corrupt file), and it pairs with the member-scoped
  * rejection in `manifest.ts` so the next member added never reproduces it.
+ *
+ * Bumped to 3 by BAPI-1102, which added the two-phase `lifecycle` field and the
+ * `laneScope` a phase-two request carries. Same reasoning, now for the RECORD
+ * shape rather than the member set: `parsePlaneManifest` rejects an unsupported
+ * top-level key outright, so a v3 manifest read by a v2 binary would be rejected
+ * as "unsupported field 'lifecycle'" — a message about a field, for what is
+ * really a version gap. Reading v1 and v2 stays supported and a manifest without
+ * `lifecycle` is interpreted as a fully-up single-phase plane, which is exactly
+ * what an older build wrote.
  */
-export const PLANE_MANIFEST_SCHEMA_VERSION = 2;
+export const PLANE_MANIFEST_SCHEMA_VERSION = 3;
 /**
  * Every schema version this build can READ.
  *
@@ -54,7 +63,7 @@ export const PLANE_MANIFEST_SCHEMA_VERSION = 2;
  * legible, inflicted from the other side. Accepting 1 costs nothing: the two
  * versions differ only in whether `observer` may appear among the members.
  */
-export const PLANE_MANIFEST_SUPPORTED_SCHEMA_VERSIONS = [1, 2];
+export const PLANE_MANIFEST_SUPPORTED_SCHEMA_VERSIONS = [1, 2, 3];
 /** Runtime artifact directory, relative to the repository root. */
 export const PLANE_RUNTIME_DIR = ".bridge/plane";
 /** Manifest filename inside {@link PLANE_RUNTIME_DIR}. */
@@ -200,3 +209,17 @@ export const PLANE_HEARTBEAT_HEALTH_STATES = [
     "never_seen",
     "unknown",
 ];
+/**
+ * Every lifecycle phase, in occurrence order, with the one terminal failure
+ * phase last. Order carries no meaning to the transition guard — which is
+ * expected/next, never "forward only" — so `lanes-failed` sitting after `ready`
+ * says it is not part of the progression, not that it follows readiness.
+ */
+export const PLANE_LIFECYCLE_PHASES = [
+    "control-plane-starting",
+    "control-plane-ready",
+    "lanes-starting",
+    "lanes-ready",
+    "ready",
+    "lanes-failed",
+];

package/build/polling-policy.js

@@ -0,0 +1,72 @@
+/**
+ * The ONE polling policy shared by every wait in this process (BAPI-1104, R77).
+ *
+ * `pollForResult` in `index.ts` has carried these numbers since BAPI-659, and the
+ * bounded-wait primitive added by this ticket needs the same tolerance for the
+ * same reasons. Two independent copies would drift the moment either is tuned,
+ * and the drift would be invisible: one wait would give up on a transient outage
+ * the other rode out, and nothing would report the disagreement. So the values
+ * live here once and both callers import them.
+ *
+ * Nothing in this module holds mutable state. A policy that could be reconfigured
+ * at runtime is a policy two callers can observe differently, which is precisely
+ * the property this extraction exists to remove.
+ */
+/**
+ * Bound on CONSECUTIVE transport (fetch/header) failures before a poll loop
+ * gives up recoverably. Independent of the deadline and of the polling
+ * intervals — a single resolved response resets the counter to zero.
+ *
+ * Moved here verbatim from `index.ts` (BAPI-659). The value is unchanged.
+ */
+export const MAX_CONSECUTIVE_POLL_FAILURES = 3;
+/**
+ * The default first-poll delay used when a caller supplies no schedule.
+ *
+ * `pollForResult` waits before its FIRST request, not after it — an artifact is
+ * never ready the instant a generation is submitted, and an immediate probe only
+ * spends a request to learn that.
+ */
+export const DEFAULT_INITIAL_POLL_DELAY_MS = 15_000;
+/**
+ * The steady-state delay `pollForResult` backs off to once a poll has been
+ * running for longer than {@link POLL_BACKOFF_AFTER_MS}.
+ */
+export const DEFAULT_STEADY_POLL_DELAY_MS = 30_000;
+/**
+ * Elapsed time after which the default (schedule-free) cadence backs off from
+ * {@link DEFAULT_INITIAL_POLL_DELAY_MS} to {@link DEFAULT_STEADY_POLL_DELAY_MS}.
+ */
+export const POLL_BACKOFF_AFTER_MS = 60_000;
+/**
+ * The delay before the next poll under the DEFAULT (schedule-free) cadence.
+ *
+ * This is the exact rule `pollForResult` applied inline before this module
+ * existed: 15s until a minute has elapsed, 30s thereafter. Expressed as a pure
+ * function of elapsed time so the bounded-wait primitive can apply the identical
+ * curve without re-deriving it, and so a test can assert the curve directly.
+ */
+export function defaultPollDelayMs(elapsedMs) {
+    return elapsedMs > POLL_BACKOFF_AFTER_MS
+        ? DEFAULT_STEADY_POLL_DELAY_MS
+        : DEFAULT_INITIAL_POLL_DELAY_MS;
+}
+/**
+ * Ceiling on a SINGLE probe request, before it is treated as a transport failure.
+ *
+ * Deliberately far shorter than the 240-second bounded window (see
+ * `bounded-wait.ts`): a probe that hangs must not eat the whole window, because a
+ * window that produced no observation at all is indistinguishable to the caller
+ * from one that observed "still pending" — and the second is a fact while the
+ * first is a stall. Each call additionally clamps this to the time actually
+ * remaining, so the ceiling can never overshoot the deadline.
+ */
+export const MAX_PROBE_TIMEOUT_MS = 30_000;
+/**
+ * Bounded jitter applied on top of the backoff delay, in milliseconds.
+ *
+ * Exists so several waiting workers do not synchronize onto the same probe
+ * instants after a shared upstream blip. Small relative to the delays above: the
+ * point is to break lockstep, not to reshape the cadence.
+ */
+export const MAX_POLL_JITTER_MS = 1_000;

package/build/readiness-check.js

@@ -2,7 +2,7 @@
  * The canonical shared readiness-check contract (BAPI-1055, AC-6).
  *
  * Conductor prerequisite probing is spread across five loci — `bridge doctor`
- * ({@link file:./install-doctor.ts}), `conductor doctor`
+ * ({@link file:./install-doctor.ts}), `epic-implementer doctor`
  * ({@link file:./conductor/doctor.ts}), `plane` preflight
  * ({@link file:./plane/preflight.ts}), the server `conductor-readiness`
  * collector, and the unified install doctor
@@ -277,7 +277,7 @@ export function createReadinessCheck(input) {
 /** Fixed prose for a check that had to be replaced because it was malformed. */
 export const READINESS_MALFORMED_CHECK_DETAIL = "this prerequisite reported a result that failed the readiness contract, so its real state is unknown";
 /** Fixed remediation for a replaced malformed check. */
-export const READINESS_MALFORMED_CHECK_REMEDIATION = "re-run `conductor readiness`; if it persists, run `conductor doctor` and `install conductor` to re-collect this locus.";
+export const READINESS_MALFORMED_CHECK_REMEDIATION = "re-run `epic-implementer readiness`; if it persists, run `epic-implementer doctor` and `install conductor` to re-collect this locus.";
 /** Fixed label for a replaced malformed check. */
 export const READINESS_MALFORMED_CHECK_LABEL = "Unreadable prerequisite";
 /**
@@ -330,7 +330,7 @@ export function summarizeReadinessChecks(checks) {
 /** Fixed stand-in for a source detail that failed the secret-safety contract. */
 export const READINESS_UNSAFE_DETAIL_REPLACEMENT = "detail withheld — the source reported it in a form this report may not carry";
 /** Fixed stand-in for a source remediation that failed the secret-safety contract. */
-export const READINESS_UNSAFE_REMEDIATION_REPLACEMENT = "re-run `conductor readiness`; this prerequisite's own fix text could not be carried into this report safely.";
+export const READINESS_UNSAFE_REMEDIATION_REPLACEMENT = "re-run `epic-implementer readiness`; this prerequisite's own fix text could not be carried into this report safely.";
 /**
  * Build a check, degrading REJECTED prose rather than losing the finding — and
  * never throwing.