🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP →
@clawplays/ospec-cli
Advanced tools
@clawplays/ospec-cli - npm Package Compare versions
@@ -49,3 +49,3 @@ --- | ||
| - الإغلاق تلقائي عند الجاهزية: عندما ينجح `ospec verify [changes/active/<change>]` ولا توجد required pending decision أو بوابة إضافة (plugin gate) حاجبة، شغّل `ospec finalize [changes/active/<change>]` بنفسك——لا تتوقف بعد نجاح `ospec verify` أو `ospec archive ... --check` (الـ `--check` معاينة فقط) ولا تنتظر طلب المستخدم. لا توقف الإغلاق إلا حين تحتاج بوابة فعلاً إلى إنسان: required decision غير مُجابة، أو بوابة إضافة حاجبة غير معتمدة (مثل Stitch أو Checkpoint)، أو blockers حقيقية يبلّغ عنها verify أو archive، أو طلب صريح من المستخدم للمعاينة أو الموافقة قبل الأرشفة | ||
| - الأرشفة القسرية استثناء بتفويض صريح من المستخدم وليست مسارا احتياطيا تلقائيا. أبلغ أولا عن كل البوابات الفاشلة وعناصر `NOT_VERIFIED` وتأكد من عدم وجود Loop action معلق، ثم شغّل `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. لا تحول الفشل إلى نجاح؛ يبقى الأرشيف incomplete وaccepted-risk. | ||
| - الأرشفة القسرية استثناء بتفويض صريح من المستخدم وليست مسارا احتياطيا تلقائيا. أبلغ أولا عن كل البوابات الفاشلة وعناصر `NOT_VERIFIED`. يجوز بقاء pending Loop pointer فقط عندما تكون كل item مسجلة نهائيا كـ `completed` أو `failed` أو `expired`؛ أما الحالة المفقودة أو `issued` أو `running` فتمنع الأرشفة. ثم شغّل `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. لا تحول الفشل إلى نجاح؛ يبقى الأرشيف incomplete وaccepted-risk. | ||
| - بوابات القرار وخيارات brainstorm ملك للمستخدم: **لا تختر الخيار الموصى به تلقائياً ولا تحلّ بوابة بنفسك**——اعرض كل بوابة عبر سلّم القدرات (واجهة سؤال أصلية ← واجهة خطة/موافقة ← نص محادثة عادي) وانتظر اختيار المستخدم الفعلي؛ البوابات الإلزامية تحجب التنفيذ والإرسال حتى يجيب المستخدم، و`recommended` مجرد تلميح يُعرض على المستخدم | ||
@@ -52,0 +52,0 @@ - اكتب كل وثيقة change وbrainstorm تنشئها بلغة وثائق المشروع (`documentLanguage` في `.skillrc` / إرشادات `for-ai/` المُدارة)؛ لا تخلط العربية والإنجليزية داخل change واحد |
@@ -54,3 +54,3 @@ --- | ||
| - الإغلاق تلقائي عند الجاهزية: عندما ينجح `ospec verify [changes/active/<change>]` ولا توجد required pending decision أو بوابة إضافة (plugin gate) حاجبة، شغّل `ospec finalize [changes/active/<change>]` بنفسك——لا تتوقف بعد نجاح `ospec verify` أو `ospec archive ... --check` (الـ `--check` معاينة فقط) ولا تنتظر طلب المستخدم. لا توقف الإغلاق إلا حين تحتاج بوابة فعلاً إلى إنسان: required decision غير مُجابة، أو بوابة إضافة حاجبة غير معتمدة (مثل Stitch أو Checkpoint)، أو blockers حقيقية يبلّغ عنها verify أو archive، أو طلب صريح من المستخدم للمعاينة أو الموافقة قبل الأرشفة | ||
| - الأرشفة القسرية استثناء بتفويض صريح من المستخدم وليست مسارا احتياطيا تلقائيا. أبلغ أولا عن كل البوابات الفاشلة وعناصر `NOT_VERIFIED` وتأكد من عدم وجود Loop action معلق، ثم شغّل `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. لا تحول الفشل إلى نجاح؛ يبقى الأرشيف incomplete وaccepted-risk. | ||
| - الأرشفة القسرية استثناء بتفويض صريح من المستخدم وليست مسارا احتياطيا تلقائيا. أبلغ أولا عن كل البوابات الفاشلة وعناصر `NOT_VERIFIED`. يجوز بقاء pending Loop pointer فقط عندما تكون كل item مسجلة نهائيا كـ `completed` أو `failed` أو `expired`؛ أما الحالة المفقودة أو `issued` أو `running` فتمنع الأرشفة. ثم شغّل `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. لا تحول الفشل إلى نجاح؛ يبقى الأرشيف incomplete وaccepted-risk. | ||
| - بوابات القرار وخيارات brainstorm ملك للمستخدم: **لا تختر الخيار الموصى به تلقائياً ولا تحلّ بوابة بنفسك**——اعرض كل بوابة عبر سلّم القدرات (واجهة سؤال أصلية ← واجهة خطة/موافقة ← نص محادثة عادي) وانتظر اختيار المستخدم الفعلي؛ البوابات الإلزامية تحجب التنفيذ والإرسال حتى يجيب المستخدم، و`recommended` مجرد تلميح يُعرض على المستخدم | ||
@@ -57,0 +57,0 @@ - اكتب كل وثيقة change وbrainstorm تنشئها بلغة وثائق المشروع (`documentLanguage` في `.skillrc` / إرشادات `for-ai/` المُدارة)؛ لا تخلط العربية والإنجليزية داخل change واحد |
@@ -51,3 +51,3 @@ --- | ||
| - Closeout is automatic when ready: once `ospec verify [changes/active/<change>]` passes and no required user decision or blocking plugin gate is pending, run `ospec finalize [changes/active/<change>]` yourself — do not stop after a passing `ospec verify` or `ospec archive ... --check` (`--check` is a preview only) and do not wait for the user to ask. Only pause closeout when a gate genuinely needs a human: a pending required user decision, an unapproved blocking plugin gate (for example Stitch or Checkpoint), real blockers reported by verify or archive, or an explicit user request to preview or approve before archiving | ||
| - Force archive is an explicit user exception, never an automatic fallback. First report the failing gates and every `NOT_VERIFIED` item and confirm there is no pending Loop action. Then use `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. Preserve failures; the archive remains incomplete and accepted-risk. | ||
| - Force archive is an explicit user exception, never an automatic fallback. First report the failing gates and every `NOT_VERIFIED` item. A retained pending Loop pointer is safe only when all item states are durably `completed`, `failed`, or `expired`; missing, `issued`, or `running` items still block. Then use `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. Preserve failures; the archive remains incomplete and accepted-risk. | ||
| - Decision gates and brainstorm options belong to the user: never auto-select the recommended option or resolve a gate yourself — present every gate with the capability ladder (a native question UI, else a plan/approval UI, else plain chat text) and wait for the user's actual choice; required gates block implementation and dispatch until the user answers, and `recommended` is only a hint to show the user | ||
@@ -54,0 +54,0 @@ - Write every change document and brainstorm you author in the project's document language (`.skillrc` `documentLanguage` / managed `for-ai/` guidance); do not mix Chinese and English within a change |
@@ -56,3 +56,3 @@ --- | ||
| - Closeout is automatic when ready: once `ospec verify [changes/active/<change>]` passes and no required user decision or blocking plugin gate is pending, run `ospec finalize [changes/active/<change>]` yourself — do not stop after a passing `ospec verify` or `ospec archive ... --check` (`--check` is a preview only) and do not wait for the user to ask. Only pause closeout when a gate genuinely needs a human: a pending required user decision, an unapproved blocking plugin gate (for example Stitch or Checkpoint), real blockers reported by verify or archive, or an explicit user request to preview or approve before archiving | ||
| - Force archive is an explicit user exception, never an automatic fallback. First report the failing gates and every `NOT_VERIFIED` item and confirm there is no pending Loop action. Then use `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. Preserve failures; the archive remains incomplete and accepted-risk. | ||
| - Force archive is an explicit user exception, never an automatic fallback. First report the failing gates and every `NOT_VERIFIED` item. A retained pending Loop pointer is safe only when all item states are durably `completed`, `failed`, or `expired`; missing, `issued`, or `running` items still block. Then use `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. Preserve failures; the archive remains incomplete and accepted-risk. | ||
| - Decision gates and brainstorm options belong to the user: never auto-select the recommended option or resolve a gate yourself — present every gate with the capability ladder (a native question UI, else a plan/approval UI, else plain chat text) and wait for the user's actual choice; required gates block implementation and dispatch until the user answers, and `recommended` is only a hint to show the user | ||
@@ -59,0 +59,0 @@ - Write every change document and brainstorm you author in the project's document language (`.skillrc` `documentLanguage` / managed `for-ai/` guidance); do not mix Chinese and English within a change |
@@ -49,3 +49,3 @@ --- | ||
| - 準備ができたら closeout は自動：`ospec verify [changes/active/<change>]` が通過し、required pending decision や blocking なプラグイン gate がない場合は、自分で `ospec finalize [changes/active/<change>]` を実行する——通過した `ospec verify` や `ospec archive ... --check`（`--check` は preview のみ）で止まらず、ユーザーの依頼を待たない。closeout を止めるのは gate が本当に人を必要とするときだけ：未回答の required decision、未承認の blocking プラグイン gate（例：Stitch や Checkpoint）、verify や archive が報告する実際の blocker、またはユーザーが archive 前に preview/承認を明示的に求めた場合 | ||
| - 強制 archive はユーザーが明示した例外であり、自動 fallback ではない。失敗 gate とすべての `NOT_VERIFIED` 項目を報告し、pending Loop action がないことを確認してから、`ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <正確な-change-名> --reason "<受容するリスク>"` を実行する。失敗を pass に書き換えず、archive は incomplete / accepted-risk のままにする。 | ||
| - 強制 archive はユーザーが明示した例外であり、自動 fallback ではない。失敗 gate とすべての `NOT_VERIFIED` 項目を報告する。pending Loop pointer が残っていても、全 item が永続的に `completed`、`failed`、`expired` のいずれかなら安全である。状態欠落、`issued`、`running` は引き続き archive を阻止する。その後 `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <正確な-change-名> --reason "<受容するリスク>"` を実行する。失敗を pass に書き換えず、archive は incomplete / accepted-risk のままにする。 | ||
| - 決定ゲートと brainstorm の選択肢はユーザーのもの：**推奨オプションを自動選択したり、自分でゲートを resolve したりしない**——能力ラダー（ネイティブ質問 UI → plan/承認 UI → 素のチャットテキスト）で各ゲートをユーザーに提示し、ユーザーの実際の選択を待つ。required ゲートはユーザーが答えるまで実装とディスパッチをブロックし、`recommended` はユーザーに見せるヒントにすぎない | ||
@@ -52,0 +52,0 @@ - あなたが作成するすべての change ドキュメントと brainstorm は、プロジェクトのドキュメント言語（`.skillrc` の `documentLanguage` / 管理対象の `for-ai/` ガイダンス）で書く。1 つの change 内で中国語と英語を混在させない |
@@ -54,3 +54,3 @@ --- | ||
| - 準備ができたら closeout は自動：`ospec verify [changes/active/<change>]` が通過し、required pending decision や blocking なプラグイン gate がない場合は、自分で `ospec finalize [changes/active/<change>]` を実行する——通過した `ospec verify` や `ospec archive ... --check`（`--check` は preview のみ）で止まらず、ユーザーの依頼を待たない。closeout を止めるのは gate が本当に人を必要とするときだけ：未回答の required decision、未承認の blocking プラグイン gate（例：Stitch や Checkpoint）、verify や archive が報告する実際の blocker、またはユーザーが archive 前に preview/承認を明示的に求めた場合 | ||
| - 強制 archive はユーザーが明示した例外であり、自動 fallback ではない。失敗 gate とすべての `NOT_VERIFIED` 項目を報告し、pending Loop action がないことを確認してから、`ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <正確な-change-名> --reason "<受容するリスク>"` を実行する。失敗を pass に書き換えず、archive は incomplete / accepted-risk のままにする。 | ||
| - 強制 archive はユーザーが明示した例外であり、自動 fallback ではない。失敗 gate とすべての `NOT_VERIFIED` 項目を報告する。pending Loop pointer が残っていても、全 item が永続的に `completed`、`failed`、`expired` のいずれかなら安全である。状態欠落、`issued`、`running` は引き続き archive を阻止する。その後 `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <正確な-change-名> --reason "<受容するリスク>"` を実行する。失敗を pass に書き換えず、archive は incomplete / accepted-risk のままにする。 | ||
| - 決定ゲートと brainstorm の選択肢はユーザーのもの：**推奨オプションを自動選択したり、自分でゲートを resolve したりしない**——能力ラダー（ネイティブ質問 UI → plan/承認 UI → 素のチャットテキスト）で各ゲートをユーザーに提示し、ユーザーの実際の選択を待つ。required ゲートはユーザーが答えるまで実装とディスパッチをブロックし、`recommended` はユーザーに見せるヒントにすぎない | ||
@@ -57,0 +57,0 @@ - あなたが作成するすべての change ドキュメントと brainstorm は、プロジェクトのドキュメント言語（`.skillrc` の `documentLanguage` / 管理対象の `for-ai/` ガイダンス）で書く。1 つの change 内で中国語と英語を混在させない |
@@ -51,3 +51,3 @@ --- | ||
| - 准备好就自动收尾：当 `ospec verify [changes/active/<change>]` 通过、且没有 required pending decision 或 blocking 插件 gate 时，自己运行 `ospec finalize [changes/active/<change>]`——不要停在通过的 `ospec verify` 或 `ospec archive ... --check`（`--check` 只是预览），也不要等用户来要求。只有当某个 gate 确实需要人工时才暂停收尾：尚未答复的 required decision、未批准的 blocking 插件 gate（如 Stitch 或 Checkpoint）、verify 或 archive 报出的真实 blocker，或用户明确要求先预览或批准再归档 | ||
| - 强制归档只能是用户明确授权的例外，不能作为自动兜底。先报告全部失败门禁和 `NOT_VERIFIED` 项，并确认没有 pending Loop action；再运行 `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <精确-change-名称> --reason "<已接受风险>"`。不得把失败改写为通过；归档必须保持 incomplete 和 accepted-risk 标记。 | ||
| - 强制归档只能是用户明确授权的例外，不能作为自动兜底。先报告全部失败门禁和 `NOT_VERIFIED` 项。保留的 pending Loop 指针只有在全部 item 已持久化为 `completed`、`failed` 或 `expired` 时才安全；缺失状态、`issued` 或 `running` 仍阻止归档。随后运行 `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <精确-change-名称> --reason "<已接受风险>"`。不得把失败改写为通过；归档必须保持 incomplete 和 accepted-risk 标记。 | ||
| - 决策门和 brainstorm 选项属于用户：**绝不要自动选"推荐项"、也不要自己 resolve 决策门**——用能力阶梯（原生问答 UI → Plan/审批 UI → 纯聊天文字）把每个门呈现给用户，等用户真正回答；required 门在用户回答前会阻塞实现与派发，`recommended` 只是给用户看的提示 | ||
@@ -54,0 +54,0 @@ - 你产出的每个 change 文档和 brainstorm 都要用项目的文档语言（`.skillrc` 的 `documentLanguage` / 托管 `for-ai/` 指引）书写；同一个 change 内不要中英文混用 |
@@ -56,3 +56,3 @@ --- | ||
| - 准备好就自动收尾：当 `ospec verify [changes/active/<change>]` 通过、且没有 required pending decision 或 blocking 插件 gate 时，自己运行 `ospec finalize [changes/active/<change>]`——不要停在通过的 `ospec verify` 或 `ospec archive ... --check`（`--check` 只是预览），也不要等用户来要求。只有当某个 gate 确实需要人工时才暂停收尾：尚未答复的 required decision、未批准的 blocking 插件 gate（如 Stitch 或 Checkpoint）、verify 或 archive 报出的真实 blocker，或用户明确要求先预览或批准再归档 | ||
| - 强制归档只能是用户明确授权的例外，不能作为自动兜底。先报告全部失败门禁和 `NOT_VERIFIED` 项，并确认没有 pending Loop action；再运行 `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <精确-change-名称> --reason "<已接受风险>"`。不得把失败改写为通过；归档必须保持 incomplete 和 accepted-risk 标记。 | ||
| - 强制归档只能是用户明确授权的例外，不能作为自动兜底。先报告全部失败门禁和 `NOT_VERIFIED` 项。保留的 pending Loop 指针只有在全部 item 已持久化为 `completed`、`failed` 或 `expired` 时才安全；缺失状态、`issued` 或 `running` 仍阻止归档。随后运行 `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <精确-change-名称> --reason "<已接受风险>"`。不得把失败改写为通过；归档必须保持 incomplete 和 accepted-risk 标记。 | ||
| - 决策门和 brainstorm 选项属于用户：**绝不要自动选"推荐项"、也不要自己 resolve 决策门**——用能力阶梯（原生问答 UI → Plan/审批 UI → 纯聊天文字）把每个门呈现给用户，等用户真正回答；required 门在用户回答前会阻塞实现与派发，`recommended` 只是给用户看的提示 | ||
@@ -59,0 +59,0 @@ - 你产出的每个 change 文档和 brainstorm 都要用项目的文档语言（`.skillrc` 的 `documentLanguage` / 托管 `for-ai/` 指引）书写；同一个 change 内不要中英文混用 |
@@ -62,3 +62,3 @@ --- | ||
| 12. Closeout is automatic when ready: once implementation, `verification.md`, documentation policy, plugin gates, and `review.md` are aligned and `ospec verify [changes/active/<change>]` passes, run `ospec finalize [changes/active/<change>]` yourself. Do not stop at `ospec archive ... --check` (it is a preview only) and do not wait for the user to ask before archiving. **Closeout uses `direct-closeout` (archive locally, no PR) and `manual` merge as defaults — do NOT ask the user about PR, merge, branch, or worktree strategy; uncommitted change/OSpec files in the working tree are normal and do not block archive. Only open a PR if the user explicitly asked.** Only pause closeout when a gate genuinely needs a human: a pending required user decision, an unapproved blocking plugin gate (e.g. Checkpoint), real blockers reported by verify or archive, or an explicit user request to preview or approve before archiving. | ||
| 13. Force archive is never automatic. Use it only after the user explicitly accepts incomplete work: report the failed gates, confirm there is no pending Loop action, then run `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. Preserve failed and `NOT_VERIFIED` evidence; the archive is marked incomplete and must not be presented as completed behavior. | ||
| 13. Force archive is never automatic. Use it only after the user explicitly accepts incomplete work: report the failed gates and inspect any pending Loop pointer. It is safe only when every action item is durably `completed`, `failed`, or `expired`; missing, `issued`, or `running` items still block. Then run `ospec finalize [changes/active/<change>] --force-archive --confirm-force-archive <exact-change-name> --reason "<accepted risk>"`. Preserve failed and `NOT_VERIFIED` evidence; the archive is marked incomplete and must not be presented as completed behavior. | ||
@@ -65,0 +65,0 @@ ## Commands |
@@ -92,3 +92,3 @@ --- | ||
| 14. Use `ospec finalize [changes/active/<goal>]` as the normal closeout path. Closeout is automatic when ready: once the goal is complete and `ospec verify` passes with no required user decision or blocking gate pending, run `ospec finalize` yourself — do not stop at `ospec archive ... --check` (preview only) or wait for the user to ask. **`ospec execute finish` strategy prompts (PR / merge / branch / worktree) are optional with safe defaults (`direct-closeout` + `manual` merge) — do NOT ask the user about them; uncommitted change/OSpec files are normal and do not block archive. Only open a PR if the user explicitly asked.** Only pause for a genuine human gate: a pending required decision, an unapproved blocking plugin gate (e.g. Checkpoint), real verify/archive blockers, or an explicit user request to preview or approve first. | ||
| 15. Force archive is never automatic. Only after the user explicitly asks to accept an incomplete Goal, report every failing gate and `NOT_VERIFIED` item, double-check that no Loop action or child is pending, and run `ospec finalize [changes/active/<goal>] --force-archive --confirm-force-archive <exact-goal-name> --reason "<accepted risk>"`. Do not rewrite failed evidence as passed. The resulting archive remains `forced`, `incomplete`, and `accepted-risk`, not completed behavior. | ||
| 15. Force archive is never automatic. Only after the user explicitly asks to accept an incomplete Goal, report every failing gate and `NOT_VERIFIED` item, then double-check the Loop action items. A retained pending pointer is allowed only when every item is durably `completed`, `failed`, or `expired`; missing, `issued`, or `running` items still block. Run `ospec finalize [changes/active/<goal>] --force-archive --confirm-force-archive <exact-goal-name> --reason "<accepted risk>"`. Do not rewrite failed evidence as passed. The resulting archive remains `forced`, `incomplete`, and `accepted-risk`, not completed behavior. | ||
@@ -95,0 +95,0 @@ ## Commands |
+1
-1
@@ -65,3 +65,3 @@ #!/usr/bin/env node | ||
| const services_1 = require("./services"); | ||
| const CLI_VERSION = '1.8.21'; | ||
| const CLI_VERSION = '1.8.22'; | ||
| 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]'); |
+1
-1
| { | ||
| "name": "@clawplays/ospec-cli", | ||
| "version": "1.8.21", | ||
| "version": "1.8.22", | ||
| "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", |
+1
-1
@@ -187,3 +187,3 @@ <h1><a href="https://ospec.ai/" target="_blank" rel="noopener noreferrer">OSpec.ai</a></h1> | ||
| - use `ospec finalize` to rebuild indexes and archive the accepted change | ||
| - force archive is never automatic: it requires the force flag, an exact change-name confirmation, and an audit reason; it refuses a pending Loop action and marks the archive `forced`, `incomplete`, and `accepted-risk` instead of completed | ||
| - force archive is never automatic: it requires the force flag, an exact change-name confirmation, and an audit reason; it refuses any missing, `issued`, or `running` Loop item, but may preserve an unconsumed pointer whose items are all terminal; the archive is marked `forced`, `incomplete`, and `accepted-risk` instead of completed | ||
| - new nested projects archive under `.ospec/changes/archived/YYYY-MM/YYYY-MM-DD/<change-name>`; CLI shorthand under `changes/archived/...` still works | ||
@@ -190,0 +190,0 @@ - existing flat archives are reorganized by `ospec update` |
+1
-1
@@ -58,3 +58,3 @@ --- | ||
| - Keep reviewers independent: they read scoped evidence, do not edit implementation, do not accept hidden severity downgrades, and report findings before summaries. Record actionable findings in both Markdown and the sibling structured `*.findings.json`. | ||
| - Do not archive while task graph, review, decision, documentation, optional-step, worker-status, or verification gates are unresolved during normal closeout. Force archive is an explicit user-directed exception only: first report the unresolved gates and `NOT_VERIFIED` evidence, then require `--force-archive`, an exact-name `--confirm-force-archive`, and a non-empty audit reason. Never infer this authorization from urgency, a blocker, or a request to "finish"; never run it while a Loop action is pending. | ||
| - Do not archive while task graph, review, decision, documentation, optional-step, worker-status, or verification gates are unresolved during normal closeout. Force archive is an explicit user-directed exception only: first report the unresolved gates and `NOT_VERIFIED` evidence, then require `--force-archive`, an exact-name `--confirm-force-archive`, and a non-empty audit reason. Never infer this authorization from urgency, a blocker, or a request to "finish". A pending Loop pointer is safe only when every action item is durably terminal (`completed`, `failed`, or `expired`); any missing, `issued`, or `running` item still blocks archive. | ||
@@ -61,0 +61,0 @@ Detailed goal artifacts live under `changes/active/<change>/artifacts/agents/` and `artifacts/reviews/`. Read their current packet or `for-ai/execution-protocol.md` for exact paths and commands instead of expanding the entire inventory here. |
Sorry, the diff of this file is too big to display
New alerts
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Fixed alerts
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Improved metrics
- Total package byte prevSize
3420151
0.06%- Lines of code
59786
0.01%No dependency changes