You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes from the review of the previous commit.
The flag was silently dropped on daemon-delegated pushes: when the local daemon
owns the archive, `pg push` posts to /api/v1/push/pg, and neither the request
nor the handler carried it, so the whole archive was backfilled anyway. It now
travels in the request and maps into SyncOptions.
Whether --full was requested cannot be decided inside Push: callers pass
`cfg.Full || didResync`, so any automatic resync looked like explicit intent and
disabled the flag. The precedence is resolved at the CLI instead, where the
user's own flag is known.
The boundary scoped session selection only, while other phases stayed
archive-wide, so pre-boundary content was uploaded regardless. A bounded push
now refuses when a vector source is attached, because embeddings carry raw text
and cannot be bounded, and skips cursor usage events for the same reason a
filtered push already skips them: the rows are global and unattributed.
Freshness is now proven rather than inferred. The reset paths clear the
watermark, so an empty watermark alone could not distinguish a genuinely new
target from an established one whose marker was lost or whose first push failed
part-way, and re-seeding there would permanently skip the history those resets
exist to restore. Boundary state, marker presence, and whether a reset ran on
this pass are all required.
Also documents the flag and its interactions in the command reference.
0 commit comments