Exercise Play Mode suspension across reload settings and in-flight work

[wallstop]

Context

PR #19 adds lifecycle guards that suspend Data Visualizer indexing, refresh, persistence, processor execution, asset mutations, and controls during Play Mode. It queues invalidation and resumes deferred work after returning to Edit Mode. The implementation is validated by compilation plus the existing EditMode and runtime PlayMode suites, but the transition matrix is not yet automated.

Scope

Add an editor integration suite or local Unity MCP scenario covering all four combinations:

• domain reload enabled / scene reload enabled
• domain reload enabled / scene reload disabled
• domain reload disabled / scene reload enabled
• domain reload disabled / scene reload disabled

Repeat transitions while the window is open and closed, including:

• object indexing in progress
• search-cache population in progress
• asset import/delete/move invalidation during Play Mode
• a window first enabled during Play Mode
• repeated enter/exit cycles and close/disable/destroy during each state

Acceptance criteria

• No package scheduler, delayed callback, asset postprocessor, processor constructor, or package-driven asset mutation runs during Play Mode.
• The last available view remains intact, the paused indicator is visible for suspended loads, and mutation/inspector controls are disabled.
• Invalidation is coalesced while paused and the minimum necessary work resumes after EnteredEditMode without duplicate subscriptions or stale-generation updates.
• Closing, script reload, and domain reload leave no recurring scheduled item or live-asset cache owned by the window.
• The scenario restores original Play Mode project settings even when a test fails.
• The report includes transition timings and verifies the Play-entry p95 budget independently for open/idle, open/indexing, and closed cases.

Related: #19

[wallstop]

Progress update from Unity 6000.4.6f1 MCP: with the Data Visualizer window open, I exercised one enter/exit cycle for all four domain-reload/scene-reload configurations. The window remained present and both global search and create controls reported disabled in Play Mode. The original host settings (enterPlayModeOptionsEnabled=true; DisableDomainReload | DisableSceneReload) were restored, and the editor was left in Edit Mode. In-flight indexing/search, repeated transitions, and timing coverage remain open.

[wallstop]

Follow-up MCP matrix evidence from PR #19 (Unity 6000.4.6f1, /Users/wallstop/Code/DataVisualizer):

• 300 temporary settings assets; two in-flight object-load cycles and one first-enable-during-Play cycle for each of the four domain-reload/scene-reload combinations.
• The combined schedule captured loading=True and pending=101 immediately before every Play request.
• All configurations reached suspended=True, disabled search/create controls, queued SignalRefresh as refreshQueued=True, and restored controls after Edit Mode.
• Domain-reload-enabled cases rebuilt deferred initialization. Reload-disabled cases retained loading=True, pending=101, and “Loading paused while playing”.
• First-enable-during-Play reached deferred=True and resumed cleanly in all four configurations.
• Cleanup removed the exact fixture and restored True|DisableDomainReload, DisableSceneReload.

Remaining gap: the unfocused MCP host did not automatically advance the scheduled object pump after resume for reload-disabled cases; the resumed snapshot still had 101 pending GUIDs. Search-cache work was already ready in this fixture, so this does not establish in-flight search suspension.

[wallstop]

Production follow-up for issue #20 is now in commit bf1817f.

The Data Visualizer no longer depends on a focused UI Toolkit scheduler for object/search batch continuations. A guarded, tracked EditorApplication.update pump is unregistered during Play Mode and cleanup, then scheduled on resume even when refresh invalidation was coalesced. Deferred reconstruction also clears stale queued-refresh state.

Unity MCP evidence on 6000.4.6f1:

• 300-asset fixture with object loading (101 pending) and search loading (201 pending) captured atomically before Play.
• During Play: suspended=True, both queues retained for reload-disabled cases, paused indicator visible, search/create controls disabled.
• After resume: both queues drained to zero, searchReady=True, queued=False without manual continuation.
• Close-during-Play and reopen passed in all four reload configurations with no live old window or pending queue.

Local gates: Unity EditMode 64/64, PlayMode 5/5, repository self-tests 7/7, benchmark/scenario tests 16/16, CSharpier, release-tree and 72-entry .unitypackage validation passed. Remaining issue #20 scope is asset import/delete/move invalidation and explicit script-reload/disable/destroy coverage plus separate Play-entry p95 cases.

[wallstop]

Validation update for 3843989:

• Python benchmark/scenario tests: 20/20.
• Unity 6000.4.6f1: full EditMode 64/64 and runtime PlayMode 5/5.
• Fresh MCP smoke with 225 disposable settings assets and reload disabled: real AssetDatabase.ImportAsset, MoveAsset, and DeleteAsset each queued refreshQueued=True while object/search work remained suspended, then resumed cleanly; the moved asset was restored and the fixture removed.
• Fixture-settings smoke selected Assets/Editor/DataVisualizerSettings.asset, confirming disposable settings assets do not replace the host settings.
• Domain-reload polling now retries transient MCP transport failures until the scenario deadline.

The full four-configuration matrix remains covered for the existing repeated/close/first-enable paths. A full mutation pass across domain-reload configurations remains an environment follow-up because the host MCP pipeline drops during the domain-reload transition.

[wallstop]

Completed a direct Unity MCP four-configuration matrix on Unity 6000.4.6f1 using a fresh 300-asset fixture per configuration. For domain+scene, domain-only, scene-only, and no-reload modes, each run passed two repeated in-flight cycles, real ImportAsset/MoveAsset/DeleteAsset callbacks with queued invalidation and drained work, script create/recompile while suspended, close-during-Play, and first-enable-during-Play. Final host state was Edit Mode with original reload settings restored, no fixture/probe, and no open window. The remaining issue scope is explicit disable/destroy cleanup coverage.

[wallstop]

Follow-up validation: the new destroy-during-Play cycle was run across all four reload configurations on Unity 6000.4.6f1 with a 300-asset fixture. Each case destroyed the real window while suspended, observed zero remaining window instances, exited Play Mode, reopened successfully with suspended=False, loading=False, pending=0, searchPending=0, and searchReady=True, then cleaned the fixture and restored True|DisableDomainReload, DisableSceneReload. This closes the explicit destroy/disable cleanup gap.