dsh-rerun-core

The shared vocabulary every rerun package agrees on: branded ids, the frozen-identity and measurement record types, content hashing, and the one process primitive three packages need.

It installs NO context key. Like dsh-brand, it is dependency-free vocabulary; the services live in the seam packages.

Two things here are load-bearing:

• LoggedEvent models a session-log record as { type, seq, time, data } with data: unknown. Logs are written by the harness UNDER TEST, which is a different build — often a different release line, since rerun versions independently. The reader's own SessionEventMap is not authoritative over the file.
• runProcess kills the process TREE on timeout. child.kill() signals only the direct child, and what rerun launches is an agent that spawns shells and search binaries of its own.

Model Experience

None. This package never contributes to a model request: it runs in the orchestrator process, and the model calls it cares about happen inside a separate attempt subprocess running a different build of DSH entirely.

KV Cache effect

None; it neither assembles nor sends a provider request.

Known Limitations and Deferred Work

• Hashing is SHA-256, not the BLAKE3 the design named. It is in the Node standard library and no part of this framework is hash-rate bound.
• Windows process-tree termination goes through taskkill /T, which is best-effort: Windows has no process groups, so a grandchild that re-parents itself can survive.