@osfactory/har 1.16.2 → 1.17.0
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.
|
@@ -17,10 +17,16 @@ harness or report it; do not fall back to ad-hoc commands.
|
|
|
17
17
|
`har env verify <id> --full`. Commit in the session worktree.
|
|
18
18
|
3. **Stop at handoff** — report summary, session branch and preview URLs, then
|
|
19
19
|
wait. Never autonomously `complete`, `teardown`, push, or open a PR.
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
20
|
+
4. **All slots taken?** Occupied slots always block a launch, and you never free
|
|
21
|
+
one yourself. Run `har env status`, then show the user every slot — branch,
|
|
22
|
+
work unit, what it achieves, last verify, and whether its commits are merged,
|
|
23
|
+
pushed or unpushed — and recommend which to close: merged or abandoned work
|
|
24
|
+
with nothing left to do first; never one with unpushed commits. On approval:
|
|
25
|
+
`complete` / `teardown <id>`, then launch.
|
|
26
|
+
|
|
27
|
+
Customize the harness only through `harness.env`, `stages.json` + `.har/stages/`,
|
|
28
|
+
`.har/hooks/` and `.har/plugins/` — there is no generated `.har/*.sh` entry-point
|
|
29
|
+
surface.
|
|
24
30
|
|
|
25
31
|
Full detail — slot environment, readiness, definition of done, project commands,
|
|
26
32
|
commit gate: [`.har/README.md`](.har/README.md) and [`.har/stages.json`](.har/stages.json).
|
|
@@ -12,6 +12,7 @@ har env status # or ./.har/agent-cli.sh 1 status
|
|
|
12
12
|
|
|
13
13
|
- One slot ≈ one task. If slot 1 is occupied by unrelated work, use slot 2+ (limit: `agentSlots` in `.har/stages.json`).
|
|
14
14
|
- Occupied slots always block a new launch: run `har env teardown <id>` (or `complete <id>`) first, then launch again.
|
|
15
|
+
- All slots occupied? Never free one on your own. Show the user each slot (branch, work unit, what it achieves, last verify, merged / pushed / unpushed commits) and recommend which to close — merged or abandoned work with nothing left to do first, never one with unpushed commits. Free it only after approval.
|
|
15
16
|
|
|
16
17
|
## 2. Launch — BEFORE editing any file
|
|
17
18
|
|
|
@@ -11,6 +11,12 @@ never in the main checkout.
|
|
|
11
11
|
- Occupied slots always block a new launch: `har env complete <id>` (or `teardown <id>`),
|
|
12
12
|
then `har env launch <id>`. A new launch never chooses `main` for you — switch the
|
|
13
13
|
main checkout to your intended base first.
|
|
14
|
+
- When every slot is occupied, do not pick one to free on your own. Run
|
|
15
|
+
`har env status` and give the user a slot-by-slot summary: branch, bound work
|
|
16
|
+
unit, what the session achieves, last verify, and whether its commits are merged,
|
|
17
|
+
pushed, or unpushed (`git log <base>..<branch>`, PR state). Recommend which slot
|
|
18
|
+
to close — merged or abandoned work with nothing left to do first; never one with
|
|
19
|
+
unpushed commits — and free it with `complete` / `teardown` only after approval.
|
|
14
20
|
- `teardown` removes the worktree but **keeps the session branch** so you can push it
|
|
15
21
|
or open a PR (`--delete-branch` to drop it).
|
|
16
22
|
- If launch fails after creating a worktree/env file, the registry records `status: failed`.
|