@open-agent-toolkit/cli 0.3.15 → 0.3.16

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

@@ -5,7 +5,7 @@ disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Bash(git:*), Bash(oat:*), AskUserQuestion
 metadata:
-  version: 1.4.3
+  version: 1.4.4
 ---
 
 # Progress Router
@@ -179,6 +179,8 @@ Read `{project}/state.md` frontmatter:
 - `oat_hill_completed` - Completed HiLL checkpoints
 - `oat_skill_gate_overrides` - Configured lifecycle gates this project
   deliberately disabled, keyed by gate-aware skill name
+- `oat_implement_exit_gate` - The implementation exit gate record
+- `oat_quick_start_gate` - The quick-start plan gate record
 
 **Display format:**
 
@@ -191,6 +193,8 @@ Read `{project}/state.md` frontmatter:
    Completed: {oat_hill_completed as checkmarks}
    HiLL Pending: {yes/no for current phase}
    Gate Overrides: {gate-aware skill keys from oat_skill_gate_overrides, or "None"}
+   Quick-Start Gate: {status}/{disposition}, decided {decided_at}, fingerprint {config_fingerprint} (as recorded), or "None"
+   Exit Gate: {status}/{disposition} as recorded, or "None"
    Blockers: {oat_blockers or "None"}
    Next: {recommended_skill}
 ```
@@ -203,6 +207,16 @@ even when no gate is currently configured for that skill, and never infer a
 configured gate from an override alone. This is read-only reporting: never add,
 remove, or repair the map here.
 
+Both gate records share the core defined in
+`references/docs/gate-approval-record.md`. Report a quick-start record as that
+doc describes: its stored fields as recorded, with `config_fingerprint` shown as
+provenance and never recomputed, or `malformed` when its fields do not form a
+valid record. Report the exit-gate
+record's `status` and `disposition` as recorded; its freshness belongs to the
+implementation workflow and is not re-derived here. Either record adds no route
+and no warning: quick plan readiness stays the single routing rule for quick
+plans. Show "None" for an absent record, and never write or repair one here.
+
 ### Step 5: Determine Next Skill
 
 Based on project state, recommend next action.

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

@@ -0,0 +1,80 @@
+# Lifecycle Gate Approval Record
+
+A configured lifecycle gate ends in an outcome the operator or a later session
+needs to see again: it passed, it warned, the operator explicitly continued
+past a failure, the project disabled it, or it blocked. Chat output does not
+survive the session, so the skill that runs the gate persists the outcome in
+project `state.md`. This document defines the record's shared core once; each
+carrier names where it lives and what it adds.
+
+## Core record
+
+```yaml
+<carrier>:
+  status: allowed # allowed | blocked
+  disposition: passed # passed | warned | prompt_approved | project_disabled; null when blocked
+  config_fingerprint: '<stable hash of the resolved gate declaration>'
+  reviewed_head: '<full SHA of the commit the gate reviewed>'
+  decided_at: '2026-10-02T15:20:00Z'
+```
+
+- `status`: `allowed` | `blocked`.
+- `disposition`: `passed`, `warned`, `prompt_approved`, or `project_disabled`
+  when `status` is `allowed`; `null` when `status` is `blocked`.
+- `config_fingerprint`: the writer's stable hash of the resolved gate
+  declaration it ran (command, description, `onFailure`, `maxAttempts`, and the
+  project override state), recorded as provenance. Implement recomputes its own
+  carrier's fingerprint under its Step 14 rules; quick-start readers do not.
+- `reviewed_head`: the full 40-character SHA of the commit the gate reviewed,
+  recorded as provenance. `null` when no gate ran.
+- `decided_at`: the ISO 8601 UTC time the outcome was decided. A record written
+  before `decided_at` existed is not malformed for that reason alone.
+
+## Write rules
+
+| Gate outcome                                                    | Record                                                      |
+| --------------------------------------------------------------- | ----------------------------------------------------------- |
+| Passed its threshold                                            | `allowed` / `passed`                                        |
+| Failed under `onFailure: warn`                                  | `allowed` / `warned`                                        |
+| Failed under `onFailure: prompt`, operator explicitly continued | `allowed` / `prompt_approved`                               |
+| Failed under `onFailure: prompt`, operator declined or deferred | `blocked` / `null`                                          |
+| `block` still failing after `maxAttempts`                       | `blocked` / `null`                                          |
+| Configured but disabled by project override (no launch)         | `allowed` / `project_disabled`                              |
+| Launch, transport, validation, or receive failure               | `blocked` / `null`                                          |
+| Not configured                                                  | no record (quick-start); implement writes `allowed/no_gate` |
+
+Only an explicit operator continuation writes `prompt_approved`. Declining,
+deferring, giving no response, or running under `OAT_AUTONOMOUS=1` writes
+`blocked`, never anything that reads as approval. A rerun of the same gate
+replaces the record.
+
+## Carriers
+
+- **`oat_implement_exit_gate`** (`oat-project-implement`,
+  `references/completion-and-closeout.md` Step 14) uses this core and keeps its
+  additional values and fields there: the `pending` and `stale` statuses, the
+  `no_gate` disposition, and the resolution, attempt, launch, receive, waiver,
+  and freshness fields. Its own effective-delta freshness rule decides whether a
+  record is current.
+- **`oat_quick_start_gate`** (`oat-project-quick-start`, Gate Execution) carries
+  exactly the core.
+
+## Reading a quick-start record
+
+Readers report a quick-start record as recorded and do not recompute
+`config_fingerprint`: no CLI emits a canonical fingerprint for the quick-start
+gate, so a recomputation could not be reproduced across sessions. They do not
+route on the record either.
+
+- Report `status`, `disposition`, `decided_at`, and `config_fingerprint` (as
+  provenance) exactly as stored.
+- Report the record as malformed when `status` and `disposition` do not form
+  one of the combinations in the write rules, or when a present `decided_at` is
+  not a valid ISO 8601 UTC time.
+- `reviewed_head` is provenance only and is not compared with `HEAD`, because
+  the quick-start completion step commits after the gate.
+- An absent record means none was written: no gate was configured, the gate
+  has not reached an outcome, or the plan predates the record. Readers do not
+  infer which.
+
+Readers never write, repair, or infer a record.

package/assets/skills/oat-project-quick-start/SKILL.md

@@ -5,9 +5,9 @@ argument-hint: '<project-name> ["project description"]'
 oat_gateable: true
 disable-model-invocation: true
 user-invocable: true
-allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
+allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Task
 metadata:
-  version: 2.3.17
+  version: 2.3.18
 ---
 
 # Quick Start Project
@@ -846,7 +846,7 @@ as the last check before plan and project completion:
 
    Handle all three `resolution` values explicitly:
    - `not_configured`: no gate is configured; proceed directly to the completion steps in Step 3.7 below.
-   - `configured_disabled_by_project`: the operator disabled this configured gate for this project. Do not launch any process. Emit `configured but disabled by project override`, including the project path and the `projectOverride` source from the envelope, then proceed directly to the completion steps in Step 3.7 below. A project-disabled gate never enters the passed, missing, or failed branches, and its `configuredGate` is evidence only, never executed.
+   - `configured_disabled_by_project`: the operator disabled this configured gate for this project. Do not launch any process. Emit `configured but disabled by project override`, including the project path and the `projectOverride` source from the envelope, write `oat_quick_start_gate` as `allowed/project_disabled` with `reviewed_head: null` per **Persist the gate outcome** below, then proceed directly to the completion steps in Step 3.7 below. A project-disabled gate never enters the passed, missing, or failed branches, and its `configuredGate` is evidence only, never executed.
    - `configured`: continue with the steps below, executing `effectiveGate` exactly as configured.
 
    A null, missing, malformed, or unrecognized result is an operational failure
@@ -891,6 +891,17 @@ as the last check before plan and project completion:
    - `prompt`: surface the gate failure and ask the human how to proceed.
    - `warn`: record the gate failure and continue.
 
+   **Complexity review at `maxAttempts`.** When `block` attempts are exhausted,
+   dispatch the complexity review that
+   `references/docs/complexity-review-fallback.md` defines for the plan bundle
+   before escalating, then show its decision message with the accumulated
+   feedback; under `OAT_AUTONOMOUS=1`, put the same content in the boundary
+   report instead. Record the operator's choice with the report path in
+   `implementation.md`. Agents never select the disposition. Only exhausted
+   `block` attempts trigger the review. To launch it, load the current
+   `oat-project-dispatch-subagents/SKILL.md` and follow it, resolving the route
+   as that doc's "Routing outside implement" section describes.
+
 7. Runtime selection note: the review-only declaration carries producer
    identity, not reviewer runtime identity. By default, `oat gate review` and
    `oat gate cross-provider-exec` resolve the current host from built-in
@@ -905,6 +916,23 @@ A gate that ends in `block` after attempts are exhausted, or at an unresolved
 `prompt` boundary, means the completion steps below MUST NOT run; the phase
 stays `in_progress` and resumable.
 
+**Persist the gate outcome.** For a configured gate, including one disabled by
+project override, write `oat_quick_start_gate` to `$PROJECT_PATH/state.md` with
+the core fields defined in `references/docs/gate-approval-record.md` once the
+gate reaches its outcome, and commit it with the next quick-start bookkeeping
+commit or before stopping:
+
+- passed: `allowed/passed`;
+- `warn` failure: `allowed/warned`;
+- a `prompt` failure the operator explicitly continues past: `allowed/prompt_approved`;
+- a `prompt` failure declined or deferred (every `prompt` failure under
+  `OAT_AUTONOMOUS=1`), `block` exhausted after `maxAttempts`, or a launch,
+  validation, or receive failure: `blocked` with `disposition: null`;
+- `configured_disabled_by_project`: `allowed/project_disabled` with `reviewed_head: null` and no launch.
+
+`not_configured` writes no record. `reviewed_head` is the plan commit the gate
+reviewed and `decided_at` the decision time. A rerun replaces the record. Step 3.7 stays gated by the control flow above and does not read this record back.
+
 ### Step 3.7: Record Review Disposition and Mark Plan Complete
 
 Reach this completion boundary only after the configured gate passes or resolves