test: make the move-codex-session precision test fire its trigger once #136
Loading…
Reference in a new issue
No description provided.
Delete branch "test/move-codex-session-precision-trigger"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #132 from its review (finding).
The precision test's trigger fired for both inserted threads and moved 9007199254740993 to 9007199254740991. A double represents the second value exactly, so a snapshot that encoded integers through
Numberstill saw the change, and the test passed. The trigger now fires only for the root thread, leaving 9007199254740992, which a double cannot tell apart from the original.With
encodeSqliteValuechanged to returnNumber(value).toString(), the old test passes and the new one fails because the move exits 0. Both pass against the real encoder.move-codex-sessionprecision test fire its trigger onceReview
01M4H3Z15ZVGY6HP0X8N0RPG0B— heada63a687689b5aa837847e95349426d0dee28af26Review — j4k-oss/agent-skills @
c55fff69d7Scope: diff against base tree
40154724b696Status: dispatched — coverage complete (5/5 slots terminal)
Facts: current review-wide projection
Computed under:
Findings (0)
No findings survived.
Reviewed:
Other claims
Coverage
Coverage pass: 01M4H3Z1A055JP7WH46F9C3FAR
Accounting: complete
Slot health: healthy
move-codex-sessionshould handle Codex 0.160.1 and large native homes #132move-codex-sessionrollback should keep destination history rows it never copied #1339dfed55090a63a687689