fix(app): re-export _call_rpc and _call_realtime from violetear.client

Same root cause as the ReactiveRegistry import bug in 835dede: client.py
now lives inside the violetear.client module (good — gives state.py and
dom.py a proper module to import from). But the bundle's server-side
stubs (generated by _generate_server_stubs, one per @app.server.rpc /
.realtime function) reference `_call_rpc` and `_call_realtime` as bare
names at bundle-module scope. Those names were globals when client.py
was exec'd directly into the bundle; after the module-injection, they're
attributes of violetear.client, not bundle globals.

Symptom in browser: clicking precise mode (which triggers the precise_convert
RPC stub) raised
  NameError: name '_call_rpc' is not defined

Fix: add _call_rpc + _call_realtime to the re-export list in client_injection.

New e2e test (test_03_interactive_precise_mode_rpc_roundtrip) catches this
specific regression — it toggles to precise mode and waits for the feet
field to reflect the high-precision constant. Different code path from
the reactive-update test (which is client-only).

43 fast + 3 e2e all green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: apiad

tests/test_examples_e2e.py

@@ -114,3 +114,37 @@ def test_03_interactive_reactive_update_propagates(example_server, page):
     assert errors == [], "Browser errors during reactive update:\n  " + "\n  ".join(
         errors
     )
+
+
+@pytest.mark.e2e
+def test_03_interactive_precise_mode_rpc_roundtrip(example_server, page):
+    """Toggling to precise mode + typing routes the conversion through the
+    server-side RPC stub (`_call_rpc` in the bundle). Catches regressions in
+    the RPC-stub plumbing — different code path from the client-only proxy
+    notify exercised by the reactive-update test above."""
+    base = example_server("03_interactive.py")
+    errors = _collect_browser_errors(page)
+
+    page.goto(base + "/")
+    page.wait_for_function(
+        "() => document.getElementById('violetear-cloak') === null",
+        timeout=HYDRATION_TIMEOUT_MS,
+    )
+
+    # Toggle precise mode via the radio. The on_mode_change callback calls
+    # recompute_from_meters which calls precise_convert (the RPC stub).
+    page.check('input[type="radio"][value="precise"]')
+
+    # Wait for feet to reflect the precise constant (3.28083989501 vs 3.281
+    # in quick mode). After toggling at meters=1.0, feet should be ~3.28084.
+    page.wait_for_function(
+        "() => {"
+        "  const v = parseFloat(document.querySelector('input[data-bind-value=\"UiState.feet\"]').value);"
+        "  return v > 3.2808 && v < 3.2809;"
+        "}",
+        timeout=5_000,
+    )
+
+    assert errors == [], "Browser errors during precise-mode RPC:\n  " + "\n  ".join(
+        errors
+    )

violetear/app.py

@@ -711,13 +711,20 @@ def _generate_bundle(self) -> str:
             exec({repr(runtime_code)}, m_client.__dict__)
 
             import violetear.client
-            # Re-export the names the bundle's init_code and user code call at
-            # module scope (hydrate(globals()) and _register_client_event(...)).
+            # Re-export the names the bundle calls at module scope:
+            # - hydrate / _register_client_event: used by init_code
+            # - _call_rpc / _call_realtime: used by the server-stub functions
+            #   generated by _generate_server_stubs (one stub per @app.server.rpc
+            #   or @app.server.realtime function)
+            # - ReactiveRegistry: kept for symmetry / direct use
+            # - _dispatch_client_event: kept for symmetry
             from violetear.client import (
                 hydrate,
                 ReactiveRegistry,
                 _register_client_event,
                 _dispatch_client_event,
+                _call_rpc,
+                _call_realtime,
             )
             """
         )