Repository navigation
v1.5.2
PageSift 1.5.2 Release Notes
Release Version:
v1.5.2
Release Scope: Transaction, temporal, scheduling, and adaptive-observation correctness fixes on the1.5line (v1.5.1 -> v1.5.2)
PageSift 1.5.2 resolves seven core correctness issues covering crash-atomic storage transactions, source identity isolation, censored adaptive statistics, point-in-time historical fidelity, and scheduling boundary safety across the storage, graph, planning, sync engine, HTTP API, CLI, MCP, C FFI, Node.js, and Python layers.
Highlights
- Crash-Atomic
AtomicTxCommits (pagesift-store): Replaced contiguous plain-record batch buffering with explicitTxPut,TxDel, andTxCommitrecords guarded by a streaming BLAKE3 transaction digest. Mid-batch crashes, partial writes,ENOSPC/sync failures, or corrupt trailing bytes roll back the entire transaction on recovery while keeping existing1.5.0/1.5.1segment data readable and compactable, withu32segment offset bounds enforced cleanly. - Delete-and-Recreate ABA Protection (
pagesift-store,pagesift-engine,pagesift-api,pagesift, bindings): Added persistent monotonicsgen:<source_id>generation tracking and uniqueinstanceIdvalidation on CAS spec updates andcommit_tick_atomic, preventing stale in-flight ticks from a deleted source from committing into a newly created source sharing the sameid. Checked source existence consistently across delta queries (/v2/sources/{id}/deltas, CLI, MCP, Node.js, Python). - Censored Adaptive Learning (
pagesift-plan,pagesift-engine): Classified sync fetch failures via structuredErrorCodeinstead of error-message matching. Transport errors (DNS failure, timeouts, connection resets), browser launch/render errors,304, andDirectBrowsercaptures now leavehttp_sufficient/browser_gaincensored (None) rather than recording false negatives, and fully censored observations no longer create emptyFamilyStatsentries. Hard budget exhaustion emits explicitBudgetExhausteddeferral without fabricatingTransientFailureorUnverifiedstates. - Point-in-Time Claim History Fidelity (
pagesift-graph,pagesift-store,pagesift-api,pagesift,pagesift-mcp): Stopped lossyClaimTimelineEntryinterval coalescing from merging distinct evidence/reason/metadata transitions or forginglast_confirmed_at_msatasOfquery time. Added checked claim and conflict historical queries that propagatehistoryUnavailableacross GraphStore,/v2/graph/*,pagesift graph inspect,pagesift_graph_query, C FFI, Node.js, and Python. - Numeric & Freshness Scheduling Bounds (
pagesift-engine,pagesift-api): Eliminatedcompute_next_due_at_msclamp panics when user-configuredminIntervalSecsexceeds the default tombstone interval, guardedTickBudgetLedgeragainstu64::MAX/u128 -> u64overflow, and neutralized non-finiteimportance_weightinputs. - Pre-Creation & Legacy Inventory Point-in-Time Isolation (
pagesift-store,pagesift-api,pagesift, bindings): SeparatedNotCreatedYet(spec: null),Complete, andHistoryUnavailableinload_spec_as_of()/build_state_view(), preventing future or stale-instance specs from leaking to earlier timestamps and fixing JavaScript safe-integerf64timestamp coercion forasOfqueries inloop_ops. Removed the time-filtered liveget_inventory()fallback when checkpoints are missing or evicted, surfacinghistoryUnavailableand propagating corrupt/I/O errors instead of silent fallbacks.
Verification
- Workspace checks run after the final edit:
check_release.py,check_wall_clock.py,check_workflows.py,check_links.sh,check_file_length.sh,cargo fmt --all --check,cargo deny --config .github/deny.toml check,clippy -D warnings, release tests across touched Rust crates, Node.js@pagesift/node, and Pythonpagesift.