docs: bound repository hygiene at release and installation - #20
Open
pcvantol wants to merge 1 commit into
Open
Conversation
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.
Coordinated documentation increment
PROJECT_HYGIENE_AND_REPOSITORY_RECONCILIATION_V1, coordinated with pcvantol/forge#59, pcvantol/engineering-platform#108 and pcvantol/workspace#17.Defines hygiene assessments as source/repository/operation-scoped inputs, not global release vetoes or substitutes for artifact integrity, publication and external CD authority. Unrelated retained branches do not block every release; genuinely applicable stale/missing mandatory evidence still blocks the dependent operation.
Installation/update/uninstall cannot prune project refs/worktrees, erase cases/receipts, delete rollback history or activate delete permission. Forge remains project reasoning owner and EP remains repository observation/mutation owner.
Adds architecture, scoped HY-P roadmap and parent roadmap entry. Documentary target only; all implementation/qualification remains PLANNED. No schema, source/runtime implementation, package version, manifest pin, workflow, credential, grant, actual cleanup, publication or installed state changes. No new first-canary prerequisite.
Coordinated DAG has been structurally checked locally (10 nodes / 13 dependencies). Owning hosted checks must qualify this exact PR head; no local full repository suite or host test is claimed.