wirl 0.1.0 → 0.2.0

package/README.md

@@ -0,0 +1,55 @@
+# wirl
+
+Deploy an internal app somewhere real, privately. One command puts the folder you are in on a URL that only your company can open.
+
+```bash
+npm install -g https://app.wirl.dev/cli/wirl.tgz
+wirl login                # a link and a code; approve in the browser
+wirl init my-tool --server
+cd my-tool
+wirl dev                  # runs it here, signed in as a stub user
+wirl preview              # a private address to look at it before it is live
+wirl deploy               # builds, scans, deploys; prints the URL
+wirl share dana@company.com
+```
+
+Install it from wirl itself, as above, and run plain `wirl`. Do not run `npx wirl`: that name on npm belongs to an unrelated older package today, and `npx` would fetch that one.
+
+Sign in with your work Google account and you are in your company's workspace. Anything a colleague deploys there is yours to open, and nobody outside the company can. A personal account gets a space of its own.
+
+## What an app is
+
+A static folder needs nothing. A server-side app is one JavaScript module exporting `fetch(request, env)`:
+
+- `env.DB` is a SQLite database that belongs to this app, in D1's prepared-statement shape. Rolling back code never rolls back data.
+- `x-wirl-user-id`, `x-wirl-role` and `x-wirl-org` say who the visitor is. wirl sets them after verifying the person; the browser cannot forge them.
+- Third-party APIs are called by their real URL. Declare the connection in `wirl.json`, and wirl attaches the key on the way out. The key never reaches the app, the agent that wrote it, or this machine.
+- A `public_paths` entry in `wirl.json` opens one path to the internet with no sign-in — for a Slack, Stripe or GitHub webhook — and wirl checks the sender's signature before the app is ever called.
+
+`wirl dev` runs the same bundle under Node, with the same database shape and headers, so what you see locally is what ships.
+
+## For coding agents
+
+`wirl init` writes `.claude/skills/wirl/SKILL.md` so Claude Code knows wirl is there. Agents that speak MCP can connect directly:
+
+```bash
+claude mcp add --transport http wirl https://app.wirl.dev/mcp
+```
+
+That opens the browser once to sign in. The token an agent gets can deploy, roll back and pull, and cannot share apps, change who can open them, or touch connections, members or tokens. Ticking one box at consent grants full access. See the docs for what each scope covers.
+
+## Everything else
+
+```bash
+wirl --help
+```
+
+Orgs, members, connections, transfer, move, versions, rollback, pull, previews, logs, schedules, run.
+
+## Requirements
+
+Node 22.13 or later. Credentials live in `~/.config/wirl/credentials.json` after `wirl login`, or in `WIRL_TOKEN` for CI and sandboxes.
+
+Docs: https://docs.wirl.dev. Site: https://wirl.dev. Issues: https://github.com/Brycce/wirl-platform/issues.
+
+wirl is a hosted service; use of the CLI is governed by the terms at https://wirl.dev/terms.