added comments for clarity

Author: praveendurai-okta

src/v2/view-builder/views/nfcPin/EnrollNfcPinView.js

@@ -31,7 +31,7 @@ const DeviceChallengeBody = BaseOktaVerifyChallengeView.extend({
 });
 
 /**
- * Phase 3: PIN creation — same pattern as EnrollAuthenticatorPasswordView
+ * Phase 2: PIN creation — same pattern as EnrollAuthenticatorPasswordView
  */
 const PinCreateBody = BaseForm.extend({
   className: 'nfc-pin-create',

src/v3/src/transformer/i18n/transformLaunchAuthenticatorButton.ts

@@ -27,6 +27,8 @@ export const transformLaunchAuthenticatorButton: TransformStepFn = (
     predicate: (element) => element.type === 'LaunchAuthenticatorButton',
     callback: (element) => {
       const { options } = element as LaunchAuthenticatorButtonElement;
+      // Supports authenticator-specific labels (e.g. NFC PIN uses 'oie.nfc_pin.launch.button')
+      // Falls back to OktaVerify label for backward compatibility
       const labelKey = options?.i18nKey || 'oktaVerify.button';
       addTranslation({
         element,

src/v3/src/transformer/nfcPin/transformNfcPinCreate.ts

@@ -46,7 +46,7 @@ export const transformNfcPinCreate: IdxStepTransformer = ({
   // PIN settings — map to PasswordSettings format
   const rawSettings = (
     relatesTo?.value?.settings
-    // @ts-ignore enrollmentAuthenticator may not be typed
+    // @ts-expect-error enrollmentAuthenticator may not be typed
     || context?.enrollmentAuthenticator?.value?.settings
     || {}
   ) as { minLength?: number; maxLength?: number };