Repository navigation
Enforce portable canonical audits and reconcile v0.4.1 docs - #8
Merged
Merged
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
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.
New canonical tracking must not disclose machine-specific paths. This adds a tested publication check for SMALL YAML values and command-proof contents, plus matching agent policy, canonical guidance and changelog. Existing receipts remain unchanged. New path-bearing local captures are not in this branch.
The privacy check accepts relative paths and logical aliases, handles escaped YAML, Unix/Windows/home paths and untracked proofs, and reports record locations without repeating private values. CI runs it for branches, PRs, main and the reusable release workflow. SMALL v1.1.2 does not enforce this property itself; the upstream fix remains separate.
This also carries the prepared current-source documentation correction: implemented architecture, Getting Started, source/publication distinction and accurate SMALL version. Domain-specific quality targets remain adapter policy.
Validation: full Go tests, vet, privacy regressions, clean strict validation and source-bound bundle passed. Local package checks passed before the final named-home regression; the hosted workflow must rebuild the exact final source. The previous path-bearing candidate is rejected by the gate. The docs site must import and deploy the exact matching bundle before v0.4.1 publication. No paid plan, visibility change, force push or security weakening is involved.