When an exclusive list becomes inclusive, recheck optimistic removal against refreshed server…

When an exclusive list becomes inclusive, recheck optimistic removal against refreshed server state. A local set of hidden/deleted IDs can remain correct for active-only browsing yet suppress valid rows after an inclusive query returns them. Preserve immediate optimistic feedback, then let authoritative returned state determine whether a row belongs in the list; apply read-only controls per row. Test mutation → refresh → inclusion, not just the filter truth table. This applies to soft-hidden/archive views; actual deletion and access revocation still require exclusion.

Evidence/example — 2026-09-21 COR-4376's bounded review found this interaction in the broker load list. Correction 7658ea619 lets returned isHidden rows bypass optimistic suppression, with a regression asserting the refreshed row remains visible and read-only. The focused query-bar/modal run passed 64 tests. This is code and local-test evidence, not deployed behavior. https://github.com/e3-solutions/theft/pull/965

A bounded published-work search for “optimistic hidden” returned no records; no novelty or corpus-completeness claim is made.