Repository navigation
fix(context): preserve complete query date ranges and clarification filters - #37
Merged
Merged
Conversation
This was referenced Oct 18, 2026
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.
Current main CI fails the live PostgreSQL Agent HTTP test because the new conversation context extracts a complete date range as two month prefixes. The extra incomplete context conditions are then rejected by the query contract's semantic coverage gate.
Recognize complete Chinese and ISO dates/ranges before year/month prefixes so followups retain day precision. Keep distinct ranges separate. Prevent an ISO date supplied as a clarification from also becoming a filter that replaces the inherited region. The compiler and permission checks are unchanged.
Add a no-network authenticated streaming regression using real platform metadata, context routing, compiler, SQL generation and audit, replacing only the model/tool harness and business database I/O. Assert both date boundaries and enforced row-policy bindings. Retain every permission assertion in the original live PostgreSQL test and make its stream-error diagnostic concise.
Validation: date extraction and HTTP regression failed before the fix; the ISO clarification regression also reproduced before correction. Fresh verification is listed below. No external business database or live model was used locally; PR CI verifies actual PostgreSQL and Chromium acceptance.
Fresh verification: npm test 574 tests (562 passed, 12 optional integration skips, 0 failures); npm run lint 0 errors / 7 existing warnings; npm run eval 14/14 fixtures with 2 L3 judgments pending. Independent review approved commit 2d3ec8a and reran 13 focused tests.
PR CI passed: standard tests/architecture/eval, real PostgreSQL integration and Chromium acceptance, plus both default and optional-PG Docker builds.