@bridge_gpt/mcp-server 0.2.69 → 0.2.70

package/build/conductor/readiness.js

@@ -1,3 +1,4 @@
+import { mergeReadinessPrerequisites, formatReadinessPrerequisites } from "./readiness-prerequisites.js";
 /**
  * The consolidated ADVISORY epic-implementer readiness gate (BAPI-1055, AC-6/AC-7).
  *
@@ -28,7 +29,8 @@
  * are all failures, not passes.
  *
  * **Containment.** The authoritative refusals are unchanged and live elsewhere:
- * `V2_READINESS_REQUIREMENTS` in `drive-epic.ts` remains the SOLE hard
+ * `V2_READINESS_REQUIREMENTS` (declared in `v2-readiness-requirements.ts` since
+ * BAPI-1452 and consumed by `drive-epic.ts`) remains the SOLE hard
  * route-selection predicate, and the server-side admission (A1b.1/A1b.2) remains
  * the sole hard refusal. `plane up`'s own blocking preflight still refuses a
  * bring-up on its own terms. This gate contributes to none of those decisions:
@@ -61,7 +63,8 @@
  *
  * **What replaced it.** BAPI-1136 de-personalized the merge: it now authenticates
  * with one explicitly configured, customer-held credential
- * (`BAPI_LOCAL_MERGE_TOKEN` or `BAPI_MACHINE_MERGE_TOKEN`) and never with the
+ * (`GITHUB_MERGE_TOKEN` — BAPI-1452's canonical local key, formerly
+ * `BAPI_LOCAL_MERGE_TOKEN` — or `BAPI_MACHINE_MERGE_TOKEN`) and never with the
  * ambient session. So the second check was RE-POINTED, not removed —
  * `conductor.gh-cli` still asks whether `gh` exists, and
  * `conductor.merge-credential` asks whether a credential is configured. Removing
@@ -92,17 +95,22 @@
  * unrelated additive change look like a breaking one here, or worse, hide a real
  * one.
  */
-import { PRINTED_CHECK_NAME_INSTRUCTION, PRINTED_CONDUCTOR_EXECUTOR_INSTALL_COMMAND, PRINTED_CONDUCTOR_INSTALL_COMMAND, PRINTED_CONNECT_GITHUB_COMMAND, PRINTED_EXECUTOR_ID_INSTRUCTION, PRINTED_QUALIFY_GATE_COMMAND, } from "../printed-remedy-commands.js";
+import { CONSUMER_GUIDE_POINTER, PRINTED_CHECK_NAME_INSTRUCTION, PRINTED_CONDUCTOR_EXECUTOR_INSTALL_COMMAND, PRINTED_CONDUCTOR_INSTALL_COMMAND, PRINTED_CONNECT_GITHUB_COMMAND, PRINTED_EXECUTOR_ID_INSTRUCTION, PRINTED_QUALIFY_GATE_COMMAND, } from "../printed-remedy-commands.js";
 import { mapConductorDoctorReportToReadinessChecks, } from "./doctor.js";
 import { mapInstallStatusChecksToReadinessChecks, } from "../install-doctor.js";
 import { mapPlanePreflightToReadinessChecks, } from "../plane/preflight.js";
 import { runConductorInstallDoctor, } from "./install-doctor.js";
 import { BRING_UP_SECTION_LABELS, describeGateProfile, describeGateProfileWarning, effectiveReviewModeIsRepositoryPolicy, EPIC_BRANCH_CI_SECTION_IDS, epicBranchCiSections, presentRequiredChecks, quotedSubject, } from "./readiness-sections.js";
 import { classifyBringUpFacts } from "./bring-up-facts.js";
+import { projectReadinessRowBlocking, providerRepositoryCheck, resolvedMergeModeCheck, } from "../v2-readiness-requirements.js";
 import { CI_WORKFLOW_PATH, REVIEW_WORKFLOW_PATH, ciWorkflowRemedy, repositoryWorkflowRemedy, } from "./repository-workflow-remedy.js";
 import { classifyMergeExecutionEligibility, MERGE_EXECUTION_INELIGIBLE_REMEDIATION, MERGE_EXECUTION_UNVERIFIABLE_REMEDIATION, } from "./merge-execution-eligibility.js";
 import { createReadinessCheck, createReadinessCheckSafely, summarizeReadinessChecks, validateReadinessChecks, } from "../readiness-check.js";
 import { ADMISSION_EVIDENCE_SCHEMA_VERSION, gateProfileWaivesCiWorkflow, } from "./bridge-api-client.js";
