# MapleJockey migration pilot v0.3

17 November 2026. Founder-led, private/local implementation with no new external spend.

## Start

Open **MapleJockey_Pilot.html** at the package root and choose **Run guided synthetic demo**. The eight invented files are bundled into the page. No installation, account or network is needed for this flow.

The five steps are scope, source baseline, export/re-import, restoration checks and rollback/evidence. A manual route can read explicitly selected non-sensitive files, export a portable JSON bundle and compare a re-imported bundle with the separately retained source baseline. Files and results are not automatically persisted.

Keep the directory, assessment and pilot HTML files in the same folder for their companion links. The pilot's assessment JSON can be imported into MapleJockey_Assessment.html. The observed disk assessment is already available at [pilot-assessment.json](../evidence/pilot-assessment.json).

## What was observed

The isolated disk exercise exported eight synthetic files, restored them to a fresh directory, read them back, verified all hashes and used the restored CSV/JSON to calculate the expected total of 40. Three altered-bundle cases failed safely. Rollback removed only the run-owned restored directory and the original source remained unchanged and usable.

The recorded run has 14 passed checks, zero failed checks and six Not tested checks. Two file types need application-specific review; four provider/control categories were not exercised. This 1,392-byte dataset is a functional demonstrator, not a performance benchmark or a vendor migration.

Read [Eight-file disk rehearsal result](disk-result.html) and [Pilot workbench test report](pilot-test-report.html) for the exact evidence and limits. The transfer bundle and source fixture are synthetic; metadata reports exclude their file contents.

## Files

- core.mjs: portable snapshot, SHA-256, strict bundle validation, completeness comparison and selected file-reading checks.
- fixtures.mjs: eight invented files and a meaningful restored-data computation.
- report.mjs: content-free result/report and assessment bridge.
- [Pilot workbench controls](pilot-workbench.html): standalone page source, builder and event/rendering harness.
- run_disk_rehearsal.mjs: actual isolated filesystem export, restore, readback, failure detection and rollback.
- tests/ and [Independent pilot review](pilot-independent-review.html): engine tests, independent adversarial tests and evidence review.
- [Operator walkthrough](walkthrough.html): scope, five-minute walkthrough, acceptance/sign-off form, later provider evidence requests and delivery workflow.
- [Eight-file disk rehearsal result](disk-result.html): observed result, assessment JSON, test logs, synthetic transfer bundle and actual source fixture used.

## Reproduce

Use existing Node 22 or later. No package installation is required. From the extracted project root:

```sh
node --test pilot/tests/*.test.mjs pilot/review/negative.test.mjs
node pilot/ui/smoke-test.mjs
node pilot/run_disk_rehearsal.mjs
node pilot/review/inspect_disk_evidence.mjs
node pilot/ui/build.mjs
```

The disk runner creates a new isolated synthetic run and refreshes the latest result files. It never reads a provider account or pre-existing user folder. Preserve previous result files before rerunning if you need their exact earlier timings. The source fixture includes a deliberately synthetic sentinel; tests verify that reports omit it and do not leak file contents.

## Boundaries

The guided browser flow restores into memory; the manual browser route reads a user-selected bundle and still restores into memory. The separate disk runner writes fresh local files and reads them back. Neither executes the Dropbox-to-Sync provider guide.

Local limits: 200 files, 5 MiB each, 20 MiB combined, 32 MiB JSON bundle. File content in a transfer bundle is unencrypted. Reports contain paths and hashes, which can also be sensitive. This is not an encrypted vault, signed attestation or multi-user access-control service.

The source/DOM event harness passed, but native browser visual layout, keyboard operation, file chooser and actual downloads were not verified because browser launch is restricted in this environment. Unsupported file types, tenant controls and operator business acceptance remain explicit follow-up items.
