fix(compiler): correct CIE semantics and diagnostic locations

Use standard WHILE headers and default-public class fields, resolve
pseudocode identifiers without case sensitivity, and check signed i64
literal boundaries before conversion. Preserve source locations across
recursive emission and function diagnostics.

Add 22 regression cases and update compiler examples and documentation.
Validated all 69 CTest entries with the original Linux Actions seed and
verified the release package's embedded, native and IR output paths.

3 files changed, 13 insertions, 0 deletions

diff --git a/tests/iii/integer-bound-overflow/case.json b/tests/iii/integer-bound-overflow/case.json
new file mode 100644
index 0000000..6421b0f
--- /dev/null
+++ b/tests/iii/integer-bound-overflow/case.json
@@ -0,0 +1,8 @@
+{
+  "errors": [
+    {
+      "reason": "Integer\\ literal\\ is\\ outside\\ the\\ i64\\ range",
+      "line": 1
+    }
+  ]
+}
diff --git a/tests/iii/integer-bound-overflow/notes.md b/tests/iii/integer-bound-overflow/notes.md
new file mode 100644
index 0000000..1c3171a
--- /dev/null
+++ b/tests/iii/integer-bound-overflow/notes.md
@@ -0,0 +1,3 @@
+# integer-bound-overflow
+
+The compiler must reject this program: Integer literal is outside the i64 range. The diagnostic must identify line 1; compilation must preserve existing output.
diff --git a/tests/iii/integer-bound-overflow/program.cps b/tests/iii/integer-bound-overflow/program.cps
new file mode 100644
index 0000000..6bdd156
--- /dev/null
+++ b/tests/iii/integer-bound-overflow/program.cps
@@ -0,0 +1,2 @@
+PROCEDURE Bad(Values : ARRAY[0:9223372036854775808] OF INTEGER)
+ENDPROCEDURE