Rasmus Rygaard 42bb50d502 Allow metadata updates without materializing threads (#38413) ...

## Why

Thread stores may filter a metadata patch to a no-op. Requiring every successful
update to return a `StoredThread` forces those implementations to materialize a
thread even when the caller does not need one.

## What changed

- Let `ThreadStore::update_thread_metadata` return `None` after a successful
  update that did not materialize a thread.
- Preserve the materialized-thread contract of `LiveThread` and `ThreadManager`
  metadata updates by reading the thread when the store returns `None`.
- Keep completion-only metadata updates from issuing that fallback read.

## Testing

Cover materialized in-memory updates and verify that fallback reads occur only
for callers that require the updated thread.

GitOrigin-RevId: 3059efc9d5b69e0b46e35fb5b5aa9638086654f2

2026-08-13 18:12:27 +00:00

..

local

Allow metadata updates without materializing threads (#38413)

2026-08-13 18:12:27 +00:00

error.rs

feat(app-server): add history_mode to thread (#29927)

2026-06-26 09:12:42 -07:00

in_memory.rs

Allow metadata updates without materializing threads (#38413)

2026-08-13 18:12:27 +00:00

lib.rs

Add durable reverts for paginated threads (#38292)

2026-08-13 01:56:24 +00:00

live_thread.rs

Allow metadata updates without materializing threads (#38413)

2026-08-13 18:12:27 +00:00

queue_store.rs

Add durable per-thread user submission queues (#36952)

2026-08-04 19:23:29 +00:00

store.rs

Allow metadata updates without materializing threads (#38413)

2026-08-13 18:12:27 +00:00

thread_metadata_sync.rs

Persist security risk scores in rollout history (#38363)

2026-08-13 12:04:29 +00:00

thread_sections.rs

Add appearance metadata to thread sections (#37898)

2026-08-10 23:32:42 +00:00

types.rs

Add durable reverts for paginated threads (#38292)

2026-08-13 01:56:24 +00:00