chore: release v0.10.3#9
Merged
Destynova2 merged 1 commit intodevelopfrom Mar 2, 2026
Merged
Conversation
Destynova2
added a commit
that referenced
this pull request
Mar 16, 2026
Critical: - #9 #10: Replace hard-coded HMAC key with random session key when GROB_DLP_SECRET is unset (unpredictable pseudonyms by default) High: - #11 #12: Cap Vec::with_capacity to 1024 in OpenAI transform (prevents uncontrolled allocation from malicious input) - #17 #18 #19: Add path traversal check in token_store persist() (reject ".." in file path) - #6 #7 #8: Stop logging full response bodies in OpenAI provider (log length instead, truncate to 200 chars on parse error) - #13 #14: Warn at construction if OAuth token_url uses plaintext HTTP - #15 #16: Warn at construction if Gemini base_url uses plaintext HTTP (new warn_if_cleartext() helper in providers/mod.rs) - #20 #21 #22: Annotate benchmark TLS cert bypass with lgtm comment (intentional: benchmarks use self-signed certs) - #3: Avoid flowing API key through format string in preset info - #4 #5: Remove secret values from test assertion messages Medium: - #1: Add explicit permissions block to release-plz workflow Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
38 tasks
5 tasks
Destynova2
added a commit
that referenced
this pull request
Apr 21, 2026
… + orchestration (T-SP-3 #9) provider_loop.rs was hosting three distinct concerns in a single file: 1. Provider selection (registry + CB + HC + RE-1a endpoint health) 2. Retry + error classification + single-provider dispatch 3. Outer fallback loop orchestration Split into: - src/server/dispatch/resolver.rs (~128 LoC) — resolve_provider, try_direct_provider_lookup (backward-compat path). - src/server/dispatch/retry.rs (~482 LoC) — ProviderLoopAction, ProviderAttempt, classify_and_handle_error, emit_provider_error_metrics, handle_provider_error, try_rotate_and_retry, dispatch_streaming, dispatch_non_streaming, wrap_stream_with_middleware, build_encrypted_content. - src/server/dispatch/provider_loop.rs (~275 LoC down from 808) — dispatch_provider_loop (outer loop), log_dispatch_attempt, prepare_provider_request, emit_fallback. No behavior change: public entry point src/server/dispatch/mod.rs:349 (provider_loop::dispatch_provider_loop) keeps the same signature and callers are unaffected. Validation: - cargo build --all-targets green - cargo test --lib : 949 passed, 0 failed - cargo clippy --all-targets -- -D warnings clean - RUSTFLAGS="-D warnings" cargo check --no-default-features clean Addresses Phoenix audit 2026-04-20 item #9.
Destynova2
added a commit
that referenced
this pull request
Apr 21, 2026
refactor(dispatch): split provider_loop 808 LoC into resolver + retry + orchestration (T-SP-3 #9)
Merged
Destynova2
added a commit
that referenced
this pull request
Apr 21, 2026
Two drift fixes caught by Tier 2 audit (items #6, #14): - `src/routing/classify/mod.rs`: the `route()` doc-comment listed only 6 priority levels while the actual code has 9 (auto-map, declarative tier match, and algorithmic scoring were missing). The inline numbering also had a gap (skipping #7 and duplicating #9) — renumbered to match. - `docs/explanation/architecture.md`: the request-flow mermaid still showed the pre-T-VS `router` subgraph and a single generic "Circuit Breaker" box. Updated to reflect the `routing/` parent module (classify + circuit_breaker + health_check) and the RE-1a / RE-1b split from ADR-0018, including the `is_endpoint_healthy` AND-gate and the security-layer global CB that runs after it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Destynova2
added a commit
that referenced
this pull request
Apr 21, 2026
* fix(dispatch): wire grob_hint to override complexity tier (audit #5) The MCP complexity hint (`X-Grob-Hint` header, `metadata.grob_hint` body field, or one-shot MCP tool slot) was resolved and then dropped via `let _ = grob_hint`. It now overrides `RouteDecision.complexity_tier` right after routing, so clients that know their task is trivial can opt out of `[[tiers]]` fan-out for a single request. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(routing): fix drift in router doc-comment and architecture mermaid Two drift fixes caught by Tier 2 audit (items #6, #14): - `src/routing/classify/mod.rs`: the `route()` doc-comment listed only 6 priority levels while the actual code has 9 (auto-map, declarative tier match, and algorithmic scoring were missing). The inline numbering also had a gap (skipping #7 and duplicating #9) — renumbered to match. - `docs/explanation/architecture.md`: the request-flow mermaid still showed the pre-T-VS `router` subgraph and a single generic "Circuit Breaker" box. Updated to reflect the `routing/` parent module (classify + circuit_breaker + health_check) and the RE-1a / RE-1b split from ADR-0018, including the `is_endpoint_healthy` AND-gate and the security-layer global CB that runs after it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 New release
grob: 0.10.2 -> 0.10.3 (✓ API compatible changes)Changelog
This PR was generated with release-plz.