Skip to content

feat(server): expose read-only extraction diagnostics - #1796

Draft
PsiACE wants to merge 3 commits into
masterfrom
codex/extraction-health
Draft

PsiACE wants to merge 3 commits into
masterfrom
codex/extraction-health

Conversation

@PsiACE

@PsiACE PsiACE commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

Which issue or RFC does this PR close?

Related: Artifact Processing Supervisor RFC.

Rationale for this change

A capability boolean cannot distinguish missing extraction configuration, model failures, and worker crashes.

What changes are included in this PR?

  • Expose independent extraction configuration, Supervisor state, and local observations in capabilities.
  • Retain failure evidence across later successes and classify errors without exposing provider messages.
  • Update OpenAPI, generated models, English/Chinese operating docs, and behavior tests.

Are there any user-facing changes?

GET /v1/capabilities adds a read-only extraction snapshot without model probes or diagnostic database queries. External configuration and execution state remain unknown. Observations start unverified and reset with the Runtime; historical success or failure is not a current health verdict. No migration.

How was this change tested?

  • make check
  • make contract-test (49 passed)
  • Extraction, Supervisor, composition, metrics, Server, and CLI regression suites (137 passed).
  • make e2e-test (316 passed, 64 skipped)
  • make docs-test

Tests cover missing configuration, model errors, worker crashes/timeouts, leader/standby roles, discovery failures, retained history, no-op flushes, and restart semantics. Model failures were injected; worker crash/timeout tests used real child processes. Lease-role tests used SQLite. No live model calls.

AI usage statement

Codex (GPT-6) assisted with implementation, tests, and PR preparation.

@PsiACE
PsiACE marked this pull request as draft September 29, 2026 10:18
@PsiACE PsiACE added the 1.3.0 label Sep 29, 2026

This branch has not been deployed

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant