feat(lang): def REGISTRY from "file.lres" - a game fills an open registry from its own file

The entries are read and checked against the registry's record as a
registry ... from file is, errors at the resource file's line, and they
are defs of the module that wrote the line: the registry must be open to
it, and they take that module's place in the stable order. Reseed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

examples/rejected/bad_recipes.lres

@@ -0,0 +1,3 @@
+# bad_recipes.lres - the second entry gives minutes as text
+tea { name: "Pine tea", minutes: 5 }
+splint { name: "Splint", minutes: "twenty" }

examples/rejected/craft_kit/index.ludic

@@ -0,0 +1,8 @@
+# craft_kit/index.ludic - an open registry of recipes
+module crafting
+export property Recipe {
+  key: string = ""
+  name: string = ""
+  minutes: int = 0
+}
+export open registry Recipes of Recipe as RC

examples/rejected/registry_extend_field.ludic

@@ -0,0 +1,8 @@
+# L8 + L9: a resource file that extends a registry is checked against its record, at its own line
+import "craft_kit"
+program RegistryExtendField {
+  def Recipes from "bad_recipes.lres"
+  entry {
+    print(RC_COUNT)
+  }
+}