@open-agent-toolkit/cli 0.3.18 → 0.3.20

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

@@ -6,7 +6,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
 metadata:
-  version: 1.4.3
+  version: 1.4.5
 ---
 
 # New OAT Project
@@ -73,6 +73,10 @@ Use the CLI scaffolder:
 oat project new "{project-name}" --mode spec-driven [--scope shared|local|synced]
 ```
 
+This skill scaffolds spec-driven projects only. Quick, lite, brief, and goal projects
+start from their entry skills (`oat-project-quick-start`, `oat-project-lite`,
+`oat-project-brief`, `oat-project-goal`), which run `oat project new --mode <mode>` themselves.
+
 Optional flags:
 
 - `--scope shared|local|synced` (omitting it uses `projects.defaultScope`, whose default is `synced`)

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

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Bash(git:*), Bash(oat:*), Skill
 metadata:
-  version: 1.1.5
+  version: 1.1.7
 ---
 
 # Project Next
@@ -108,6 +108,8 @@ projects, and synced records whose detached checkout is absent.
   - `oat-project-new` — Create a spec-driven project
   - `oat-project-quick-start` — Start a quick workflow project
   - `oat-project-lite` — Start a lite workflow project
+  - `oat-project-brief` — Start a brief workflow project
+  - `oat-project-goal` — Start a goal workflow project
   - `oat-project-import-plan` — Import an external plan
   - **STOP.** Do not attempt routing.
 
@@ -126,17 +128,17 @@ projects, and synced records whose detached checkout is absent.
 
 Read `"$PROJECT_PATH/state.md"` frontmatter and extract:
 
-| Field                     | Used For                                                                                     |
-| ------------------------- | -------------------------------------------------------------------------------------------- |
-| `oat_phase`               | Current lifecycle position (discovery, spec, design, plan, implement)                        |
-| `oat_phase_status`        | Phase completion state (in_progress, complete, pr_open)                                      |
-| `oat_workflow_mode`       | Routing table selection (spec-driven, quick, import, lite). Default: `spec-driven`           |
-| `oat_hill_checkpoints`    | Which phases require HiLL approval                                                           |
-| `oat_hill_completed`      | Which HiLL gates have been passed                                                            |
-| `oat_blockers`            | Informational warnings (not routing gates)                                                   |
-| `oat_implement_exit_gate` | Whether the implementation exit gate is allowed and fresh                                    |
-| `oat_quick_start_gate`    | Reported only in the Step 6 announcement; never a routing input                              |
-| `oat_lifecycle`           | Terminal status (active, paused, complete). `complete` is the terminal signal Step 5.2 reads |
+| Field                     | Used For                                                                                        |
+| ------------------------- | ----------------------------------------------------------------------------------------------- |
+| `oat_phase`               | Current lifecycle position (discovery, spec, design, plan, implement)                           |
+| `oat_phase_status`        | Phase completion state (in_progress, complete, pr_open)                                         |
+| `oat_workflow_mode`       | Routing table selection (spec-driven, quick, import, lite, brief, goal). Default: `spec-driven` |
+| `oat_hill_checkpoints`    | Which phases require HiLL approval                                                              |
+| `oat_hill_completed`      | Which HiLL gates have been passed                                                               |
+| `oat_blockers`            | Informational warnings (not routing gates)                                                      |
+| `oat_implement_exit_gate` | Whether the implementation exit gate is allowed and fresh                                       |
+| `oat_quick_start_gate`    | Reported only in the Step 6 announcement; never a routing input                                 |
+| `oat_lifecycle`           | Terminal status (active, paused, complete). `complete` is the terminal signal Step 5.2 reads    |
 
 **If state.md is missing or unreadable:** Report error and suggest running the relevant phase skill directly. STOP.
 
@@ -220,6 +222,10 @@ Phase-to-skill mapping for HiLL override:
 | design    | `oat-project-design`   |
 | plan      | `oat-project-plan`     |
 
+In brief mode the `plan` row maps to `oat-project-brief`, which owns brief
+planning; spec-driven planning is never a brief project's current-phase skill.
+In goal mode it maps to `oat-project-goal` the same way.
+
 Note: a `spec` HiLL phase only appears in legacy projects scaffolded before requirements confirmation was folded into `oat-project-design`. New projects scaffold with `['discovery', 'design']` HiLL checkpoints, so `spec` falls through to `oat-project-design` here as a graceful migration. The standalone `oat-project-spec` skill remains available as an opt-in for users who want to formalize requirements separately.
 
 Note: `implement` is intentionally omitted. Implementation-phase checkpoints are handled by `oat_plan_hill_phases` in plan.md (plan-phase-level gates), not by the workflow-level `oat_hill_checkpoints` in state.md.
@@ -300,6 +306,45 @@ for a quick project.
 | plan          | complete     | tier 1        | `oat-project-implement` \* |
 | implement     | in_progress  | —             | `oat-project-implement` \* |
 
+**Brief Mode:**
+
+| Current Phase | Phase Status | Boundary Tier | Target Skill               |
+| ------------- | ------------ | ------------- | -------------------------- |
+| plan          | in_progress  | tier 3        | `oat-project-brief`        |
+| plan          | in_progress  | tier 2        | `oat-project-brief`        |
+| plan          | complete     | tier 1        | `oat-project-implement` \* |
+| implement     | in_progress  | —             | `oat-project-implement` \* |
+
+Unlike lite, tier 2 stays with `oat-project-brief`: a brief becomes
+implementation-ready only through its recorded review disposition and single
+approval, which that skill owns. Brief progress counts phase-units, not tasks.
+
+**Goal Mode:** the control plane owns goal routing (`oat project status --json`,
+`recommendation.skill` and `recommendation.context`); dispatch that skill with
+that context. Before any milestone state exists, the planning rows match brief
+mode with `oat-project-goal` in place of `oat-project-brief`. After it exists,
+routing follows this priority, the first match winning:
+
+| Priority | Condition                                                                                                                     | Target Skill                                                    | Context                                    |
+| -------- | ----------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | ------------------------------------------ |
+| 1        | `oat_goal_status: declared_met` with an invalid outcome audit                                                                 | `oat-project-goal`                                              | `audit`                                    |
+| 1        | `declared_met`: received feedback, then pending recovery, then incomplete terminal scope, then the post-implementation router | review-receive / stage owner / `oat-project-implement` / Step 5 | `scope terminal: …`                        |
+| 2        | Actionable review artifacts                                                                                                   | `oat-project-review-receive`                                    | —                                          |
+| 2        | Pending `oat_goal_recovery` at `implementing` / `exit_gate`                                                                   | `oat-project-implement`                                         | `scope mNN/dNN: …` / `closeout mNN/dNN: …` |
+| 2        | Pending `oat_goal_recovery` at `reviewing` / `receiving` / `delivering`                                                       | by missing evidence (rows 4c–4d below)                          | the recovery's explicit scope              |
+| 3        | Active milestone membership invalid                                                                                           | `oat-project-goal`                                              | —                                          |
+| 4a       | `aligning`                                                                                                                    | `oat-project-goal`                                              | `align mNN`                                |
+| 4b       | `implementing`: incomplete unit in scope / every unit accepted                                                                | `oat-project-implement`                                         | `scope mNN: …` / `closeout mNN: …`         |
+| 4c       | `reviewing`: queued fixes or a missing, blocked or stale exit carrier                                                         | `oat-project-implement`                                         | `scope mNN: …` / `closeout mNN: …`         |
+| 4c       | `reviewing`: carrier fresh, integrated review missing or stale / produced and unreceived / passed                             | review-provide / review-receive / review-receive                | `code mNN: …` / `receive <artifact>`       |
+| 4d       | `delivering`: passed review and allowed, fresh carrier; otherwise rows 4c by missing evidence                                 | `oat-project-pr-progress`                                       | `deliver mNN`                              |
+| 4e       | `delivered`                                                                                                                   | `oat-project-goal`                                              | `realign mNN`                              |
+
+Goal progress counts phase-units per active milestone. `delivered` is not the
+endpoint: activation of the next milestone waits for the delivery's agreed
+endpoint, which `oat-project-goal` observes. The Step 5 brief phase-unit guard
+applies to goal only within the active milestone's scope at `implementing`.
+
 \* `oat-project-implement` handles both sequential and parallel execution.
 
 ### Step 4: Check for Unprocessed Reviews (Review Safety Check)
@@ -329,6 +374,14 @@ Entry condition: `oat_phase == "implement"` AND (`oat_phase_status == "complete"
 
 Apply the following checks in priority order. Stop at the first match:
 
