List view

• simulator

  Answer "what would happen if I ran this?" locally, before touching a real pipeline (epic #310). Two fidelity tiers. Tier 1 is cascade simulate: a light in-process what-if engine that replays the same orchestration logic the generated workflows invoke against the manifest and current ci.state, then prints a before to after state diff plus the ordered sequence of effects for promote, hotfix, rollback, and release, with no Docker and no GitHub calls. Tier 2 productizes the existing e2e harness (act plus gitea plus testcontainers) as a high-fidelity local integration simulator that runs the generated workflows with deploys stubbed. The scope boundary holds in both tiers: the simulator validates cascade's orchestration (state transitions, gating, divergence, rejoin), not the user's real build or deploy scripts.

  No due date

  •4/7 issues closed
  57% complete3 open4 closed

• visualizer

  Render the generated pipeline as a diagram (epic #300). A first-class cascade graph command projects cascade's existing internal model (the job DAG, the environment promotion chain, and the cross-repo flow) into a render-agnostic view model behind a pluggable emitter. Mermaid is the first emit target so a diagram commits to a README and renders natively in GitHub markdown, issues, and pull requests with no external tooling. Scope includes three granularities (environment state machine, pipeline stages, full job DAG), a theme layer with cascade and bland built-in themes, cross-repo and multi-component (monorepo) rendering, integration hooks (README, PR plan-preview, docs), and a deferred high-fidelity render engine behind the same emitter.

  No due date

  •6/10 issues closed
  60% complete4 open6 closed

• monorepo

  Multi-component (monorepo) support built on the schema-2 manifest. This consolidates the former staged milestones so all monorepo work tracks in one place. Rough sequence of work: 1. schema-2 foundation: one component-major in-memory model, parse and validate nested manifests, dual-form state, per-component generation with schema-1 output unchanged, and an optional upgrade-manifest (v1 to v2) helper. 2. Independent versioning: declare multiple components and version each from its own paths and tags. 3. Independent promotion: promote every component through the ladder independently, with per-component workflows and concurrency groups. 4. Independent hotfix, rollback, and release scoped to each component's namespace. 5. Polish: let a component target a subset of the environment ladder, document schema-2 manifests, and keep the multi-component example as permanent fleet coverage. Stage codes (used in the dependency lines of the issues in this milestone): F = schema-2 foundation, V = independent versioning, P = independent promotion (some issue bodies still call this stage "M"), R = independent hotfix, rollback, and release, X = polish.

  No due date

  •1/22 issues closed
  4% complete21 open1 closed

• v1.0.0

  Schema-stable, full GHA coverage, complete deploy model. The maturity gate, not the version integer.

  No due date

  •48/48 issues closed
  100% complete0 open48 closed