Skip to content

Refresh weekly certification verdict - #3

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/weekly-certification-verdict
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
automation/weekly-certification-verdict

Conversation

@github-actions

Copy link
Copy Markdown

Weekly Certification Refresh

This PR was generated by .github/workflows/weekly-certification-verdict.yml.

Refreshed artifacts include:

  • docs/evidence/dropin-certification-verdict.json
  • tests/ext_conformance/reports/gate/
  • tests/ext_conformance/reports/lifecycle_hooks/
  • tests/ext_conformance/reports/journeys/
  • tests/ext_conformance/reports/health_delta/
  • tests/perf/reports/stress_triage.json
  • tests/evidence_bundle/
  • tests/full_suite_gate/

@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch 2 times, most recently from dc04dbf to 0072b19 Compare July 13, 2026 10:34
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch from 0072b19 to 21075f1 Compare July 20, 2026 10:09
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch from 21075f1 to 2e1cef2 Compare July 27, 2026 10:51
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch 2 times, most recently from 8dbbe2d to fd2533b Compare August 10, 2026 08:37
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch from fd2533b to 5cd8e12 Compare August 17, 2026 08:02
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch from 5cd8e12 to 3eca151 Compare August 24, 2026 08:07
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch 2 times, most recently from fa9ec75 to 8d10fd6 Compare September 7, 2026 13:26
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch 2 times, most recently from 5e616f2 to e98d89d Compare September 21, 2026 13:47
Regenerate extension, evidence-bundle, full-suite, and drop-in certification artifacts from the scheduled evidence refresh workflow.
@github-actions
github-actions Bot force-pushed the automation/weekly-certification-verdict branch from e98d89d to 0b583f5 Compare September 28, 2026 15:06
AlexMikhalev pushed a commit that referenced this pull request Oct 18, 2026
The rebase of the exit-5 feature (9c6545c) onto v0.8.0 base auto-merged
the run_print_mode tail without conflict markers, leaving two adjacent
closing braces around the 'Ok(())' that returns from the function. The
duplicate brace parses as 'unexpected closing delimiter' and breaks the
bin build, even though the lib and tests compile cleanly.

The fix is a single deletion (one of the duplicate 'Ok(()) }' lines).
Found by 'cargo check --bin pi' on the rebased branch. Issue #3
follow-up uncovered it because the issue's own verification step
re-runs the bin build.

Refs #3
AlexMikhalev pushed a commit that referenced this pull request Oct 18, 2026
The openai-codex provider's model list was hand-maintained in
src/models.rs (5 ModelEntry blocks: gpt-5.2-codex, gpt-5.3-codex,
gpt-5.3-codex-spark, gpt-5.4, gpt-5.5). New codex releases were
invisible to /model until someone edited the file.

The crate already has the right infrastructure in
src/providers/model_fetch.rs (3,932 lines) -- it queries
GET /v1/models, caches per SHA-256 of (provider, route, credential)
for 5 minutes, falls back to built_in_models() on failure, and
supports --fetch-models ... --refresh-models --persist-models. It
just was not wired to codex.

Two narrow gates blocked it:

1. src/provider_metadata.rs -- openai-codex had routing_defaults: None.
   Every other OpenAI-compatible provider has a
   ProviderRoutingDefaults { api, base_url, auth_header, ... } so
   model_fetch can construct a request. None made codex invisible.

2. src/providers/model_fetch.rs -- openai_compat_models_url whitelisted
   only 'openai-completions' and 'openai-responses'. Codex uses
   'openai-codex-responses' (the native adapter), and its base URL
   'https://chatgpt.com/backend-api/codex' carries '/responses' as
   the call suffix (not '/chat/completions' as the existing stripper
   expected). Two line-level changes: extend the allowlist, branch
   for codex to strip '/responses' and append '/models'.

Auth is OAuth bearer, threaded through effective_model_catalog_api_key
like every other provider; the cache fingerprint already covers
credential rotation, so rotating the codex token yields a fresh
catalog entry without bleeding into the previous login's cache.

The probe ('curl https://chatgpt.com/backend-api/codex/models')
returns 401, not 404, confirming the endpoint is live. Final JSON
shape will be captured against a real Codex login in a follow-up.

Tests (3 new):
  - provider_routing_defaults_present_for_openai_codex_native_adapter
    (provider_metadata.rs): pins the routing defaults -- api,
    base_url, auth_header, reasoning, context_window, max_tokens.
  - openai_compat_url_for_openai_codex (model_fetch.rs): asserts
    the URL builder produces '.../backend-api/codex/models' for
    the canonical codex route.
  - openai_compat_url_for_openai_codex_strips_responses_suffix
    (model_fetch.rs): asserts a codex base URL with '/responses'
    appended still produces the right '/models' URL.

The static audit 'no_preset_claims_auth_it_cannot_perform' was
extended with a MODEL_FETCH_NATIVE_APIS allowlist
(['openai-codex-responses']) so the audit recognises the new
'live model discovery on a native adapter' use case alongside
the existing 'declare api family' use case. Native adapters with
a non-empty base_url are now allowed only if their api is in
that allowlist; any other combination continues to fail closed.

Test results:
  - providers::model_fetch: 48 passed, 0 failed (2 new)
  - provider_metadata::tests: 71 passed, 0 failed (1 new)
  - cargo check --bin pi: clean
  - cargo check --lib: clean

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant