[Epic] Regression safety for multi-system support #72
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ensure adding new systems never regresses 1962. Done when the full multi-system matrix runs in CI and the output contract carries the active rubric system.
Epic — child issues are tracked as sub-issues.
Epic complete — PR #457 (
be94e04) merged to develop. Children #73 (per-system CI oracle matrix) and #74 (active rubric-system stamp) done, plus #332 (per-edition commemoration limit). The multi-system matrix runs each edition against its own oracle gate, the output contract carries the active rubric system (edition) and its per-edition commemoration cap, and the 1962 golden fixture stays byte-identical throughout. 836 tests green; adversarial review clean after two doc fixes.