@hilbras/omninode 2.0.0-alpha.3 → 2.0.0-alpha.5

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 CHANGED
@@ -18,7 +18,9 @@ existing intelligence; it does not try to become another model.
18
18
 
19
19
  ## Status
20
20
 
21
- **v2.0.0-alpha.3 — v2 Phase 3: Agent Protocol v2** (after Phase 1: architecture & API stabilization, Phase 2: execution reliability) (the v2
21
+ **v2.0.0-alpha.5 — v2 Phase 5: Pipeline Lifecycle v2**
22
+ (the reliability & interoperability line: architecture → execution →
23
+ protocol → adapters → pipelines) (the v2
22
24
  roadmap is [docs/ROADMAP_V2.md](docs/ROADMAP_V2.md); the v1 plan is complete:
23
25
  the
24
26
  full loop from §28 runs in one command —
@@ -27,14 +29,35 @@ planner → plan → execution → result` — with audit logging, error recover
27
29
  production hardening (see [docs/DEVELOPMENT_PLAN.md](docs/DEVELOPMENT_PLAN.md)
28
30
  for the plan and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for the design).
29
31
 
30
- ### What changed in v2 Phase 1
31
-
32
- - All local stores now build on one shared `JsonFileStore` (atomic writes,
33
- serialized read-modify-write, schema-versioned files, corruption tolerance)
34
- with a `ProjectStores` facade.
35
- - Dependency direction corrected (adapters no longer import engine modules).
36
- - API surface stabilized and guarded: [API_STABILITY.md](docs/API_STABILITY.md),
37
- [API.md](docs/API.md), [DEPRECATIONS.md](docs/DEPRECATIONS.md).
32
+ ### What's new in v2 (so far)
33
+
34
+ - **Phase 5 — Pipeline Lifecycle**: first-class pipeline cancellation
35
+ (`omninode pipeline cancel <run-id>`: stop scheduling → cancel running
36
+ tasks → terminate agent processes → persist a `cancelled` run), `pipeline
37
+ validate` for pre-run checks (deps, cycles, agents, model references),
38
+ explicit run/step **attempts** in the run record, the
39
+ `IPipelineExecutor` contract, and recovery awareness — runs left `running`
40
+ without a `finishedAt` are flagged as interrupted in `pipeline runs`.
41
+ - **Phase 4 — Agent Adapter Hardening**: process-tree cleanup (agents run in
42
+ their own process group; timeout, cancel and Ctrl-C reap the whole tree, so
43
+ no orphaned children), explicit environment policies
44
+ (`inherit` / `allowlist` / `denylist` / `explicit`), working-directory
45
+ validation against project boundaries, per-stream output limits that kill
46
+ runaway agents, binary-safe output decoding, human-readable exit/signal
47
+ reporting, and a native `IAgentAdapter` registry so new integration styles
48
+ plug in without touching core.
49
+ - **Phase 3 — Agent Protocol v2**: versioned protocol
50
+ (`omninode-agent-protocol/2`), fully correlated envelopes, the complete
51
+ message-type set, HELLO handshake, QUESTION/RESPONSE round-trips, and
52
+ malformed input that can never crash OmniNode. Spec:
53
+ [PROTOCOL.md](docs/PROTOCOL.md).
54
+ - **Phase 2 — Execution Reliability**: a task killed after dispatch is
55
+ `unknown`, **not** `failed` — retries never duplicate side effects blindly;
56
+ bounded retries with backoff, execution identity and history.
57
+ - **Phase 1 — Architecture & API Stabilization**: one shared `JsonFileStore`
58
+ behind every local store, corrected dependency direction, and a guarded
59
+ public API ([API_STABILITY.md](docs/API_STABILITY.md), [API.md](docs/API.md),
60
+ [DEPRECATIONS.md](docs/DEPRECATIONS.md)).
38
61
 
39
62
  ### What's in v1.0
40
63