Update package metadata, scripts, and contributing docs for test suite

Author: ofriw

CONTRIBUTING.md

@@ -7,14 +7,15 @@ Welcome! This project welcomes focused, well-validated contributions. Use coding
 - **Use code research first** — understand the surrounding module responsibilities before editing.
 - **Make minimal changes** — prefer targeted edits that reuse existing mechanisms.
 - **Match existing patterns** — keep naming, lifecycle hooks, tool contracts, and TUI behavior consistent with the current code.
-- **Preserve context-management semantics** — changes to `spawn`, `ledger`, or `handoff` should keep the agent workflow predictable across session resets and compaction.
+- **Preserve context-management semantics** — changes to `spawn`, `notebook`, or `handoff` should keep the agent workflow predictable across session resets and compaction.
+- **Use static imports only for `spawn/renderer.ts`** — it registers the frame scheduler into the singleton container at module evaluation time. Switching to `await import()` will silently break test isolation because the test harness cannot overwrite the singleton before registration.
 - **AI-agent generated contributions are welcome** — include enough human intent and validation context in the PR for reviewers to trust the result.
 
 ## Suggested Workflow
 
 1. **Research the area**
-   - Identify the relevant primitive: spawn, ledger, handoff, watchdog, or extension wiring.
-   - Read nearby tests in `agenticoding.test.ts` before changing behavior.
+   - Identify the relevant primitive: spawn, notebook, handoff, watchdog, or extension wiring.
+   - Read the relevant suite in `tests/unit/` before changing behavior.
 
 2. **Plan the smallest safe change**
    - Reuse existing state and lifecycle hooks when possible.
@@ -38,6 +39,13 @@ Before submitting, check that your change:
 - Handles reset, cancellation, and stale-session cases where relevant.
 - Keeps docs aligned with the package version and installed behavior.
 
+## Tests
+
+- `npm test` — runs the unit suite under `tests/unit/` via the in-repo Node test runner.
+- `npm run test:snapshots:check` — runs only the render-snapshot tests; fails on any drift in `tests/__snapshots__/`.
+- `npm run test:snapshots:update` — rewrites the golden files in `tests/__snapshots__/` after an intentional render change. Review the diff carefully: snapshot updates are the only signal that catches unintended UI regressions.
+- `npm run test:e2e` — runs the process-isolated end-to-end suite under `tests/e2e/`.
+
 ## Community
 
 Use GitHub Issues for bug reports and feature requests. Keep discussions concrete: describe the agent workflow you expected, what happened instead, and any reproduction steps.

package.json

@@ -2,7 +2,7 @@
   "name": "pi-agenticoding",
   "version": "0.3.0",
   "type": "module",
-  "description": "Context management primitives for the pi coding agent — spawn, ledger, handoff",
+  "description": "Context management primitives for the pi coding agent — spawn, notebook, handoff",
   "license": "MIT",
   "keywords": [
     "pi-package"
@@ -17,7 +17,15 @@
     "@earendil-works/pi-tui": "*",
     "typebox": "*"
   },
+  "scripts": {
+    "test": "node ./scripts/run-node-test.mjs tests/unit/**/*.test.ts",
+    "test:e2e": "node ./scripts/run-node-test.mjs tests/e2e/**/*.test.ts",
+    "test:all": "npm run test && npm run test:e2e",
+    "test:snapshots:check": "node ./scripts/run-node-test.mjs tests/unit/render-snapshots.test.ts",
+    "test:snapshots:update": "node ./scripts/run-node-test.mjs --update-snapshots tests/unit/render-snapshots.test.ts"
+  },
   "devDependencies": {
+    "fast-check": "^4.8.0",
     "typescript": "^6.0.3"
   },
   "pi": {