You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description:
The "PR Validation Pipeline" section in docs/architecture/workflows.md no longer accurately describes pr-validation.yml after PR #2213 introduced the pr-validation-success aggregator gate and gate-completeness-check job.
Specific stale content:
Line 124 states the workflow "runs 16 parallel jobs" — the workflow now has 31 jobs (29 validation jobs + pr-validation-success gate + gate-completeness-check).
Line 177 states "All jobs run in parallel with no dependencies" — this is incorrect now that pr-validation-success has a needs: list covering all 29 other jobs, and gate-completeness-check enforces that needs: list stays complete.
The jobs table (lines 157–175) is missing the new gate and completeness-check jobs, and is also missing many of the 29 validation jobs added since this section was last written.
The Mermaid flowchart does not reflect the aggregator gate structure.
Describe the pr-validation-success aggregator gate as the single required status check that gates merge, and gate-completeness-check as the job that enforces gate completeness.
Update the jobs table to include all current jobs.
Update or replace the Mermaid diagram to reflect the gate-based dependency structure.
Steps to Reproduce:
See PR #2213 (ci(workflows): add PR validation merge gate and fix docusaurus workflow) for the changes that introduced the gate.
Component: Documentation
Bug Description:
The "PR Validation Pipeline" section in
docs/architecture/workflows.mdno longer accurately describespr-validation.ymlafter PR #2213 introduced thepr-validation-successaggregator gate andgate-completeness-checkjob.Specific stale content:
pr-validation-successgate +gate-completeness-check).pr-validation-successhas aneeds:list covering all 29 other jobs, andgate-completeness-checkenforces thatneeds:list stays complete.Expected Behavior:
The section should:
pr-validation-successaggregator gate as the single required status check that gates merge, andgate-completeness-checkas the job that enforces gate completeness.Steps to Reproduce:
See PR #2213 (
ci(workflows): add PR validation merge gate and fix docusaurus workflow) for the changes that introduced the gate.Additional Context:
Stale documentation:
docs/architecture/workflows.md— PR Validation Pipeline section (lines ~122–177)Authoritative source:
.github/workflows/pr-validation.ymland.github/workflows/README.mdReviewed and validated by a qualified human reviewer