docs: spec-sync pipeline (Problem 3) implementation plan#98
Draft
yzld2002 wants to merge 1 commit into
Draft
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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.
Adds the implementation plan for the spec-sync pipeline (Problem 3 — sequenced first, before the V2 SDK code).
What's here: just the plan doc —
docs/superpowers/plans/2026-07-07-spec-sync-pipeline-ade-python.md. No source/CI changes yet.Contents: a scheduled two-phase pipeline (mechanical snapshot+reference-models commit, then a
claude-code-actionAI wiring commit) that tracks the live OpenAPI spec and opens a gated PR on drift. Gates:griffesurface-lock (baseline = last release tag), staging contract tests, existing lint/test/typecheck. Staging-in / production-out. 10 tasks with complete scripts + workflow YAML.Verified during planning: both V1 specs return 200 (loop is buildable today, no aide dependency); the
/v1/ade/extract/jobsdrift is real — the inaugural proof-run.Key adaptation flagged for review:
datamodel-code-generatoroutput is committed underspecs/_generated/as a reference for the AI phase, not shipped types (this repo's types are Stainless-shaped + compat-guaranteed).Tracking: #97 · related: #95 (Problem 2), #96 (V2 plan doc)
🤖 Generated with Claude Code