# Reproduce the local node evidence

Use Node 24 or newer. From the source directory run `node build.mjs`, then `node --test --test-isolation=none tests/*.test.mjs`. Run `scripts/jc-001-authority.ps1` in PowerShell 7 for the real failing child process and denied evidence rewrite test. Each JC run retains its own evidence directory.

For real browser storage fixtures, run `node scripts/browser-fixture-server.mjs`. In a fresh test profile open `http://127.0.0.1:8805/__test` and activate Run unused origin tests. This harness writes only synthetic data on that local test origin and refuses to start on an existing record. Nine checks exercise migration, competing writes, corruption, deletion and import. The public build does not include test routes or controls.

Then open Explore from the fixture link, Ask, activate Show the Record by keyboard, Verify and Continue. Record the Node ID, Record ID, snapshot fingerprint, current text and version count. Close the tab. Open a new tab at the same Explore URL. Verify and compare those values. This is LN-001 and LN-002 at tab reopen scope, not process restart.

Export node through the UI. In unused origin `http://127.0.0.1:8806/explore/`, choose that downloaded JSON file, explicitly confirm resuming the exported node and import it. Verify and compare IDs, hashes and texts. These are independent origin databases within the same browser, not different physical computers.

On port 8805, the fixture page's Alter synthetic stored payload button changes a committed payload without updating fingerprints. Opening Explore and pressing Verify must show a conflict, and must not silently repair it. The fixture also tests fingerprint alteration separately.

On port 8806, explicitly delete the synthetic content, export again and inspect the actual downloaded JSON. It must have empty versions and a time/count receipt, and must exclude every old text, old version fingerprint and old record ID. Importing the old export into this used node must be rejected. A new profile cannot know that content in an old export was deleted elsewhere.

Optional full process restart test: install Playwright in a development environment, start the local fixture server, and run `node scripts/node-reopen.mjs`. Set `ARKOSOM_CHROME_PATH` for an installed Chrome if needed, and `ARKOSOM_PLAYWRIGHT_MODULE` to a file URL when using a separately installed module. This script launches an isolated profile, closes the browser process, starts it again and checks identity, content and verification. It was blocked from launching in the authoring environment and is NOT TESTED here.

Browser persistence APIs: [IndexedDB transaction durability](https://developer.mozilla.org/en-US/docs/Web/API/IDBDatabase/transaction) and [StorageManager.persist](https://developer.mozilla.org/en-US/docs/Web/API/StorageManager/persist). Neither a passing reopen test nor a persistence grant proves survival of device loss or a compromised host.