+**Brief phase-unit guard (brief mode, applied first).** When
+`oat_workflow_mode: brief` and `oat_lifecycle` is not `complete`, read
+`project.progress.phases` from `oat project status --json`. If any phase has
+`provisional: true` or `completed` below `total`, route to
+`oat-project-implement` before every check below and announce: "Incomplete
+phase-units remain in the active scope". A `complete` or `pr_open` phase status
+alone never finalizes a brief project.
+
 **5.0: Unresolved implementation exit gate**
 
 Before every other post-implementation route, inspect
@@ -479,7 +532,8 @@ and fall through to 5.3, and do not route to `oat-project-implement` even when
 signal here — neither a null current task nor a `complete` or `pr_open`
 `oat_phase_status` is terminal, because an active project reaches both while it
 still owns pending revision work. The guard is workflow-mode independent: it
-applies identically to `spec-driven`, `quick`, `import`, and `lite` projects.
+applies identically to `spec-driven`, `quick`, `import`, `lite`, `brief`, and
+`goal` projects.
 
 For every other `oat_lifecycle` value the check below is unchanged.
 
@@ -529,7 +583,10 @@ Ignore matching rows outside `REVIEWS_SECTION`; they are not review events.
 routes directly to `oat-project-pr-final` before the summary check below.
 Announce: "Final review passed — creating final PR". Optional lite summary or
 documentation work is owned by the immutable implementation closeout snapshot,
