Change exit codes for compute phase skip reason in bounce msg

Author: SpyCheese

crypto/block/transaction.cpp

@@ -3288,8 +3288,8 @@ bool Transaction::prepare_bounce_phase(const ActionPhaseConfig& cfg) {
                        .store_long(in_msg_info.created_at, 32)  // created_at:uint32
                        .finalize_novm());                       // original_info:^NewBounceOriginalInfo
     if (compute_phase->skip_reason != ComputePhase::sk_none) {
-      body.store_long(0, 8);                                // bounced_by_phase:uint8
-      body.store_long(compute_phase->skip_reason - 1, 32);  // exit_code:int32
+      body.store_long(0, 8);                             // bounced_by_phase:uint8
+      body.store_long(-compute_phase->skip_reason, 32);  // exit_code:int32
     } else if (!compute_phase->success) {
       body.store_long(1, 8);                          // bounced_by_phase:uint8
       body.store_long(compute_phase->exit_code, 32);  // exit_code:int32

doc/GlobalVersions.md

@@ -253,10 +253,10 @@ new_bounce_body#fffffffe
 - `original_info` - value, lt and unixtime of the original message.
 - `bounced_by_phase`:
   - `0` - compute phase was skipped. `exit_code` denotes the skip reason:
-    - `exit_code = 0` - no state (account is uninit or frozen, and no state init is present in the message).
-    - `exit_code = 1` - bad state (account is uninit or frozen, and state init in the message has the wrong hash).
-    - `exit_code = 2` - no gas.
-    - `exit_code = 3` - account is suspended.
+    - `exit_code = -1` - no state (account is uninit or frozen, and no state init is present in the message).
+    - `exit_code = -2` - bad state (account is uninit or frozen, and state init in the message has the wrong hash).
+    - `exit_code = -3` - no gas.
+    - `exit_code = -4` - account is suspended.
   - `1` - compute phase failed. `exit_code` is the value from the compute phase.
   - `2` - action phase failed. `exit_code` is the value from the action phase.
 - `exit_code` - 32-bit exit code, see above.