agentic-orchestrator 0.1.13 → 0.1.15

package/spec-files/progress.md

@@ -1006,3 +1006,94 @@ Open blockers:
   - Expanded tests:
     - `apps/control-plane/test/cli-helpers.spec.ts` now asserts retry command omits `profile` from `gates.run` payload.
     - `apps/control-plane/test/supervisor-collaborators.spec.ts` adds regressions proving build/qa skip retries on non-retryable gate errors.
+
+---
+
+✅ **Entry 180 — Add AGENTS.md parity guide for coding agents**
+
+- **Goal:** Provide a Codex/agent-facing operational guide equivalent to `CLAUDE.md` so agent behavior stays consistent across tools.
+- **Changes made:**
+  - `AGENTS.md` — added a repository-root agent guide mirroring `CLAUDE.md` sections: build/test commands, architecture overview, key patterns, lint constraints, CLI change checklist, coverage thresholds, `spec-files/progress.md` update rules, and spec execution workflow.
+  - `AGENTS.md` — clarified CLI documentation maintenance to keep `CLAUDE.md` and `AGENTS.md` aligned when command surfaces change.
+- **Result:** Documentation update completed. Command/test execution not required for this change.
+
+---
+
+✅ **Entry 181 — Expand M42 spec with concrete ProviderFactory object model**
+
+- **Goal:** Remove ambiguity in `agentic_orchestrator_real_worker_provider_execution_spec.md` by defining exactly how ProviderFactory is implemented and what concrete provider objects planner/builder/qa runtime will use.
+- **Changes made:**
+  - `spec-files/outstanding/agentic_orchestrator_real_worker_provider_execution_spec.md`
+    - bumped spec version to `1.1`
+    - replaced high-level Section 4 with normative ProviderFactory design details:
+      - explicit `WorkerProviderFactory`/`CreateWorkerProviderInput` contract
+      - concrete object set: `DefaultWorkerProviderFactory`, `CliWorkerProvider`, `ApiWorkerProvider`, `NullWorkerProvider`, and parser objects
+      - deterministic provider-to-adapter mapping table for `codex|claude|kiro-cli|copilot|custom|gemini`
+      - normative factory decision algorithm including `provider_stub_disallowed` and `provider_runtime_unavailable` behavior
+      - explicit planner/builder/qa lifecycle and clarification that roles consume sessions from one runtime-scoped provider instance
+      - required provider module decomposition boundaries/files
+    - updated file-level targets to include new provider factory/adapter/parser files.
+- **Result:** Spec now contains implementation-ready ProviderFactory semantics and object lifecycle detail for planner/builder/qa execution paths.
+
+---
+
+✅ **Entry 182 — Draft standalone human-input interaction protocol spec (M43)**
+
+- **Goal:** Define a dedicated, implementation-ready specification for how planner/builder/qa request user input, pause deterministically, and resume after answers.
+- **Changes made:**
+  - `spec-files/outstanding/agentic_orchestrator_human_input_interaction_protocol_spec.md` (new)
+    - Added full protocol spec for first-class question/answer lifecycle (ask, persist, pause, answer, resume, timeout).
+    - Defined new runtime status contract (`awaiting_input`) and state frontmatter additions (`human_input.*`).
+    - Defined new MCP tools: `feature.question_create`, `feature.question_list`, `feature.question_answer` with required schemas and idempotency requirements.
+    - Specified WorkerDecisionLoop integration (`REQUEST.action=ask_user_input`), run/wave skip semantics, and context enrichment contract.
+    - Specified CLI additions (`aop questions`, `aop answer`) and status/dashboard output fields.
+    - Included normative edge-case matrix, implementation milestones (M43.1-M43.5), file-level targets, verify-path test plan, acceptance criteria, and risk mitigations.
+- **Result:** Standalone spec created in `spec-files/outstanding/` with explicit cluster behavior for human-input pauses and deterministic resume semantics.
+
+---
+
+✅ **Entry 183 — Add explicit OOP/architecture guardrails to M42 provider execution spec**
+
+- **Goal:** Make implementation expectations explicit that M42 work must follow OOP and architecture best-practice constraints (KISS, SRP, SOLID-oriented design, hexagonal boundaries).
+- **Changes made:**
+  - `spec-files/outstanding/agentic_orchestrator_real_worker_provider_execution_spec.md`
+    - added new section `0.4 OOP and Architecture Guardrails (Mandatory)` with normative requirements for:
+      - KISS
+      - SRP
+      - SOLID-oriented interface/dependency rules
+      - Hexagonal architecture boundaries (ports/adapters)
+      - composition over inheritance
+      - high cohesion / low coupling
+    - added explicit module-boundary requirements tying those principles to factory/adapter/parser/supervisor separation.
+- **Result:** M42 spec now explicitly mandates OOP and architecture best-practice implementation constraints for all agents executing the spec.
+
+---
+
+✅ **Entry 184 — Add explicit Design Principles section to CLAUDE.md and AGENTS.md**
+
+- **Goal:** Make architecture and design best-practice guidance explicit in both assistant instruction docs.
+- **Changes made:**
+  - `CLAUDE.md`
+    - added new `## Design Principles` section with explicit guidance for KISS, SRP, pragmatic SOLID application, Hexagonal Architecture boundaries, composition over inheritance, and high cohesion/low coupling.
+  - `AGENTS.md`
+    - added matching `## Design Principles` section with the same explicit principles so Codex and Claude guidance remain aligned.
+- **Result:** Both assistant docs now explicitly call out the requested design principles and architecture expectations.
+
+---
+
+✅ **Entry 185 — Align M43 human-input protocol spec with Design Principles standards**
+
+- **Goal:** Ensure the standalone human-input protocol spec explicitly enforces the same OOP/architecture standards now defined in `CLAUDE.md` and `AGENTS.md`.
+- **Changes made:**
+  - `spec-files/outstanding/agentic_orchestrator_human_input_interaction_protocol_spec.md`
+    - bumped version to `1.1`
+    - added new section `0.4 OOP and Architecture Guardrails (Mandatory)` with explicit normative requirements for:
+      - KISS
+      - SRP
+      - pragmatic SOLID application (open/closed, interface segregation, dependency inversion)
+      - Hexagonal architecture boundaries
+      - composition over inheritance
+      - high cohesion / low coupling
+    - added concrete module-boundary requirements so question lifecycle domain logic, state transitions, adapters, and normalized provider payload handling remain separated.
+    - extended acceptance criteria to require compliance with Section 0.4 boundaries.
+- **Result:** Both newly authored specs (M42 + M43) now explicitly encode the same design-principle constraints for implementing agents.