Per-spec HasSubStateMachine placement
Part 16 §B.3 places the HasSubStateMachine reference on the parent
state node, not the FSM root. The fluent builder currently attaches
the reference from the FSM root because FluentFiniteStateMachineState
does not materialize per-state instance NodeStates — state nodes are
shared across all instances of the type. Browsing
HasSubStateMachine from the FSM root via GetSubStateMachineAsync
and the typed accessors above works against this wiring; clients that
strictly browse from the state node will not discover the sub-SM. A
future iteration may materialize per-state instance nodes to align
with the spec;
Per-spec
HasSubStateMachineplacementPart 16 §B.3 places the
HasSubStateMachinereference on the parentstate node, not the FSM root. The fluent builder currently attaches
the reference from the FSM root because
FluentFiniteStateMachineStatedoes not materialize per-state instance NodeStates — state nodes are
shared across all instances of the type. Browsing
HasSubStateMachinefrom the FSM root viaGetSubStateMachineAsyncand the typed accessors above works against this wiring; clients that
strictly browse from the state node will not discover the sub-SM. A
future iteration may materialize per-state instance nodes to align
with the spec;