Keep continuing task checkpoints current across revisions - #573
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.
A continuing task could lose its latest checkpoint or notes after repeated edits: task_update_fields appended old and new values until the bounded reader excluded the newly written state. The paper-email responsibility demonstrated this as a task_update_readback_mismatch.
Use the existing singleton editor for current optional task fields, retaining replaced TextValues for recovery. This keeps checkpoint, evidence, progress, notes and role fields current without changing authority or adding a history store.
Validation: 85 targeted task, continuation and storage tests pass. The new storage test reproduces legacy overflow, then verifies 55 revisions through actual text persistence, task point/list reads and the canonical effect receipt; unrelated content, another task and translations survive. The previous additive behaviour fails this same test. Clear and repeated-value cases pass. No new Ruff findings; the two existing files retain their prior lint baseline.
Jira: JVNAUTOSCI-2244. This supports the continuing-responsibility programme under JVNAUTOSCI-2721; it does not establish paper adequacy or activate recurrence.