-not this fallback router.
+not this fallback router. The lite shortcut does not apply to brief projects:
+brief closeout takes 5.5 through 5.7 and never skips the summary. Goal
+terminal closeout follows brief closeout after a valid declaration; its `pr`
+step is satisfied by delivery coverage.
 
 **5.5: Summary not done**
 

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

@@ -58,6 +58,19 @@ replaces the record.
   record is current.
 - **`oat_quick_start_gate`** (`oat-project-quick-start`, Gate Execution) carries
   exactly the core.
+- **`oat_brief_gate`** (`oat-project-brief`, Gate Execution) carries exactly the
+  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-plan/SKILL.md

@@ -6,7 +6,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash(git:*), Bash(oat template:*), Glob, Grep, AskUserQuestion
 metadata:
-  version: 1.4.17
+  version: 1.4.19
 ---
 
 # Planning Phase
@@ -20,8 +20,8 @@ Before a parent-branch commit, verify `oat internal commit-paths --help` succeed
 ## Prerequisites
 
 This skill is the plan authoring path for **spec-driven** projects only. Quick,
-import, and lite modes have dedicated entry skills that produce `plan.md`
-directly.
+import, lite, brief, and goal modes have dedicated entry skills that produce
+`plan.md` directly.
 
 Read `oat_workflow_mode` from `{PROJECT_PATH}/state.md` (default: `spec-driven`):
 
@@ -29,6 +29,8 @@ Read `oat_workflow_mode` from `{PROJECT_PATH}/state.md` (default: `spec-driven`)
 - **`quick`**: **Stop.** Spec-driven planning does not apply here: the quick workflow authors `plan.md` itself and owns it through its own review disposition. Step 1 routes the project by the named **quick plan readiness** predicate instead of assuming the plan is finished.
 - **`import`**: **Stop.** If a normalized `plan.md` exists, tell the user: "Imported plan is ready. Run `oat-project-implement` to begin execution." If no `plan.md` exists, tell the user: "Run `oat-project-import-plan` to import and normalize the external plan first."
 - **`lite`**: **Stop.** Tell the user: "Lite planning is owned by `oat-project-lite`; run it to author or resume the combined plan contract."
