pr2.4

crates/console/prometeu-vm/src/virtual_machine.rs

@@ -26,7 +26,7 @@ pub enum LogicalFrameEndingReason {
     EndOfRom,
     /// Execution hit a registered breakpoint.
     Breakpoint,
-    /// A runtime trap occurred (e.g., OOB, invalid gate).
+    /// A runtime trap occurred (e.g., out-of-bounds access).
     Trap(TrapInfo),
     /// A fatal error occurred that cannot be recovered (e.g., stack underflow).
     Panic(String),

files/TODOs.md

@@ -1,54 +1,3 @@
-# PR-2.4 — Consolidate Trap and Error Surface
-
-### Briefing
-
-With HIP removed, the runtime trap surface must be simplified and aligned with the new stack+heap model.
-
-### Target
-
-* Define a minimal, coherent set of runtime traps.
-* Remove traps that only existed for HIP/RC semantics.
-
-### Work items
-
-* Audit the VM’s trap/error enums.
-* Remove HIP/RC-related traps.
-* Keep only traps that remain meaningful, such as:
-
-  * Illegal instruction.
-  * Stack underflow/overflow.
-  * Invalid jump target.
-  * Out-of-bounds memory access.
-* Ensure trap handling paths are consistent and deterministic.
-
-### Acceptance checklist
-
-* [ ] Trap enum contains only relevant traps.
-* [ ] No HIP/RC trap names remain.
-* [ ] VM compiles and tests pass.
-
-### Tests
-
-* Adjust any tests expecting removed trap codes.
-
-### Junie instructions
-
-**You MAY:**
-
-* Delete unused trap variants.
-* Refactor match statements accordingly.
-
-**You MUST NOT:**
-
-* Add new trap categories without approval.
-* Change the meaning of existing non-legacy traps.
-
-**If unclear:**
-
-* Ask before modifying trap semantics.
-
----
-
 # PR-2.5 — Prepare Call Frame Structure for Closures and Coroutines
 
 ### Briefing