@open-agent-toolkit/cli 0.3.19 → 0.3.20

package/assets/skills/oat-project-implement/references/docs/gate-approval-record.md

@@ -62,6 +62,15 @@ replaces the record.
   core, written and read under the same rules as `oat_quick_start_gate`. It is
   absent when no gate is configured, and nothing routes on it: it is provenance
   only.
+- **`oat_milestone_gates[mNN].plan` and `.exit`** (goal mode;
+  `oat-project-goal` writes `plan` after each milestone's approval, and
+  `oat-project-implement`'s milestone closeout writes `exit`) carry the core
+  plus `resolution` (`configured`, `no_gate`, or `project_disabled`), a
+  `subject` binding (`plan` or `code` and the milestone's ordered phase set),
+  and derived `freshness` with `freshness_reason`. `reviewed_head` is `null`
+  for `no_gate` and `project_disabled`, and `no_gate` is written rather than
+  omitted because routing reads these carriers. `oat-project-brief`'s
+  `references/brief-contract.md` section 12.4 is their contract.
 
 ## Reading a quick-start record
 

package/assets/skills/oat-project-implement/references/phase-execution.md

@@ -17,8 +17,10 @@ responsible for file boundaries, verification, and task commits.
 
 #### Brief-Mode Phase Execution
 
-When `oat_workflow_mode` is `brief`, each phase is one phase-unit with Intent
-and Exit evidence instead of planned tasks. Every rule in this route still
+When `oat_workflow_mode` is `brief` or `goal`, each phase is one phase-unit
+with Intent and Exit evidence instead of planned tasks; goal also scopes every
+run to a milestone, recovery or terminal phase set (`plan-and-resume.md`, Goal
+Projects). Every rule in this route still
 applies except where this subsection replaces it, and
 `oat-project-brief/references/brief-contract.md` (sections 3, 6, 7, and 10) is
 authoritative where the two differ. The subsection is inert for every other
@@ -200,7 +202,7 @@ Before each phase:
      spec: {PROJECT_PATH}/spec.md
      implementation: {PROJECT_PATH}/implementation.md
      discovery: {PROJECT_PATH}/discovery.md
-   workflow_mode: {spec-driven|quick|import|lite|brief} # lite is always a single phase; brief phases carry Intent and Exit evidence, not tasks
+   workflow_mode: {spec-driven|quick|import|lite|brief|goal} # lite is always a single phase; brief and goal phases carry Intent and Exit evidence, not tasks
    active_provider: {codex|claude|cursor|other}
    phase_base_head: {PHASE_BASE_HEAD}
    worktree: {assigned checkout}
@@ -1217,6 +1219,11 @@ summary, and design/plan deviations. `oat_plan_hill_phases` lists phases after
 which execution pauses; an empty list means every phase.
 In brief modes an empty list means none (`plan-and-resume.md` Step 2.5), and a
 phase boundary is reached only when the phase-unit is accepted.
+In goal mode the last accepted phase of a milestone or recovery scope leads to
+Goal Milestone Closeout (`completion-and-closeout.md`), not to the final
+review: the milestone's integrated review is requested with its explicit
+`code mNN: <ordered phase ids>` scope after the exit carrier is allowed and
+fresh, and `code final` belongs to terminal closeout only.
 
 Before a configured non-final HiLL pause, run auto-review when enabled. Scope
 starts after the last passed whole-phase review and ends at the current phase.

package/assets/skills/oat-project-implement/references/plan-and-resume.md

@@ -24,6 +24,32 @@ logged brief edits Step 2.2 allows (adding, splitting, reordering, or making
 phases concrete within the approved outcomes); those are part of brief
 execution, not scope expansion.
 
+### Goal Projects
+
+When `state.md` records `oat_workflow_mode: goal`, every brief-family rule
+above applies, and `oat-project-brief/references/brief-contract.md` section 12
+wins where this route restates it. Goal adds a scope to each run:
+
+- **Active scope.** Read the router's context (`oat project status --json`,
+  `recommendation.context`): `scope mNN: <ordered phase ids>` is the active
+  milestone's ordered phase set from the shared Milestones reader;
+  `scope mNN/dNN: …` or a pending `oat_goal_recovery` record is a recovery
+  scope (its `phase_ids`); `scope terminal: …` is the terminal execution scope
+  after a declaration, which excludes audited `deferred` and `retired`
+  phases; `closeout mNN: …` or `closeout mNN/dNN: …` runs the scoped milestone
+  closeout in `completion-and-closeout.md` (Goal Milestone Closeout) without
+  dispatching a phase. Never widen a scope to phases of another milestone.
+- **Ownership.** Implement never writes `oat_milestone`, never activates a
+  milestone, never registers a delivery, and never writes `declared_met`: it
+  consumes the declaration. It writes only the milestone status and recovery
+  stage transitions that Goal Milestone Closeout names.
+- **Recovery isolation.** Executing a recovery scope for an older delivery
+  leaves `oat_milestone`, `oat_milestone_status`, `oat_current_task_id`, and
+  `oat_current_task` unchanged; progress is recorded in the journal and the
+  recovery record.
+- **Invalid membership.** A `Active milestone membership invalid` reason stops
+  before dispatch and routes to `oat-project-goal`.
+
 ### Step 1: Check Plan Complete
 
 ```bash
@@ -388,7 +414,8 @@ cat "$PROJECT_PATH/implementation.md" 2>/dev/null | head -20
   record ID (brief contract section 8). Resolve a record ID to its phase and a
   phase ID to itself; `null`, an unknown ID, or an accepted or extracted unit
   resolves to the first incomplete phase-unit in document order within the
-  active scope, which is every phase in brief. Phase-units come from the brief's
+  active scope, which is every phase in brief and the Goal Projects scope in
+  goal. Phase-units come from the brief's
   `## Phase` headings, never from task headings, and a provisional phase is
   incomplete. Print `Resuming from {phase_id}.` and apply the Step 2.2
   provisional rule before dispatching it. When every phase-unit in the active

package/assets/skills/oat-project-lite/SKILL.md

@@ -7,7 +7,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
 metadata:
-  version: 1.1.9
+  version: 1.1.10
 ---
 
 # Lite Project