wayari 0.1.0

package/README.md

@@ -0,0 +1,41 @@
+# wayari
+
+Ship PRs while you sleep. Merge them with your eyes open.
+
+`wayari` runs a software factory from your terminal. You describe a job on a repo, it opens a
+channel, puts coding agents on it, runs the gate (typecheck, build, tests, and the repo's own
+checks) after every stage, and opens one reviewed pull request. You merge it.
+
+## Install
+
+```
+npm i -g wayari
+wayari doctor
+```
+
+macOS and Linux. It needs Node 20 or newer, tmux, git, `gh` signed in, and at least one agent CLI
+such as Claude Code. `wayari doctor` names anything missing and the fix beside it.
+
+## First run
+
+```
+wayari serve                                   # in a terminal you keep open
+wayari start "the goal" --repo . --lead opus   # in another: opens a channel, staffs it
+wayari                                         # where things stand
+wayari merge <channel>                         # when the pull request is ready
+```
+
+`--hours 8 --limit 20` on `start` lets a channel run unattended until then, stopping at the cap.
+Without them it runs while you watch.
+
+## What it writes outside its own directory
+
+`wayari serve` adds its status hooks to `~/.claude/settings.json` so it can hear an agent's state
+without reading its screen. Your own hooks are untouched. `wayari uninstall` takes them back out;
+`wayari uninstall --data` removes the data directory too. The command's data lives in `~/.wayari`,
+or in the Wayari app's directory when the app is installed, or wherever `WAYARI_HOME` points.
+
+## Feedback
+
+`wayari feedback "what happened"` opens a prefilled GitHub issue with the version and the doctor's
+verdicts. The issues are at https://github.com/jawadjalal/wayariapp/issues.

package/bin/wayari.mjs

@@ -0,0 +1,30 @@
+#!/usr/bin/env node
+// The installed `wayari`. `dist/wayari.mjs` is the repo's `scripts/wayari.mjs` bundled with the core
+// it calls (`scripts/build-cli.mjs`). This file only refuses what the bundle cannot survive: the
+// factory keeps agents alive in tmux, which Windows does not have, so it says so here in one line
+// rather than failing inside node-pty on the first shift.
+if (process.platform === 'win32') {
+  console.error('wayari runs on macOS and Linux. It keeps agents alive in tmux, which Windows does not have. WSL works.')
+  process.exit(1)
+}
+import { spawn } from 'node:child_process'
+import { existsSync } from 'node:fs'
+import { resolve } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+// INSIDE AN AGENT'S PANE, THE WORD `wayari` IS THE AGENT'S. Every agent on a shift is briefed to
+// call `wayari claim` and `wayari done`, and those verbs belong to the shim the app writes at
+// `<userData>/bin/wayari` and puts first on the pane's PATH. The agent's own shell then sources its
+// rc files, which put `~/.local/bin` or `/opt/homebrew/bin` back in front, and there this operator
+// command sits once `npm link` or `npm i -g wayari` has run. On 2026-09-05 two builders each got this
+// file's usage back from `wayari claim` and `wayari done`, nothing was claimed, no done ever reached
+// the factory, no gate ran, and the channel ran out its clock at $5.28. The app sets `WAYARI_CLI` to
+// the shim's path in every hook-capable pane, so that variable is how this file knows it is standing
+// where the shim should, and it hands the whole command over.
+const shim = process.env.WAYARI_CLI
+if (shim && existsSync(shim) && resolve(shim) !== fileURLToPath(import.meta.url)) {
+  const agent = spawn(shim, process.argv.slice(2), { stdio: 'inherit', env: process.env })
+  agent.on('exit', (code, signal) => process.exit(code ?? (signal ? 1 : 0)))
+} else {
+  await import('../dist/wayari.mjs')
+}