AnonTopics can get out of sync with named Topics

When the anonymous topic and named topics are out of sync, the stateChanglesOnly behavior breaks after a restart because the user expects the last known state stored in the named topic, but the anonTopic takes precedent.

We need to investigate how the topics got out of sync, and possibly changing the precedence to be in favor of the named topic.

Start by tracing how AnonTopics and named Topics are persisted and reconciled during restart, focusing on stateChanglesOnly behavior. Reproduce a case where the topics are out of sync, then establish and verify which topic supplies the last known state.

Written by the indexing model from the issue text.