Repository navigation
test(projects): measure released extraction contract boundaries - #176
Merged
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.
Project-context claims need more than valid JSON and a matching quote. Add a bounded, manual synthetic study of released
@wirecat/cli-core/documentsextractMemorieson Core0.358.0/Base0.47.1, using 33 fake-completion cases and the existing external-I/O guard. Record package integrity, executed function/entry/fixture/runner hashes and metadata-only outcomes; link the study from the project index and metric process.The study preserves observed boundaries: unknown kinds reject, unsupported fields are accepted then stripped, length/count limits and exact substrings are enforced, and one bad quote rejects a batch. It explicitly demonstrates accepted contradictory claims and wrong attribution using a shared exact quote. External message/mail/document/meeting labels remain outside the SDK contract. Fake responses are not an LLM quality, semantic entailment or attribution evaluation.
Validation: 33 cases matched (16 accepted/17 rejected), targeted Biome, full docs check, targeted Markdown and spelling, staged gitleaks, and diff checks pass. All commands used isolated HOME/XDG/store/state/TMPDIR; retained SDK prefix manifests and lock integrity matched exact releases. No store API, model/network call, live account, new runtime dependency, CI suite or frozen benchmark modification. No production extraction/proposal behavior changed. The installation lock hash is run-specific, not a retained portable dependency lock.