@webappwiz/cli 0.0.10 → 0.0.11

package/index-8xj4zxqp.js

@@ -1,343 +0,0 @@
-import {
-  table
-} from "./index-pyjg1rtk.js";
-// package.json
-var version = "0.0.10";
-
-// skills/add.ts
-import { ConsoleLogger } from "webappwiz/log";
-import { NodeFs } from "webappwiz/system";
-
-// skills/skill.ts
-import { dirname } from "node:path";
-
-// templates/arbor.skill.md
-var arbor_skill_default = `---
-name: arbor
-description: Use the @webappwiz/arbor CLI to land your work on trunk, or a base branch given as an argument, from an isolated git worktree without pull requests. Read this before making any code change in an arbor repository, since it decides where the work happens, and whenever you need to add, claim, merge, remove, list, show, locate, or escalate a task.
-version: 0.0.10
----
-
-# Using arbor
-
-\`arbor\` runs many agents on one repo, each in its own git worktree, landing on
-trunk without pull requests. Run it with \`bunx @webappwiz/arbor <command>\` (or
-\`arbor\` if on PATH). \`arbor --help\` explains the commands; this file covers
-only what the CLI cannot tell you.
-
-**Rule:** never use raw git for state transitions arbor covers. Every landing
-goes through \`arbor merge\`. The only exception is finishing an in-progress
-rebase (\`git add\`, \`git rebase --continue\`), then merging again.
-
-A failed command prints \`{reason}\` JSON on stdout and instructions on stderr:
-do what stderr says. The one case to memorize is exit 4 \`lease_lost\`: stop,
-do not retry, another agent owns the tree.
-
-## Before you start
-
-Other agents may already be working. Before creating anything, list the files
-you expect to touch, then \`arbor ls\`, and for each task in flight compare with
-its changed files:
-\`git -C "$(arbor path <task>)" diff --name-only main...task/<task>\`
-(\`arbor show <task>\` for its plan; neither takes its lease).
-
-If nothing overlaps, carry on. If something does, \`arbor add\` your task if you
-have not already and record the overlap in \`ARBOR.md\` (which task, which
-files). Some overlap is normal: work alongside and accept the rebase. Only
-when the overlap is significant and you expect merge conflicts that would be
-hard to resolve, \`arbor wait <task>\` on the task you overlap with instead:
-let it land first and your rebase is onto its work rather than against it.
-
-Waiting is caution, reserved for overlap that warrants it. Escalate
-instead only when the other task is doing something majorly different from
-yours, or contrary to it: rewriting what you are extending, or asked for the
-opposite of what you were. Then \`arbor escalate\` and ask the user whether to
-wait for it, work alongside it and accept the rebase, or drop yours.
-
-Act on how the wait ends:
-
-- \`removed\`: it landed or was dropped. Redo the overlap check (trunk moved)
-  and carry on.
-- \`escalated\`: your work is blocked on a person too. Tell the human what it
-  is blocked on and wait.
-- \`orphaned\`, \`stray\`, \`unrecorded\` or \`unknown\`: that tree is broken. A tree
-  mid-merge can read as \`orphaned\` for a moment, so \`wait\` once more before
-  believing it, then say so and ask.
-- exit 14 \`timeout\`, still \`working\` or \`merging\`: \`wait\` again (with
-  \`--timeout-secs\` if the task looks close), or offer the choice of
-  working alongside it or picking up something else, saying what you have not
-  started.
-
-A \`stale\` lease on a \`working\` task is normal (arbor only heartbeats while a
-command runs): watch a task's status, never its lease.
-
-## Workflow
-
-1. \`arbor add <task>\`, or \`arbor claim <task>\` to resume one. When this skill
-   is invoked with a branch argument (\`/arbor feature/auth\`), or the user
-   names the branch the work should land on, pass it as \`--base\` to every
-   task you create for that request. Otherwise omit \`--base\`; never guess a
-   base from the currently checked-out branch.
-2. Fill in the \`ARBOR.md\` stub \`add\` wrote at the worktree root (see below)
-   before touching code.
-3. Do the work, updating \`ARBOR.md\` as you go; commit with git (arbor never
-   commits for you).
-4. \`arbor merge\`. On failure, do what stderr says and merge again.
-
-A successful merge deletes the worktree, and your working directory with it:
-\`cd\` to the main tree (merge prints its path) before running anything else.
-
-## Escalation
-
-Merge only work you verified yourself. Escalate instead when verification
-needs a person: external services, destructive migrations, anything tests
-cannot confirm. And if the user asked to see the work before it lands,
-escalate regardless.
-
-1. \`arbor escalate <reason>\`.
-2. Under \`## Blocked\` in \`ARBOR.md\`, state what needs verifying, ending in a
-   question a yes/no or a sentence can answer.
-3. Leave something the human can look at and print its **absolute path**
-   (start from \`arbor path <task>\`). For anything visual or UX, that means a
-   screenshot; if producing one is expensive or has side effects, ask before
-   starting and say what it will cost.
-
-If you claim a tree whose \`## Blocked\` question is unanswered, do not resume
-or merge: ask the user and wait for the answer.
-
-## Reporting
-
-However a task ends, say so in one block; only a merge names a base:
-
-\`\`\`markdown
-### ✅ Merged \`<task>\` onto \`<base>\`
-
-One sentence blending what the task set out to do with where it ended up.
-\`\`\`
-
-\`\`\`markdown
-### ⚠️ Escalated \`<task>\`
-
-One sentence blending what the task set out to do with what it now waits on.
-\`\`\`
-
-\`\`\`markdown
-### 🛑 Removed \`<task>\`
-
-One sentence blending what the task set out to do with why you \`arbor rm\`ed
-it instead.
-\`\`\`
-
-Anything else worth saying goes after this block, not instead of it.
-
-## ARBOR.md
-
-Your session can die at any moment; \`ARBOR.md\` is what lets a stranger
-\`arbor claim\` the task and continue. Fill in the stub \`add\` wrote to this
-shape:
-
-\`\`\`\`markdown
-# <task>
-
-## Goal
-
-One or two lines on what done means.
-
-## Files
-
-- every/path/you/plan/to/touch.ts
-
-## Done
-
-- [x] finished steps move here: these checkboxes are the only progress the
-      task reports
-
-## Next
-
-- [ ] every step you can foresee, roughly one commit each
-
-## Notes
-
-Decisions, dead ends, and how to verify.
-\`\`\`\`
-
-Keep the whole file current throughout implementation, not at the end: after
-each step lands, check it off and move it to \`## Done\`, and when the set of
-files you are touching changes, change \`## Files\` to match. A stale plan is
-worse than none, and a session that dies mid-task reports nothing.
-
-\`arbor show <task>\` prints the file and every way it departs from the
-expected shape; run it on your own task after writing the file. \`add\` excludes
-\`ARBOR.md\` from git for you: never commit it, and never mention it in a commit
-message.
-
-## Committing
-
-Plain, human-style commit messages with **no attribution**: no
-\`Co-authored-by:\` trailers, no "Generated with", no agent or model names, no
-\`--author\` overrides. Commit as often as it helps you; a task usually takes
-fewer than 5 commits, and wanting many more means the task wants splitting,
-not squashing.
-`;
-
-// templates/webappwiz.skill.md
-var webappwiz_skill_default = `---
-name: webappwiz
-description: Check whether the webappwiz package already covers a piece of infrastructure before writing it by hand or adding a dependency for it. Read this before writing any of: time, clocks, durations or timers; logging; id generation; HTTP serving; CLI argument parsing; background tasks or queues; web workers; markdown parsing; typed event emitters; 2D geometry or spatial indexes; filesystem, env or process access; typed RPC over fetch; schema validation; AbortSignal plumbing; disposable resources; browser scroll, animation frames or visibility. Also use whenever the user says webappwiz.
-version: 0.0.10
----
-
-# Using webappwiz
-
-\`webappwiz\` is the parts of a web app that get written again every time, behind
-interfaces a test can replace. One package, one subpath per module. Before
-writing any of that here, find out whether it already exists there.
-
-Its README carries the whole catalogue, a table of every subpath and what it is
-for. Read it from \`node_modules/webappwiz/README.md\`, or, in a project that has
-not installed it yet, from
-\`https://raw.githubusercontent.com/jaredjj3/webappwiz/main/packages/webappwiz/README.md\`.
-
-Nothing in the table is close: say so in a line and write it here. Something is:
-read that module's own README and the exports of its \`index.ts\`, and judge
-against what is actually needed rather than the one-line blurb.
-
-## It fits
-
-\`bun add webappwiz\` and import the subpath. There is no package entry point, so
-import \`webappwiz/time\`, never \`webappwiz\`. Fakes live under \`/testing\` beside
-what they replace.
-
-## It nearly fits
-
-Do not vendor it, fork it, or patch \`node_modules\`. Write what this project
-needs here so nobody is blocked, leave a \`TODO: webappwiz/<subpath> once <gap>\`
-on it, and hand the gap over: print the block below and tell the user to give it
-to an agent working on the webappwiz repo.
-
-\`\`\`markdown
-In \`packages/webappwiz/<subpath>\`: <the gap, in a sentence>.
-
-Wanted by <this project> for <the usecase, concretely>.
-
-What is there now: <the export that comes closest, and where it stops>.
-What is missing: <the smallest change that closes the gap: one more method, a
-widened parameter, another implementation of an interface>.
-Called like: <the call site, written the way the caller wants to write it>.
-\`\`\`
-
-Describe the gap and stop. Do not design the API in the handoff: that repo has a
-style guide and a judge, and neither of them is here.
-
-## It does not fit
-
-One line naming the subpath you read and why it is not the one, then write it
-here. A wrong module taken up is worse than one written twice.
-
-## Rules
-
-- Never edit the webappwiz repository from this project's thread.
-- Never copy its source into this project.
-- Reading the table is the whole check, and it is cheap. Do it before adding a
-  dependency, not after.
-`;
-
-// skills/skill.ts
-var bundled = { arbor: arbor_skill_default, webappwiz: webappwiz_skill_default };
-function versionOf(md) {
-  const frontmatter = md.match(/^---\n([\s\S]*?)\n---/)?.[1] ?? "";
-  return frontmatter.match(/^version:\s*(.+)$/m)?.[1]?.trim() ?? null;
-}
-function available(skills) {
-  return Object.entries(skills).toSorted(([left], [right]) => left.localeCompare(right));
-}
-async function copy(name, doc, dir, opts) {
-  const target = `${dir}/.agents/skills/${name}/SKILL.md`;
-  await opts.fs.mkdir(dirname(target));
-  await opts.fs.write(target, doc);
-  opts.log.info(`wrote ${target}`);
-}
-
-// skills/add.ts
-async function add(opts) {
-  const log = opts.log ?? new ConsoleLogger;
-  const fs = opts.fs ?? new NodeFs;
-  const skills = opts.skills ?? bundled;
-  const doc = skills[opts.skill];
-  if (doc === undefined) {
-    const have = available(skills).map(([name]) => name);
-    throw new Error(`no such skill: ${opts.skill} (have ${have.join(", ")})`);
-  }
-  await copy(opts.skill, doc, opts.dir, { log, fs });
-}
-
-// skills/ls.ts
-import { ConsoleLogger as ConsoleLogger2, color } from "webappwiz/log";
-import { NodeFs as NodeFs2 } from "webappwiz/system";
-async function ls(opts) {
-  const log = opts.log ?? new ConsoleLogger2;
-  const fs = opts.fs ?? new NodeFs2;
-  const skills = opts.skills ?? bundled;
-  const rows = [["skill", "ships", "installed"].map(color.dim)];
-  let stale = 0;
-  for (const [name, doc] of available(skills)) {
-    const ships = versionOf(doc) ?? "?";
-    const installed = await fs.read(`${opts.dir}/.agents/skills/${name}/SKILL.md`).then(versionOf).catch(() => null);
-    if (installed !== null && installed !== ships) {
-      stale++;
-    }
-    rows.push([name, ships, installed ?? "-"]);
-  }
-  const lines = table(rows);
-  if (stale > 0) {
-    lines.push("", `${stale} out of date: run \`skills update\``);
-  }
-  log.info(lines.join(`
-`));
-}
-
-// skills/update.ts
-import { ConsoleLogger as ConsoleLogger3 } from "webappwiz/log";
-import { NodeFs as NodeFs3 } from "webappwiz/system";
-async function update(opts) {
-  const log = opts.log ?? new ConsoleLogger3;
-  const fs = opts.fs ?? new NodeFs3;
-  const installed = await fs.readdir(`${opts.dir}/.agents/skills`).catch(() => []);
-  const skills = opts.skills ?? bundled;
-  const ours = available(skills).filter(([name]) => installed.includes(name));
-  if (ours.length === 0) {
-    log.info(`no webappwiz skills in ${opts.dir}: add one with \`skills add\``);
-    return;
-  }
-  for (const [name, doc] of ours) {
-    await copy(name, doc, opts.dir, { log, fs });
-  }
-}
-
-// update.ts
-import { basename } from "node:path";
-import { ConsoleLogger as ConsoleLogger4 } from "webappwiz/log";
-import { NodeFs as NodeFs4, walk } from "webappwiz/system";
-var DEPENDENCY = /("(?:webappwiz|@webappwiz\/[^"]+)"\s*:\s*")(?!workspace:)[^"]*(")/g;
-async function update2(opts) {
-  const log = opts.log ?? new ConsoleLogger4;
-  const fs = opts.fs ?? new NodeFs4;
-  let count = 0;
-  for await (const path of walk(opts.dir, { fs })) {
-    if (basename(path) !== "package.json") {
-      continue;
-    }
-    const before = await fs.read(path);
-    const after = before.replace(DEPENDENCY, `$1${opts.version}$2`);
-    if (after === before) {
-      continue;
-    }
-    await fs.write(path, after);
-    log.info(`updated ${path}`);
-    count++;
-  }
-  log.info(`${count} package.json pinned to ${opts.version}`);
-  await update({ dir: opts.dir, log, fs, skills: opts.skills });
-}
-
-export { version, add, ls, update, update2 as update1 };

