Skip to content

infra_openapi_types_freshness_gate: infra_openapi_types_freshness_gate — offline OpenAPI export + types.ts freshness gate #408

@SoundMindsAI

Description

@SoundMindsAI

Why

Defined as Phase 2 in infra_generated_artifact_freshness_gate/feature_spec.md §3 "Phase boundaries". Phase 1 (the copy-docs freshness gate — FR-1, FR-3, FR-9) ships first because it is pure-filesystem and zero-infra. This work carries the OpenAPI-export + types.ts half, which has a real import-cleanliness investigation and a banner-determinism fix.

The parent's implementation_plan.md covers both phases (Epic 1 = Phase 1, Epic 2 = Phase 2). This standalone folder is the discoverable idea-stage record of the Phase 2 half if Phase 1 ships alone; if both phases ship in one pass, this folder is retired at finalization.

Status

  • Stage: IDEA
  • Priority: P2 (same as parent)

Definition of done

Definition of done lives in the linked artifact(s) below — open it before starting.

Artifacts

How to execute

  1. Preflight the idea against the current codebase (catches stale file/line references, obsolete deferral rationale, drifted dependencies):

    /idea-preflight docs/00_overview/planned_features/02_mvp2/infra_openapi_types_freshness_gate/idea.md
    

    The skill applies patches in-place; review with git diff after it runs.

  2. Run the full pipeline autonomously (spec → plan → implement → PR):

    /pipeline docs/00_overview/planned_features/02_mvp2/infra_openapi_types_freshness_gate --auto
    

    --auto skips inter-stage approval pauses but keeps all hard quality gates (cross-model review via GPT-5.5 in spec-gen + impl-plan-gen, per-story verification gates, test coverage audit, CI watch, Gemini adjudication, final cross-model review). The PR is opened but NOT merged — you merge it manually after review.

  3. If you don't want full autonomy, drop the --auto flag — the pipeline will pause for approval between each stage (spec, plan, implement) so you can review and request changes.

Notes

This issue is part of the MVP2 backlog issue-coverage sweep (2026-06-02) — every active MVP2 folder should have a tracking issue so external contributors can discover the work without grep-ing the planned-features tree. If you pick this up, drop a comment so others don't duplicate; if you find the linked idea/spec stale, run /idea-preflight first to refresh it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    mvp2MVP2 backlog itemneeds-preflightIdea-stage; run /idea-preflight before /pipelinepriority/P2P2 — important to file, not blockingtype/infraInfra — tooling, CI, deploy

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions