Mike0021/MiniCPM5-2B-WebGPU-Pi-HTTP

1# Local folder validation2 3September 16, 2026. Duplicate only: `Mike0021/MiniCPM5-2B-WebGPU-Pi-HTTP`.4 5- Production build and 29 unit tests passed. Seven new OS-backed adapter tests cover lazy reads, shell/tool writes, file creation/copy/rename/delete, directory creation, restored baselines, conflicts, cancellation, write failure, unsupported operations, virtual paths outside the mount, and concurrent preview/tool writes. Failed creation also removes its still-empty placeholder.6- Browser integration passed in Chromium 152 using real OPFS directory handles through the real worker and IndexedDB. Only the picker is replaced in this suite. Checks cover user activation, staging/diff/application, demo restoration, reload/reconnect, external conflicts, discard, picker cancellation, iframe fallback, and 1440/390/320px layouts. `local-folder-browser.json` records results.7- Separately, a headed Chromium 152 test on an isolated X display used the **native OS directory picker**, selected a real test directory, accepted Chromium's read permission, edited README.md, reviewed its diff, then accepted write permission. Node read the host file and confirmed `# Native edited\n` on disk. This was not OPFS or a mock picker. Earlier test attempts accidentally denied the read permission with a forwarded Enter key; clicking the chooser's Open button and then Allow completed the native flow.8- WebKit 26 at 390px correctly reports that direct folder access is unsupported and keeps all three demo files available. This is a WebKit engine test, not a physical Safari/iPhone test.9- The browser integration suite also passed against the deployed duplicate (`local-folder-live.json`). Existing editor and read-following regression suites passed on the production build.10- Actual MiniCPM5-2B WebGPU trial on the deployed duplicate: read app.js, change its exported greeting from Hello to Bonjour, leave other files unchanged, and verify. The model completed in **9.935 seconds** after a **5.499-second** cached model load. Exactly one file was staged, the real OPFS file remained unchanged before Apply, and the reviewed Apply wrote the expected contents. The actual model/tool messages are in `local-folder-agent-live.json`. This trial used an actual browser directory handle with a supplied picker; OS folder permissions and host-disk writes were tested separately above.11 12Native reproduction: open the standalone app in Chrome, select a small disposable project with Link a folder, allow read access, edit a file and Stage edit. Verify the original file is unchanged. Open Review & apply, inspect the diff, click Apply to folder, allow write access, and verify the file on disk. Back to demo restores the original demo; reload then Reconnect folder restores the local session. Change a previously read file externally before applying a staged edit to check conflict handling.13 14These checks validate the adapter and UI. They are not a general model reliability benchmark. Multi-file application has no OS transaction and can partially succeed; errors retain pending changes and report the count applied.15