fix: a conformance verdict that never said which version gave it - #39
Merged
Merged
Conversation
Codex is refused by ai-stp-cli 0.0.7 -- 'a scoped projection profile names an unknown target scope' -- while the provider kit this program vendors and verifies byte-for-byte, 0.2.4, gives target_scope the enum ["project", "user_root"]. The checker shipped beside that kit carries ["project"] alone. Six harnesses pass 23 of 23. The declaration stands: it is true against the artifact a provider is told to build against. Raised with the consumer, who owns both. The README section that already warned to check the checker's version now gives both versions and both answers, because its closing claim that all seven pass against a checker carrying the field is no longer true. Also here: claude moves to 2.1.250 with every other pin re-measured; the codex baseline key permission_profiles becomes product_permission_profiles, because a baseline records what the vendor does and provider-info declares what this provider does, and one word on two axes gets bound together by somebody -- refused now by surfaces::disagreements, reading the forbidden names from the kit's own schema rather than from a list that would drift. Claude-Session: https://claude.ai/code/session_01BgFJL6e1vwwzimvP9tJDHY
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
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.
Rendered from the private source.
Codex is refused by the consumer's released checker, and nothing noticed.
Six harnesses pass 23 of 23. Antigravity's project scope passes every case, so the scoped-profile machinery is not in question -- one enum member is.
The declaration stands: it is true against the artifact a provider is told to build against, and which ships with a checksum manifest so a provider can prove it did. Nothing routes to user_root yet. Raised with the consumer, who owns both artifacts.
The README section that already told readers to check the checker's version now names both versions and both answers -- its closing claim that all seven pass against a checker carrying the field is no longer true.
Also here:
https://claude.ai/code/session_01BgFJL6e1vwwzimvP9tJDHY