Make Healthcheck easy to discover, try, and give safe feedback on - #13
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
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.
Visitors previously landed on a standards pitch and a workflow that required a hand-built FMT-002 fixture, even though the local Healthcheck preview can read their existing Codex Desktop logs. The English and Chinese README now lead with the working Git install, supported formats, and a direct first-run guide.
Adds an optional first-run issue form that separates first discovery from the reason for trying the tool, without requesting raw logs or full reports. A public casebook links the merged OpenLIT contribution and Urusilla counterexamples, distinguishing contributions from adoption. The older campaign table is repaired so project rows are no longer mixed into the invariants table.
Validation: 109 Healthcheck tests and selftest passed; issue-form YAML parsed; changed Markdown local links resolve; spec-drift and whitespace checks passed. No runtime changes. PyPI remains explicitly pending, and feedback is optional.