Require explicit extern members in extern class/object and update docs

notes/kotlin_bridge_binding.md

@@ -12,6 +12,9 @@ This note describes the Lyng-first workflow where a class is declared in Lyng an
 - Kotlin can store two opaque payloads:
   - `instance.data` (per instance)
   - `classData` (per class)
+- `extern class` / `extern object` are pure extern surfaces:
+  - all members in their bodies must be explicitly `extern`;
+  - Lyng member bodies inside extern classes/objects are not supported.
 
 ## Lyng: declare extern members
 
@@ -70,3 +73,4 @@ LyngClassBridge.bind(className = "Foo", module = "bridge.mod", importManager = i
 - Use `init { ... }` / `initWithInstance { ... }` with `ScopeFacade` receiver; access instance via `thisObj`.
 - `classData` and `instance.data` are Kotlin-only payloads and do not appear in Lyng reflection.
 - Binding after the first instance of a class is created throws a `ScriptError`.
+- If you need Lyng-side helpers for an extern type, add them as extensions, e.g. `fun Foo.helper() = ...`.

notes/new_lyng_type_system_spec.md

@@ -276,6 +276,7 @@ Map inference:
 - `{ "a": 1, "b": "x" }` is `Map<String,Int|String>`.
 - Empty map literal uses `{:}` (since `{}` is empty callable).
 - `extern class Map<K=String,V=Object>` so `Map()` is `Map<String,Object>()` unless contextual type overrides.
+- `extern class` / `extern object` are declaration-only; members in their bodies must be explicitly marked `extern`.
 
 Flow typing:
 - Compiler should narrow types based on control-flow (e.g., `if (x != null)` narrows `x` to non-null inside the branch).