+- **`brief`**: **Stop.** Tell the user: "Brief planning is owned by `oat-project-brief`; run it to author or resume the Project Brief."
+- **`goal`**: **Stop.** Tell the user: "Goal planning is owned by `oat-project-goal`; run it to author, amend, or re-align the Project Brief and its milestones."
 
 ## Plan Format Contract
 
@@ -162,6 +164,25 @@ Exit skill.
 
 Exit skill.
 
+**Mode: `brief`** — **STOP.** Print:
+
+```
+⚠️  This project uses brief mode. Run `oat-project-brief` to author or resume
+    its Project Brief; brief phases carry intent and exit evidence, not tasks.
+```
+
+Exit skill.
+
+**Mode: `goal`** — **STOP.** Print:
+
+```
+⚠️  This project uses goal mode. Run `oat-project-goal` to author, amend, or
+    re-align its Project Brief and milestones; goal phases carry intent and
+    exit evidence, not tasks.
+```
+
+Exit skill.
+
 **Mode: `import`** — **STOP.** Check if `"$PROJECT_PATH/plan.md"` exists:
 
 - If yes: Print: "Imported plan is ready. Run `oat-project-implement` to begin execution."

package/assets/skills/oat-project-plan-writing/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Glob, Grep
 metadata:
-  version: 1.2.35
+  version: 1.2.37
 ---
 
 # Plan Writing Contract
@@ -87,8 +87,8 @@ then continue without formatting.
 ## Managed Dispatch Readiness and Review Contract
 
 All plan-producing workflows and their artifact reviews use this contract:
-spec-driven planning, quick-start, lite planning, imported plans, and
-provider-plan-via-import.
+spec-driven planning, quick-start, lite planning, brief and goal authoring,
+imported plans, and provider-plan-via-import.
 The contract runs before a plan becomes implementation-ready and immediately
 before each artifact review dispatch.
 
@@ -564,7 +564,7 @@ Every `plan.md` produced or edited by any OAT skill **must** satisfy these invar
 
 ```yaml
 ---
-oat_plan_source: spec-driven | quick | imported | lite # origin workflow mode
+oat_plan_source: spec-driven | quick | imported | lite | brief | goal # origin workflow mode
 oat_status: in_progress | complete # plan lifecycle status
 oat_ready_for: null | oat-project-implement # downstream consumer
 # Optional after implementation confirmation:
@@ -669,11 +669,15 @@ Required inputs vary by workflow mode. The calling skill reads `oat_workflow_mod
 | `quick`       | `discovery.md` + repo knowledge context          | No          |
 | `import`      | Preserved external source + normalized `plan.md` | No          |
 | `lite`        | `plan.md` only                                   | No          |
+| `brief`       | `plan.md` (Project Brief) from the interview     | No          |
+| `goal`        | `plan.md` (Project Brief with Milestones)        | No          |
 
 - **`spec-driven`**: Plan is derived from a complete design document. All design components must be covered by tasks.
 - **`quick`**: Plan is generated directly from discovery decisions and repo knowledge. No design artifact is required.
 - **`import`**: External plan is preserved in `references/imported-plan.md` and normalized into canonical format. Subsequent edits follow this contract.
 - **`lite`**: `plan.md` is the sole requirements and implementation contract. It carries Summary, Decisions, Assumptions, Out of Scope, and Validation Criteria before one sequential phase; no discovery, spec, or design artifact is required.
+- **`brief`**: `plan.md` is the Project Brief authored by `oat-project-brief`: Goal, Outcomes with intended evidence, Approach, Decisions, Known Unknowns, and `## Phase pNN:` blocks with Intent and Exit evidence instead of tasks. `oat project validate-plan` applies the brief profile. Stable Task IDs, task totals, and the task grammar in this contract do not apply to the brief; execution records live in `implementation.md`, and the Reviews preservation rules apply unchanged.
+- **`goal`**: `plan.md` is a Project Brief authored and amended by `oat-project-goal`, with the brief rules above plus a canonical `## Milestones` table (`oat-project-brief/references/brief-contract.md` section 12.1). `oat project validate-plan` applies the goal profile on top of the brief profile. Each milestone's approval is evidenced by its `oat_milestone_gates[mNN].plan` carrier after the first approval (section 12.4).
 
 ## Resume and Edit Guardrails
 

