Clean up end-user documentation - #4
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 40a6df0c77
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .\csokit.exe verify ".\game.cso" --deep --sha256 | ||
|
|
||
| Detect an input format: | ||
| Verification supports CSO, ZSO, and DAX where indicated by the command help. |
There was a problem hiding this comment.
For ZSO or DAX input, the basic form shown immediately above does not work: VerifyShallow rejects every format except CSO1/CSO2 as UnsupportedContainer. Since both this sentence and the release notes now advertise ZSO/DAX verification without that qualification, users can reasonably substitute those extensions and receive exit code 12; document that these formats require --deep and include a working example.
Useful? React with 👍 / 👎.
1 participant
Keep one practical end-user README.
Keep concise release notes and required legal notices.
Remove internal reports, archive files, scorecards, contributor notes, and duplicated documentation.
Full hardening verification passed.