v0.5.0

v0.5.0 Release Notes

Three More Answers

• Did caching get worse? investigate compares the share of recorded input
  tokens served from cache, with field coverage checked in both windows.
• Is this collector configuration ready? diagnose checks supported YAML,
  points to settings and line numbers, and can print a reviewed standalone
  shadow configuration without changing your existing setup.
• Which windows look unusual? scan compares summary windows with a preceding
  baseline and explains changes in attempts, tokens per attempt, missing usage,
  user/session concentration, newly prominent contributors, and tool errors.

All commands run locally. scan and investigate read summary files, while
diagnose reads configuration. No service or account is required.

Try It

fleetdiff diagnose collector.yaml
fleetdiff scan --expected app ./summary-archive
fleetdiff investigate --help

From the source checkout, run sh examples/cache.sh, sh examples/diagnose.sh,
and sh examples/scan.sh. The scan example includes a quiet series:
sh examples/scan.sh --quiet.

Automation

diagnose exits with 0 for passing supported checks, 3 for blocking findings,
and 4 for unsupported or indeterminate configuration. scan exits with 0 when
quiet, 3 for unusual windows, and 4 when history or coverage is insufficient.
Both offer JSON output. Input/output errors use 1; invalid options use 2.

Scan uses conservative median/MAD thresholds, volume guards, sketch bounds, and
optional persistence. Test thresholds on your own quiet history before paging.
Missing usage is a coverage change, not a reduction in consumption. A contributor
newly prominent in retained candidates is not necessarily a newly created identity.

Upgrade

Verify checksums and release provenance as described in
operations, then replace the binary. No summary migration,
collector upgrade, or window reset is required. Existing comparison JSON remains
version 1; cache comparison adds a question to investigation output. Select
questions by ID rather than array position. New diagnosis and scan JSON formats
are independently versioned.

Scan needs retained history. The collector's in-memory retention also removes
old exported files; use the separate archive helper
before those files expire. Longer disk retention independent of memory remains
a separate collector change. Old summaries without cache field coverage report
that answer as unavailable.

Diagnosis checks a supported static subset, not live deployment behavior. It
does not resolve environment variables, includes, or configuration providers.
Unknown settings require review. See diagnosis,
scanning, and
cache comparison for the contracts.