# Changelog

## Unreleased

## 0.25.0

Requires contracts 0.22 (`>=0.22,<0.23`), with exact release prerequisite
`contracts-v0.22.0`. Package and execution-profile qualification remain separate.

- Evaluate copied archives with `--evidence-origin-root` or the matching API
  keyword. Resolve captured absolute evidence references beneath the current
  evidence-index directory while preserving their recorded identities and
  verifying size and digest through the existing bounded reader.
- Reject references outside the original root, duplicate relocated paths,
  symlinks, missing files and changed bytes. Keep calibration and evaluator
  admission tied to the external operator profile.

## 0.24.0

Requires contracts 0.22 (`>=0.22,<0.23`), with exact release prerequisite
`contracts-v0.22.0`. Package and execution-profile qualification remain separate.

- Allow `RosGraphObserver` to use an initialized caller-owned ROS context through
  the keyword-only `context` argument. The observer owns its node, executor and
  thread, and leaves a borrowed context running on closure or construction failure.
- Ignore process-wide ROS remaps and parameter overrides on the observer node
  in both context modes. Subscribe to `/clock` when declared in the expected graph
  or explicitly requested with `observe_clock=True`.
- Render a synthetic `qualification-verdict` JUnit test case that fails for every
  non-passing verdict (`incomplete`, `failed`, `error`, `cancelled`). Assertion
  and coverage cases keep their own outcomes, and the CLI exit-code contract
  (0 passed, 1 completed non-pass, 2 handled exception) is unchanged.

## 0.23.1

Requires contracts 0.22 (`>=0.22,<0.23`), with exact release prerequisite
`contracts-v0.22.0`. Earlier contracts minors are not supported by this release.
Package and execution-profile qualification remain separate.

- Correct the packaged requirements reference and align the 0.23 compatibility
  documentation with the contracts dependency declared in package metadata.

- Add optional local OCI archive assessment with an external operator profile,
  captured read-only inputs and bounded execution; retain raw responses and
  validate assertions before producing v3 results.

- Bound gh/Cosign stdout and stderr during verification, including direct-child
  cleanup after output overflow or a command deadline.

- Honor an explicit positive raw-evidence capture limit in the verified byte API.
  Preserve the default 8 MiB capture limit and the separate structured-document
  limit, source identity checks and streaming behavior.

## 0.22.3

Requires contracts 0.21 (`>=0.21,<0.22`), with exact release prerequisite
`contracts-v0.21.1`. Package and execution-profile qualification remain separate.

- Document the existing bounded file capture, read-only graph observer and
  readiness submodule interfaces, including their caller-owned trust and
  deadline boundaries. Their implementations and behavior are unchanged.
- Exercise these interfaces from an isolated installed-wheel consumer.

## 0.22.2

Requires contracts 0.21 (`>=0.21,<0.22`), with exact release prerequisite
`contracts-v0.21.1`. Package and execution-profile qualification remain separate.

- Preserve excluded lower edges of explicit histogram buckets when proving
  threshold outcomes. Keep upper edges inclusive and tightened minima closed.
- Reject recorded extrema that contradict the first or last occupied bucket
  before returning statistics. Counts and recorded means remain exact for valid
  histograms.

## 0.22.1

Requires contracts 0.21 (`>=0.21,<0.22`), with exact release prerequisite
`contracts-v0.21.1`. Package and execution-profile qualification remain separate.

- Check operator profile write permissions on the same open descriptor used to
  capture its bounded bytes. Reject group/other writable captured profiles even
  if a later path lookup would observe a restrictive mode or replacement file.
- Preserve ordinary evidence and wheel read defaults. Regular 0600 and 0644
  operator profiles remain supported.

## 0.22.0

Requires contracts 0.21 (`>=0.21,<0.22`), with exact release prerequisite
`contracts-v0.21.1`. Package and execution-profile qualification remain separate.

- Evaluate captured native v2 software/simulation inputs through public
  JSON/JUnit, aggregation and qualification interfaces without creating ROS
  graph, DDS or clock observations.
- Add immutable assessment controls and bounded captured calibration inputs.
  Execute selected metric assertions or authenticated product code without
  changing the original scenario/runtime. Bind each new assessment to the exact
  original result bytes and retain distinct result IDs, outcomes and coverage.
- Authenticate evaluator wheels through operator-owned GitHub or explicit
  private Cosign key-only policies; bind installed source and original entry
  points to captured wheel bytes before guarded execution. Audit receipts alone
  do not grant executable admission.
- Add public verified evidence-byte access and an installed author example that
  genuinely computes counter minus captured offset. Check numerical failures,
  unavailable/invalid calibration and read-only archive transplantation.
