Add PicoRunner local launch manifest and README badge

[bigmints]

Summary

PicoRunner is a desktop app for installing and running supported open-source apps locally. It manages setup, launch and updates so users can use these apps without manually configuring a development environment.

Add a root manifest for the existing Vite web app: Node 24, locked npm dependencies, production build and Vite preview on IPv4 loopback with assigned host/port, strict-port handling and HTTP / readiness. Diagrams remain in browser IndexedDB. Optional .env and .env.local configuration is declared for preservation; no sharing backend is provisioned. The README documents local browser storage and the separate optional backend.

Add one README badge with the canonical upstream repository encoded in the launch URL. Only picorunner.toml and README.md change; app source, dependencies and lockfiles are unchanged.

Validation (2026-10-16)

Exact upstream base: 7683bdf90a8db5d284dc6b2bc545831aa4b6dd76. Publication workspace: macOS arm64, Node 24.22.0; checks used an isolated checkout. Existing PicoRunner submissions and the current default-branch head were rechecked before creating the fork.

• Clean npm ci --no-audit --no-fund: passed, including the existing Husky setup.
• npm run lint: passed.
• npm run build: passed.
• README formatted with repository Prettier; the existing lint-staged/Prettier commit hook passed.
• Contribution review: focused main-based change, imperative commit message, no application/UI changes. No large feature or unrelated outreach.
• Manifest launch with an assigned free test port: npm run preview -- --host 127.0.0.1 --port 58300 --strictPort returned HTTP 200 for / and 3 referenced built JS/CSS assets. This is an HTTP check, not a browser UI test. Only the check's owned process was stopped afterward; its assigned port was confirmed closed.
• TOML syntax and manifest-v1 JSON Schema validation passed using the schema source in the PicoRunner website repository. The single badge query decodes to the canonical upstream URL. Whitespace checks passed and the lockfile is byte-identical to the base.

Canonical PicoRunner/macOS sanity (2026-10-16)

A separate runtime worker imported the canonical upstream URL at the exact base commit 7683bdf90a8db5d284dc6b2bc545831aa4b6dd76 through PicoRunner 0.3.14 on macOS 26.6.2 (25G83), Apple Silicon arm64. Native discovery selected the root dev script; import completed in 21 seconds at attempt zero, without a manual source patch. Installer readiness checks and the browser UI passed.

• Core task: Created SQLite diagram PicoRunner disposable schema, tables pico_authors(id) and pico_books(id,author_id); INTEGER column types; dragged books.author_id to authors.id, observed2tables/1relationship/0problems; saved and exported SQL.
• Persistence: After native Stop/Start and browser reload: named diagram, both named tables,1relationship and0problems retained.
• Cleanup: stopped via PicoRunner; synthetic diagram and managed source retained. Managed sources and synthetic state were retained; no uninstall is claimed.
• The exported DDL executed successfully in isolated in-memory SQLite with both tables and the expected foreign key. Sharing and external databases were not exercised.

These native development-route observations are separate from this proposed production manifest. Canonical installation with the proposed manifest, semantic manifest acceptance and managed updates remain unverified. The manifest's command-level production build/HTTP check is documented above.

The runtime archive SHA-256 is e00c532c1d6d46897e167b2f7b8a92ec9650f8e8a726681c4b52bfd39570f294; all member hashes and exact package/license bytes were independently verified. The batch retained all 16 prior entries, but it did not leave all prior state unchanged: a stale control briefly started a pre-existing app and restored it stopped, and a different pre-existing app's stored port changed with no lifecycle/configuration action issued in the batch; cause unknown.

Public redacted canonical runtime report contains the distinct install, launch, health, core-task, restart and cleanup observations.

Keep this draft open for review. No merge, deployment or catalog acceptance is asserted.

[vercel]

@bigmints is attempting to deploy a commit to the dottle's projects Team on Vercel.

A member of the Team first needs to authorize it.