@bridge_gpt/mcp-server 0.2.53 → 0.2.55

package/build/plane/status.js

@@ -6,7 +6,7 @@
  * a hole in the roster (a member that crashed and was deliberately not
  * restarted) is precisely what this command exists to *show*.
  */
-import { probeManifestMembers, readPlaneManifest, } from "./manifest.js";
+import { planeManifestLifecycle, probeManifestMembers, readPlaneManifest, } from "./manifest.js";
 import { PLANE_RUNTIME_DIR, PLANE_RUNTIME_LOG_PATH, } from "./types.js";
 /** Read the manifest and probe every recorded pid. Strictly read-only. */
 export async function getPlaneStatus(repoRoot, deps) {
@@ -32,6 +32,8 @@ export async function getPlaneStatus(repoRoot, deps) {
         supervisorPgid: manifest.supervisorPgid,
         supervisorLiveness: deps.proc.isAlive(manifest.supervisorPid),
         unrecognizedMemberNames: read.unrecognizedMemberNames,
+        lifecycle: planeManifestLifecycle(manifest),
+        epicRunId: manifest.epicRunId ?? null,
         createdAt: manifest.createdAt,
         updatedAt: manifest.updatedAt,
         members: probeManifestMembers(manifest, deps.proc).map((probe) => ({
@@ -45,6 +47,36 @@ export async function getPlaneStatus(repoRoot, deps) {
         })),
     };
 }
+/**
+ * The lifecycle phase, in operational terms rather than as a bare enum value.
+ *
+ * Each line says what has happened AND what is being waited for, because the
+ * intermediate phases are the ones an operator sees when something is wrong and
+ * "lanes-starting" alone does not say whether that is normal.
+ *
+ * `ready` deliberately does NOT claim the run is dispatchable. A plane can be
+ * fully up while the reconciler still holds dispatch — feature-branch index
+ * preparation is the common case — and a status line that conflated "every
+ * process is up" with "work is flowing" would send an operator hunting for a
+ * problem in the plane that is not there.
+ */
+function describeLifecycle(phase) {
+    switch (phase) {
+        case "control-plane-starting":
+            return "control plane starting (server, reconciler)";
+        case "control-plane-ready":
+            return "control plane ready — waiting for a scoped executor-lane request";
+        case "lanes-starting":
+            return "executor lanes starting — each waits for its own heartbeat gate";
+        case "lanes-ready":
+            return "executor lanes ready — starting the dead-man observer";
+        case "ready":
+            return "plane ready (this reports PROCESSES, not whether the run is dispatchable)";
+        case "lanes-failed":
+            return ("executor lanes FAILED — the lane cohort was stopped and the control plane was " +
+                "left running; nothing is claiming jobs. Wind it down with `plane down`.");
+    }
+}
 /** One line per member: name, state, exit status where known, log path. */
 export function formatPlaneStatus(result) {
     if (!result.ok)
@@ -55,6 +87,8 @@ export function formatPlaneStatus(result) {
     const lines = [
         `Plane ${result.planeId}`,
         `  supervisor   pid ${result.supervisorPid} (group ${result.supervisorPgid}) — ${result.supervisorLiveness}`,
+        `  lifecycle    ${describeLifecycle(result.lifecycle)}`,
+        ...(result.epicRunId !== null ? [`  epic run     ${result.epicRunId}`] : []),
         `  started      ${result.createdAt}`,
         `  updated      ${result.updatedAt}`,
         "",