- Retain restrictive existing JSON/JUnit modes and apply OS umask to new files.
  Separate synthetic JUnit observation/coverage identities from assertion cases.
- Forward the caller's pinned extension registry to every loaded bundle role.
  The preceding 0.21.0 wheel forwarded it only to the scenario; current loading
  uses the complete registry on runtime/model/dataset/permit/verification inputs.
- Record actual installed distribution inventory in assessment environments,
  without process IDs, local paths or incidental timestamps. Preserve native
  measurement-clock identity separately from UTC provenance. V2 physical
  qualification and automatic native playback remain outside this release.

## 0.21.0

Requires contracts 0.20 (`>=0.20,<0.21`), with release prerequisite
[contracts-v0.20.0](https://github.com/mmkolpakov/robotics-runtime/releases/tag/contracts-v0.20.0).

- Observe late-joining retained ROS topics through an explicit `transient_local`
  profile: reliable, transient-local durability and keep-last history with depth
  10. Cached delivery requires a compatible retained publisher; no republish or
  application-specific readiness exception is introduced. The four previous
  profiles and implicit volatile `/clock` observation remain unchanged.

## 0.20.1

Requires contracts 0.19 (`>=0.19,<0.20`), with release prerequisite
[contracts-v0.19.0](https://github.com/mmkolpakov/robotics-runtime/releases/tag/contracts-v0.19.0).

- Add an optional, explicit import of SignalFlag SDK 1.8.0 JSONL emissions into
  native scalar gauge samples. Require selected numeric fields, declared units,
  and exact Unix-nanosecond timestamps; preserve scoped source-byte provenance.
- Reuse strict JSON parsing and document budgets, checking LF record counts
  before allocation. Keep opaque retention and qualification independent, with
  no SDK runtime dependency or endpoint compatibility claim.

## 0.20.0

Requires contracts 0.19 (`>=0.19,<0.20`), with release prerequisite
[contracts-v0.19.0](https://github.com/mmkolpakov/robotics-runtime/releases/tag/contracts-v0.19.0).

- Load the canonical `dataset-manifest.v2` bag model for one or more finalized
  MCAP members. Reject v1 dataset documents in the current execution bundle;
  historical v1 inputs remain associated with the previously published package
  pair.
- Validate the captured dataset document against its recorded digest before
  execution. Preserve immutable metadata and member declarations when the source
  document changes after loading.

## 0.19.2

Requires contracts 0.18 (`>=0.18,<0.19`), with release prerequisite
[contracts-v0.18.3](https://github.com/mmkolpakov/robotics-runtime/releases/tag/contracts-v0.18.3).

- Keep timing evaluation outcomes separate from invalid-input errors. Preserve
  unavailable observations and proven violations through typed results, then
  fold them into acceptance through the existing public status order.
- Add regressions for missing timing samples, invalid timing metadata and the
  distinction between completed timing failures and validation errors.

## 0.19.1

Requires contracts 0.18 (`>=0.18,<0.19`), with release prerequisite
[contracts-v0.18.2](https://github.com/mmkolpakov/robotics-runtime/releases/tag/contracts-v0.18.2).

- Reject missing or mismatched scenario/runtime robot-description bindings when
  loading an execution bundle, before explanation or live observation. Preserve
  optional bindings and leave filesystem/XML admission with the consumer.
- Add optional per-file raw-evidence byte limits to acceptance, aggregation,
  OTLP and trace processing. Preserve existing behavior when no limit is supplied.

## 0.19.0

The first harness release from the `robotics-runtime` workspace requires
contracts 0.18 (`>=0.18,<0.19`). Its release prerequisite is
[contracts-v0.18.1](https://github.com/mmkolpakov/robotics-runtime/releases/tag/contracts-v0.18.1).
The wheel and source distribution remain independently installable.

- Evaluate causal message pairs and connected trace paths, attributing channel
  spans by their declared topic. Fold acceptance and campaign verdicts through
  the canonical status order.
- Recheck expected graph and lifecycle conditions during measurement. Expire
  cached lifecycle state when a GetState request stops answering.
- Evaluate realtime factor in sliding windows, cumulative histogram baselines
  and resets, and interior gaps in delta coverage. Retain proven violations
  when other observations are unavailable.
- Read finalized evidence through bounded, contained file descriptors and retry
  partial or missing inputs to the deadline. Write UTC result timestamps and
  preserve an existing run context when create-run is repeated.
- Accept finalized receipt inventories and digest-pinned extension schemas.
  Verify evaluator sources against receipt and RECORD data and reject external
  bytecode caches.
- Expose HarnessError and HarnessInputError with stable identifiers and exit
  codes. Preserve dependency causes and structured issue paths in diagnostics.
- Ship type information, support Python 3.12–3.14 and relax supported runtime
  dependency ranges.
