feat: Implement RunStep error reporting and refactor charge sequences

- Added RunStepErrorCode to Xbee status protocol and CResult.

- Defined detailed operational error codes in EnumData.cs.

- Updated _SM_RUN_*.cs to report specific error codes before proper error transitions.

- Renamed and refactored charge-related sequence files.

Cs_HMI/Project/Class/CResult.cs

@@ -41,6 +41,7 @@ namespace Project
         public string Memo;
         public eResult ResultCode { get; set; }
         public eECode ResultErrorCode;
+        public eECode RunStepErrorCode { get; set; }
         public string ResultMessage { get; set; }
         public Boolean isError { get; set; }
         public int retry = 0;
@@ -192,6 +193,7 @@ namespace Project
             Memo = string.Empty;
             isError = false;
             ResultCode = eResult.NoError;
+            RunStepErrorCode = eECode.NOERROR;
             ResultMessage = string.Empty;
         }
 

Cs_HMI/Project/Class/EnumData.cs

@@ -50,7 +50,7 @@ namespace Project
         NOERROR,
         EMERGENCY,
         NOMODELV,
-        USER_STOP ,
+        USER_STOP,
         USER_STEP,
 
         AGVCONN,
@@ -65,8 +65,20 @@ namespace Project
         DION,
 
         NOTALLOWUP,
-    }
 
+        // Operational Errors
+        CART_EXIST,
+        MARK_TIMEOUT,
+        MARK_SENSOR_FAIL,
+        LIFT_ERROR,
+        AGV_SPEED_FAIL,
+        AGV_STOP_FAIL,
+        PATH_INTEGRITY_FAIL,
+        TURN_FAIL,
+        NO_CHARGEPOINT,
+        NOTSET_CHARGEPOINT,
+        ALREADY_CHARGE,
+    }
 
     public enum eResult : byte
     {