refactor(examples): group multifile scripted_demo into a folder

[chaliy]

What

Reorganize examples/ so that multifile examples each live in their own folder.

• Move the four scripted_demo files into examples/scripted_demo/:
  • scripted_demo.rs → main.rs (so Cargo still auto-discovers it as the scripted_demo example)
  • scripted_demo.py, scripted_demo.json, scripted_demo.toml (names kept)
• Remove the orphan top-level examples/package.json and examples/package-lock.json — leftovers from when the TypeScript example lived at the top level. The real TS example already lives in examples/node/ with its own pinned lockfile.
• Update every path reference: the example sources (comments, Script::from_file, the TOML script_path), .github/workflows/ci.yml, examples/README.md (including pointing the TypeScript section at examples/node/), and docs/api.md.

Why

The scripted_demo example is made of four files that belonged together but sat flat in examples/, mixed in with the single-file examples. Grouping them into a folder (matching the existing examples/node/ TS example) makes the layout consistent and self-documenting, and clears out unused package files.

How

git mv the files into the new folder, rename the Rust entrypoint to main.rs to preserve Cargo example auto-discovery, then update all path references across sources, CI, README, and docs.

Risk

• Low
• Path-only reorganization, no library/server logic changed. The risk surface is stale path references; all known references were updated and exercised.

Checklist

• Tests added or updated — no new code paths (pure file move + path updates); full suite still green (cargo test: 44 passed), clippy/fmt clean, ./tests/smoke_test.sh passed, and the scripted server was booted from the new config path. cargo run --example scripted_demo builds and loads the script from the new location.
• Backward compatibility considered — cargo run --example scripted_demo unchanged; only on-disk file locations moved.

---

Generated by Claude Code