feat: ship ReasonKit Think v0.2 governance release - #1
Merged
Conversation
added 26 commits
July 31, 2026 08:36
Adopt current protocol negotiation and model APIs while preserving the stdio transport and existing capability surface. Refresh transitive security fixes and extend compatibility probing through MCP 2026-07-28.
Define exact core, standard, and full discovery inventories and probe all supported protocol versions. Plant evidence-free verification and unknown-stage failures as a cross-stream runtime gate; the live matrix becomes green after protocol and governance integration.
Block published vulnerabilities with cargo audit while recording the eight reasonkit-mem warning advisories as explicit debt.
Default to the 13-tool governance path, retain exact 33/47-tool expansion packs, expose the active contract as a resource, and return dual text plus structured JSON tool results.
Remove the unbound reasonkit-mem cache and its transitive audit warnings while preserving the full-pack think_query name as an explicit experimental_memory_unavailable compatibility route.
Exercise criticality preservation, blocker-only consensus, transactional policy overrides, and scaffold-only convergence over the live MCP wire contract.
Treat only unset or agent as healthy and fall back safely for invalid or unavailable external modes. Narrow dual-format documentation to handler-generated application results.
Resolve bare MCP commands through PATH, preserve exact and version drift evidence, and fail closed on unrelated version output. Enforce package, Registry, and pinned cargo-dist validation without adding a release workflow.
Record primary-source MCP ecosystem findings, reconcile shipped v0.2 behavior, and define evidence-native v0.3 through protocol-stable v1.0 opportunities.
Reject reserved authorship-tag spoofing, require a trusted agent-authored frontier, exclude heuristic nodes from answers, align provenance, and cover the complete wire path.
Build cargo package verification in a dedicated target directory so extracted crate sources cannot poison development or smoke-test binaries.
# Conflicts: # README.md
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.
Summary
Verification
Release boundary
The GitHub integration is ready. The v0.2.0 tag and public release will be cut from the integrated commit. crates.io publication requires maintainer authentication or a configured trusted publisher; neither credential path is currently present in the repository.