@bridge_gpt/mcp-server 0.2.59 → 0.2.62

package/build/merge-workflow-drift.js

@@ -0,0 +1,97 @@
+/**
+ * Canonical byte identity for the Epic Implementer merge workflow (BAPI-1136).
+ *
+ * The merge workflow is the one file in a customer repository that can perform a
+ * privileged write on Bridge's behalf, so "is the installed copy the copy Bridge
+ * ships?" has to be answerable cheaply, in more than one place, and with one
+ * answer. This module is that one place.
+ *
+ * It follows `claude-review-workflow-drift.ts`'s shape deliberately: a leaf
+ * module with NO filesystem, network, or subprocess access, importing only the
+ * shared Git blob hash so two workflow-identity implementations cannot drift
+ * apart about what "the same file" means. Callers acquire bytes however their
+ * own layer already does and hand them in.
+ *
+ * Nothing here logs file content: a classification carries a path, a pair of
+ * SHAs, and a closed-vocabulary state — never bytes, never provider text.
+ */
+import { computeGitBlobSha } from "./claude-review-workflow-drift.js";
+import { MERGE_WORKFLOW_PATH } from "./conductor/merge-execution-contract.js";
+import { renderEpicImplementerMergeWorkflow } from "./merge-workflow.js";
+export { MERGE_WORKFLOW_PATH };
+/**
+ * The Git blob SHA-1 of the workflow this build renders.
+ *
+ * Computed, never hardcoded. A checked-in literal would be a second byte source
+ * the renderer could silently diverge from — exactly the drift this module
+ * exists to make impossible.
+ */
+export function canonicalMergeWorkflowSha() {
+    return computeGitBlobSha(Buffer.from(renderEpicImplementerMergeWorkflow(), "utf8"));
+}
+/**
+ * Every Bridge-published historical rendering of the merge workflow, by Git blob
+ * SHA, with the contract version it declared.
+ *
+ * A future contract version adds its predecessor's SHA here, and only then can
+ * {@link classifyMergeWorkflowContent} return `managed_version_older`.
+ *
+ * ## Why a version-1 entry exists without a version bump (BAPI-1257)
+ *
+ * The first entry is a rendering that was published AS version 1 and then
+ * corrected WITHIN version 1. Its fork-origin guard read
+ * `jq -r '.isCrossRepository // true'`, and jq's `//` yields its right-hand side
+ * when the left is null OR FALSE — so a same-repository pull request, which
+ * every epic child is, read as `true` and the merge was refused as fork-origin.
+ * That rendering could never merge anything.
+ *
+ * The marker version is deliberately NOT bumped: the wire contract, the dispatch
+ * inputs and the command-fetch protocol are all unchanged, and
+ * `MERGE_WORKFLOW_EXPECTED_VERSION` is the server's deploy-ordering check, not a
+ * byte checksum. But without this entry a repository holding that rendering
+ * classifies as `modified_or_unrecognized`, and the installer's preflight hard
+ * refuses to touch a workflow Bridge does not recognise — leaving no automated
+ * path off a copy that cannot merge. Registering the superseded SHA restores it:
+ * the copy classifies `managed_version_older` and the installer opens its
+ * ordinary upgrade pull request.
+ *
+ * The SHA is the Git blob SHA of the complete superseded rendering, which is
+ * what {@link canonicalMergeWorkflowSha} computes for the current one.
+ *
+ * ## The version-1 entry added by BAPI-1259
+ *
+ * `0d44c814…` is the last version-1 rendering (the one BAPI-1257 corrected).
+ * Contract version 2 adds the `operation` input and the integration job, so a
+ * repository holding that rendering is an ordinary managed older version and
+ * the installer opens its upgrade pull request.
+ */
+export const MANAGED_MERGE_WORKFLOW_HISTORY = new Map([
+    ["3d4956c9447223c37075069352cdd9aae2d561dc", 1],
+    ["0d44c81436005beb3c314de1b98eaf972ef3b4db", 1],
+]);
+/**
+ * Classify an installed copy against the canonical bytes.
+ *
+ * `existing` is `null` for an absent file. The comparison is on RAW BYTES, not
+ * normalized text: a copy that differs only in line endings is still a copy this
+ * installer did not write, and treating it as identical would let a rewrite hide
+ * behind a whitespace-insensitive compare.
+ */
+export function classifyMergeWorkflowContent(existing) {
+    if (existing === null)
+        return "not_installed";
+    const canonical = renderEpicImplementerMergeWorkflow();
+    if (existing === canonical)
+        return "identical";
+    const sha = computeGitBlobSha(Buffer.from(existing, "utf8"));
+    if (MANAGED_MERGE_WORKFLOW_HISTORY.has(sha))
+        return "managed_version_older";
+    return "modified_or_unrecognized";
+}
+/** Operator-facing gloss for each classification. Secret-free and path-only. */
+export const MERGE_WORKFLOW_CLASSIFICATION_TEXT = {
+    not_installed: `${MERGE_WORKFLOW_PATH} is not installed`,
+    identical: `${MERGE_WORKFLOW_PATH} already matches the version this build ships`,
+    managed_version_older: `${MERGE_WORKFLOW_PATH} is an older Bridge-managed version and can be upgraded`,
+    modified_or_unrecognized: `${MERGE_WORKFLOW_PATH} has been modified or is not a version Bridge published`,
+};