Repository navigation
Prepare @proofable/mcp 0.1.7 for reviewer scan - #4
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![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: 102e7f0c3b
ℹ️ 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".
| | Check whether a qualifying proof already exists | `proofable_proofs_check` | | ||
| | Reuse a current proof or get the next verification step | `proofable_verify_or_guide` | | ||
| | Create or refresh a proof | `proofable_verify` | | ||
| | Prepare and submit a check needing another signer | `proofable_verify_prepare`, `proofable_verify_submit` | |
There was a problem hiding this comment.
When 0.1.7 is tagged, the release workflow publishes this package and registry manifest, but CHANGELOG.md still has an empty Unreleased section and ends at 0.1.6. As a result, the newly public prepare/submit workflow and changed Vault replacement behavior are absent from the repository's promised record of notable package, plugin, and skill changes; document them under Unreleased or a 0.1.7 section before release.
Useful? React with 👍 / 👎.
1 participant
Change
Update manifest and skill projection for explicit prepare/submit verification and aligned Vault guidance. Version 0.1.7 remains a candidate.
Evidence
npm run validate: passed.ssot:release-gate: passed.Acceptance boundary
Deploy matching protocol, perform live E2E, run portal rescan, and confirm reviewer acceptance before publication.