feat(generator): build full SDK generation foundation - #7
Draft
nmorgan-cb wants to merge 5 commits into
Draft
Conversation
🟡 Heimdall Review Status
|
nmorgan-cb
force-pushed
the
toshi/plan-service-generator-upgrade
branch
from
September 2, 2026 17:43
d0671ee to
5e2693d
Compare
This was referenced Sep 2, 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
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.
Description
Builds the foundation for deterministic, full Prime Java SDK generation from the committed OpenAPI specification.
SpecParser, which captures operation IDs, HTTP methods, paths, tags, merged parameters, request/response schemas, numeric 2xx statuses, summaries, and optional SDK naming extensions fromapiSpec/prime-public-spec.yaml.SpecModelsandOperationBindingmetadata for subsequent request, response, service, and factory generation phases.docs/agent-planning artifacts so they do not enter the public repository.This consolidated PR supersedes the former stacked PRs #8 and #9. It intentionally does not yet replace the existing handwritten DTO/service sources; the parser and binding contract must be accepted before enabling client-surface source replacement.
Generated with Toshi
Type of Change
Checklist