Skip to content

Validate tests/fixtures/fractal PROVENANCE blob IDs against the pinned fixture #118

Open

Description

@schickling-assistant

tests/fixtures/fractal/PROVENANCE and infrastructure-PROVENANCE record per-file source blob IDs and the fractal revision, but no check validates those hashes against the fractal-fixture input. parity_drift.rs:57-76 reads only the path column. Found during #117. Add a check that each recorded blob ID equals the blob of that path at the pinned fixture revision.

Posted on behalf of @schickling
field value
agent_identity agent/compoundingtech/mergemaster
session 01a19dbc
agent_persona generalist
agent_supervisor unavailable
agent_tool OMP
agent_tool_version 18.12.5
agent_runtime OMP 18.12.5
agent_model anthropic/claude-opus-5-5
worktree unknown

Activity

  1. schickling-assistant commented on Nov 10, 2026

    @schickling-assistant
    ContributorAuthor

    Also in scope (Janitor P3 on #120): after #120 removes the resync rows, scripts/PROVENANCE still has the header # Commit: e83871ec, and 29 table rows (for example scripts/ci-evidence-gate, table 4400fdf7 vs tree 2952f895) do not match the tree. crates/mergemaster-evidence/src/parity_drift.rs:107 reads that line, so the scheduled drift report measures from e83871ec. Fix: regenerate the header and table at fractal e2721e52 (the step A source). Deferred from #120 because it adds at least 60 lines, which would exceed the 280-line PR limit.

    Posted on behalf of @schickling
    field value
    agent_identity agent/compoundingtech/mergemaster
    session 01a19dbc
    agent_persona generalist
    agent_supervisor unavailable
    agent_tool OMP
    agent_tool_version 18.12.5
    agent_runtime OMP 18.12.5
    agent_model anthropic/claude-opus-5-5
    worktree unknown
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions