@clawplays/ospec-cli - npm Package Compare versions

Comparing version 1.8.18 to 1.8.19

assets/for-ai/ar/execution-protocol.md

@@ -64,2 +64,3 @@ ---
 - في Goal مملوكة لـ controller، استخدم `ospec loop tick [changes/active/<change>]` بعد اكتمال كل worker task لإنشاء مراجعة موحدة مرتبطة بـ executor provenance الحقيقي وحزمة محدودة النطاق. استخدم `ospec execute review ... --task <task-id>` مباشرةً فقط خارج controller Loop
+- تربط task review المسار canonical الدقيق `artifacts/agents/worker-reports/<task-id>.md` لنفس المهمة داخل target snapshot. يمكن لـ repair تعديل هذا report الدقيق للمهمة نفسها فقط؛ تبقى تقارير المهام الأخرى وأي controller artifacts عشوائية محظورة. إذا أشارت legacy finding إلى canonical report غير موجود في snapshot القديم، نفّذ fresh task-review action التي يصدرها Loop قبل repair ولا تعدّل historical evidence يدوياً
 - عند تفعيل `documentation_updates` في task graph، يجب أن تحتوي كل مهمة على المصفوفة (`[]` عند عدم الحاجة)، وأن يظهر كل مسار docs معلن أيضا في `target_files` للمهمة نفسها، وأن يملك دليلا على تغير فعلي بين dispatch وcomplete. يعد الحذف الذي تمت مراجعته تغييرا صالحا عندما يثبت evidence أن baseline موجودا أصبح مفقودا عند الإكمال. عبر محاولات repair المتعددة يقارن finalize أول baseline بالحالة النهائية المكتملة، ويشترط أن تطابق workspace أحدث evidence لمالك المسار المعلن، لذلك لا يكفي تغيير قديم ولا يمر التراجع اللاحق. إذا غير controller closeout مسارا معلنا بعد آخر worker dispatch، فلا تعتمد الحالة النهائية إلا مراجعة task لاحقة بحالة APPROVED، وexecutor provenance صالح، وtarget snapshot يطابق الملف الحالي تماما؛ ولا تحل هذه المراجعة محل meaningful-change chain. تبقى التشغيلات القديمة بلا baseline متوافقة فقط عندما تظل الوثيقة المعلنة موجودة، وتعرض الدليل كغير متحقق.
@@ -66,0 +67,0 @@ - بعد اعتماد task-level reviews واكتمال task graph، دع `ospec loop tick` التالي ينشئ final review في controller Loop؛ استخدم `ospec execute review` من دون `--task` فقط خارج controller Loop

assets/for-ai/en-US/execution-protocol.md

@@ -66,2 +66,3 @@ ---
 - After a worker records `DONE` or `DONE_WITH_CONCERNS`, use `ospec loop tick [changes/active/<change>]` in a controller-owned Goal to create the combined reviewer action with real executor provenance and a scoped `artifacts/agents/review-packages/*.diff`. Use `ospec execute review ... --task <task-id>` only outside a controller Loop
+- A task review binds the exact canonical `artifacts/agents/worker-reports/<task-id>.md` into its target snapshot. A repair may edit only that same task's exact report path; another task's report and arbitrary controller artifacts remain blocked. When a legacy finding names an unsnapshotted canonical report, execute the fresh task-review action emitted by Loop before repair instead of editing historical evidence
 - After all task-level reviews are approved and the task graph is completed, let the controller's next `ospec loop tick` create the combined final review. Use `ospec execute review` without `--task` only outside a controller Loop
@@ -68,0 +69,0 @@ - Use `ospec execute feedback [changes/active/<change>] [--stage spec|quality]` after a review artifact has a non-`PENDING` decision to write `artifacts/agents/review-feedback-plan.json` and `artifacts/agents/review-feedback-plan.md`; handle review feedback through accept, revise, clarify, or blocked actions before dispatching more work, and create a required user decision gate when feedback changes scope, direction, API, UI, risk, or accepted tradeoffs

assets/for-ai/ja-JP/execution-protocol.md

@@ -63,2 +63,3 @@ ---
 - controller-owned Goal では、各 worker task 完了後に `ospec loop tick [changes/active/<change>]` で実 executor provenance に結び付いた統合 review と task-scoped package を作成する。`ospec execute review ... --task <task-id>` を直接使うのは non-controller workflow のみとする
+- task review は、その task の正確な canonical `artifacts/agents/worker-reports/<task-id>.md` を target snapshot に結び付ける。repair が編集できるのは同じ task の正確な report path だけであり、別 task の report と任意の controller artifact は引き続き block する。legacy finding が snapshot 未登録の canonical report を指す場合は、history を手編集せず、Loop が発行する fresh task-review action を実行してから repair する
 - task graph で `documentation_updates` を有効にした場合、各 task に配列を持たせ（不要なら `[]`）、宣言した docs path を同じ task の `target_files` に含め、dispatch から complete までの有意な content change evidence を残す。既存 baseline が完了時に missing になったことを evidence が証明する reviewed deletion は有効な変更である。複数 repair attempt では finalize が最初の baseline と最後の完了状態を比較し、workspace がその path の最新 declared owner evidence と一致することを要求するため、古い変更や後続の reversion は通過しない。controller closeout が最後の worker dispatch 後に宣言 path を変更した場合、その最終状態を許可できるのは、より後に実行され、executor provenance が有効で、現在の target snapshot と完全一致する APPROVED task review だけであり、meaningful-change chain の代わりにはならない。baseline のない旧 run は宣言文書が現在も存在する場合だけ互換性を保ち、未検証と表示する。
