Repository navigation
Conversation
|
Landing: allow · c57626f No blocking findings. The six new cases and |
There was a problem hiding this comment.
One stale path in the provenance doc; the consolidation otherwise checks out (44 nodes pass, and the recorded provider bodies keep their pinned SHA-256).
Non-blocking: the PR title and body still describe the recording/contract split that 4bfda4f reverted, so the merge commit message will record a separation the tree does not have.
e1d20b0 to
b35523c
Compare
ef48617 to
43e5247
Compare
b35523c to
c57626f
Compare
|
Incorporated into |
Summary
Extend the existing Goose/Fantasy golden suite with six provider recordings for Z.ai, Grok, OpenRouter and Azure. Numbered JSON/SSE inputs, loading, streaming consistency and tool round trips share one runner.
PROVIDER-SAMPLES.mdpins the Fantasy source commit, cassette paths, transformations and response hashes. Republic request conventions are distinguished from the recording evidence. No production code or dependencies change.Stack
Commit ancestry:
main(including #102) → #101 → #103 → #104 → #105.#103 and #104 target their preceding layer for incremental review. #105 targets
mainand integrates all four layer commits. Merge #105 with a merge commit only after all four current heads have passing native checks and a matching Landingallow. Preserving ancestry lets GitHub mark the lower layers as indirectly merged. Do not squash/rebase the integration merge.Validation
c57626f033e2caf6e2154d28092d5764eaa8dd69.uv run pytest -q— 596 passed.uv run prek run --all-files— passed.uv run ty check— passed.