Skip to content

Refresh ProcessMapping drift canary: 10/78 → 13/89 - #16

Merged
ProfessorPolymorphic merged 1 commit into
mainfrom
fix-processmapping-drift-canary
Jul 9, 2026
Merged

Refresh ProcessMapping drift canary: 10/78 → 13/89#16
ProfessorPolymorphic merged 1 commit into
mainfrom
fix-processmapping-drift-canary

Conversation

@ProfessorPolymorphic

Copy link
Copy Markdown
Contributor

The live ui-insight/ProcessMapping data/allowed_values.json has grown to 13 controlled-value groups / 89 values (new groups: CoverageAssertionMode, CoverageDepth, CoverageStatus, RedactionStatus, …), but scripts/check_governance_drift.py still asserted the old 10 / 78. That made the drift canary fail on every PR that runs the drift workflow — a latent failure, since no recent PR had touched vendor/data-governance downstream.

Updates the expected counts to match the live registry. Pre-existing drift, unrelated to the concurrent paused-status work.

The live ui-insight/ProcessMapping repo's data/allowed_values.json grew to
13 controlled-value groups / 89 values (added CoverageAssertionMode,
CoverageDepth, CoverageStatus, RedactionStatus, etc.). The drift canary
still expected 10/78, so it failed on any PR that runs the drift workflow.
Update the expectation to match the live registry.
@ProfessorPolymorphic
ProfessorPolymorphic merged commit 74e1341 into main Jul 9, 2026
1 check passed
@ProfessorPolymorphic
ProfessorPolymorphic deleted the fix-processmapping-drift-canary branch July 9, 2026 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant