Real-time index of opencode sessions
doc: clarify all alternative designs use watchman for change detection
+3
-1
+3
-1
doc/discovery/watchman.md
+3
-1
doc/discovery/watchman.md
···
506
506
507
507
## Appendix: Alternative Design Sketches
508
508
509
+
All alternatives below use watchman for change detection — the subscription and event loop are the same. The difference is what happens *after* watchman tells us a file changed: how we track, invalidate, and reload affected in-memory objects.
510
+
509
511
### A. Channel-Driven Eager Reload
510
512
511
-
Instead of dirty-tracking, the watcher task classifies events into `SessionEvent` variants and sends them over a `tokio::sync::mpsc` channel. A dedicated consumer task eagerly reloads affected objects.
513
+
The watcher task classifies watchman events into `SessionEvent` variants and sends them over a `tokio::sync::mpsc` channel. A dedicated consumer task eagerly reloads affected objects.
512
514
513
515
```rust
514
516
// Watcher produces typed events