Skip to content

Expose observation failure codes and document audit follow-up - #47

Draft
Odenknight wants to merge 1 commit into
mainfrom
fix/audit-observation-diagnostics-20260908
Draft

Expose observation failure codes and document audit follow-up#47
Odenknight wants to merge 1 commit into
mainfrom
fix/audit-observation-diagnostics-20260908

Conversation

@Odenknight

Copy link
Copy Markdown
Owner

The scheduled observation failed September 7 and 8 with OBS_INDEX_FAILED but no useful log diagnostic. Local reproduction identifies a frozen 2.1.2 projection expectation versus current 2.2.0 producer identity; provider counts and request digest match. This does not establish a latency regression.

Print only the existing allowlisted failure code, document full-history verification, and record the reproduction plus release/distribution next steps in docs/USEFULNESS-AUDIT-FOLLOWUP-20260908.md.

Validation: all 12 observation qualification tests pass on Linux Node 24.19.0; bundled full observation still fails as expected and now prints OBS_INDEX_FAILED. git diff --check passes. Frozen fixtures, thresholds and receipt semantics are unchanged. The versioned 2.2 observation successor remains outstanding; this PR does not fix or claim a green observation lane. No release or publication is requested.

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