docs: capture Forge spec-vs-runtime findings#20
Merged
Conversation
Captures the four spec mismatches surfaced while building the Servers slice (#18 + #19) plus the open-strings-not-enums decision from the Providers slice (#16 + #17). Append future findings here so the next debugging session can find the answer without re-running live-fire investigations. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 20, 2026
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.
Summary
Small docs-only PR adding `docs/FINDINGS.md`. Records five concrete places where Forge's runtime behavior diverges from `docs/forge.openapi.json` (or where we made a deliberate design call around an ambiguity), each with the spec claim, the actual behavior, and which SDK code accommodates it.
Entries:
Test plan
🤖 Generated with Claude Code