@@ -65,0 +66,0 @@ - task graph 完了後の final review も controller Loop の次の `ospec loop tick` で発行する。`--task` なしの `ospec execute review` を直接使うのは non-controller workflow のみとする

assets/for-ai/zh-CN/execution-protocol.md

@@ -66,2 +66,3 @@ ---
 - worker 记录 `DONE` 或 `DONE_WITH_CONCERNS` 后，controller-owned Goal 用 `ospec loop tick [changes/active/<change>]` 生成带真实 executor provenance 的合并 review action 和范围受控的 `artifacts/agents/review-packages/*.diff`；只有非 controller 流程才直接运行 `ospec execute review ... --task <task-id>`
+- task review 会把精确的本任务 canonical `artifacts/agents/worker-reports/<task-id>.md` 绑定进 target snapshot。repair 只能编辑同一任务的这个精确 report 路径；其他任务 report 和任意 controller artifact 仍然阻塞。旧 finding 若指向未被当时 dispatch 快照绑定的 canonical report，应执行 Loop 自动发出的 fresh task-review action 后再 repair，不得手改历史 evidence
 - task graph 启用 `documentation_updates` 后，每个 task 都必须包含该数组（没有则为 `[]`）；声明的 docs 路径必须同时出现在同一 task 的 `target_files` 中，并具有从 dispatch 到 complete 的有效内容变化证据。若 evidence 证明已有 baseline 在完成时变为不存在，则经过 review 的删除属于有效变化。多轮 repair 时，finalize 比较首个 baseline 与最终完成态，并要求当前工作区匹配该路径最后一个声明 owner 的 evidence，旧修改或后续回退不能通过。如果 controller closeout 在最后一次 worker dispatch 后修改了声明路径，只有更晚、executor provenance 有效且 target snapshot 精确匹配当前文件的 APPROVED task review 才能授权最终状态；它不能替代 meaningful-change 证据链。没有历史 baseline 的旧流程仅在声明文档仍存在时保持兼容，并必须把证据标记为无法验证。
@@ -68,0 +69,0 @@ - 所有单任务 review 通过且 task graph 完成后，controller Loop 用下一次 `ospec loop tick` 生成最终整体 review；只有非 controller 流程才直接运行不带 `--task` 的 `ospec execute review`

assets/global-skills/codex/ospec-goal/SKILL.md

@@ -24,2 +24,3 @@ ---
 - **Progress and feedback are artifact-backed.** Task status, task/final review decisions, grouped repair waves, verification evidence, `state.json`, and `run-log.jsonl` carry progress between fresh contexts. Process exit alone does not complete an action. Dispatch only items returned in `actions`; a durable `pending` record with an empty action list is observation state and must not be relaunched.
+- **Worker reports are task-owned review evidence.** Every fresh task review binds the exact canonical `artifacts/agents/worker-reports/<task-id>.md` into its target snapshot. A structured repair may name only that same task's exact report path; another task's report, a parent artifact directory, review history, and arbitrary controller evidence remain out of scope. If an older review finding names a canonical report that its dispatch did not snapshot, execute the fresh task-review action emitted by Loop before repair; do not hand-edit or delete the old finding.
 - **Guards are enforced before new work.** Pause/STOP, iteration/deadline/token/time budgets, no-progress limits, comprehension-review checkpoints, required decisions, approved document reviews, ready workspace evidence, and L3 allowlists can stop or pause the loop.
@@ -26,0 +27,0 @@ - **Document review is convergent.** Specialist design/plan review uses two rounds and 30 minutes as default convergence thresholds. In continuous mode, a new structured finding-ID set may continue automatically; a repeated or cycling set stops. Cache/pending reuse, heartbeat, lease recovery, and deterministic preflight do not consume rounds. Never use `--force` to bypass a guard. Strict mode retains the exact user-authorized extra-round window. Read the prior findings sidecar and resolution evidence before the full document when revising. Every structured finding must have a non-empty unique ID.

dist/cli.js

@@ -65,3 +65,3 @@ #!/usr/bin/env node
 const services_1 = require("./services");
-const CLI_VERSION = '1.8.18';
+const CLI_VERSION = '1.8.19';
 function showInitUsage() {
@@ -68,0 +68,0 @@ console.log('Usage: ospec init [root-dir] [--summary "..."] [--tech-stack node,react] [--architecture "..."] [--document-language en-US|zh-CN|ja-JP|ar]');

package.json

 {
   "name": "@clawplays/ospec-cli",
-  "version": "1.8.18",
+  "version": "1.8.19",
   "description": "Official OSpec CLI package for spec-driven development (SDD) and document-driven development in AI coding agent and CLI workflows.",
@@ -5,0 +5,0 @@ "main": "dist/index.js",

SKILL.md

@@ -52,2 +52,3 @@ ---
 - Dispatch scoped worker packets, use the launch plan with the current harness native agent mechanism, record completion, then perform one combined task review.
+- Treat each task's canonical `artifacts/agents/worker-reports/<task-id>.md` as review-bound evidence. A fresh task review snapshots it alongside declared targets; a repair may edit only that same task's exact report path. When a legacy review finding names an unsnapshotted canonical report, let Loop issue a fresh review before repair instead of editing history or widening artifact scope.
 - A worker profile is logical (`mechanical`, `standard`, `strong_reasoning`, `review`, `final_review`). Harness-specific model names come from `.skillrc`; absence is explicit and falls back to the harness default.
@@ -54,0 +55,0 @@ - Record optional provider usage sidecars through the supported completion command. Metrics are evidence, not an archive gate unless project policy says otherwise.

New alerts

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Improved metrics

Total package byte prevSize

3391759

0.24%

Lines of code

59433

0.13%

No dependency changes