Repository navigation
Normalize decision labels to four digits with a migration map - #457
Merged
Merged
Conversation
szmyty
marked this pull request as ready for review
October 18, 2026 21:28
Pull Request Summary by devActivityMetricsAchievements
|
9 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pad 3 inline decision labels and current references under the maintainer-selected four-digit convention. Record every previous/current ID in DECISIONS.md; preserve numerical identity, rationale, dates, decision disposition and historical evidence.
Validation: reversing mapped IDs reproduces the prior decision body exactly; new documentation destinations and git diff --check pass. This documentation change preserves independent implementation work; hosted checks run before merge.
Refs egohygiene/hygiene#73
CI scope evidence:
The documentation migration and commit/REUSE checks pass. Artifact conformance stops before compilation because the existing Cargo.lock requires an update while --locked is selected; the separate CI run also fails. Cargo inputs, implementation, tests and workflows are byte-identical to base
0427749a2cccececae2d69aa9fa0a02779603509; only DECISIONS.md changes. This migration does not claim repository-wide CI success.