Add plan-bounded resets for Fusion execution contexts

[michaelstaib]

No description provided.

[Copilot]

Pull request overview

This PR introduces plan-bounded reset behavior for OperationPlanContext to avoid clearing per-node state across the full allocated capacity when only a smaller subset of node slots is active for a given OperationPlan/IncrementalPlan. It also derives plan capabilities (dynamic schema names, batch nodes) to further limit what state is reset/cleared.

Changes:

• Add UsesDynamicSchemaNames / UsesBatchNodes capability derivation to OperationPlan and IncrementalPlan.
• Update OperationPlanContext pooling + per-event reset logic to clear only the active node slot range and only the state required by the plan’s capabilities.
• Add new tests covering subscription-event reuse resets and pool reuse across differently-sized plans (including an initialize-failure path).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/HotChocolate/Fusion/test/Fusion.Execution.Tests/Execution/OperationPlanContextResetTests.cs	Adds tests validating Begin() resets per-event state when the same context is reused for subscription events, and validates capability derivation.
src/HotChocolate/Fusion/test/Fusion.Execution.Tests/Execution/OperationPlanContextPoolingTests.cs	Adds pooling tests ensuring state from large plans doesn’t leak into smaller plans and that failed initialization returns the context to the pool.
src/HotChocolate/Fusion/src/Fusion.Execution/Execution/OperationPlanContext.Pooling.cs	Tracks active node slot count + plan capabilities during Initialize() and clears/disposes only the active range during Clean().
src/HotChocolate/Fusion/src/Fusion.Execution/Execution/OperationPlanContext.cs	Restricts per-event reset work to the active node slot range and capability-gated state.
src/HotChocolate/Fusion/src/Fusion.Execution/Execution/Nodes/OperationPlan.cs	Derives and stores plan capabilities (UsesDynamicSchemaNames, UsesBatchNodes) by scanning nodes.
src/HotChocolate/Fusion/src/Fusion.Execution/Execution/Nodes/IncrementalPlan.cs	Derives and stores plan capabilities (UsesDynamicSchemaNames, UsesBatchNodes) by scanning nodes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Patch coverage

100.0% of changed lines covered (83/83)

File	Covered	Changed	Patch %
…/src/Fusion.Execution/Execution/Nodes/IncrementalPlan.cs	15	15	100.0% 🟢
…/Fusion/src/Fusion.Execution/Execution/Nodes/OperationPlan.cs	15	15	100.0% 🟢
…/Fusion.Execution/Execution/OperationPlanContext.Pooling.cs	35	35	100.0% 🟢
…/src/Fusion.Execution/Execution/OperationPlanContext.cs	17	17	100.0% 🟢
…/Execution/Results/FetchResultStore.Pooling.cs	1	1	100.0% 🟢

---

Project coverage: 53.7% (230851/429607 lines)