docs: document pricing_or_model_changed, confidence_reason format, policy accumulation, and ingest edge cases#30
Merged
Conversation
… format, policy accumulation, and ingest edge cases - operations-and-policy.md: add 'Pricing and model change detection' section explaining the three conditions that set pricing_or_model_changed (provider, pricing_version, model), cross-provider diff support, and where the flag surfaces (CLI note, HTTP pricing block, web UI warning banner) - operations-and-policy.md: merge constraint evaluation into confidence tiers section; document confidence_reason format strings and that all policy constraints are checked (failure reasons accumulate — multiple reasons can appear on one blocked promotion) - cli.md: add edge-case table for 'runs ingest' covering empty file (exits 0, inserts 0), malformed JSONL (exits non-zero), JSON array input, and duplicate run_id idempotency Covers codepaths added/hardened in v1.0.3 (tests/test_ledger.py, tests/test_spine.py). Co-authored-by: Gottam Sai Bharath <Gsbreddy@users.noreply.github.com>
Gsbreddy
approved these changes
May 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation-only PR covering three knowledge gaps exposed by v1.0.3 test additions.
Why
The v1.0.3 release hardened test coverage in
test_ledger.pyandtest_spine.pyfor behaviors that existed in code but had no corresponding developer reference:pricing_or_model_changed(cross-provider, cross-version, cross-model diffs)confidence_reasonstring looks like and when it appearsruns ingesthandles empty files, malformed JSONL, and JSON array inputChanges
docs/operations-and-policy.mdpricing_or_model_changed(provider, pricing_version, model field), explains cross-provider diff support, and notes where the flag surfaces (CLI note, HTTPpricingblock, web UIfd-alert--warnbanner)confidence_reasonformat" subsection documenting the four possible reason strings and how they appear in policy failure messagesdocs/cli.mdflightdeck runs ingest: empty file (exits 0,Inserted 0 events), malformed JSONL (exits non-zero), JSON array, and duplicaterun_ididempotencyValidation
uv sync --frozen --extra devuv run python -m ruff check src tests— all checks passeduv run python -m pytest— 93 passedSchema / Storage Impact
Risk
Documentation-only. No code changes.
Notes
Triggered by push to
mainatdf7628b(docs(web-ui): document v1.0.3 UI changes).