CI Workflow Topology Grill Status

Branch Dashboard

Current Round

• Round: R6
• Current frontier: empty
• Shared-understanding confirmation: confirmed

Working Direction

pull request
  ci                    affected lint, types, and behavioral tests
  browser-smoke         only for backoffice/browser changes
  candidate             14-day JSON receipt for exact tested tree

main or reviewed release intent
  release-classifier    none | baseline | npm | mixed
  publication           build/package-specific proof, publish, reconcile, read back
                        no replay of PR test suites

Glossary

Terms

• Verification Authority: Exact successful pull-request evidence for one commit tree that publication may trust without rerunning the same tests.
• Affected Verification: Validation selected from the changed workspace dependency graph plus explicit safety fallbacks.
• Publication Workflow: Protected mutation path that consumes reviewed release intent and exact verification evidence, then publishes and reconciles external state.
• Candidate Evidence: Immutable JSON receipt binding a successful same-repository pull-request run to its exact tested Git tree.
• Stable Aggregate Check: One required check name that reports the result of every applicable pull-request proof, including intentional path-based skips.

Relationships

• One source tree has at most one accepted Verification Authority record per workflow contract.
• Affected Verification and any applicable browser proof contribute to the Stable Aggregate Check.
• The Publication Workflow consumes Candidate Evidence for the exact release tree.
• The release-impact classifier chooses which product mutation the Publication Workflow performs.

Axioms

• Pull requests never publish production artifacts.
• Release mutations are never cacheable.
• Unknown release impact fails closed.
• A skipped path-specific proof is valid only when the change classifier proves that its owned surface is unaffected.
• Publication must never treat a green result from another tree as authority.
• Superseded pull-request runs are cancelled.
• The stable aggregate check always runs even when owned path-specific proofs are skipped.
• A none release classification performs no product mutation.
• Tests execute only for pull-request revisions; publication trusts only exact matching successful evidence.
• Turbo's affected graph and declared global inputs own change selection.
• Publication performs a package-integrity precondition, not a package test suite.
• Publication does not execute an installed tarball.
• Pull-request verification, main release intent, and external-drift witnesses live in separate workflows.
• main and scheduled workflows never replay the pull-request suite.
• Release runs serialize and never cancel.
• Every deterministic retained check is an owning package's cacheable Turbo task; root scripts only delegate to turbo run.
• Trusted internal pull requests, main, and release verification share one signed remote-cache namespace when task inputs are identical.
• Fork pull requests may restore default-branch GitHub Actions Turbo cache entries but may write only to an isolated pull-request cache scope.
• CLI symlink, race, permission, rollback, and interrupted-write tests do not survive as "native witnesses" under another workflow name.

Flagged Ambiguities

• "Copy TanStack" may mean copy Changesets, or only copy the separation between PR verification and release publication. Q3 resolves this.
• "Run tests once" means once per pull-request revision. Cache reuse remains a separate mechanism.
• "Affected" means Turbo dependency selection plus declared global inputs and explicit repository-level tasks.
• "Package smoke" includes installed-tarball execution and is removed from every lane. Publication retains only package-integrity inspection.
• Candidate Evidence is not a package artifact. Its proposed JSON form is a small receipt that binds a successful PR run to the tested Git tree.
• PR and main commit SHAs may differ while their Git trees are identical. Candidate Evidence binds publication authority to the tree rather than assuming SHA equality.

Parked Branches

• Beta, canary, and npm staged publication remain parked.
• GitHub billing recovery and the next paid Actions attempt are external execution gates, not workflow-design decisions.
• Concrete test deletions remain owned by the integrated CI Test Suite Pruning requirements.