Skip to content

fix(reporting): preserve mixed coverage partitions - #1927

Closed
rachitm022 wants to merge 1 commit into
mainfrom
rmatani/ai-22388-sdk-core-reporting-publishes-trusted
Closed

rachitm022 wants to merge 1 commit into
mainfrom
rmatani/ai-22388-sdk-core-reporting-publishes-trusted

Conversation

@rachitm022

Copy link
Copy Markdown
Collaborator

Why

Part of AI-22388. A summary with full and unknown reporting obligations could report coverage.status=unknown while leaving buys from full obligations out of every public classification array. That violates the reporting coverage partition and hides known coverage.

Scope

  • Project each summary buy into exactly one classification using its obligations across periods. Full plus unknown periods become a partial summary; a buy present in both is partially covered.
  • Keep unknown buys visible in both period and summary projections without inventing package IDs.
  • Cover mixed obligations through the public get_reporting_status handler and generated response validation, alongside focused projection tests.

This is a status projection fix only. It does not resolve or freeze package membership, change obligation creation or acquisition, publish package revisions, or modify the separate source-local calendar PR #1926.

Validation

  • Focused ledger and Core reporting lifecycle tests: 84 passed, 1 skipped.
  • make lint and make typecheck-all passed; Ruff formatting and staged diff checks passed.
  • Full local make test on macOS: 18,953 passed, 2,874 skipped, 1 expected failure, 7 failures in Linux/TypeScript interop tests. This is consistent with the Mac-only failures reported on the calendar PR; Linux CI is the full-suite gate.

Remaining AI-22388 work

PR2 must choose between nullable immutable obligation JSONB and a transactional sidecar for per-period (buy, package) evidence. Its resolver must distinguish authoritative missing history from transient read failure and carry evidence reference and visibility timing. Versioned source request/manifest support, row admission and qualified explicit-zero publication follow separately.

@rachitm022 rachitm022 closed this Nov 19, 2026
@rachitm022

Copy link
Copy Markdown
Collaborator Author

Closed while the required full Linux make test gate is rerun. The reviewed two-file status projection diff and local plan remain in Yeosu. A fresh draft will open only after the full gate passes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant