@open-agent-toolkit/cli 0.3.7 → 0.3.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/assets/agents/oat-codebase-mapper.md +3 -2
- package/assets/agents/oat-reviewer.md +5 -13
- package/assets/agents/skeptical-evaluator.md +6 -2
- package/assets/bundle-metadata.json +1 -1
- package/assets/docs/cli-utilities/backlog-lifecycle.md +3 -2
- package/assets/docs/cli-utilities/bootstrap.md +5 -2
- package/assets/docs/cli-utilities/config-and-local-state.md +13 -6
- package/assets/docs/cli-utilities/configuration.md +25 -10
- package/assets/docs/cli-utilities/tool-packs.md +60 -10
- package/assets/docs/cli-utilities/workflow-gates.md +37 -0
- package/assets/docs/contributing/code.md +9 -5
- package/assets/docs/provider-sync/commands.md +17 -8
- package/assets/docs/provider-sync/instruction-sync.md +241 -39
- package/assets/docs/provider-sync/providers.md +20 -0
- package/assets/docs/provider-sync/scope-and-surface.md +3 -1
- package/assets/docs/reference/cli-reference.md +4 -1
- package/assets/docs/reference/oat-directory-structure.md +12 -11
- package/assets/docs/reference/troubleshooting.md +19 -4
- package/assets/docs/workflows/projects/evidence-layers.md +5 -1
- package/assets/docs/workflows/projects/implementation-execution.md +22 -8
- package/assets/docs/workflows/projects/lifecycle.md +4 -6
- package/assets/docs/workflows/projects/retro.md +7 -0
- package/assets/public-package-versions.json +4 -4
- package/assets/skills/oat-agent-instructions-analyze/SKILL.md +4 -4
- package/assets/skills/oat-agent-instructions-analyze/references/analysis-artifact-template.md +5 -5
- package/assets/skills/oat-agent-instructions-analyze/references/docs/rules-files.md +14 -11
- package/assets/skills/oat-agent-instructions-analyze/references/quality-checklist.md +2 -2
- package/assets/skills/oat-agent-instructions-analyze/scripts/resolve-instruction-files.sh +4 -3
- package/assets/skills/oat-agent-instructions-analyze/scripts/resolve-providers.sh +17 -6
- package/assets/skills/oat-agent-instructions-apply/SKILL.md +3 -3
- package/assets/skills/oat-agent-instructions-apply/references/docs/rules-files.md +14 -11
- package/assets/skills/oat-dispatch-subagents/SKILL.md +1 -1
- package/assets/skills/oat-dispatch-subagents/references/managed-claude-example.json +387 -0
- package/assets/skills/oat-dispatch-subagents/references/record-schema.md +75 -0
- package/assets/skills/oat-doctor/SKILL.md +17 -13
- package/assets/skills/oat-project-autonomous/references/gate-inventory.md +1 -1
- package/assets/skills/oat-project-document/references/docs/autonomy-contract.md +1 -1
- package/assets/skills/oat-project-implement/SKILL.md +2 -2
- package/assets/skills/oat-project-implement/references/completion-and-closeout.md +33 -11
- package/assets/skills/oat-project-implement/references/dispatch-and-dry-run.md +24 -22
- package/assets/skills/oat-project-implement/references/docs/autonomy-contract.md +1 -1
- package/assets/skills/oat-project-implement/references/phase-execution.md +109 -8
- package/assets/skills/oat-project-lite/SKILL.md +23 -1
- package/assets/skills/oat-project-lite/references/docs/autonomy-contract.md +1 -1
- package/assets/skills/oat-project-next/SKILL.md +3 -3
- package/assets/skills/oat-project-pr-final/references/docs/autonomy-contract.md +1 -1
- package/assets/skills/oat-project-progress/SKILL.md +2 -2
- package/assets/skills/oat-project-quick-start/references/docs/autonomy-contract.md +1 -1
- package/assets/skills/oat-project-retro/SKILL.md +70 -6
- package/assets/skills/oat-project-review-provide/SKILL.md +3 -1
- package/assets/skills/oat-project-review-provide-remote/SKILL.md +3 -1
- package/assets/templates/docs-app-mkdocs/docs/contributing.md +1 -3
- package/assets/templates/pjm-agents.md +7 -3
- package/assets/templates/state.md +2 -2
- package/dist/agents/canonical/resolve.d.ts +6 -4
- package/dist/agents/canonical/resolve.d.ts.map +1 -1
- package/dist/agents/canonical/resolve.js +6 -4
- package/dist/commands/backlog/archive.d.ts +10 -2
- package/dist/commands/backlog/archive.d.ts.map +1 -1
- package/dist/commands/backlog/archive.js +22 -6
- package/dist/commands/backlog/index.d.ts.map +1 -1
- package/dist/commands/backlog/index.js +5 -1
- package/dist/commands/backlog/rewrite-references.d.ts +41 -0
- package/dist/commands/backlog/rewrite-references.d.ts.map +1 -0
- package/dist/commands/backlog/rewrite-references.js +516 -0
- package/dist/commands/config/index.d.ts +1 -0
- package/dist/commands/config/index.d.ts.map +1 -1
- package/dist/commands/config/index.js +69 -34
- package/dist/commands/gate/index.d.ts.map +1 -1
- package/dist/commands/gate/index.js +51 -2
- package/dist/commands/gate/review-verdict.d.ts +22 -0
- package/dist/commands/gate/review-verdict.d.ts.map +1 -1
- package/dist/commands/gate/review-verdict.js +111 -0
- package/dist/commands/init/index.d.ts +6 -0
- package/dist/commands/init/index.d.ts.map +1 -1
- package/dist/commands/init/index.js +27 -4
- package/dist/commands/init/tools/index.d.ts +18 -1
- package/dist/commands/init/tools/index.d.ts.map +1 -1
- package/dist/commands/init/tools/index.js +84 -17
- package/dist/commands/init/tools/project-guidance.d.ts +19 -4
- package/dist/commands/init/tools/project-guidance.d.ts.map +1 -1
- package/dist/commands/init/tools/project-guidance.js +58 -15
- package/dist/commands/init/tools/workflows/index.d.ts.map +1 -1
- package/dist/commands/init/tools/workflows/index.js +5 -1
- package/dist/commands/instructions/instructions.types.d.ts +105 -4
- package/dist/commands/instructions/instructions.types.d.ts.map +1 -1
- package/dist/commands/instructions/instructions.types.js +4 -5
- package/dist/commands/instructions/instructions.utils.d.ts +161 -6
- package/dist/commands/instructions/instructions.utils.d.ts.map +1 -1
- package/dist/commands/instructions/instructions.utils.js +650 -12
- package/dist/commands/instructions/sync/sync.d.ts.map +1 -1
- package/dist/commands/instructions/sync/sync.js +256 -18
- package/dist/commands/instructions/validate/validate.d.ts.map +1 -1
- package/dist/commands/instructions/validate/validate.js +36 -8
- package/dist/commands/pjm/index.d.ts.map +1 -1
- package/dist/commands/pjm/index.js +19 -4
- package/dist/commands/pjm/init.d.ts +3 -0
- package/dist/commands/pjm/init.d.ts.map +1 -1
- package/dist/commands/pjm/init.js +23 -5
- package/dist/commands/project/dispatch/canonical-role.d.ts +33 -0
- package/dist/commands/project/dispatch/canonical-role.d.ts.map +1 -0
- package/dist/commands/project/dispatch/canonical-role.js +114 -0
- package/dist/commands/project/dispatch/index.d.ts.map +1 -1
- package/dist/commands/project/dispatch/index.js +3 -1
- package/dist/commands/project/dispatch/record.d.ts.map +1 -1
- package/dist/commands/project/dispatch/record.js +146 -4
- package/dist/commands/shared/agents-md.d.ts +26 -5
- package/dist/commands/shared/agents-md.d.ts.map +1 -1
- package/dist/commands/shared/agents-md.js +182 -3
- package/dist/commands/sync/apply.d.ts.map +1 -1
- package/dist/commands/sync/apply.js +28 -21
- package/dist/commands/tools/guidance/index.d.ts +15 -0
- package/dist/commands/tools/guidance/index.d.ts.map +1 -0
- package/dist/commands/tools/guidance/index.js +81 -0
- package/dist/commands/tools/index.d.ts.map +1 -1
- package/dist/commands/tools/index.js +2 -0
- package/dist/commands/tools/shared/sync-evidence.d.ts.map +1 -1
- package/dist/commands/tools/shared/sync-evidence.js +32 -5
- package/dist/config/oat-config.d.ts +57 -3
- package/dist/config/oat-config.d.ts.map +1 -1
- package/dist/config/oat-config.js +223 -15
- package/dist/config/resolve.d.ts.map +1 -1
- package/dist/config/resolve.js +12 -2
- package/dist/engine/compute-plan.d.ts.map +1 -1
- package/dist/engine/compute-plan.js +31 -3
- package/dist/providers/claude/dispatch-envelope.d.ts +53 -0
- package/dist/providers/claude/dispatch-envelope.d.ts.map +1 -1
- package/dist/providers/claude/dispatch-envelope.js +324 -48
- package/dist/providers/claude/rule-transform.js +1 -1
- package/dist/providers/copilot/rule-transform.js +1 -1
- package/dist/providers/cursor/rule-transform.js +1 -1
- package/dist/providers/identity/absolute-paths.d.ts +13 -0
- package/dist/providers/identity/absolute-paths.d.ts.map +1 -1
- package/dist/providers/identity/absolute-paths.js +27 -14
- package/dist/providers/identity/generic-dispatch-record.d.ts +212 -0
- package/dist/providers/identity/generic-dispatch-record.d.ts.map +1 -1
- package/dist/providers/identity/generic-dispatch-record.js +78 -19
- package/dist/providers/identity/oat-dispatch-record.d.ts +5 -0
- package/dist/providers/identity/oat-dispatch-record.d.ts.map +1 -1
- package/dist/providers/identity/oat-dispatch-record.js +11 -2
- package/dist/providers/shared/registry.d.ts +6 -0
- package/dist/providers/shared/registry.d.ts.map +1 -1
- package/dist/providers/shared/registry.js +30 -0
- package/dist/rules/canonical/parse.d.ts.map +1 -1
- package/dist/rules/canonical/parse.js +38 -3
- package/package.json +2 -2
|
@@ -274,7 +274,7 @@ remains immutable baseline evidence for the original p01-t01 verification.
|
|
|
274
274
|
| `oat-dispatch-subagents/references/provider-claude.md` | `fbe3a21e9533 -> NG` |
|
|
275
275
|
| `oat-dispatch-subagents/references/provider-codex.md` | `95b0f82018c7 -> NG` |
|
|
276
276
|
| `oat-dispatch-subagents/references/provider-cursor.md` | `f781555295a9 -> NG`; `55ccfef14fd6 -> NG` |
|
|
277
|
-
| `oat-dispatch-subagents/references/record-schema.md` | `78f8069274a8 -> NG`; `1c9a84c4d1e0 -> NG`; `2a63da6e3a96 -> NG`; `30762d53b043 -> NG`
|
|
277
|
+
| `oat-dispatch-subagents/references/record-schema.md` | `78f8069274a8 -> NG`; `1c9a84c4d1e0 -> NG`; `2a63da6e3a96 -> NG`; `30762d53b043 -> NG`; `66bc2f0d4fda -> NG` |
|
|
278
278
|
| `oat-project-dispatch-subagents/SKILL.md` | `eca03ad1ca12 -> PDISPATCH-01`; `59fbcdc79cea -> PDISPATCH-01` |
|
|
279
279
|
| `oat-project-plan/SKILL.md` | `f99e44b39932 -> PLAN-12`; `7e6a9854504b -> NG` |
|
|
280
280
|
| `oat-project-complete/SKILL.md` | `0177956707aa -> NG`; `8305b5bb65ef -> NG`; `3c0b26f0ff1c -> NG`; `8cc1fa5aab1e -> COMPLETE-01`; `4c209fbb4716 -> COMPLETE-01`; `02e4175e1171 -> COMPLETE-01`; `d698d4f98e76 -> COMPLETE-01`; `9f86a7218d93 -> COMPLETE-01`; `024713698d9a -> COMPLETE-01`; `c327995053fa -> COMPLETE-01`; `61f81d4ec7c1 -> COMPLETE-01`; `14fb2e56809f -> COMPLETE-01`; `7d4ff668744d -> COMPLETE-01`; `502a6c141784 -> COMPLETE-01`; `fb7e2db356af -> COMPLETE-01`; `f73f8476360a -> NG`; `1e15f420039f -> NG`; `cc234032ddd7 -> NG`; `1dd54687229b -> NG`; `fc05c8303cd2 -> NG`; `24be721d635e -> NG` |
|
|
@@ -7,7 +7,7 @@ disable-model-invocation: true
|
|
|
7
7
|
user-invocable: true
|
|
8
8
|
allowed-tools: Read, Write, Bash(git:*), Bash(oat:*), Bash(oat project log:*), Glob, Grep, AskUserQuestion, Task
|
|
9
9
|
metadata:
|
|
10
|
-
version: 2.3.
|
|
10
|
+
version: 2.3.14
|
|
11
11
|
---
|
|
12
12
|
|
|
13
13
|
# Implementation Phase
|
|
@@ -102,7 +102,7 @@ record only the gate decision and its review/dispatch provenance.
|
|
|
102
102
|
After every code commit and after every phase/review-fix completion, you MUST commit the OAT tracking files (project: `implementation.md`, `state.md`, `plan.md`) as a separate bookkeeping commit. Refresh the repo dashboard with `oat state refresh` before staging when available, but do not stage `.oat/state.md`; it is generated dashboard state and is normally gitignored. Do not defer, batch, or skip these commits under the reasoning that they "aren't related to the implementation." Skipping a bookkeeping commit is the primary cause of cross-session state drift and will cause the next implementation run to fail bookkeeping cross-checks. If bookkeeping commits feel frequent, that is the intended design — they are cheap and they prevent drift.
|
|
103
103
|
|
|
104
104
|
**CRITICAL — Review boundaries require a committed artifact baseline.**
|
|
105
|
-
Do not enter checkpoint review, final review, revise, or PR-final handoff with dirty core project artifacts (`discovery.md`, `spec.md`, `design.md`, `plan.md`, `implementation.md`, `state.md`). If one of those boundaries is next and artifact bookkeeping is still uncommitted, stop and create the bookkeeping commit first.
|
|
105
|
+
Do not enter checkpoint review, final review, revise, or PR-final handoff with dirty core project artifacts (`discovery.md`, `spec.md`, `design.md`, `plan.md`, `implementation.md`, `state.md`). If one of those boundaries is next and artifact bookkeeping is still uncommitted, stop and create the bookkeeping commit first. The per-phase review is such a boundary: commit the phase's task ledger (`references/phase-execution.md` Step 7a) before dispatching the per-phase reviewer, and write review-outcome bookkeeping after the review returns (Step 7b).
|
|
106
106
|
|
|
107
107
|
**CRITICAL — Intentional artifact divergence must be recorded.**
|
|
108
108
|
If implementation intentionally diverges from `spec.md`, `design.md`, or `plan.md`, record the delta in `implementation.md` before the next phase/review boundary. Include what diverged, why it diverged, whether the implementation or original artifact is now source of truth, and any follow-up artifact updates or explicit deferral. Do not leave accepted design drift only in chat, a review artifact, or code comments; final summary generation depends on `implementation.md` preserving the delta.
|
|
@@ -384,13 +384,13 @@ and can never be reused as a fresh `allowed` result once the gate is
|
|
|
384
384
|
re-enabled; the re-enabled gate requires a new configured generation.
|
|
385
385
|
|
|
386
386
|
New generations persist `implementation_fingerprint` as
|
|
387
|
-
`sha256:effective-delta-
|
|
387
|
+
`sha256:effective-delta-v2:<digest>`. Resolve the logical integration base from
|
|
388
388
|
the tracked PR's exact base ref, then the repository's configured remote default
|
|
389
389
|
branch; missing or ambiguous resolution fails closed. Persist the logical base
|
|
390
390
|
ref as `implementation_base_ref`; require exactly one merge base between that
|
|
391
391
|
ref and each compared HEAD.
|
|
392
392
|
|
|
393
|
-
Prefix the fingerprint input with the bytes `effective-delta-
|
|
393
|
+
Prefix the fingerprint input with the bytes `effective-delta-v2\0`. Hash the
|
|
394
394
|
exact NUL-delimited byte stream from Git
|
|
395
395
|
`--raw -z --no-renames --no-abbrev` output, which includes both base and final
|
|
396
396
|
modes and full object IDs for blobs, symlinks, deletions, and gitlinks. Run with
|
|
@@ -398,13 +398,29 @@ modes and full object IDs for blobs, symlinks, deletions, and gitlinks. Run with
|
|
|
398
398
|
format owns path framing and byte ordering; do not parse and reserialize it,
|
|
399
399
|
abbreviate object IDs, enable rename detection, or hash human patch output.
|
|
400
400
|
|
|
401
|
-
Exclude
|
|
402
|
-
self-referential
|
|
403
|
-
|
|
404
|
-
|
|
405
|
-
|
|
406
|
-
|
|
407
|
-
|
|
401
|
+
Exclude the exact `$PROJECT_PATH/state.md` checkpoint carrier, which would make
|
|
402
|
+
the digest self-referential, and every path under `.oat/projects/` and
|
|
403
|
+
`.oat/repo/`, whose project artifacts and repository records never make the
|
|
404
|
+
gate stale. Use Git's literal exclusion pathspecs
|
|
405
|
+
`:(exclude,literal)$PROJECT_PATH/state.md`, `:(exclude,literal).oat/projects`,
|
|
406
|
+
and `:(exclude,literal).oat/repo`, not globs. A literal directory pathspec
|
|
407
|
+
excludes that directory and everything beneath it, never a sibling whose name
|
|
408
|
+
merely starts the same way. `.oat/templates/`, `.oat/scripts/`,
|
|
409
|
+
`.oat/config*.json`, and `.oat/sync/` stay fingerprinted, as does every other
|
|
410
|
+
path. The `.oat/projects` exclusion names the default location literally; a
|
|
411
|
+
project whose configured `projects.root` lies outside `.oat/projects/` keeps
|
|
412
|
+
its other artifacts fingerprinted (more staleness, never less). Validate the
|
|
413
|
+
state carrier independently as the structured transition above.
|
|
414
|
+
|
|
415
|
+
Stored `sha256:effective-delta-v1:<digest>` values keep v1 semantics and are
|
|
416
|
+
never reinterpreted: recompute them with the `effective-delta-v1\0` prefix and
|
|
417
|
+
only the exact `$PROJECT_PATH/state.md` exclusion. A v1 generation stays v1
|
|
418
|
+
until it goes stale; its replacement generation uses v2.
|
|
419
|
+
|
|
420
|
+
Set `freshness_head` to `reviewed_head` and `freshness_fingerprint` to
|
|
421
|
+
`implementation_fingerprint` when the generation starts. These rolling fields
|
|
422
|
+
preserve the accepted tree outcome after later authorized closeout transitions
|
|
423
|
+
without changing the immutable reviewed basis.
|
|
408
424
|
|
|
409
425
|
An in-flight `pending` or `blocked` generation reuses its persisted resolved
|
|
410
426
|
configuration and never re-resolves it. Recompute the fingerprint from those
|
|
@@ -561,9 +577,14 @@ disposition.
|
|
|
561
577
|
closeout-only. A path category alone is insufficient: the corresponding
|
|
562
578
|
persisted gate or sequence transition must own that descendant boundary;
|
|
563
579
|
unknown or mixed work is substantive.
|
|
564
|
-
- For a qualified `sha256:effective-delta-
|
|
580
|
+
- For a qualified `sha256:effective-delta-v2:<digest>` or
|
|
581
|
+
`sha256:effective-delta-v1:<digest>` value, require the
|
|
565
582
|
persisted `implementation_base_ref`, `freshness_head`, one current merge base,
|
|
566
583
|
and 64-character lowercase hexadecimal implementation and freshness digests.
|
|
584
|
+
Recompute with the stored value's own version prefix and exclusion set.
|
|
585
|
+
Under v2, a descendant commit whose changes all fall inside the v2 exclusion
|
|
586
|
+
set leaves the effective delta unchanged; it is neither substantive nor
|
|
587
|
+
unknown and needs no owning transition.
|
|
567
588
|
Missing or malformed inputs fail closed. Walk descendants after
|
|
568
589
|
`freshness_head` in commit order. Ignore a checkpoint-persistence commit only
|
|
569
590
|
after verifying its diff changes the exact state carrier and nothing else.
|
|
@@ -587,7 +608,8 @@ disposition.
|
|
|
587
608
|
or workflow configuration changes make the prior result `stale`.
|
|
588
609
|
- Every stale transition preserves prior provenance for audit, requires a
|
|
589
610
|
current final lifecycle review for the changed basis, and starts a new
|
|
590
|
-
generation using the qualified fingerprint format
|
|
611
|
+
generation using the current qualified fingerprint format,
|
|
612
|
+
`effective-delta-v2`.
|
|
591
613
|
|
|
592
614
|
Before approval-aware sequencing, final HiLL approval, implementation
|
|
593
615
|
completion, or success output, run the configured gate:
|
|
@@ -513,33 +513,35 @@ Claude rules:
|
|
|
513
513
|
- Before any managed effort-pinned Claude launch, pass the real completed
|
|
514
514
|
resolver JSON, the selected generated `.claude/agents/<variant>.md`
|
|
515
515
|
definition, and the exact proposed payload through the shipped record
|
|
516
|
-
producer.
|
|
517
|
-
|
|
518
|
-
|
|
519
|
-
|
|
520
|
-
|
|
521
|
-
|
|
522
|
-
|
|
523
|
-
|
|
524
|
-
|
|
525
|
-
|
|
526
|
-
|
|
527
|
-
}
|
|
528
|
-
|
|
529
|
-
|
|
530
|
-
|
|
531
|
-
|
|
532
|
-
|
|
516
|
+
producer. Its managed input has three keys: `claudeLaunch` (`resolution`,
|
|
517
|
+
the resolver's `--json` output verbatim; `definition`, the generated
|
|
518
|
+
definition text; `payload`, `{ "variant": "<variant>" }`), `recordBase`, and
|
|
519
|
+
`event`. Produce `event` with
|
|
520
|
+
`oat project dispatch canonical-role --role <oat-phase-implementer|oat-reviewer> --request-id <recordBase.request_id> --skill-dir "${SKILL_DIR}" --json`,
|
|
521
|
+
which prints the `canonical-role-resolution` evidence (redacted paths,
|
|
522
|
+
content digest, tier misses) the recorder accepts unchanged; never write that
|
|
523
|
+
evidence by hand. A `missing` result is still valid evidence and carries the
|
|
524
|
+
recovery commands for the absent role: surface those commands to the
|
|
525
|
+
operator, and note that a later fresh-child fallback still stops under the
|
|
526
|
+
canonical fallback role rule above. Copy the shape of
|
|
527
|
+
`${DISPATCH_SKILLS_ROOT}/oat-dispatch-subagents/references/managed-claude-example.json`,
|
|
528
|
+
one complete validated input per role; its `record-schema.md` section lists
|
|
529
|
+
the `recordBase` fields and the derived fields `recordBase` must omit.
|
|
530
|
+
|
|
531
|
+
Assemble the input with a JSON-aware tool such as `jq --slurpfile` and
|
|
532
|
+
`--rawfile`. Set the pre-launch record base to `launch_status: planned` and
|
|
533
533
|
`child_outcome: null`, then run
|
|
534
534
|
`oat project dispatch record --event-file <input> --json` without
|
|
535
535
|
`--project`. Require `status: validated-only`. Launch only
|
|
536
536
|
`record.payload.variant` (and `record.payload.model` when present) from that
|
|
537
537
|
result. The producer rejects a missing or stale variant, an absent or drifted
|
|
538
|
-
generated definition, and a conflicting per-call model.
|
|
539
|
-
|
|
540
|
-
|
|
541
|
-
|
|
542
|
-
the
|
|
538
|
+
generated definition, and a conflicting per-call model. It reports every
|
|
539
|
+
violation it finds in one run, one `stage path: message` line each, so fix
|
|
540
|
+
them together and rerun. After the terminal child outcome, rebuild through
|
|
541
|
+
the same managed input with the terminal status; persistence remains subject
|
|
542
|
+
to the opt-in rule above. Never copy model, effort, selector, candidate, or
|
|
543
|
+
payload fields into the record base: the accepted envelope owns and derives
|
|
544
|
+
them.
|
|
543
545
|
|
|
544
546
|
- Derive `model_axis=selected:<model>` and `effort_axis=selected:<effort>` from
|
|
545
547
|
resolver output and the constructed variant payload. Legacy model-only
|
|
@@ -274,7 +274,7 @@ remains immutable baseline evidence for the original p01-t01 verification.
|
|
|
274
274
|
| `oat-dispatch-subagents/references/provider-claude.md` | `fbe3a21e9533 -> NG` |
|
|
275
275
|
| `oat-dispatch-subagents/references/provider-codex.md` | `95b0f82018c7 -> NG` |
|
|
276
276
|
| `oat-dispatch-subagents/references/provider-cursor.md` | `f781555295a9 -> NG`; `55ccfef14fd6 -> NG` |
|
|
277
|
-
| `oat-dispatch-subagents/references/record-schema.md` | `78f8069274a8 -> NG`; `1c9a84c4d1e0 -> NG`; `2a63da6e3a96 -> NG`; `30762d53b043 -> NG`
|
|
277
|
+
| `oat-dispatch-subagents/references/record-schema.md` | `78f8069274a8 -> NG`; `1c9a84c4d1e0 -> NG`; `2a63da6e3a96 -> NG`; `30762d53b043 -> NG`; `66bc2f0d4fda -> NG` |
|
|
278
278
|
| `oat-project-dispatch-subagents/SKILL.md` | `eca03ad1ca12 -> PDISPATCH-01`; `59fbcdc79cea -> PDISPATCH-01` |
|
|
279
279
|
| `oat-project-plan/SKILL.md` | `f99e44b39932 -> PLAN-12`; `7e6a9854504b -> NG` |
|
|
280
280
|
| `oat-project-complete/SKILL.md` | `0177956707aa -> NG`; `8305b5bb65ef -> NG`; `3c0b26f0ff1c -> NG`; `8cc1fa5aab1e -> COMPLETE-01`; `4c209fbb4716 -> COMPLETE-01`; `02e4175e1171 -> COMPLETE-01`; `d698d4f98e76 -> COMPLETE-01`; `9f86a7218d93 -> COMPLETE-01`; `024713698d9a -> COMPLETE-01`; `c327995053fa -> COMPLETE-01`; `61f81d4ec7c1 -> COMPLETE-01`; `14fb2e56809f -> COMPLETE-01`; `7d4ff668744d -> COMPLETE-01`; `502a6c141784 -> COMPLETE-01`; `fb7e2db356af -> COMPLETE-01`; `f73f8476360a -> NG`; `1e15f420039f -> NG`; `cc234032ddd7 -> NG`; `1dd54687229b -> NG`; `fc05c8303cd2 -> NG`; `24be721d635e -> NG` |
|
|
@@ -684,8 +684,11 @@ degradation is forbidden for the invalid run.
|
|
|
684
684
|
### Per-Phase Review
|
|
685
685
|
|
|
686
686
|
The root workflow owns implementation review. After validating the phase
|
|
687
|
-
report
|
|
688
|
-
|
|
687
|
+
report (sequential phases; see the parallel-group note below), commit Step 7a
|
|
688
|
+
pre-review bookkeeping before resolving or dispatching the reviewer, so the
|
|
689
|
+
reviewed head carries the phase's current task ledger. Then resolve and
|
|
690
|
+
dispatch exactly one fresh `oat-reviewer` round at the configured review
|
|
691
|
+
ceiling:
|
|
689
692
|
|
|
690
693
|
```bash
|
|
691
694
|
oat project dispatch-ceiling resolve \
|
|
@@ -703,6 +706,17 @@ commit range, task IDs and boundaries, artifacts, verification evidence,
|
|
|
703
706
|
configured axes, selection reason, and candidates. Require a timestamped review
|
|
704
707
|
artifact under the project's `reviews/` directory.
|
|
705
708
|
|
|
709
|
+
The Review Scope names review-outcome bookkeeping as out of scope: this
|
|
710
|
+
review's `## Reviews` row and its disposition, the Orchestration Run entry for
|
|
711
|
+
this review's outcome, the deferred phase-outcome and review-orchestration
|
|
712
|
+
project-log entries, and the ledger's record of any review-fix commit. Step 7b
|
|
713
|
+
writes all of them after the review returns, so their absence at the reviewed
|
|
714
|
+
head is not a finding. The task ledger itself stays in scope and must be
|
|
715
|
+
current at the reviewed head, because Step 7a committed it before dispatch.
|
|
716
|
+
In a parallel group the phase worktree under review does not carry the root
|
|
717
|
+
ledger (step 10 of Parallel Group Execution commits it once after fan-in), so
|
|
718
|
+
that phase's Review Scope also names the task ledger as out of scope.
|
|
719
|
+
|
|
706
720
|
For a managed capped review, bind the exact provider argument to the actual
|
|
707
721
|
invocation: `providers.codex.dispatchArgs.variant`,
|
|
708
722
|
`providers.claude.dispatchArgs.variant` for an effort-pinned target,
|
|
@@ -755,7 +769,9 @@ and workers never write `project-log.md` or append this entry.
|
|
|
755
769
|
|
|
756
770
|
No project-log write happens anywhere between a reviewer returning and a fix
|
|
757
771
|
child being dispatched. The deferred orchestration entry is appended with the
|
|
758
|
-
phase-outcome entry at Step
|
|
772
|
+
phase-outcome entry at Step 7b and committed by that half's bookkeeping. Step
|
|
773
|
+
7a's commit lands before the reviewer is dispatched, so it cannot dirty that
|
|
774
|
+
window either.
|
|
759
775
|
|
|
760
776
|
After successful signal and orchestration validation, validate the review
|
|
761
777
|
artifact scope and commit range.
|
|
@@ -796,8 +812,10 @@ worktree in Outstanding Items.
|
|
|
796
812
|
|
|
797
813
|
### Optional External Phase Review Gate
|
|
798
814
|
|
|
799
|
-
After the root-owned per-phase reviewer passes and
|
|
800
|
-
run `oat_phase_review_gate` for selected phases
|
|
815
|
+
After the root-owned per-phase reviewer passes and both halves of Step 7
|
|
816
|
+
bookkeeping are committed, run `oat_phase_review_gate` for selected phases. The
|
|
817
|
+
gate reviews the committed ledger after both Step 7 halves — which, after a fix
|
|
818
|
+
loop or in a parallel group, is newer than the head the per-phase reviewer saw:
|
|
801
819
|
|
|
802
820
|
```bash
|
|
803
821
|
oat --json gate review \
|
|
@@ -817,6 +835,11 @@ and `handoff` is non-null.
|
|
|
817
835
|
implementer under the bounded loop, then re-run root review and the gate.
|
|
818
836
|
- target execution, artifact validation, or missing-artifact failure: stop.
|
|
819
837
|
|
|
838
|
+
The phase row stays `in_progress` until this gate passes and every review
|
|
839
|
+
disposition is settled; the bookkeeping that records the passing gate sets it
|
|
840
|
+
`complete`, and gate retry exhaustion sets it `blocked` (see Step 7b's phase
|
|
841
|
+
row transitions).
|
|
842
|
+
|
|
820
843
|
Gate retry rounds use the same orchestration retry limit. Gate independence,
|
|
821
844
|
configured provenance, liveness telemetry, and fail-closed behavior are
|
|
822
845
|
unchanged.
|
|
@@ -879,7 +902,65 @@ target-preserving execution and must be recorded.
|
|
|
879
902
|
|
|
880
903
|
### Step 7: Artifact Updates After Each Phase (or Group)
|
|
881
904
|
|
|
882
|
-
After each phase or parallel group
|
|
905
|
+
After each phase or parallel group, Step 7 runs in two halves around the
|
|
906
|
+
per-phase review, each with its own commit.
|
|
907
|
+
The split exists so the reviewer never evaluates a head whose task ledger is
|
|
908
|
+
stale by construction, while the tree stays clean for a bounded fix child.
|
|
909
|
+
|
|
910
|
+
#### Step 7a: Pre-Review Bookkeeping
|
|
911
|
+
|
|
912
|
+
Run after the phase report validates and before Per-Phase Review dispatches the
|
|
913
|
+
reviewer. Write the phase's task ledger:
|
|
914
|
+
|
|
915
|
+
- the `implementation.md` task and phase completion rows: each planned task's
|
|
916
|
+
status and commit; keep the phase row `in_progress` (tasks complete, review
|
|
917
|
+
pending), because the phase's terminal status depends on its review;
|
|
918
|
+
- the `state.md` resume pointer (`oat_current_task`, last commit, and
|
|
919
|
+
timestamp), advanced consistently with `implementation.md` so the two
|
|
920
|
+
resume pointers never disagree;
|
|
921
|
+
- when the phase report carried a recovery attempt, after the matching
|
|
922
|
+
handoff-matrix row validates, clear the terminal `pending_attempt` marker,
|
|
923
|
+
preserve `used_attempts`, and append the validated canonical recovery event
|
|
924
|
+
to `implementation.md`;
|
|
925
|
+
- remove legacy `oat_execution_mode: subagent-driven`; and
|
|
926
|
+
- preserve any configured retry override.
|
|
927
|
+
|
|
928
|
+
The task rows, resume pointer, and recovery settlement do not depend on the
|
|
929
|
+
review outcome, which is why they can move ahead of the review; the recovery
|
|
930
|
+
settlement is validated from the phase report, not from the review. A
|
|
931
|
+
terminal-stop branch that ends without a review (`failed-attempt`,
|
|
932
|
+
`direction-required`, or `BLOCKED`) records its event and marker disposition
|
|
933
|
+
through the Step 7a commit block and then stops; it has no Step 7b. Commit it
|
|
934
|
+
through the same scope-resolving branch as Step 7b, including the synced-scope
|
|
935
|
+
`oat project push` path. Why this keeps the fix-child
|
|
936
|
+
preflight clean: the pre-review writes are committed before the reviewer is
|
|
937
|
+
dispatched, so the tree is clean when a bounded fix child is dispatched after
|
|
938
|
+
the review. The Optional External Phase Review Gate later sees this committed
|
|
939
|
+
ledger plus Step 7b's writes.
|
|
940
|
+
|
|
941
|
+
Pre-review bookkeeping is mandatory:
|
|
942
|
+
|
|
943
|
+
```bash
|
|
944
|
+
oat state refresh
|
|
945
|
+
PROJECT_SCOPE=$(oat project scope "{PROJECT_PATH}" --format value) || { echo "oat: cannot resolve project scope for {PROJECT_PATH}; refusing to commit artifacts" >&2; exit 1; }
|
|
946
|
+
# fail closed: never fall back to branch bookkeeping when scope resolution fails
|
|
947
|
+
if [ "$PROJECT_SCOPE" = "synced" ]; then
|
|
948
|
+
oat project push "{PROJECT_PATH}" --message "chore(oat): record {pNN} task ledger before review" || { echo "oat: project push failed; run oat project pull, resolve the reported state, and retry" >&2; exit 1; }
|
|
949
|
+
else
|
|
950
|
+
git add {PROJECT_PATH}/implementation.md {PROJECT_PATH}/state.md {PROJECT_PATH}/plan.md
|
|
951
|
+
[ -f {PROJECT_PATH}/project-log.md ] && git add {PROJECT_PATH}/project-log.md
|
|
952
|
+
git commit -m "chore(oat): record {pNN} task ledger before review"
|
|
953
|
+
fi
|
|
954
|
+
```
|
|
955
|
+
|
|
956
|
+
A parallel group makes this commit once after fan-in, together with Step 7b
|
|
957
|
+
(step 10 of Parallel Group Execution), because its phase worktrees do not carry
|
|
958
|
+
the root ledger.
|
|
959
|
+
|
|
960
|
+
#### Step 7b: Post-Review Bookkeeping
|
|
961
|
+
|
|
962
|
+
Run after the phase's terminal review outcome (pass, or retry exhaustion).
|
|
963
|
+
Write the review-outcome bookkeeping that Step 7a leaves out:
|
|
883
964
|
|
|
884
965
|
- append an Orchestration Run with phase outcomes, task commits, phase/root
|
|
885
966
|
review result, fix iterations, dispatch stamps, selection reasons,
|
|
@@ -891,10 +972,30 @@ After each phase or parallel group:
|
|
|
891
972
|
move an event status backward;
|
|
892
973
|
- apply the Reviews Ledger Mutation Contract above before every disposition or
|
|
893
974
|
archive re-point;
|
|
894
|
-
-
|
|
895
|
-
|
|
975
|
+
- set the phase's `implementation.md` row from the review outcome: `blocked`
|
|
976
|
+
on retry exhaustion; on a passing review, keep the row nonterminal
|
|
977
|
+
(`in_progress`) while any review-fix task added by review-receive is open or
|
|
978
|
+
a selected Optional External Phase Review Gate has not yet passed, and set
|
|
979
|
+
`complete` only under the rule below; update the phase summary for any
|
|
980
|
+
review-fix commits;
|
|
981
|
+
- append the deferred phase-outcome and review-orchestration entries through
|
|
982
|
+
`oat project log append`;
|
|
983
|
+
- update `state.md` last commit and timestamp for any review-fix commit, and
|
|
984
|
+
its current task when the phase outcome changes it; and
|
|
896
985
|
- preserve any configured retry override.
|
|
897
986
|
|
|
987
|
+
Phase row transitions: a passing root review (zero Critical and zero High) can
|
|
988
|
+
still queue Medium or Low fix tasks through review-receive, and the selected
|
|
989
|
+
phase gate runs after this step, so neither makes the phase complete by itself.
|
|
990
|
+
An added review-fix task keeps the row `in_progress` and names the queued task;
|
|
991
|
+
the bookkeeping that completes that task re-evaluates the row. A `blocked` gate
|
|
992
|
+
keeps the row `in_progress` through the bounded fix loop; gate retry exhaustion
|
|
993
|
+
sets it `blocked`. Set the row `complete` only when every review disposition is
|
|
994
|
+
settled and every selected phase gate has passed, in whichever bookkeeping
|
|
995
|
+
commit observes that last condition: this Step 7b commit when nothing is
|
|
996
|
+
queued and no gate is selected, otherwise the commit that records the final
|
|
997
|
+
review-fix task or the passing gate.
|
|
998
|
+
|
|
898
999
|
Bookkeeping is mandatory:
|
|
899
1000
|
|
|
900
1001
|
```bash
|
|
@@ -7,7 +7,7 @@ disable-model-invocation: true
|
|
|
7
7
|
user-invocable: true
|
|
8
8
|
allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
|
|
9
9
|
metadata:
|
|
10
|
-
version: 1.1.
|
|
10
|
+
version: 1.1.6
|
|
11
11
|
---
|
|
12
12
|
|
|
13
13
|
# Lite Project
|
|
@@ -159,6 +159,28 @@ PROJECT_PATH=$(oat config get activeProject)
|
|
|
159
159
|
Confirm `state.md` reports `oat_workflow_mode: lite`, `oat_phase: plan`, and
|
|
160
160
|
`oat_phase_status: in_progress`. Do not create discovery or design artifacts.
|
|
161
161
|
|
|
162
|
+
**Consolidating earlier scaffolds.** When this new Lite project absorbs work
|
|
163
|
+
that earlier project scaffolds already started — those directories are being
|
|
164
|
+
retired into this one rather than continued — record what was absorbed in
|
|
165
|
+
`"$PROJECT_PATH/state.md"` frontmatter as one frontmatter write immediately
|
|
166
|
+
after the scaffold above, before Step 1. `PROJECT_PATH` here is the value
|
|
167
|
+
re-resolved after `oat project new`, never the pre-scaffold value, which still
|
|
168
|
+
names the previously active project. The fields have the same shapes that
|
|
169
|
+
`oat-project-quick-start` records:
|
|
170
|
+
|
|
171
|
+
- `absorbed_projects: [<slug>]` — the project slug of every retired scaffold,
|
|
172
|
+
which also names the scaffold directory under the projects root that this
|
|
173
|
+
project supersedes.
|
|
174
|
+
- `absorbed_backlog_ids: [<BL-id>]` — every backlog ID those scaffolds carried
|
|
175
|
+
into this project.
|
|
176
|
+
|
|
177
|
+
Record both fields only when a consolidation actually happened; an absent field
|
|
178
|
+
and an empty list are equivalent. A resumed Lite project keeps whatever it
|
|
179
|
+
already recorded. These two fields are the only inputs the absorbed-project
|
|
180
|
+
retirement sweep reads at completion, where retiring a scaffold is treated as a
|
|
181
|
+
semantic claim about the planning surfaces rather than the physical removal of
|
|
182
|
+
a directory. The write travels with this project's next `state.md` commit.
|
|
183
|
+
|
|
162
184
|
### Step 1: Read Repository Knowledge
|
|
163
185
|
|
|
164
186
|
Read repository instructions and the minimum durable context needed for the
|
|
@@ -274,7 +274,7 @@ remains immutable baseline evidence for the original p01-t01 verification.
|
|
|
274
274
|
| `oat-dispatch-subagents/references/provider-claude.md` | `fbe3a21e9533 -> NG` |
|
|
275
275
|
| `oat-dispatch-subagents/references/provider-codex.md` | `95b0f82018c7 -> NG` |
|
|
276
276
|
| `oat-dispatch-subagents/references/provider-cursor.md` | `f781555295a9 -> NG`; `55ccfef14fd6 -> NG` |
|
|
277
|
-
| `oat-dispatch-subagents/references/record-schema.md` | `78f8069274a8 -> NG`; `1c9a84c4d1e0 -> NG`; `2a63da6e3a96 -> NG`; `30762d53b043 -> NG`
|
|
277
|
+
| `oat-dispatch-subagents/references/record-schema.md` | `78f8069274a8 -> NG`; `1c9a84c4d1e0 -> NG`; `2a63da6e3a96 -> NG`; `30762d53b043 -> NG`; `66bc2f0d4fda -> NG` |
|
|
278
278
|
| `oat-project-dispatch-subagents/SKILL.md` | `eca03ad1ca12 -> PDISPATCH-01`; `59fbcdc79cea -> PDISPATCH-01` |
|
|
279
279
|
| `oat-project-plan/SKILL.md` | `f99e44b39932 -> PLAN-12`; `7e6a9854504b -> NG` |
|
|
280
280
|
| `oat-project-complete/SKILL.md` | `0177956707aa -> NG`; `8305b5bb65ef -> NG`; `3c0b26f0ff1c -> NG`; `8cc1fa5aab1e -> COMPLETE-01`; `4c209fbb4716 -> COMPLETE-01`; `02e4175e1171 -> COMPLETE-01`; `d698d4f98e76 -> COMPLETE-01`; `9f86a7218d93 -> COMPLETE-01`; `024713698d9a -> COMPLETE-01`; `c327995053fa -> COMPLETE-01`; `61f81d4ec7c1 -> COMPLETE-01`; `14fb2e56809f -> COMPLETE-01`; `7d4ff668744d -> COMPLETE-01`; `502a6c141784 -> COMPLETE-01`; `fb7e2db356af -> COMPLETE-01`; `f73f8476360a -> NG`; `1e15f420039f -> NG`; `cc234032ddd7 -> NG`; `1dd54687229b -> NG`; `fc05c8303cd2 -> NG`; `24be721d635e -> NG` |
|