Repository navigation
docs: focus release documentation on Docflow features - #31
Merged
Merged
Conversation
Rationale: record verified documentation work and its checked-PR completion boundary.
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.


Keep Docflow release documentation focused on its published features. Update the README, usage guide, site and packaged documentation while retaining the native-host qualification limits. The existing release-help URL and all legacy anchors now lead to concise Docflow package guidance with public release and installation links.
Plan 0082; Codex sole writer on
docs/public-release-scope. No skills, runtime logic, gates or versions changed. The fixture producer changes only receipt wording; its source-bound copy and manifest were refreshed together.Verification at work HEAD
56ba7e919d6d76f274f30b34b7da3944d3be84eb(all commands rerun successfully on completion HEAD0619dc6bd3fb282ec613d99856c9ad953ae95f3f):node scripts/verify.mjs: exit 0,verify: OK (version 0.10.0, 14 skills, 63 ADRs, 72 shipped plan items).node evals/run.mjs: exit 0, 13 passed, 0 failed, 0 skipped.node --test evals/repository-producer.test.mjs: exit 0, 27 passed.GEM_HOME=/tmp/hq-qa/docflow-release-pages-gems GEM_PATH=/tmp/hq-qa/docflow-release-pages-gems /tmp/hq-qa/docflow-release-pages-gems/bin/jekyll build --safe --source docs --destination /tmp/hq-qa/docflow-public-docs-pages: exit 0.python /tmp/hq-qa/check-docflow-public-docs.py: exit 0; 25 HTML pages, 873 local links/anchors, all 9 prior release-help IDs preserved, targeted public-content review passed.npm pack --json --pack-destination /tmp/hq-qa/docflow-public-docs-pack-work: exit 0; all 384 payload paths preserved, 15 intended documentation/receipt files changed, all remaining bytes identical. SHA-2563b1565892f0c9bbb837e2034ac0cfc45b1af0f66701799f07f83d63959aa8d69.Status at a glance
0619dc6bd3fb282ec613d99856c9ad953ae95f3f.Note
Refocuses public documentation on Docflow package features and installation guidance. Retains native-host qualification limits, the existing release-help URL and legacy anchors.
Fixture receipt wording and source-bound metadata are refreshed together; skills, runtime logic, gates and versions are unchanged.
Reviewed by Cursor Bugbot for commit 0619dc6. Bugbot is set up for automated code reviews on this repo. Configure here.