Skip to content

Keep one root usage README and enforce the documentation boundary - #5

Merged
nicodes merged 1 commit into
docs/readme-boundary-base-20261029from
docs/readme-boundary-clean-20261029
Oct 30, 2026
Merged

nicodes merged 1 commit into
docs/readme-boundary-base-20261029from
docs/readme-boundary-clean-20261029

Conversation

@nicodes

@nicodes nicodes commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Keep one root README with client installation, configuration and usage. Maintain authored documentation in the private documentation repository, retain functional inputs under non-Markdown names, and enforce the layout and reviewed README digest in CI.

Validation: canonical publication/layout checks pass; functional plugin migrations were regression tested. The documentation-policy job validates this exact head.

This PR uses a cleaned base so its diff contains no removed private material. After exact-head checks pass, the approved head will replace the original public main during the separately recorded leased history cleanup.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

@nicodes
nicodes merged commit 7fbd1ea into docs/readme-boundary-base-20261029 Oct 30, 2026
4 checks passed
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