JuliusBrussee/caveman · error · Error

adapter-specific build_sha256 values must differ

Error message

adapter-specific build_sha256 values must differ

What it means

Error "adapter-specific build_sha256 values must differ" thrown in JuliusBrussee/caveman.

Source

Thrown at packages/shared/contracts/scripts/validate-schemas.mjs:79

if (claude.harness !== "claude" || pi.harness !== "pi") {
  throw new Error("agent conformance fixtures must cover claude and pi");
}

for (const key of [
  "normalized_context_digest",
  "plan_sha256",
  "ordered_transform_ids",
  "provider_visible_digest",
  "recovery_handles",
  "accounting_method",
  "failure_fallback",
]) {
  if (JSON.stringify(claude[key]) !== JSON.stringify(pi[key])) {
    throw new Error(`agent conformance mismatch: ${key}`);
  }
}
if (claude.build_sha256 === pi.build_sha256) {
  throw new Error("adapter-specific build_sha256 values must differ");
}
if (claude.failure_fallback !== "original") {
  throw new Error("unknown adapter failure must preserve original bytes");
}

console.log(
  `validated ${files.length} JSON schemas and ${fixtureFiles.length} static agent contract fixtures (not executable parity)`,
);

View on GitHub (pinned to 27d5a3981a)

Solutions

1. Use distinct build_sha256 values for each adapter fixture.

When it happens

Trigger: Thrown at packages/shared/contracts/scripts/validate-schemas.mjs:79 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of JuliusBrussee/caveman@27d5a3981a (2026-08-15). Data as JSON: /api/errors/066658bc4fb2c7d4. Report an issue: GitHub.