Currently a primary may write resumability state when persistResumeState is called. When a primary shuts down, or rolls back after stepping down, it calls abortWithoutCleanup which also writes the state.

In the roll back case, the standby writing data on its own is definitely violating the disagg  contract. I think even when primary writes, it's also incorrect since the writes aren't replicated.

For the scope of this project we can skip writing this data for primary driven index builds.