Closes the gap N8 just opened: the REPL parses + collects an optional
`[path]` so `spawn <Name>` resolves through `ModuleScope` (actor decl,
wrong kind, or unknown) instead of accepting any string. The behavior
body stays trivial — the evaluator lands at order 2.

A new public `ck_driver::app::run_actor` shares lookup with the REPL so
a permanent corpus integration test (`tests/corpus.rs`) exercises the
same pipeline a user gets at `ck --interactive`. The first two apps —
`tests/corpus/noop/` and `tests/corpus/helloWorld/` — assert today's
lifecycle (ActorSpawned → ActorDespawned { Normal }) and ratchet up
automatically as later orders land.

Architecture rule R1 records the new `ck_driver` edges to the front-end
(ck_hir, ck_parser, ck_resolve, ck_syntax) because the REPL now projects
a single file into a `ModuleScope`.

@@ -0,0 +49,4 @@
+/// Returns a rendered diagnostic string if the file fails to load (lex / parse
+/// / collect diagnostics fire), or a plain-language error if `actor` does not
+/// name an actor decl in the loaded module.
+pub fn run_actor(path: &Path, actor: &str) -> Result<Vec<MetaEvent>, String> {

@@ -0,0 +71,4 @@
+
+    // N3 + N4 — body resolution against the merged scope and the linked table,
+    // with the effect table in hand for qualified `Effect::op` paths.
+    let mut body_diagnostics: Vec<Diagnostic> = Vec::new();

@@ -0,0 +16,4 @@
+/// Where the repo's `tests/corpus/` lives, relative to this integration test's
+/// own crate. `CARGO_MANIFEST_DIR` is `<repo>/src/rust/crates/ck_driver`; the
+/// repo root is four parents up.
+fn repo_root() -> PathBuf {