0.2.6 — date-windowed Runtime Reports

Date-windowed Runtime Reports

halo report --from 2026-06-01 --to 2026-06-30 renders a report covering only the review window — the disclosure shape audit periods and security reviews ask for.

• Only in-window records are embedded in the page; records outside the window never enter the artifact.
• The browser re-verifies the window against its anchor — the chain head immediately before the window — so window integrity is checked client-side without the full chain.
• The full chain is verified at generation; a windowed report is refused on a chain that fails verification (same rule as halo export).
• Witness checkpoints that land inside the window are re-verified in the browser; checkpoints before and beyond it are disclosed, including that the chain continues past the window.
• The report banner states exactly what the artifact is: which records of how many, the window bounds, the anchor, and the chain head at generation.

Multi-agent attribution

Chains that carry more than one agent now say so: the report header counts and names the fleet, and the activity table attributes each action to the agent that performed it.

AIUC-1 control mapping

The README's compliance-stack section now names the specific AIUC-1 Accountability controls the records serve (E015.4 tamper-evident logging; E015.2 execution-chain and authorization records), and halo verify states the claim its result supports: tamper-evident relative to the verified head.

Records written by 0.2.6 verify with any prior verifier; no format changes.