package/assets/skills/oat-project-pr-final/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Write, Bash(awk:*), Bash(gh:*), Bash(git:*), Bash(mktemp:*), Bash(oat:*), Bash(rm:*), Glob, Grep, AskUserQuestion
 metadata:
-  version: 1.6.9
+  version: 1.6.11
 ---
 
 # Project PR (Final)
@@ -29,6 +29,9 @@ Generate a PR-ready summary grounded in canonical OAT artifacts, including:
 - In `spec-driven` mode: `{PROJECT_PATH}/spec.md` and `{PROJECT_PATH}/design.md` are required
 - In `quick`/`import`/`lite` mode: `spec.md`/`design.md` are optional; lite
   proceeds with a reduced assurance note because plan.md is its full contract
+- In `brief` mode: `plan.md` (the Project Brief) and `implementation.md` are
+  required, `discovery.md`/`spec.md`/`design.md` are absent by design, and
+  `summary.md` is required exactly as in quick mode
 
 **Required (recommended to proceed):**
 
@@ -177,7 +180,56 @@ If `WORKFLOW_MODE=spec-driven`, also require:
 ls "$PROJECT_PATH/spec.md" "$PROJECT_PATH/design.md" 2>/dev/null
 ```
 
-If `WORKFLOW_MODE` is `quick`, `import`, or `lite`, proceed without spec/design and include a reduced assurance note in the PR body. For lite, explicitly note that plan.md is the reduced artifact contract and the absence of discovery/spec/design is intentional.
+If `WORKFLOW_MODE` is `quick`, `import`, `lite`, or `brief`, proceed without spec/design and include a reduced assurance note in the PR body. For lite, explicitly note that plan.md is the reduced artifact contract and the absence of discovery/spec/design is intentional. For brief, the note names the Project Brief (`plan.md`) as the requirements contract, audited against its numbered Outcomes, with the phase journal as the evidence record; the absence of discovery/spec/design is intentional.
+
+**Goal mode (`oat_workflow_mode: goal`).** pr-final is the terminal delivery
+registration owner, not a second project PR (brief contract sections 12.7 and
+12.9). Run Step 1.5 instead of Steps 2–6.
+
+### Step 1.5: Goal Terminal Delivery Registration (`goal` only)
+
+1. **Declaration first.** Require `oat_goal_status: declared_met` and a valid
+   outcome audit: run `oat project closeout-check "$PROJECT_PATH" --json`
+   (read-only). A `not-declared` or `audit-invalid` refusal routes to
+   `oat-project-goal`; refusals naming the review owners, scoped implement, or
+   `oat-project-pr-progress` route there. Continue only when the remaining
+   refusal is `phase-uncovered` (`nextOwner.skill: oat-project-pr-final`).
+2. **No redundant PR.** When the boundary reports no uncovered accepted phase,
+   delivery coverage already holds: create no pull request, write no state, and
+   report that the configured `pr` step is satisfied by delivery coverage at its
+   position (implement records `satisfied_by: { pr: delivery-coverage }`).
+3. **Terminal scope.** The terminal delivery's frozen `scope` is the uncovered
+   accepted phases named by the refusal, ordered by the brief, never audited
+   `deferred`, `retired`, or `extracted` phases. A delivery never spans
+   milestones (`goal-delivered-scope-changed`), so uncovered phases in several
+   milestones register one terminal delivery per milestone, in milestone order.
+   Registered from one head branch, they share the same member pull request:
+   the second delivery's `gh pr list` attach finds the PR the first one
+   created, and that shared member is expected, not a duplicate
+   (`oat-project-brief/references/brief-contract.md` section 12.7, Shared
+   members). Coverage judges each delivery's own scope and bound evidence.
+4. **Same registration contract.** Load the current
+   `oat-project-pr-progress/SKILL.md` and, for each terminal delivery, run its
+   Step 5.5 steps 1–3 and 4–7 as written (never step 3a, which
+   re-checks the active milestone's own registered delivery) with `kind: pr`: refresh, a
+   deliverable `oat project delivery check` (`status: ok`) for the subject,
+   stale evidence stopping before registration, the `registering` entry with
+   its lookup keys, reciprocal links, the integrated review and the captured
+   `exit_gate`, idempotent create-or-attach through `gh pr list`, and the
+   member and `status: open` record. The Step 5 ledger-path guard runs before
+   `gh pr create`. While the boundary still reports `phase-uncovered`, a
+   `summary` step configured before `pr` writes only project-directory files
+   and defers its repo-level ledger and decision-record
+   writes until this registration is done (`oat-project-summary` Step 6, Goal
+   terminal deferral), so the terminal subject stays deliverable.
+5. **Log.** After the registration commit, append exactly one structural entry
+   and commit it in this step:
+   `oat project log append --project "$PROJECT_PATH" --structural --producer oat-project-pr-final --ref <dNN> --idempotency-key "<goal-slug>-register-<dNN>" --body "Registered terminal delivery <dNN> (<ordered phase ids>) at <url>; <goal-slug>-register-<dNN>"`.
+   Never pre-check log configuration: the helper no-ops when logging is
+   disabled.
+6. Re-run `oat project closeout-check "$PROJECT_PATH" --json` and report the
+   next owner. Coverage completes only when every terminal delivery reaches its
+   agreed endpoint (`oat project delivery refresh` observes it).
 
 ### Step 2: Check Final Review Status
 
@@ -254,6 +306,10 @@ only for the remaining available artifacts; do not invoke
 `oat-project-summary` for lite. This branch ends Step 3.0 and jumps directly to
 Step 3.1.
 
+Brief projects take the non-lite branch below: `summary.md` is generated or
+refreshed exactly as in quick mode, with freshness decided by
+`oat_summary_phase_fingerprint` (`oat-project-summary` Step 3).
+
 **Non-lite branch only:** If the route contract sets
 `GENERIC_SUMMARY_REACHABLE=true`, check if `{PROJECT_PATH}/summary.md` exists:
 
@@ -277,6 +333,11 @@ Read:
 - `{PROJECT_PATH}/discovery.md` (recommended for quick mode)
 - `{PROJECT_PATH}/references/imported-plan.md` (recommended for import mode)
 
+In brief mode `plan.md` is the Project Brief (Goal, Outcomes, Approach,
+Constraints and Out of Scope, Decisions, phases, and Reviews) and
+`implementation.md` is the per-phase journal; spec, design, and discovery are
+absent by design and are not read.
+
 If `implementation.md` exists, check for a filled `## Final Summary (for PR/docs)` section:
 
 - If missing or obviously empty, warn the user that PR/docs quality will suffer and recommend:
@@ -388,7 +449,7 @@ oat_project: { PROJECT_PATH }
 
 ## Goals / Non-Goals
 
-{brief bullets from available requirement artifacts: spec in spec-driven mode; discovery/import source in quick/import; plan contract in lite}
+{brief bullets from available requirement artifacts: spec in spec-driven mode; discovery/import source in quick/import; plan contract in lite; the brief's Goal, Outcomes, and Constraints and Out of Scope in brief}
 
 ## Changes
 
@@ -775,3 +836,4 @@ If `state.md` is missing, skip with a warning.
 - User has clear next step to open PR (manual or gh)
 - Project `state.md` shows `oat_phase_status: pr_open`
 - Next milestone references both `oat-project-revise` (for feedback) and both supported `oat-project-complete` orderings
+- Goal mode: a terminal delivery was registered only after a valid declaration and audit, only for uncovered accepted phases, through the pr-progress registration contract, with one structural log entry per registration; no PR was created when coverage already held