@osfactory/har 0.10.0 → 0.12.0

package/README.md

@@ -4,8 +4,9 @@
 
 # har — Your AI harness orchestrator
 
-[![Release](https://img.shields.io/github/v/release/antoineFrau/har)](https://github.com/antoineFrau/har/releases)
-[![CI](https://github.com/antoineFrau/har/actions/workflows/test.yml/badge.svg)](https://github.com/antoineFrau/har/actions/workflows/test.yml)
+[![Release](https://img.shields.io/github/v/release/os-factory/har)](https://github.com/os-factory/har/releases)
+[![CI](https://github.com/os-factory/har/actions/workflows/test.yml/badge.svg)](https://github.com/os-factory/har/actions/workflows/test.yml)
+[![Documentation](https://img.shields.io/badge/docs-harproject.cloud-38c976)](https://harproject.cloud/)
 
 **Make any repository agent-ready without binding it to one coding agent, test runner, or hosted platform.**
 
@@ -24,20 +25,20 @@ HAR does not own the coding LLM and does not replace CI/CD. It gives agents a st
 
 ## Install
 
-**From npm** (after the first GitHub Release — `@osfactory/har` is not on npm yet):
+**From npm:**
 
 ```bash
-npm install -g @osfactory/har
+npm install -g @osfactory/har@latest
 ```
 
-**From source** (recommended until the first release):
+**From source:**
 
 ```bash
-git clone https://github.com/antoineFrau/har har-project && cd har-project
+git clone https://github.com/os-factory/har har-project && cd har-project
 npm install && npm run build && npm link
 ```
 
-See [AGENT.md](./AGENT.md) for architecture and coding-agent guidance, and [CONTRIBUTING.md](./CONTRIBUTING.md) for the full development workflow, testing on sample projects, and project layout. To report security issues, see [SECURITY.md](./SECURITY.md).
+Read the [full documentation](https://harproject.cloud/). See [AGENT.md](./AGENT.md) for architecture and coding-agent guidance, and [CONTRIBUTING.md](./CONTRIBUTING.md) for the full development workflow, testing on sample projects, and project layout. To report security issues, see [SECURITY.md](./SECURITY.md).
 
 ## Harness profiles
 
@@ -135,7 +136,16 @@ my-app/
 
 HAR stages are project-defined operations with stable identifiers and normalized results. A stage can be as simple as `verify` or as specific as `browser-e2e`, `migration-check`, `accessibility`, or `load-smoke`.
 
-The important boundary is that HAR runs and reports stages generically. It does not need a special Playwright, migration, accessibility, or load-test API in the core product.
+The important boundary is that HAR runs and reports stages generically. It does not need a special Playwright, migration, accessibility, or load-test API in the core product. The authoring contract (command vs script stages, the script contract, how `verificationStages` controls `verify --full`) ships into every harness as `.har/STAGES.md`.
+
+### Custom stages
+
+Register the project's real checks so they run in `verify --full` and surface to every agent:
+
+```bash
+har env add-stage unit-tests --custom --kind test --command "npm test" --verification
+har env add-stage db-integrity --custom --script   # scaffolds .har/stages/db-integrity.sh
+```
 
 ### Playwright (optional)
 
@@ -154,7 +164,8 @@ See `.har/stages/PLAYWRIGHT.md` in the target repo after applying the template.
 | Command | Description |
 |---------|-------------|
 | `har env init` | Scaffold `.har/` + print coding-agent adaptation prompt |
-| `har env add-stage playwright` | Add Playwright `browser-e2e` stage + test scaffold |
+| `har env add-stage playwright` | Add a stage template (`playwright`, `rocketsim`; `--list` shows all) |
+| `har env add-stage <id> --custom` | Register a project-specific stage (`--command "npm test"` or `--script`) |
 | `har env maintain` | Validate harness + print maintenance prompt |
 | `har env launch 1` | Launch agent slot 1 |
 | `har env verify 1` | Run verification |