@coresource/hz 0.21.4 → 0.21.6
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.
- package/README.md +13 -2
- package/dist/hz.mjs +21012 -12711
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -23,6 +23,16 @@
|
|
|
23
23
|
|
|
24
24
|
Both commands avoid retired `/plan/*` routes in the normal planning flow.
|
|
25
25
|
|
|
26
|
+
## Agent harness library
|
|
27
|
+
|
|
28
|
+
This repo now also includes an additive generic harness under `src/agent-harness/**` with focused proof coverage in `test/agent-harness/**`.
|
|
29
|
+
|
|
30
|
+
- Public entrypoint: `src/agent-harness/index.ts`
|
|
31
|
+
- Core surfaces: messages, gateway adapter, state store, tools/permissions, orchestration, boundary+summary compaction, proactive auto-compaction, restoration attachments, agent loop, subagents/tasks/plan-mode, built-in tool wrappers, and repo-confined authoring tools (`file_write`, `file_edit`, `notebook_edit`)
|
|
32
|
+
- Memory surfaces: persistent memory, automatic extraction, session summaries and session-memory compaction, relevance recall, consolidation, and repo-local team-memory sync contracts with fake/injected adapters plus ETag/delta-sync behavior
|
|
33
|
+
- Proof coverage: `test/agent-harness/**` now includes compatibility, authoring, compaction, restoration, memory, team-sync, and cross-area lifecycle suites that keep the harness headless and validate repo-local behavior without live OAuth or backend dependencies
|
|
34
|
+
- Scope note: the harness is reusable source-level infrastructure; this mission did **not** cut the current CLI or `src/investigation-loop.ts` over to it
|
|
35
|
+
|
|
26
36
|
## Local artifacts
|
|
27
37
|
|
|
28
38
|
Planning state is stored under `~/.hz/cloud-launches/<request-id>/`:
|
|
@@ -31,12 +41,13 @@ Planning state is stored under `~/.hz/cloud-launches/<request-id>/`:
|
|
|
31
41
|
|----------|---------|
|
|
32
42
|
| `request.json` | Normalized request identity and launch bootstrap metadata |
|
|
33
43
|
| `planner-state.json` | Mutable planner state: milestones, work items, assertions, dependencies, clarification items, diagnostics, investigation findings |
|
|
34
|
-
| `mission-draft.json` | Finalized mission snapshot (created only on approval) |
|
|
44
|
+
| `mission-draft.json` | Finalized mission snapshot (created only on approval), including the finalized `plannerPlan` and generated infrastructure artifacts under `artifacts.files` |
|
|
35
45
|
| `plan-history.json` | Finalized revision history and supersession lineage |
|
|
36
|
-
| `infrastructure/` | Generated deployables, TDD skills, and idempotent init scripts |
|
|
37
46
|
|
|
38
47
|
Resume, reuse, and supersession all hang off deterministic launch identity derived from normalized task text plus sorted, deduped absolute repo paths.
|
|
39
48
|
|
|
49
|
+
Generated markdown, shell, and YAML artifacts such as `AGENTS.md`, `.hz/library/*.md`, `.hz/services.yaml`, `.hz/init.sh`, and `.hz/skills/*/SKILL.md` are currently embedded in `mission-draft.json` under `artifacts.files`; local planning does not materialize a standalone `infrastructure/` directory.
|
|
50
|
+
|
|
40
51
|
## Auth and environment
|
|
41
52
|
|
|
42
53
|
Planning uses the existing CLI auth surface:
|