docs: retire maintainer-only validation artifacts - #17
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: ebecedee52
ℹ️ 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".
| - Removed the maintainer-only Turkish acceptance guide, pilot-study templates, | ||
| and the obsolete Codex capability probe matrix from the public package. |
There was a problem hiding this comment.
The pilot tooling is still part of the public package and CLI (cewp pilot create, record, status, and export), but this removal eliminates its only workflow guide. A repo-wide search leaves only one-line help entries and historical release notes; in particular, users invoking pilot record --from have no supported documentation for constructing or classifying the required pilot-observation/v1 input. Either retain a current public pilot-command reference or stop exposing these commands as a supported package surface.
Useful? React with 👍 / 👎.
| assert(previousIndex > releaseIndex, "Phase 12 release precedes earlier release history"); | ||
| const unreleased = releaseNotes.slice(unreleasedIndex, releaseIndex); | ||
| assert(/No changes yet|Manual acceptance/i.test(unreleased), "Unreleased truthfully records current post-beta work"); | ||
| assert(/\S/.test(unreleased), "Unreleased truthfully records current post-beta work"); |
There was a problem hiding this comment.
This assertion is now unconditional whenever the preceding ordering check passes, because unreleased always contains the non-whitespace text ## Unreleased. If a future change removes every note beneath that heading, the contract will still report that post-beta work is truthfully recorded. Test the section after stripping the heading, or require an expected empty-state/change entry.
Useful? React with 👍 / 👎.
Summary
Validation