Repository navigation
roadmap.yaml aggregate goes stale vs entries/ after main merges: generate it, stop committing it #5897
Description
check_roadmap_fragment_required.sh fails (#5862 twice, #5876) because the committed aggregate docs/roadmaps/roadmap.yaml drifts from entries/ whenever main merges. Fix: freeze roadmap-base.yaml, gitignore roadmap.yaml, generate via make roadmap-aggregate (and a CI step before sov.roadmap-valid). Readers listed in the PR.
Activity
ci: generate the roadmap aggregate in every section workspace; G4 + b…
ci: completion_is_cited scans the generated roadmap.yaml, not roadmap…
ci: judge the generated aggregates additively; G4 covers renames and …
ci: G5 Pmat-Ticket trailer check; G3b loads the fragment YAML (Refs #…
ci: G5 judges trailers as sov does (last paragraph), skips merge_grou…
ci: G3b reads fragments through roadmap_fragments.py, no inline pytho…
ci: G5 reads the PR range past .git/shallow and FAILs when unreadable…
ci: G5 self-test rows that fail without the shallow fallback; unreada…
fix(ci): #5901 guard-tree reds: ledger path follows the roadmap renam…
fix(ci): #5901 row-58 fixture names roadmap-base.yaml + entries/ (gen…
docs(#5901): state the Python growth plainly (Refs #5897)