v0.3.0: User and session contributors
v0.3.0 Release Notes
These notes describe v0.3.0. Verify the published archive's provenance and checksums
before installation; the installer defaults to this version.
What Changes
fleetdiff investigate can answer two more questions when the input summaries
contain compatible measurements:
- Which tracked users account for tokens or model attempts?
- Which sessions have a high enough share to investigate?
Use collector v0.3.0 with optional topk_keys, or compatible sketchkit summary
files containing top_users, top_sessions, or their _requests variants.
Fleetdiff still reads summary files, not raw traces, and makes no network calls.
Session candidates require a share lower bound strictly above --flag-share
(default 0.25) and complete relevant observations. The share is of attributed
sketch weight, not all application traffic. Request weighting works when usage is
missing; token-weighted flags are withheld when usage is incomplete. A flag is a
reason to investigate, not proof of a loop, a root cause, or wasted money.
fleetdiff investigate --before before/ --after after/ --expected app \
--flag-share 0.25The existing demo fixtures show prompt attribution; they do not fabricate session
measurements. Collect two complete windows with session ranking enabled to answer
the session question. See Investigation.
Compatibility
- Comparison JSON remains version 1. Text now says "Model attempts" rather than
"Requests"; the existingrequestsJSON field is unchanged. - Missing optional measurements in either window or any input producer yield
cannot_determine, never zero. Differing extraction contracts remain errors. - Raw identifiers are not recovered from hashes. Hashes remain hidden unless
explicitly requested. Do not interpret pseudonymous summaries as anonymous. - Upgrade the reader before enabling the collector's new rankings. No migration
or rewrite of saved v0.2.0 summary files is required. New rankings cannot be
reconstructed for old windows. Older readers cannot answer these questions.
The installer now detects the platform and verifies attestations and checksums
before extraction. Error messages name missing CLI flags without echoing values.
Supported platforms remain Linux/macOS on amd64/arm64. Installation and rollback
instructions are in Operations.
Verification
The release workflow checks each exact archive on its native platform, including
threshold boundaries, missing usage, old windows, and hidden metadata. Linux also
has an offline, unprivileged smoke test. Archives, dependency inventory, checksums,
and provenance must all be verified before publishing the draft release.
This is a pre-1.0 release, not an enterprise support promise. It does not enforce
budgets, stop agent runs, reconstruct raw requests, or produce a billing ledger.