@@ -654,7 +654,7 @@ refresh and checkpoint publication finish, including failed checkpoint retries.
654654Candidate files are opened through the view's retained snapshot reader. Every
655655query ends with a root-verified epoch check, including empty and filename-only
656656responses; replacing the directory cannot pair old candidates with a new root.
657- Both auto and poll modes perform full
657+ In the legacy v1 daemon, both auto and poll modes perform full
658658verification every ` --poll-interval ` seconds after completion (default 120), also
659659repairing missed bytes, ignores and external Git/global configuration changes.
660660Native notifications allow earlier incremental repair. ` --no-watch ` disables
@@ -1299,26 +1299,52 @@ Under the view's work/publication gates, tgrep checks the exact current pin,
12991299checkpoint and input epoch before completing such a job without changing the
13001300ready view or invalidating its readers. Its original token/request is retained;
13011301the terminal receipt reports ` coalesced: true ` , the existing reconciled epoch
1302- and zero new reconciliation work. This does not postpone periodic verification.
1303- Explicit refresh always verifies; periodic repair, watcher uncertainty and
1302+ and zero new reconciliation work. This does not postpone polling verification.
1303+ Explicit refresh always verifies; polling repair, watcher uncertainty and
13041304rescan events invalidate for full verification before queuing reconciliation.
13051305A newer invalidation therefore cannot be skipped by the coalescing check.
13061306
1307- ** Recurring-repair limitation:** the bounded initial pipeline does not eliminate
1308- periodic full verification. This implementation has no integrated, lossless
1309- checkout change journal. File timestamps, Windows ` ChangeTime ` , a clean Git
1310- status, or a drained watcher queue do not prove absence of unreported writes
1311- (including active/mapped writers). An unavailable/inactive journal, including on
1312- ReFS, must not be treated as an empty journal. First attachment/restore, explicit
1313- full refresh, watcher error/overflow, Git/ignore changes and periodic fallback
1314- therefore continue to require full verification. The default 120-second interval
1315- after completion is retained, not silently lengthened or disabled.
1316- Online ` namespace.status ` , ` views.status ` and ordinary ` status ` expose
1317- ` reconciliation_policy ` with ` periodic_full_verification ` , ` interval_ms ` ,
1318- ` incremental_coverage: "unavailable" ` , ` change_journal: "not-integrated" ` ,
1319- ` full_verification_reason: "no-trusted-change-coverage" ` and repair triggers.
1320- ` --no-watch ` explicitly disables automatic repair; it does not supply coverage
1321- evidence or skip first-attachment verification.
1307+ ** Managed update policy:** healthy native-watcher views have no timer-driven
1308+ full-reconciliation safety pass. Elapsing the former 120-second interval does
1309+ not invalidate or reread an otherwise quiet ready view. Silently missed changes
1310+ can therefore remain stale indefinitely, even while ready. This is an explicitly
1311+ accepted staleness tradeoff, not proven coverage. There is no integrated lossless
1312+ checkout change journal; timestamps, Windows ` ChangeTime ` , clean Git status and
1313+ a drained watcher queue still do not prove absence of unreported writes
1314+ (including active/mapped writers). An unavailable/inactive journal is not an
1315+ empty journal and does not justify skipping initial content verification.
1316+
1317+ First attachment/restore, explicit full refresh, reported watcher error/overflow
1318+ or rescan, and observed Git/ignore changes retain full verification and the
1319+ existing publication gates. Normal native file events still invalidate their
1320+ paths. Explicit ` --watch-mode poll ` and actual native-watcher unavailability,
1321+ failure or budget exhaustion use periodic full reconciliation as their update
1322+ mechanism, not a redundant native safety pass. They wait ` --poll-interval `
1323+ seconds after completion (default 120). ` --no-watch ` disables both automatic
1324+ update mechanisms but not initial verification or explicit refresh. Legacy v1
1325+ and ordinary-server policies are unchanged.
1326+
1327+ ` hello ` advertises ` event-driven-native-reconciliation ` . Online ` views.status `
1328+ and ordinary ` status ` expose the effective ` watch_mode ` , ` watch_fallback ` and
1329+ ` reconciliation_policy ` . It reports ` native_periodic_full_verification: false ` ,
1330+ ` native_missed_changes: "may-remain-stale-indefinitely" ` ,
1331+ ` incremental_coverage: "unavailable" ` and ` change_journal: "not-integrated" ` .
1332+ ` periodic_full_verification ` is true only for an effectively polling view;
1333+ ` interval_ms ` is then its active interval and ` full_verification_reason ` is
1334+ ` "polling-update-mechanism" ` . Both fields are null otherwise. The configured
1335+ ` poll_interval_ms ` remains visible even when no periodic work is enabled;
1336+ ` configured_watch_mode ` is ` auto ` , ` poll ` or ` disabled ` .
1337+
1338+ Online ` namespace.status ` and ` maintenance.status ` distinguish configuration
1339+ from effective per-view behavior: the same policy has
1340+ ` scope: "monitored-views" ` plus ` native_views ` , ` polling_views ` and ` disabled_views `
1341+ counts. Its ` periodic_full_verification ` means at least one monitored view is
1342+ polling, not that all views have a safety timer. A namespace configured as
1343+ ` auto ` can contain both healthy native views and fallback-polling views. With
1344+ no polling monitors its active interval/reason are null, even if polling is
1345+ configured for future views. Repair triggers include ` poll-interval ` only when
1346+ polling is active. Use explicit refresh or ` --no-index ` when watcher-dependent
1347+ freshness is insufficient.
13221348
13231349` views.adaptive ` takes ` view ` , ` owner ` , ` expected_version ` , ` allocation_version `
13241350in an operation envelope. Adaptive policy evaluates the worktree's captured
0 commit comments