typecheck: diagnose missing CHECK TYPE expression

README.md

@@ -153,6 +153,12 @@ If the learner leaves out the expression as well, the checker explains all three
 CHECK TYPE needs an expression, IS, and a type. Try: CHECK TYPE score IS NUMBER.
 ```
 
+If `IS` is present but the expression is missing, Claro points out that the expression belongs before `IS`:
+
+```text
+CHECK TYPE needs an expression before IS. Try: CHECK TYPE score IS NUMBER.
+```
+
 If the learner writes `IS` but leaves out the expected type, Claro names the missing piece and shows a complete example:
 
 ```text

docs/CURRENT_STATUS.md

@@ -54,6 +54,7 @@ Ready now:
 - `CHECK TYPE` gives a direct repair hint when the learner forgets the `IS` keyword, for example `CHECK TYPE score` reports `CHECK TYPE needs IS. Try: CHECK TYPE score IS NUMBER.`
 - `CHECK TYPE` gives a direct repair hint when `IS` has no expected type, for example `CHECK TYPE score IS` reports `CHECK TYPE score needs a type after IS. Try: CHECK TYPE score IS NUMBER.`
 - `CHECK TYPE` explains when the learner leaves out the expression as well, for example bare `CHECK TYPE` reports `CHECK TYPE needs an expression, IS, and a type. Try: CHECK TYPE score IS NUMBER.`
+- `CHECK TYPE` explains when `IS` is present but the expression is missing, for example `CHECK TYPE IS NUMBER` reports `CHECK TYPE needs an expression before IS. Try: CHECK TYPE score IS NUMBER.`
 - `CHECK TYPE` rejects extra words after a valid expected type with a direct repair hint, so `CHECK TYPE score IS NUMBER TEXT` explains that only one type belongs in the check
 - `CHECK TYPE` rejects unknown expected type names with a beginner-facing list of supported types
 - typed list/map checks through `claro typecheck`, including a nested `LIST OF MAP` insertion example

docs/ROADMAP.md

@@ -77,6 +77,7 @@ Keep declared return types honest: `claro typecheck` now reports friendly diagno
 
 8q.2. Keep `CHECK TYPE` declarations unambiguous: extra words after a valid expected type now get a direct repair hint instead of being reported as an unknown type.
 8q.3. Keep `CHECK TYPE` declarations complete: a bare `CHECK TYPE` now explains that the expression, `IS`, and expected type are all required, with a complete repair example.
+8q.4. Keep `CHECK TYPE` declarations ordered: `CHECK TYPE IS NUMBER` now explains that an expression belongs before `IS`, with a complete repair example.
 
 ### 1. Strong static types
 

tests/typecheck_missing_expression_with_is_bad.claro

@@ -0,0 +1 @@
+CHECK TYPE IS NUMBER

tools/validate_typecheck_diagnostics.py

@@ -299,6 +299,9 @@ EXPECTED = {
     "tests/typecheck_missing_expression_bad.claro": [
         "tests/typecheck_missing_expression_bad.claro:1: CHECK TYPE needs an expression, IS, and a type. Try: CHECK TYPE score IS NUMBER.",
     ],
+    "tests/typecheck_missing_expression_with_is_bad.claro": [
+        "tests/typecheck_missing_expression_with_is_bad.claro:1: CHECK TYPE needs an expression before IS. Try: CHECK TYPE score IS NUMBER.",
+    ],
     "tests/typecheck_extra_check_type_tokens_bad.claro": [
         "tests/typecheck_extra_check_type_tokens_bad.claro:2: CHECK TYPE score has extra text after type NUMBER. Keep only the expression, IS, and one type.",
     ],