fix: repair native lookup limits and incomplete evidence acceptance - #172
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
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.
Read-only diagnosis recovered the exact original readiness turns through documented App Server thread/read: each contains five items and a failed list_threads(limit: 100), not an absent model result. Desktop read_thread still exposes zero items; no claim to repair that host discrepancy. Cap native inventory at 50 in the skill and bilingual public prompts. A valid manager inventory still omitted the pair; title resolution and end-to-end onboarding remain open. Reject empty completed turns in the structural auditor, with a regression and retained native proof revalidation. Full npm test: 460 passed, one optional native skip, 55 schema cases and seven transitions, 146 Markdown files clean. New pinned workflow fetched anonymously with exact source parity. No new model turns, task resume, peer sends, installations or private storage reads. Corrected the existing community reply in place rather than adding a status-only comment.