Repository navigation
Prepare v2.2.0 release and correct citation truncation markers - #15
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
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.
Bump engine/app version to 2.2.0 while retaining record schema_version 2.0.0, and correct citation-window truncation indicators. Left cuts now prefix
[truncated]…; right cuts suffix…[truncated]. Only sides actually cut receive markers, with the complete marked citation and all markers inside the 1,000-character cap. Windows that cannot fit remain rejected with the existing full-note UI notice.Regenerated the historical goldens and artifacts using the docs/testing.md acceptance clock, 2026-09-01T00:00:00Z. Audited every generated file before copying into the repository: six golden files change engine_version, five evaluation artifacts change engine_version, and status.json changes app_version, each 2.1.3 → 2.2.0. No other generated fields change. Policy snapshots, drift, provenance, sources and rulebook files remain unchanged.
Added docs/releases/v2.2.0.md covering PRs #11–#14, the two-step pre-demo monitor procedure, the exact copied-note/persistence/checkbox regexes, attestation context behavior, and remaining false-READY examples. Scratch evaluation confirms N1b, cross-sentence copy-forward, and laterality/attribution examples still reach READY with four attestations at the acceptance clock. Those limitations are stated plainly.
Validation:
[truncated]…+ 973 ×a+⟦完整 😀 citation⟧; right⟦完整 😀 citation⟧+ 973 ×b+…[truncated]; both[truncated]…+ 480 ×a+⟦完整 😀 citation⟧+ 481 ×b+…[truncated].PR #14 was merged with merge commit 34d622f before branching. The hosted main demo was rebooted via Streamlit Community Cloud and returned PENDING_VERIFICATION for the lumbar MRI smoke test; the expanded full note, neighboring context, and read-full-note captions were visible. This release branch remains unmerged and untagged; it is not deployed by that reboot.