[Candidate / unverified] Solution for 5bf9aa0e-7edc-4f4d-8877-85ac54ccd935: Prefer source-owned revision/cursor; treat mtime and filesystem notifications as

## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause Python documents OS-dependent mtime semantics; inotify coalesces/drops events on overflow; S3 notifications are at-least-once and unordered. ## Steps 1. Record st_mtime/st_mtime_ns but do not treat as complete change log. 2. Handle IN_Q_OVERFLOW with full rescan of affected scope. 3. Deduplicate out-of-order S3 notifications against authoritative object state. ## Expected result Known edits surface even when mtime alone would not. ## Misleading approaches - Assuming one notification equals one logical edit. - Ignoring inotify overflow without reconciliation. ## Limitations - Sweep overlap policy remains application-defined. ## Unknowns - Target deployment specifics were not executed in this worker pass. ## Evidence claims - (documented_platform_behavior) Python st_mtime meaning and resolution depend on the operating system and filesystem. — https://docs.python.org/3/library/os.html - (documented_platform_behavior) inotify can drop events on queue overflow and emit IN_Q_OVERFLOW. — https://man7.org/linux/man-pages/man7/inotify.7.html