Skip to content

CCIX-213: Expose lifecycle UNKNOWN causes - #93

Merged
yti93 merged 19 commits into
mainfrom
youssef/ccix-213-lifecycle-unknown-causes
Aug 10, 2026
Merged

CCIX-213: Expose lifecycle UNKNOWN causes#93
yti93 merged 19 commits into
mainfrom
youssef/ccix-213-lifecycle-unknown-causes

Conversation

@yti93

@yti93 yti93 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Why

Lifecycle UNKNOWN findings currently conflate unsupported versions, source failures, malformed data, and inventory gaps, preventing operators from distinguishing healthy unsupported coverage from broken lifecycle inputs.

What

  • Add bounded UNKNOWN causes and lifecycle data sources to findings, snapshots, and Prometheus aggregates without engine/version labels
  • Preserve endoflife.date response provenance and classify product, cycle, malformed-payload, and source failures
  • Add machine-readable local override ownership/review metadata with strict validation and warn-only overdue reviews
  • Document the new diagnostics and override operating contract

Risk Assessment

Medium — this changes lifecycle lookup diagnostics and adds metrics/snapshot fields, while preserving existing status counts, Temporal activity contracts, snapshot schema v4, and graceful UNKNOWN behavior.

References

Generated with Amp

yti93 and others added 18 commits August 5, 2026 13:47
@yti93
yti93 marked this pull request as ready for review August 5, 2026 21:45
@yti93
yti93 requested a review from a team as a code owner August 5, 2026 21:45
@yti93
yti93 enabled auto-merge (squash) August 10, 2026 17:39
@yti93
yti93 requested a review from spicykay August 10, 2026 17:41
@yti93
yti93 disabled auto-merge August 10, 2026 18:29
@yti93
yti93 merged commit 6444604 into main Aug 10, 2026
6 checks passed
@yti93
yti93 deleted the youssef/ccix-213-lifecycle-unknown-causes branch August 10, 2026 18:29
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.

2 participants