npm - @ipul-labs/forge - Versions diffs - 1.16.0 → 1.16.1 - Mend

@ipul-labs/forge 1.16.0 → 1.16.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2) hide show

package/package.json +1 -1
package/bin/README.md +0 -210

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@ipul-labs/forge",
-  "version": "1.16.0",
+  "version": "1.16.1",
   "description": "AI-powered code change & deploy control panel — connects Claude, GitLab, and Kubernetes",
   "type": "module",
   "main": "server/forge/routes.js",

package/bin/README.md DELETED Viewed

@@ -1,210 +0,0 @@
-# `forge-agent` — CLI
-> Type an issue, accept the suggested fix, and watch it merge to production. One command.
-`forge-agent` is the headless half of [Forge](../README.md). Same orchestrator the web UI uses, no browser required.
----
-## Install
-```bash
-npm install -g forge-agent
-```
-Or run from a checkout without installing:
-```bash
-node bin/forge-agent.js <command>
-```
-You'll need:
-- **Node.js 20+**
-- **`claude` CLI** installed and authenticated (`claude auth login`)
-- A **GitLab / GitHub / Azure DevOps** personal access token
----
-## First-time setup
-```bash
-forge-agent init        # interactive wizard — writes .env + ~/.forge/config.json
-forge-agent doctor      # confirm node, git, claude CLI, token, and config are all ready
-```
-`init` walks you through:
-1. `FORGE_TOKEN` (a generated default — accept with Enter)
-2. `PORT` (only matters if you also want the web UI)
-3. SCM provider (gitlab / github / azuredevops, arrow keys)
-4. Primary repo, then **add another?** (loop to add secondaries — needed for cross-repo features)
-5. SCM token (masked input)
----
-## The headline command
-```bash
-forge-agent ship <iid>
-```
-Walks an issue from "open ticket" to "deployed in production" in one command, pausing for `y/N` at every step that changes shared state:
-```
-ship <iid>
-  ├─ analyze          (or load cached if you've already analysed)
-  ├─ review proposal  (per-file diff + summary + divergence warnings)
-  ├─ ?accept          → continue, refuse, or refine with feedback
-  ├─ validate         (lint / typecheck / test against the proposed contents)
-  ├─ ?apply           → branch + commit + open MR
-  ├─ watch CI
-  ├─ ?ci-fix          (only if the pipeline fails — re-analyse with logs, push to same branch)
-  ├─ ?merge           → merge to main
-  ├─ watch deploy     (post-merge pipeline)
-  └─ ?close issue
-```
-**Resumable.** If you abort or the process dies, re-run `forge-agent ship <iid>` and it picks up at the next gate (state lives in `~/.forge/sessions/`).
-**Confirm-by-default.** Cursor on every gate defaults to *no*. Pass `--yes` (or set `FORGE_YES=1`) for unattended mode.
-```bash
-forge-agent ship 42                     # interactive, all gates
-forge-agent ship 42 --all-repos         # cross-repo (web-app + api + …)
-forge-agent ship 42 --yes               # unattended, no prompts
-forge-agent ship 42 --auto              # arm auto-merge instead of merging now
-forge-agent ship 42 --skip-validate     # skip the auto-validate before apply
-```
----
-## Discover what to work on
-```bash
-forge-agent issues                      # latest open issues, sorted by recency
-forge-agent issues --label feature      # filter by label
-forge-agent issues --mine               # filter by author (FORGE_USER || USER)
-forge-agent issues --json | jq .        # pipe-friendly
-forge-agent issue 42                    # full description, labels, URL
-```
----
-## Drive each phase by hand
-`ship` is a thin orchestrator — every phase is also a standalone command. Useful when you want to inspect, iterate, or only do part of the flow.
-```bash
-forge-agent analyze 42 --all-repos      # produce + cache a fresh analysis
-forge-agent show                        # re-render the most recent analysis
-forge-agent show 42                     # ...for a specific issue
-forge-agent refine --feedback "use Resend instead of SendGrid"
-forge-agent validate                    # lint/typecheck/test the proposal
-forge-agent apply --validate            # gate apply on green validation
-forge-agent watch                       # poll the MR pipeline
-forge-agent ci-fix                      # re-analyse with failed-job logs, push to same branch
-forge-agent merge                       # confirm + merge
-forge-agent merge --auto                # arm auto-merge instead
-forge-agent resolution-check            # ask the model: did this MR actually fix the issue?
-forge-agent close                       # confirm + close the issue
-```
-`<iid>`-less commands resolve via the **HEAD pointer** — the most recently touched session. Like `git`'s HEAD: whatever you analysed last is what `show`/`validate`/`apply`/`watch`/`merge`/`close` operate on unless you pass an explicit `<iid>`.
----
-## Sessions (`~/.forge/sessions/`)
-Each issue you work on gets a directory:
-```
-~/.forge/sessions/<repo>/<iid>/
-  analysis.json    last cached analyzeIssue result
-  state.json       { phase, branch, mrIid, mrUrl, lastPipelineStatus, ... }
-  events.ndjson    append-only audit log
-~/.forge/sessions/HEAD                "<repo>/<iid>" — the most recently touched session
-```
-Inspect and clean:
-```bash
-forge-agent session list                # table of all sessions, HEAD marked *
-forge-agent session list --json
-forge-agent session show                # full state of HEAD
-forge-agent session show 42             # ...for a specific issue
-forge-agent session clean 42            # remove one session
-forge-agent session clean --all         # wipe everything
-```
-Override the location with `FORGE_SESSIONS_PATH` (handy for CI or test isolation).
----
-## Common workflows
-### Ship a small fix, fully unattended
-```bash
-forge-agent ship 42 --yes
-```
-Don't do this on prod the first time. Watch a couple of runs interactively first.
-### Drive review explicitly
-```bash
-forge-agent analyze 42 --all-repos      # produce
-forge-agent show                        # review on the same screen later
-forge-agent refine --feedback "..."     # iterate
-forge-agent ship 42                     # pick up where you left off
-```
-### Run from CI
-```bash
-FORGE_YES=1 forge-agent ship 42
-```
-`--json` is available on `analyze`, `issues`, `issue`, `repos list`, `session list/show`, `watch`, and `validate` — pipe-safe outputs that bypass Ink.
-### Recover from a failed step
-Just re-run the same command. State is on disk; it picks up where it left off.
-```bash
-forge-agent ship 42                     # if it died mid-flow, this resumes
-forge-agent ci-fix                      # if CI failed, fix it without re-running ship
-```
----
-## Doctor & troubleshooting
-```bash
-forge-agent doctor
-```
-Sequential checklist — `node`, `git`, `claude`, `FORGE_TOKEN`, config file, frontend build. Exits non-zero if any check fails.
-If `analyze` is timing out (5-minute Claude CLI cap), narrow the scope:
-```bash
-forge-agent analyze 42 --secondary group/api    # explicit secondary instead of --all-repos
-```
-If `apply` says "no repos to validate against", check `forge-agent repos list` and your session's `primary` field.
----
-## Reference
-- [`docs/cli.md`](../docs/cli.md) — full command reference, every flag
-- [`docs/cli-ship-workflow.md`](../docs/cli-ship-workflow.md) — design + status of the end-to-end ship workflow (per-phase delivery, decisions, risks)
-- [`../README.md`](../README.md) — the broader Forge project (web UI, server, multi-provider details)
----
-## License
-MIT — same as the rest of Forge.