@kylecheng3146/agent-ops 0.0.1 → 0.1.1

package/README.md

@@ -6,17 +6,66 @@ verification, safe lifecycle hooks, and independent review into a repeatable
 engineering workflow.
 
 This repository is in its foundation stage. The CLI, hook runtime, normative
-specification, and installation profiles are being developed in a reviewable
-feature branch before the first pre-1.0 release.
+specification, and installation profiles are being developed as a reviewable
+pre-1.0 interface.
 
-The current CLI is an unreleased development interface. Its packed artifact is
-checked by `npm run package:check`; command behavior may change before the first
-tagged pre-1.0 release.
+The CLI is published as `@kylecheng3146/agent-ops` as a pre-1.0 interface;
+command behavior may change before 1.0.
+
+## Quick start from npm
+
+Requires Node.js `>=22.14.0`. Install the published CLI globally:
+
+```bash
+npm install --global @kylecheng3146/agent-ops@latest
+agent-ops --version
+```
+
+You can run it without a global install with `npx`. When the command runs in
+an interactive terminal without arguments, it opens the setup wizard
+automatically:
+
+```bash
+npx --yes @kylecheng3146/agent-ops@latest
+```
+
+Use `--help` for the complete command reference or provide explicit options in
+automation. The wizard never writes files until you review and confirm its
+installation plan.
+
+Preview a project installation before changing files:
+
+```bash
+agent-ops init \
+  --dry-run --scope project --harness both --profile core --json
+```
+
+After reviewing the plan, apply it explicitly with `--yes`:
+
+```bash
+agent-ops init --scope project --harness both --profile core --yes
+```
+
+The remaining day-to-day checks are:
+
+```bash
+agent-ops trust status --json
+agent-ops doctor --json
+agent-ops config explain --json
+agent-ops update --dry-run --json
+agent-ops update --yes --json
+agent-ops uninstall --dry-run --json
+```
+
+Use `--scope user` with user-home installations. Keep `--dry-run` for any
+operation you want to inspect before applying; non-interactive automation should
+pass `--yes` only after reviewing the plan. Add `--json` when another tool will
+consume the result.
 
 ## Quick start from a source checkout
 
-Version 0.1.0 is prepared for release but has not yet been published to npm.
-Until the protected release workflow completes, use a source checkout:
+For development or to run the repository version directly, use a source
+checkout:
 
 ```bash
 git clone https://github.com/kylecheng3146/agent-ops.git
@@ -40,16 +89,17 @@ updates, and removal are separate commands:
 node dist/packages/cli/src/bin.js init --scope project --harness both --profile core --yes
 node dist/packages/cli/src/bin.js trust status --json
 node dist/packages/cli/src/bin.js doctor --json
-node dist/packages/cli/src/bin.js update --target-version 0.1.0 --dry-run --json
+node dist/packages/cli/src/bin.js config explain --json
+node dist/packages/cli/src/bin.js update --dry-run --json
 node dist/packages/cli/src/bin.js uninstall --dry-run --json
 ```
 
 The commands after `init --yes` are post-apply operations; `doctor` may report
 an unknown probe status until a repository-specific verification setup exists.
 
-Use `--scope user` with user-home installations. Do not install from npm until
-the `v0.1.0` tag has been published; the release workflow is the source of the
-published package and provenance record.
+For a full command reference, run `agent-ops --help`. The `task`, `verify`, and
+`review` commands support acceptance tracking and independent verification when
+the project configuration defines those workflows.
 
 ## Project principles
 
@@ -62,8 +112,9 @@ published package and provenance record.
 
 ## Project status
 
-No npm package has been published yet. Do not depend on the current repository
-as a stable interface until a tagged release is available.
+A pre-1.0 npm package is published. Use `@latest` for the current release, or
+pin a specific version in automation when reproducibility matters; review
+release notes before upgrading.
 
 Documentation:
 

package/dist/packages/cli/src/cli.js

@@ -1,8 +1,22 @@
 import { CliArgumentError, parseArgs } from "./args.js";
 import { errorEnvelope, okEnvelope, writeEnvelope } from "./output.js";
 import { completeInitChoices } from "./wizard.js";
+const WELCOME_BANNER = [
+    "+--------------------------------------------------+",
+    "|          LOOP ENGINEERING TOOLKIT               |",
+    "|       Safe setup for Codex + Claude Code         |",
+    "+--------------------------------------------------+"
+].join("\n");
+export function renderWelcome(color) {
+    const cyan = color ? "\u001b[36m" : "";
+    const bold = color ? "\u001b[1m" : "";
+    const reset = color ? "\u001b[0m" : "";
+    return `${cyan}${bold}${WELCOME_BANNER}${reset}\n\n`;
+}
 export const HELP_TEXT = `Usage: agent-ops <command> [options]
 
+Run \`agent-ops\` without arguments in a terminal to start the interactive setup wizard.
+
 Commands:
   init       Plan or install agent-ops
   config explain
@@ -41,10 +55,15 @@ function writeAndReturn(io, envelope, json, exitCode) {
     return exitCode;
 }
 export async function runCli(argv, io, services) {
-    const json = wantsJson(argv);
+    const launchesWizard = argv.length === 0 && io.isTTY;
+    const effectiveArgv = launchesWizard ? ["init"] : argv;
+    if (launchesWizard) {
+        io.writeStdout(renderWelcome(process.env.NO_COLOR === undefined && process.env.TERM !== "dumb"));
+    }
+    const json = wantsJson(effectiveArgv);
     let args;
     try {
-        args = parseArgs(argv);
+        args = parseArgs(effectiveArgv);
     }
     catch (error) {
         if (error instanceof CliArgumentError) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kylecheng3146/agent-ops",
-  "version": "0.0.1",
+  "version": "0.1.1",
   "description": "Evidence-driven development loops for Codex and Claude Code",
   "type": "module",
   "license": "MIT",