Repository navigation
feat(api): regenerate clients from core development (onboarding door) - #38
Merged
Merged
Conversation
2 tasks done
…ng door) Rebased onto the new generation flow: no spec checked in anymore — make api-generate builds core at the Makefile's CORE_REF, runs its api-check, normalizes, and generates. Bump CORE_REF to current development (977e8bf) so the generated surface includes the onboarding door (Onboard / PlanOnboarding; operation ids are core's route names now) alongside the recording clients, and export CheckResponse for one-off generated calls (SCI's write-through consumes it). 💘 Generated with Crush Assisted-by: Crush:rits/zai-org/glm-5-3
gurnben
force-pushed
the
feat/api-onboarding
branch
from
October 29, 2026 18:51
a88641f to
2d690c8
Compare
Member
Author
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gurnben The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
9 tasks done
Merged
5 tasks done
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.
Plan:
plans/traust-standardization/5-sci-onboarding/02-gurney-collectors.md(gate G2)Started by gurney.
What
Spec refresh of the generated clients to traust-core
a01dae2(43 paths, 91 schemas, up from 37/67 at38a165e):POST /v1/onboarding+POST /v1/onboarding/plan— the onboarding door core#273 landed (idempotent product + repositories + refs + teams registration with baseline order planning), which SCI's collector write-through consumes at gate G2.Generated surface only — the bindings are unchanged and all existing tests pass.
make api-generateis drift-free at this commit.Note: builds on merged #35's pipeline; orthogonal to #36/#37 (their spec inputs are the classifier recording composition).
Jira: XWING-2438