@open-agent-toolkit/cli 0.1.63 → 0.1.64

package/assets/agents/oat-phase-implementer.md

@@ -1,6 +1,6 @@
 ---
 name: oat-phase-implementer
-version: 1.0.7
+version: 1.0.8
 description: Implements one plan phase end-to-end, commits each task separately, self-checks between tasks, and handles bounded review fixes when resumed by oat-project-implement.
 tools: Read, Write, Edit, Bash, Grep, Glob, Task
 color: cyan
@@ -90,6 +90,14 @@ Read each required artifact once at phase start:
 Extract all phase tasks, dependency order, file boundaries, verification
 commands, commit messages, and phase-wide verification before editing.
 
+## Artifact Hygiene
+
+Artifact hygiene contract: Before finishing or committing, format every file you created or edited. Use the concrete write/fix formatting command supplied by the governing plan, task, or brief. If none is usable, discover the repository's documented write/fix command from applicable `AGENTS.md`/`CLAUDE.md` instructions and relevant package manifests; do not infer or hardcode a formatter. Prefer a file-scoped invocation when supported, and avoid rewriting unrelated files. If no command is discoverable, warn once with `no format command discovered in repo instructions; skipping`, then continue.
+
+After formatting, run the repository's applicable gate set over the produced
+diff, explicitly including artifact writes. This supplements rather than
+replaces every task and phase verification command below.
+
 ## Mode: Implement
 
 ### 1. Verify Phase Base

package/assets/agents/oat-reviewer.md

@@ -1,6 +1,6 @@
 ---
 name: oat-reviewer
-version: 1.1.6
+version: 1.1.7
 description: Unified reviewer for OAT projects - mode-aware verification of requirements/design alignment and code quality. Writes a review artifact to disk by default, or returns structured findings in-memory when dispatched in structured-output mode.
 tools: Read, Bash, Grep, Glob, Write
 color: yellow
@@ -84,6 +84,13 @@ Use workflow mode to determine required evidence:
 Do not mark missing optional artifacts as findings.
 If required artifacts for the mode are unexpectedly missing, record a workflow contract gap.
 
+## Artifact Hygiene
+
+Artifact hygiene contract: Before finishing or committing, format every file you created or edited. Use the concrete write/fix formatting command supplied by the governing plan, task, or brief. If none is usable, discover the repository's documented write/fix command from applicable `AGENTS.md`/`CLAUDE.md` instructions and relevant package manifests; do not infer or hardcode a formatter. Prefer a file-scoped invocation when supported, and avoid rewriting unrelated files. If no command is discoverable, warn once with `no format command discovered in repo instructions; skipping`, then continue.
+
+After formatting, run only repository checks relevant to the files changed;
+writing a prose artifact does not imply unrelated full test suites.
+
 ## Process
 
 ### Step 1: Load Artifacts

package/assets/docs/contributing/skills.md

@@ -56,6 +56,28 @@ Skill behavior is defined by frontmatter plus the process contract in each `SKIL
 - Keep `AGENTS.md` skills table synchronized with `.agents/skills`.
 - Require explicit user approval for destructive or state-advancing transitions.
 
+### Artifact-writing hygiene
+
+Every role or skill that creates or edits tracked output must include the
+artifact hygiene contract at its writing boundary. The writer uses a concrete
+write/fix formatting command supplied by its plan, task, or brief. If none is
+usable, it discovers the repository's documented command from applicable
+`AGENTS.md` / `CLAUDE.md` instructions and relevant package manifests.
+
+Contracts must distinguish write/fix commands from check-only commands, prefer
+a file-scoped invocation when supported, avoid unrelated whole-tree rewrites,
+and never infer or hardcode a formatter. If no command can be discovered, the
+writer warns once with
+`no format command discovered in repo instructions; skipping` and continues.
+Run only verification relevant to the changed files unless the role's
+definition of done requires broader gates.
+
+For planned implementation, plan-producing skills resolve this command once and
+place it in every artifact-writing task. Runtime discovery remains the fallback
+for direct lifecycle writers and incomplete or stale plans. When the same
+contract crosses dispatch boundaries, keep each copy self-contained and protect
+equivalence with contract tests.
+
 ## Recommended Starting Points
 
 - Use `create-oat-skill` when the new skill belongs to an OAT lifecycle or maintenance flow.

package/assets/docs/workflows/projects/artifacts.md

@@ -57,6 +57,36 @@ Manual and auto review artifacts do not require the gate-only fields.
 
 Artifacts are the project system of record; automation and routing should derive from these files, not memory.
 
+### Formatting and verification hygiene
+
+Tracked artifacts are part of the repository diff, so artifact writers format
+them before finishing or committing. During plan authoring, OAT resolves the
+repository's documented write/fix command from applicable `AGENTS.md` /
+`CLAUDE.md` instructions and relevant package manifests. Each task that writes
+an artifact receives a concrete invocation, scoped to that task's files when
+the command supports paths.
+
+Downstream implementers execute that supplied command without repeating
+discovery. Roles and lifecycle skills that write outside a planned task,
+including reviewers and documentation, summary, PR, and quick-start flows, use
+the same discovery procedure as a fallback. Gate-originated review prompts also
+carry the contract so review artifacts follow the same rule across runtimes.
+
+Writers must:
+
+- prefer a documented write/fix command over a check-only command;
+- avoid inferring or hardcoding a formatter;
+- scope the write to created or edited files when supported;
+- avoid whole-tree rewrites that could absorb unrelated changes; and
+- warn once with
+  `no format command discovered in repo instructions; skipping` when no command
+  is discoverable, then continue.
+
+Formatting supplements the applicable verification contract. Phase
+implementation runs repository gates over its produced diff, including
+artifact writes. Prose-only lifecycle work runs only checks relevant to the
+files it changed.
+
 ## Coordination parents
 
 Project splitting introduces a coordination-only parent artifact. It records shared context and child relationships, but it is not an executable lifecycle project.

package/assets/docs/workflows/projects/dispatch-ceiling.md

@@ -64,6 +64,19 @@ existing cells. Planning shows the complete recommendation before asking which
 scope should own it. If the resulting ladder is still missing or incomplete,
 planning remains blocked rather than replacing the user's explicit values.
 
+Before offering adoption, planning runs `oat config list --json` once and treats
+its output as the effective boundary across shared, repo-local, user, and
+bundled-default precedence. A complete effective ladder skips adoption even
+when the current project has not selected a policy or named ceiling. Adoption
+is offered only when the resolved provider/tier cells are actually missing,
+empty, malformed, or incomplete.
+
+Ladder completeness and project-ceiling selection are separate checks. In
+particular, `oat project dispatch-ceiling resolve` returning `matrix: null` can
+mean that the project policy or ceiling is unresolved; it does not prove that
+the effective reusable ladders are absent. When ladders are complete, planning
+proceeds directly to the project-specific policy choice.
+
 The ownership boundary is deliberate:
 
 | Source                                     | Config location                | Codex materialization output          |

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.1.63",
-  "docs-config": "0.1.63",
-  "docs-theme": "0.1.63",
-  "docs-transforms": "0.1.63"
+  "cli": "0.1.64",
+  "docs-config": "0.1.64",
+  "docs-theme": "0.1.64",
+  "docs-transforms": "0.1.64"
 }