Skip to content

refactor(status): remove the redundant health mirror - #140

Open
vriesd wants to merge 1 commit into
mainfrom
refactor/health-cache-owner
Open

refactor(status): remove the redundant health mirror#140
vriesd wants to merge 1 commit into
mainfrom
refactor/health-cache-owner

Conversation

@vriesd

@vriesd vriesd commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Why

Health was stored in both HealthCacheState.cached and a HEALTH mirror. This implements Plan 22's first unit by keeping the existing cache as the sole authoritative cached value.

Scope

Remove the mirror, its initialization copy, publication callback, invalidation writes, and test re-export. GNOME fixtures now seed the actual cache after advancing its generation. The one-second source check, ten-second TTL, background refresh, and invalidation callers retain their behavior.

Verification

All 20 status tests and seven non-ignored GNOME tests passed. The new cache test verifies repeated fixture seeding and rejects pending work from an older generation. Independent source review found no blockers. The two environment-dependent GNOME cases remain ignored; physical desktop acceptance is still open.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 5, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-05T18:47:50.155450Z ba0edc9 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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