fix: correct simulation severity mapping and transaction hash logging

Author: sudo-robi

Frontend/src/components/SimulateIncident.tsx

@@ -45,9 +45,8 @@ const SimulateIncident = () => {
 
       if (res.ok) {
         addLog("Transaction confirmed on-chain!");
-        const match = data.output?.match(/0x[a-fA-F0-9]{64}/);
-        if (match) {
-          addLog(`TX Hash: ${match[0]}`);
+        if (data.txHash) {
+          addLog(`TX Hash: ${data.txHash}`);
         }
         addLog(`Success: ${data.status}`);
       } else {

Frontend/src/pages/api/simulate-incident.ts

@@ -9,9 +9,8 @@ export default async function handler(req: NextApiRequest, res: NextApiResponse)
   const { type, priority, parentId } = req.body;
 
   // Severity mapping: Frontend sends 0(P0), 1(P1), 2(P2), 3(P3). 
-  // Contract expects uint256 severity. 
-  // We'll map high severity (P0, P1) to 3, P2 to 2, P3 to 1.
-  const severityScore = (priority === 0 || priority === 1) ? 3 : (priority === 2 ? 2 : 1);
+  // Contract expects uint256 severity (0: low, 1: med, 2: critical).
+  const severityScore = (priority === 0 || priority === 1) ? 2 : (priority === 2 ? 1 : 0);
 
   try {
     console.log(`🚀 Simulating incident: ${type} with severity ${severityScore}, parent: ${parentId || 0}`);