package/index-htwb54c6.js

@@ -1,44 +0,0 @@
-// rules.ts
-import { defineRules } from "@webappwiz/rules";
-import {
-  ClassesOverFunctionExports,
-  CommentsSayWhyNotWhat,
-  DevServersFindAPort,
-  DocCommentsAddressUsers,
-  ExportLeadsTheFile,
-  FakesOverMocks,
-  MatchersOverTestLogic,
-  NamedOptionsLast,
-  NoEmDashes,
-  ObjectsOverCallbacks,
-  OneClassPerFile,
-  OneDirPerInterface,
-  ParametersDeclareFields,
-  ReactiveOverUseState,
-  ResourcesAreDisposable,
-  SimpleTestSetup,
-  TestsOwnTheirState
-} from "@webappwiz/rules/catalog";
-var JUDGE_RULES = defineRules({
-  rules: [
-    new NoEmDashes,
-    new OneClassPerFile,
-    new ExportLeadsTheFile,
-    new ParametersDeclareFields,
-    new ClassesOverFunctionExports,
-    new ObjectsOverCallbacks,
-    new NamedOptionsLast,
-    new SimpleTestSetup,
-    new TestsOwnTheirState,
-    new FakesOverMocks,
-    new MatchersOverTestLogic,
-    new CommentsSayWhyNotWhat,
-    new DocCommentsAddressUsers,
-    new OneDirPerInterface,
-    new DevServersFindAPort,
-    new ReactiveOverUseState,
-    new ResourcesAreDisposable
-  ]
-});
-
-export { JUDGE_RULES };