+import { ESCALATION_REACHABILITY_REMEDY, emailTransportDetailForChannel, isFailedEmailTransportDiagnostic, resolveEffectiveEscalationChannel, } from "../escalation-reachability.js";
+// BAPI-1490 — the reachability row lives in a neutral module so drive-epic can build it
+// without referencing this gate; it is re-exported here for gate consumers.
+export { ESCALATION_REACHABILITY_CHECK_ID, buildEscalationReachabilityCheck, } from "../escalation-reachability.js";
 /** This report's own schema version. See the module docstring. */
 export const CONDUCTOR_READINESS_GATE_SCHEMA_VERSION = 1;
 /** Fixed statement carried in every report, so no consumer can mistake it for a gate. */
@@ -115,11 +123,18 @@ export const CONDUCTOR_READINESS_ADVISORY_NOTICE = "Advisory only. This report n
 // ---------------------------------------------------------------------------
 /** The complete server-side prerequisite set, in render order. */
 export const SERVER_READINESS_DESCRIPTORS = [
+    // BAPI-1452 — the launch summary order: the Setup-page unattended posture
+    // first, then the supporting merge facts. The hard-coded `auto-merge` and
+    // `merge-approval` rows are RETIRED: an unattended run's own merges are
+    // authorized by the run and this one switch, not by the legacy repository
+    // merge flags, so reporting those flags here described a decision they no
+    // longer make.
+    { id: "unattended-posture", label: "Unattended posture (Setup page)" },
+    { id: "resolved-merge-mode", label: "Resolved merge mode" },
+    { id: "provider-repository", label: "Provider repository" },
     { id: "supervisor-setup", label: "Supervisor setup" },
     { id: "supervisor-config", label: "Supervisor configuration" },
     { id: "supervisor-required-checks", label: "Supervisor required CI checks" },
-    { id: "auto-merge", label: "Auto-merge posture" },
-    { id: "merge-approval", label: "Merge approval configuration" },
     { id: "review-policy", label: "Review policy" },
     { id: "github-credentials", label: "GitHub App credentials" },
     { id: "github-actions-permission", label: "GitHub App actions permission" },
@@ -149,7 +164,6 @@ export const SERVER_READINESS_DESCRIPTORS = [
     // BAPI-1102 — the two unattended repository prerequisites plus the aggregate the
     // third unattended refusal reads. Noun phrases, like every row above: these
     // render as list items under a source heading, not as sentences.
-    { id: "unattended-consent", label: "Repository unattended consent" },
     { id: "unattended-notify-default", label: "Escalation channel (webhook or email)" },
     { id: "repository-workflow-readiness", label: "Repository workflow readiness" },
 ];
@@ -176,33 +190,32 @@ const SERVER_FAILURE_COPY = {
 const SERVER_REMEDIATIONS = {
     supervisorSetup: `run \`${PRINTED_CONDUCTOR_INSTALL_COMMAND}\` (or \`setup-epic\`) for this repository to write the project-default supervisor posture. ${PRINTED_CHECK_NAME_INSTRUCTION}`,
     supervisorConfig: `run \`${PRINTED_CONDUCTOR_INSTALL_COMMAND}\` for this repository to write the project-default supervisor configuration. ${PRINTED_CHECK_NAME_INSTRUCTION}`,
-    mergeApproval: "set the merge-approval requirement explicitly in the supervisor configuration rather than leaving it unset.",
     reviewPolicyMissing: "set the repository review-policy default so the merge path and the code_review gate read the same signal.",
     reviewPolicyDivergent: "align the repository review-policy default with the done gate's review_state condition, or confirm the difference is intended.",
     githubCredentials: `connect GitHub from the Bridge setup UI or run \`${PRINTED_CONNECT_GITHUB_COMMAND}\` so owner, repository id, and installation id all resolve.`,
     actionsProbeFailed: "re-run once credentials resolve; the permission could not be checked, which is not the same as confirmed-missing.",
-    actionsMissing: "grant the GitHub App `actions: write`; without it the conductor's workflow rerun lane fails open on 403.",
+    actionsMissing: "grant the GitHub App `actions: write`; without it the workflow rerun lane fails open on 403.",
     reconcilerUnreadable: "retry once the Bridge API is reachable; reconciler liveness is unknown here, not confirmed stale.",
     // BAPI-1360: the frozen `epic-tick` command is never named. The reconciler runs
     // inside the worker, so the first check is that the worker is up, then the run's
     // own status.
     reconcilerStale: "check the worker first (`server.worker-present`), then inspect the stalled run with `epic-implementer epic-status`.",
     executorUnreadable: "retry once the Bridge API is reachable; no executor readiness claim is ever made from local state.",
-    executorNeverSeen: `provision and start an executor (\`${PRINTED_CONDUCTOR_EXECUTOR_INSTALL_COMMAND}\` or \`executor install-service\`); readiness comes only from a live server observation. ${PRINTED_CHECK_NAME_INSTRUCTION} ${PRINTED_EXECUTOR_ID_INSTRUCTION}`,
-    executorNoneObservedNoRuns: `no action is needed to launch: \`drive-epic\` starts a run-scoped executor. To keep an executor running between runs, install one with \`${PRINTED_CONDUCTOR_EXECUTOR_INSTALL_COMMAND}\` or \`executor install-service\`. ${PRINTED_CHECK_NAME_INSTRUCTION} ${PRINTED_EXECUTOR_ID_INSTRUCTION}`,
-    executorStale: "restart the executor service; it was observed once and has gone quiet past the server's staleness threshold.",
-    reviewWorkflowUnknown: "re-run; the default branch's review workflow could not be evaluated, which is not the same as it being absent.",
-    reviewWorkflowIncomplete: "install the claude-review workflow template on the default branch so it emits both the run id and the reviewed SHA the verdict protocol reads.",
-    ciWorkflowUnknown: "re-run; the default branch's conductor CI workflow could not be evaluated, which is not the same as the guard being absent.",
+    executorNeverSeen: `provision and start an executor (\`${PRINTED_CONDUCTOR_EXECUTOR_INSTALL_COMMAND}\` or \`executor install-service\`); readiness comes only from a live server observation. ${PRINTED_CHECK_NAME_INSTRUCTION} ${PRINTED_EXECUTOR_ID_INSTRUCTION} See ${CONSUMER_GUIDE_POINTER}.`,
+    executorNoneObservedNoRuns: `no action is needed to launch: \`drive-epic\` starts a run-scoped executor. To keep an executor running between runs, install one with \`${PRINTED_CONDUCTOR_EXECUTOR_INSTALL_COMMAND}\` or \`executor install-service\`. ${PRINTED_CHECK_NAME_INSTRUCTION} ${PRINTED_EXECUTOR_ID_INSTRUCTION} See ${CONSUMER_GUIDE_POINTER}.`,
+    executorStale: `restart the executor service; it was observed once and has gone quiet past the server's staleness threshold. See ${CONSUMER_GUIDE_POINTER}.`,
+    reviewWorkflowUnknown: `re-run; the default branch's review workflow could not be evaluated, which is not the same as it being absent (see ${CONSUMER_GUIDE_POINTER}).`,
+    reviewWorkflowIncomplete: `install the claude-review workflow template on the default branch so it emits both the run id and the reviewed SHA the verdict protocol reads (see ${CONSUMER_GUIDE_POINTER}).`,
+    ciWorkflowUnknown: `re-run; the default branch's Epic Implementer CI workflow could not be evaluated, which is not the same as the guard being absent (see ${CONSUMER_GUIDE_POINTER}).`,
     // BAPI-1359: the missing-guard remedy is built by `ciWorkflowRemedy` (the shared
     // formatter), because its wording depends on WHY the guard is missing — a
     // confirmed Alembic chain, an older server, or an unreadable answer.
-    olderServer: "upgrade the Bridge API deploy so it reports this fact; its state is unknown here, not healthy.",
+    olderServer: "retry later; the server did not report this fact, so its state is unknown here, not healthy. If it persists, email info@bridgegpt.ai.",
     // BAPI-1102. Each names the ONE action that clears it, and none of them
     // mentions a webhook URL, a destination, or any configuration value.
     // BAPI-1273: consent defaults ON; the repository owner switches it on the
     // admin panel's Setup page. No MCP or CLI surface ever writes it.
-    unattendedConsent: "turn on 'Allow unattended Epic Implementer runs' on the repository's Setup page in the Bridge admin panel, or run setup with --attended. If it is already on, contact Bridge support.",
+    unattendedConsent: "turn on 'Allow unattended Epic Implementer runs' on the repository's Setup page in the Bridge admin panel, or run setup with --attended. If it is already on, email info@bridgegpt.ai.",
     unattendedNotifyDefault: "supply a --policy-file declaring notify.webhook_url, or add an email address to the account so escalation alerts can be emailed, or run setup with --attended; an unattended run must have a working escalation channel, and notify.local_sink is not one.",
     // BAPI-1359: the `repository-workflow-readiness` remedy is built by
     // `repositoryWorkflowRemedy` (the shared formatter) from the SAME report, so it
@@ -221,7 +234,9 @@ const SERVER_REMEDIATIONS = {
  * and its own threshold values are reported as given, and
  * `V2_READINESS_REQUIREMENTS` is neither imported nor duplicated here — two
  * implementations of one classification drift, and this one is advisory while
- * that one decides a route.
+ * that one decides a route. BAPI-1452: the per-row applicability flag comes
+ * from that catalog's shared projection (`projectReadinessRowBlocking`), so this
+ * report repeats the requirements' answer instead of forming its own.
  *
  * Uncertainty is never healthy. `actions_probe_succeeded === false`, an
  * unreadable liveness read, `executor.ready === null`, and a field an older
@@ -233,7 +248,7 @@ const SERVER_REMEDIATIONS = {
  * Passing `null` (with a `failure` kind) yields the full descriptor set as
  * failures, so an unreachable server loses no prerequisite from the report.
  */
-export function mapServerReadinessToChecks(readiness, failure = "unreachable") {
+export function mapServerReadinessToChecks(readiness, failure = "unreachable", callerChannel) {
     if (readiness === null) {
         const copy = SERVER_FAILURE_COPY[failure];
         return SERVER_READINESS_DESCRIPTORS.map(({ id, label }) => createReadinessCheck({
@@ -282,21 +297,17 @@ export function mapServerReadinessToChecks(readiness, failure = "unreachable") {
             ? {}
             : { remediation: requiredChecks.remediation }),
     });
-    // Auto-merge OFF is a posture, not a gap: an operator may deliberately merge
-    // by hand. Reported, never remediated.
-    outcomes.push({
-        id: "auto-merge",
-        status: "pass",
-        detail: s.auto_merge_enabled ? "auto-merge enabled" : "auto-merge disabled (operator posture)",
-    });
-    outcomes.push(s.merge_approval_required_set
-        ? { id: "merge-approval", status: "pass", detail: "merge-approval requirement is set explicitly" }
-        : {
-            id: "merge-approval",
-            status: "warn",
-            detail: "the merge-approval requirement is unset, so the merge path falls back to its default",
-            remediation: SERVER_REMEDIATIONS.mergeApproval,
+    // BAPI-1452 — the retired `auto-merge` / `merge-approval` rows used to sit
+    // here. The supporting merge facts come from the shared builders, so this
+    // report and drive-epic's launch summary word them identically.
+    for (const fact of [resolvedMergeModeCheck(readiness), providerRepositoryCheck(readiness)]) {
+        outcomes.push({
+            id: fact.id.slice("server.".length),
+            status: fact.status,
+            detail: fact.detail ?? fact.label,
+            ...(fact.remediation !== undefined ? { remediation: fact.remediation } : {}),
         });
+    }
     outcomes.push(reviewPolicyOutcome(readiness));
     outcomes.push(g.credentials_complete
         ? {
@@ -359,25 +370,47 @@ export function mapServerReadinessToChecks(readiness, failure = "unreachable") {
     });
     // BAPI-1260 — appended ONLY when the server reported the block, so every
     // pre-BAPI-1260 report keeps exactly the descriptor set above.
+    //
+    // BAPI-1452 — the row flags come from the SHARED requirement projection,
+    // never from this report's own judgement: a row is flagged exactly when an
+    // applicable requirement governs it. This report still decides nothing.
     return [
-        ...described,
+        ...projectReadinessRowBlocking(described),
         ...admissionEvidenceChecks(readiness),
         // BAPI-1390 — appended ONLY when the server reported a gate profile.
         ...gateProfileChecks(readiness),
         // BAPI-1405 — always three warn-only epic-branch CI rows. An older server
-        // that omits the block renders them as "Unreported — upgrade the server",
+        // that omits the block renders them as "Unreported by the server",
         // never as "no warning".
         ...epicBranchCiChecks(readiness),
-        ...genericDiagnosticChecks(readiness),
+        ...genericDiagnosticChecks(readiness, callerChannel),
     ];
 }
-function genericDiagnosticChecks(readiness) {
+function genericDiagnosticChecks(readiness, callerChannel) {
+    // BAPI-1495 — the same resolver the reachability row uses, so both agree.
+    const channel = resolveEffectiveEscalationChannel(readiness, callerChannel);
     return (readiness.diagnostics ?? []).map((diagnostic, index) => {
         const inapplicable = diagnostic.applicability === "inapplicable";
         const declared = diagnostic.severity !== null && diagnostic.applicability !== null;
         const satisfied = declared && diagnostic.verdict === "passed" && diagnostic.applicability === "applicable";
         const advisory = diagnostic.severity === "advisory";
-        const status = !declared ? "fail" : inapplicable ? "skip" : satisfied ? "pass" : advisory ? "warn" : "fail";
+        // BAPI-1490 — a known failed email transport is a warning with fixed copy,
+        // whatever the diagnostic's severity: it reports that no person is told, and
+        // this report never blocks.
+        const transportNotLive = isFailedEmailTransportDiagnostic(diagnostic);
+        const status = transportNotLive
+            ? "warn"
+            : !declared ? "fail" : inapplicable ? "skip" : satisfied ? "pass" : advisory ? "warn" : "fail";
+        if (transportNotLive) {
+            return createReadinessCheckSafely({
+                id: `server.diagnostic-${index + 1}-${diagnostic.id.replace(/[_.]/g, "-")}`,
+                source: "server",
+                label: `Server diagnostic ${diagnostic.id}`,
+                status,
+                detail: emailTransportDetailForChannel(channel),
+                remediation: ESCALATION_REACHABILITY_REMEDY,
+            });
+        }
         return createReadinessCheckSafely({
             id: `server.diagnostic-${index + 1}-${diagnostic.id.replace(/[_.]/g, "-")}`,
             source: "server",
@@ -404,9 +437,9 @@ const ADMISSION_EVIDENCE_LABELS = {
 };
 /** Who acts, in fixed prose. Never a value from the payload. */
 const ADMISSION_OWNER_REMEDIATION = {
-    operator: "the operator re-runs guided setup (`install conductor --launch-profile <name>`) and re-observes.",
+    operator: "the operator re-runs guided setup (`install conductor`) and re-observes.",
     repository_admin: "a repository administrator resolves it (unattended consent is the 'Allow unattended Epic Implementer runs' toggle on the repository's Setup page in the Bridge admin panel); setup never grants it.",
-    bridge_operations: "escalate to Bridge operations; this is not something an operator command can change.",
+    bridge_operations: "email info@bridgegpt.ai; this is not something an operator command can change.",
 };
 /** The retired and current Bridge CI gate names, spelled once for the fixed remedies. */
 const RETIRED_GATE_NAME = "conductor-ci / gate";
@@ -462,11 +495,11 @@ function gateProfileReasonRemedy(reason, verdict, subject) {
         case "provider_evidence_unavailable":
             return (`Bridge could not read the provider's check history for ${quotedSubject(subject, "a gate-profile check")} ` +
                 `(${PROVIDER_EVIDENCE_WINDOW}), so it is unknown, not absent. Re-run readiness; if it persists, ` +
-                "escalate to Bridge operations.");
+                "email info@bridgegpt.ai.");
         case "local_command_unqualified":
             return verdict === "unable_to_verify"
                 ? `the qualification of the local gate command ${quotedSubject(subject, "in the gate profile")} could not ` +
-                    "be read, so it is unknown, not qualified. Re-run readiness; if it persists, escalate to Bridge operations."
+                    "be read, so it is unknown, not qualified. Re-run readiness; if it persists, email info@bridgegpt.ai."
                 : `the local gate command ${quotedSubject(subject, "in the gate profile")} is not qualified for the current ` +
                     "gate-profile revision (unqualified or stale). Qualify it with " +
                     `\`${PRINTED_QUALIFY_GATE_COMMAND}\`, or have a repository administrator ` +
@@ -516,7 +549,7 @@ export function gateProfileChecks(readiness) {
             status: "fail",
             detail: `${profile.read_failed ? "the stored gate profile could not be read" : "the stored gate profile is malformed"} — ${detail}`,
             remediation: profile.read_failed
-                ? "re-run readiness; if it persists, escalate to Bridge operations."
+                ? "re-run readiness; if it persists, email info@bridgegpt.ai."
                 : "a repository administrator re-saves the gate profile; setup never grants it.",
         });
     }
@@ -574,7 +607,7 @@ export function gateProfileChecks(readiness) {
  * these rows never fail, never hold a launch, and feed no verdict.
  *
  * Unlike `gateProfileChecks`, an absent or `null` block (older server) still
- * yields the three rows, each `warn` with "Unreported — upgrade the server" and
+ * yields the three rows, each `warn` with "Unreported by the server" and
  * the upgrade remediation. Emitting nothing would read as "no warning", which
  * is the wrong answer: the server simply did not say. Omitted and `null` render
  * identically. The install doctor's own copies of these sections are filtered
@@ -720,7 +753,7 @@ function unattendedOutcomes(readiness) {
     const u = readiness.unattended;
     if (u === null) {
         return [
-            "unattended-consent",
+            "unattended-posture",
             "unattended-notify-default",
             "repository-workflow-readiness",
         ].map((id) => ({
@@ -733,12 +766,12 @@ function unattendedOutcomes(readiness) {
     return [
         u.conductor_allowed
             ? {
-                id: "unattended-consent",
+                id: "unattended-posture",
                 status: "pass",
                 detail: "this repository has consented to unattended Epic Implementer runs",
             }
             : {
-                id: "unattended-consent",
+                id: "unattended-posture",
                 status: "warn",
                 detail: "unattended runs are off for this repository — an unattended run will be refused before it is created",
                 remediation: SERVER_REMEDIATIONS.unattendedConsent,
@@ -760,7 +793,7 @@ function unattendedOutcomes(readiness) {
                     // reported by the server and is never rendered here.
                     id: "unattended-notify-default",
                     status: "pass",
-                    detail: "No webhook declared; escalation alerts will be emailed to the account's email address",
+                    detail: "No repository webhook default; a run's policy may declare notify.webhook_url, otherwise escalation alerts are emailed to the account's email address",
                 }
                 : {
                     id: "unattended-notify-default",
@@ -1029,7 +1062,7 @@ function reviewWorkflowOutcome(readiness) {
             id: "review-workflow",
             status: "fail",
             detail: "this Bridge API deploy did not report the review-workflow facts",
-            remediation: SERVER_REMEDIATIONS.olderServer,
+            remediation: `${SERVER_REMEDIATIONS.olderServer} See ${CONSUMER_GUIDE_POINTER}.`,
         };
     }
     if (!w.probe_succeeded) {
@@ -1089,7 +1122,7 @@ function ciWorkflowOutcome(readiness) {
             id: "conductor-ci-workflow",
             status: "fail",
             detail: "this Bridge API deploy did not report the epic-implementer-ci workflow facts",
-            remediation: SERVER_REMEDIATIONS.olderServer,
+            remediation: `${SERVER_REMEDIATIONS.olderServer} See ${CONSUMER_GUIDE_POINTER}.`,
         };
     }
     if (!c.probe_succeeded) {
@@ -1097,8 +1130,8 @@ function ciWorkflowOutcome(readiness) {
             id: "conductor-ci-workflow",
             status: "fail",
             detail: c.workflow_present
-                ? "the conductor CI workflow is present but could not be evaluated"
-                : "the conductor CI workflow could not be found or read on the default branch",
+                ? "the Epic Implementer CI workflow is present but could not be evaluated"
+                : "the Epic Implementer CI workflow could not be found or read on the default branch",
             remediation: SERVER_REMEDIATIONS.ciWorkflowUnknown,
         };
     }
@@ -1115,7 +1148,7 @@ function ciWorkflowOutcome(readiness) {
         return {
             id: "conductor-ci-workflow",
             status: "pass",
-            detail: "the default branch's conductor CI workflow runs the migration guard",
+            detail: "the default branch's Epic Implementer CI workflow runs the migration guard",
         };
     }
     // BAPI-1359 — the guard is conditional on an Alembic chain. Three explicit
@@ -1133,7 +1166,7 @@ function ciWorkflowOutcome(readiness) {
         return {
             id: "conductor-ci-workflow",
             status: "fail",
-            detail: "the Alembic check could not be read, so it is not known whether the conductor CI workflow needs the migration guard",
+            detail: "the Alembic check could not be read, so it is not known whether the Epic Implementer CI workflow needs the migration guard",
             remediation: ciWorkflowRemedy(c),
         };
     }
@@ -1141,10 +1174,10 @@ function ciWorkflowOutcome(readiness) {
         id: "conductor-ci-workflow",
         status: "warn",
         detail: c.migration_guard_required === true && c.migration_chain_probe_succeeded === true
-            ? "the conductor CI workflow does not run the migration guard, which this repository requires because it has alembic.ini on its default branch"
+            ? "the Epic Implementer CI workflow does not run the migration guard, which this repository requires because it has alembic.ini on its default branch"
             : // An older server (no new fields) or a partial report: keep today's
                 // wording and today's behavior, and claim nothing about alembic.ini.
-                "the conductor CI workflow does not run the migration guard",
+                "the Epic Implementer CI workflow does not run the migration guard",
         remediation: ciWorkflowRemedy(c),
     };
 }
@@ -1263,7 +1296,7 @@ export async function collectConductorReadinessGate(deps) {
         ...mapPlanePreflightToReadinessChecks(planeResult, deps.planeNotApplicable, {
             ...(deps.epicRunId !== undefined ? { epicRunId: deps.epicRunId } : {}),
         }),
-        ...mapServerReadinessToChecks(installReport?.readiness ?? null, classifyServerFailure(installReport)),
+        ...mapServerReadinessToChecks(installReport?.readiness ?? null, classifyServerFailure(installReport), deps.callerChannel),
     ];
     // Validate the ASSEMBLED report, not just the pieces: an injected collector or
     // a future adapter could hand over an entry that violates the contract, and a
@@ -1276,7 +1309,15 @@ export async function collectConductorReadinessGate(deps) {
         repoName: deps.repoName ?? null,
         unavailableSources,
         checks: validated,
+        prerequisites: mergeReadinessPrerequisites(validated, installReport?.readiness?.prerequisites),
+        is_production: installReport?.readiness?.is_production,
         ...(installReport?.readiness?.diagnostics ? { diagnostics: installReport.readiness.diagnostics } : {}),
+        ...(installReport?.readiness?.escalation_channel !== undefined
+            ? { escalation_channel: installReport.readiness.escalation_channel }
+            : {}),
+        ...(installReport?.readiness?.webhook_last_delivery !== undefined
+            ? { webhook_last_delivery: installReport.readiness.webhook_last_delivery }
+            : {}),
         summary: summarizeReadinessChecks(validated),
     };
 }
@@ -1354,35 +1395,6 @@ function readinessTag(status) {
  * remediation — so neither rendering can show an operator a finding the other
  * hides. It computes no overall verdict, because there is none to compute.
  */
-export function formatConductorReadinessGateReport(report) {
-    const lines = [
-        "Conductor readiness (advisory)",
-        "══════════════════════════════",
-        `schema version: ${report.schemaVersion}`,
-        `repository:     ${report.repoName ?? "unresolved"}`,
-        "",
-    ];
-    for (const source of ["install", "conductor", "plane", "server"]) {
-        const group = report.checks.filter((check) => check.source === source);
-        if (group.length === 0)
-            continue;
-        lines.push(`[${source}]`);
-        for (const check of group) {
-            lines.push(`  ${readinessTag(check.status)}  ${check.label}  (${check.id})`);
-            if (check.detail)
-                lines.push(`          ${check.detail}`);
-            if (check.remediation)
-                lines.push(`          → ${check.remediation}`);
-        }
-        lines.push("");
-    }
-    const { pass, warn, fail, skip } = report.summary;
-    lines.push(`summary: ${pass} pass, ${warn} warn, ${fail} fail, ${skip} skip`);
-    if (report.unavailableSources.length > 0) {
-        lines.push(`sources that could not be collected: ${report.unavailableSources.join(", ")} ` +
-            "(their prerequisites above are reported as failures, not as passes)");
-    }
-    lines.push("");
-    lines.push(report.advisory);
-    return lines.join("\n");
+export function formatConductorReadinessGateReport(report, options = {}) {
+    return formatReadinessPrerequisites(report.prerequisites ?? mergeReadinessPrerequisites(report.checks), { all: options.all, isProduction: report.is_production }).join('\n');
 }