docs(mfa): drop the slice roadmap notes from comments

Author: dariusz-biela

src/components/MultifactorAuthentication/Context/MultifactorAuthenticationMainContext.tsx

@@ -87,7 +87,7 @@ function MultifactorAuthenticationContextProvider({children}: MultifactorAuthent
     const closeModal = () => send({type: 'CLOSE_MODAL'});
     const notifyModalClosed = () => send({type: 'MODAL_CLOSED'});
 
-    // The cancel-confirmation dialog lands in a later slice; until then every cancel path closes the modal directly.
+    // There is no cancel-confirmation dialog yet, so every cancel path closes the modal directly.
     const requestCancel = () => send({type: 'CLOSE_MODAL'});
     const hideCancelConfirm = () => send({type: 'CLOSE_MODAL'});
     const confirmCancel = () => send({type: 'CLOSE_MODAL'});

src/components/MultifactorAuthentication/machine/mfaMachine.ts

@@ -28,8 +28,7 @@ const DEFAULT_CONTEXT: MfaContext = {
 
 /**
  * MFA state machine. The top level models the modal lifecycle (`closed` -> `open` -> `closing`); the
- * child states of `open` map 1:1 to the screen the user currently sees. Later slices add screens as
- * `open` children and per-screen work as child states of its screen.
+ * child states of `open` map 1:1 to the screen the user currently sees.
  *
  * No state is `final`: one long-lived actor serves every MFA flow (a top-level final state would
  * stop it).
@@ -106,8 +105,7 @@ const MFAMachine = setup({
             },
             states: {
                 // This is the transparent initial screen, and its child states run the pre-screen
-                // work the user waits through. This slice adds the device check, and later slices add
-                // the registration and authorization steps as siblings.
+                // work the user waits through.
                 [MFA_STATE.PREPARING]: {
                     initial: MFA_STATE.VALIDATING_DEVICE,
                     states: {
@@ -122,9 +120,8 @@ const MFAMachine = setup({
                                     return {allowedAuthenticationMethods: context.scenario.allowedAuthenticationMethods};
                                 },
                                 // Every result enters the outcome resolver. A refusal stores its
-                                // blocking MFAError first; the resolver then selects failure from that
-                                // error, while an eligible device with no error selects success until
-                                // later slices insert registration and authorization before outcome.
+                                // blocking MFAError first, so the resolver selects failure from that
+                                // error, while an eligible device with no error selects success.
                                 onDone: [
                                     {guard: ({event}) => event.output.success, target: OUTCOME_TARGET},
                                     {target: OUTCOME_TARGET, actions: assign({error: ({event}) => getMFAFailureError(event.output)})},

src/components/MultifactorAuthentication/machine/types.ts

@@ -55,9 +55,7 @@ type MultifactorAuthenticationInitEvent<T extends MultifactorAuthenticationScena
 };
 
 /**
- * Events accepted by the machine. INIT starts a flow and the lifecycle events drive the modal. Other
- * semantic input events such as validate code and soft prompt are added by the slices that introduce
- * their states.
+ * Events accepted by the machine. INIT starts a flow and the lifecycle events drive the modal.
  *
  * CLOSE_MODAL requests the close so the flow moves to `closing`. MODAL_CLOSED is the navigator's
  * notification that the close animation fully finished, which moves `closing` to `closed` and wipes