Refactor pipeline policies, MCP registry, and unified config/runtime

README.md

@@ -14,10 +14,10 @@ TypeScript runtime for deterministic multi-agent execution with:
 ## Architecture Summary
 
 - `SchemaDrivenExecutionEngine.runSession(...)` is the single execution entrypoint.
-- `PipelineExecutor` owns runtime control flow and topology dispatch.
+- `PipelineExecutor` owns runtime control flow and topology dispatch while delegating failure classification and persistence/event side-effects to dedicated policies.
 - `AgentManager` is an internal utility used by the pipeline when fan-out/retry-unrolled behavior is required.
 - Session state is persisted under `AGENT_STATE_ROOT`.
-- Project state is persisted under `AGENT_PROJECT_CONTEXT_PATH` with domains:
+- Project state is persisted under `AGENT_PROJECT_CONTEXT_PATH` with schema-versioned JSON (`schemaVersion`) and domains:
   - `globalFlags`
   - `artifactPointers`
   - `taskQueue`
@@ -26,7 +26,9 @@ TypeScript runtime for deterministic multi-agent execution with:
 
 - `src/agents`
   - `orchestration.ts`: engine facade and runtime wiring
-  - `pipeline.ts`: DAG runner, retry matrix, abort propagation, domain-event routing
+  - `pipeline.ts`: DAG runner, retry matrix, aggregate session status, abort propagation, domain-event routing
+  - `failure-policy.ts`: hard/soft failure classification policy
+  - `lifecycle-observer.ts`: persistence/event lifecycle hooks for node attempts
   - `manifest.ts`: schema parsing/validation for personas/topologies/edges
   - `manager.ts`: recursive fan-out utility used by pipeline
   - `state-context.ts`: persisted node handoffs + session state
@@ -36,6 +38,7 @@ TypeScript runtime for deterministic multi-agent execution with:
   - `provisioning.ts`: resource provisioning and child suballocation helpers
 - `src/mcp`: MCP config types/conversion/handlers
 - `src/examples`: provider entrypoints (`codex.ts`, `claude.ts`)
+- `src/config.ts`: centralized env parsing/validation/defaulting
 - `tests`: manager, manifest, pipeline/orchestration, state, provisioning, MCP
 
 ## Setup
@@ -93,6 +96,7 @@ Actors can emit events in `ActorExecutionResult.events`. Pipeline status also em
 - hard failures: timeout/network/403-like failures tracked sequentially; at 2 consecutive hard failures the pipeline aborts fast
 - `AbortSignal` is passed into every actor execution input
 - session closure aborts child recursive work
+- run summaries expose aggregate `status`: success requires successful terminal executed DAG nodes and no critical-path failure
 
 ## Environment Variables