@yunhozz/arc 0.1.6 → 0.1.7

package/MANIFEST.sha256

@@ -6,18 +6,18 @@ d853d31ba0d1a04661adf8cae1df11058455cb5d366c52312888c9dd2e9a1fb8  claude/agents/
 d864e57a1b2b6d69435a17a5c56a0e2c68d26592dd5e510be8d0fa341762cad1  claude/agents/arc-qa.md
 bd51442a5e76d4b61cbeb7f42d43cbcc7bab890db0d39ef16002ae13f5317c34  claude/agents/arc-reviewer.md
 c20162438bb8ac6905164268f867a8f1cfdbbfd51ddfd7e795cc211cc7f8c858  claude/agents/arc-scouter.md
-525c92fb52cc45c2f779176629e11c3a21f4e4434648cd5d6e4f6d7657f536f6  claude/skill/SKILL.md
+c5002996b3feb406c52dcbb305631e98d5206176c4617933763c6f2e17da6bb3  claude/skill/SKILL.md
 0bf77247b82371b3fe12a8dbe8fd2415c98d06e676d2c234b086b1f1e661b9db  claude/skill/hooks/git-policy.json
 b188c24d1339367acfe16b81be5743298e498856915e5e91b45e1a7220dad602  claude/skill/hooks/role-git-guard.mjs
 5126d44470486cb2581790b7c8d1605c4d0ee2448b725cf536ba1141eb40fa81  claude/skill/hooks/runtime-gate.mjs
 3926dbf9c7c244ebbb0baee17b1163387979793cb81c28e90977473d1e0a85e9  claude/skill/references/commit.md
-33ccd670b9d365abcc03edbfa26761ad00970df8e46633799beee4e72e6148fe  claude/skill/references/coordination.md
+61dc37bd08a9004e67cc7b76102cf3cbcb170a08d5d3576f27dcc39dec47a692  claude/skill/references/coordination.md
 90198f8bc6d9e99cbdb32604413c708753ff8503954b6b120aa7c7f00719de96  claude/skill/references/git-recovery.md
 d4b3100626831b23f0b1cf0106ef9f3bc7e6f3d14864e9dd93ae0f8063b5bdda  claude/skill/references/handoff-prep.md
 42a13f77f2b28d660236237dff88cab166f052a178295cef253a774fd6fc8e40  claude/skill/references/handoff.md
 4172c1c8ba397ceb561e437cc6ef02d4c2d7e7ed3df1400a4efbf4b46ddca4fa  claude/skill/references/limits.md
 93a7001c6ad4215170fa331261c2d58835fcdad823724f024d5c81a450133340  claude/skill/references/planning.md
-78704f725dd82bf49f7916ef5522e8c52040ccb05e109b568796d8a9f6e52e6e  claude/skill/references/verification.md
+d25178b548e5bccd7ee5c9efea1b48e8a2f3a6275b6572ab648566eada309c2b  claude/skill/references/verification.md
 cae43b5105a1300e87526bcc286516519863b2f8c5f70cd6fe1e0950b196a762  claude/skill/references/visual-companion.md
 30d8cdcb9d7ab6396cab09cd9f5cf6b8003f5490fb5c0ffe9f5acffbb0534978  claude/skill/runtime/adapters/claude.mjs
 d30d118d3b42b805195ed05a3dea0ed3cf939eac811cf0228ca0b0cafeda7969  claude/skill/runtime/adapters/codex.mjs
@@ -28,7 +28,7 @@ b210df233983ffef326d65ae41a096fdef1b53d1e300ada3b217de3524686701  claude/skill/r
 494470cf70121ddac8d716586b0c05b1f0977f3eada8c0323ed34dc157b0db8e  claude/skill/runtime/git-query.mjs
 cde1d91eb252e212e1985cee4bac0753964ba1c507202c711adab88f020e474d  claude/skill/runtime/identity.mjs
 23339b1d2ac83c673ded090f993dee7985c785442cababdb6a3a224163451eef  claude/skill/runtime/operations.mjs
-c93f08cf6cafb5d96007df33d00dadda676c54b074fb998c2e523ecfc5e23d30  claude/skill/runtime/role-policy.json
+46b4e793c538f858b3a3e46087cd140a5a34154e6ecf5381c22b71250f289904  claude/skill/runtime/role-policy.json
 71d5696e0523f2f915a2de02cf3ded453b27783b9e09d2b98ec4aef1958a26a4  claude/skill/runtime/schema.mjs
 aa1361419c0137f74793847805a3abc076a8d782c6f590e2d28b8eee5c35065d  claude/skill/runtime/store.mjs
 e4445f3582c55861907e11dfe97ea9e87c69bcc3ff773d3d583914c198f1d024  claude/skill/scripts/apply-models.py
@@ -38,17 +38,17 @@ d9c718e4a1cce5fef343afbc623ebb82fd29b85f40270b84a0f1770f57a61a50  codex/agents/a
 793d132db240208729c2d54068634e872ead72b573c0cd4648a6e2f50e5cc56c  codex/agents/arc-qa.toml
 022f1abd7fd325ab543f6c7c5263a1d0c973be417a39ee8f3bb3295b44749fa3  codex/agents/arc-reviewer.toml
 0dc1905c3bb16e3b7117d9b38cab0c1e6e93f496afdb82f782ef830f1f3a6417  codex/agents/arc-scouter.toml
-79a113eebcaff301656fdc52f3713f0dad909ce7b55d6a0357504ca20eb48549  codex/skill/SKILL.md
+e80d96e74664741e9c6659b73c0ed5327ab0148e7b0f81a7eb7683ff43b8f094  codex/skill/SKILL.md
 019f190ee7a2ccfea059a289ca971265574b043353f89bc96e219436c9827e9e  codex/skill/hooks/runtime-gate.mjs
 ce8ab4dd1a69176fc4d76b2e9e3c81b9165586c3a29833fe855f2a085f22195e  codex/skill/references/commit.md
-263b4d59d67bc365bcf9e658ebfba1d3896662c5fcdb0f45a87a30fd6b0fd43a  codex/skill/references/coordination.md
+1aa3442643111a79985cb29ea90ca3fc357b989aaf37a1540115864d3e9c3acd  codex/skill/references/coordination.md
 be0a2e4050a0cad20d272775698be82dcc244081c4c1092de56e8a118de718b1  codex/skill/references/git-recovery.md
 39ce5bb81d1fa303394c8c2c6b0d306d9fc341a866654fdabb02a33e6f5c2dee  codex/skill/references/handoff-prep.md
 272b60b91ac05139985611d1555c417eab3ca1783655a9196511a0eda02caaba  codex/skill/references/handoff-worktree.md
 3338d9080415c3cdd4c7a5337f5c1f1d74e9f6cfb084181fe9cce78d906a1162  codex/skill/references/handoff.md
 89ae51633112f8c7bd71ab15940085e01e57d6582fb0d977c9efdf9d77ce9fc3  codex/skill/references/limits.md
 ed40f33754e4b6df683fe567b91974a381cf99ebd5ec772b493a71f17f01d5a7  codex/skill/references/planning.md
-3b89adb5bfbf91ac4937b41cdd3a5ebb2ffb652826fff9d834489bd377245e2c  codex/skill/references/verification.md
+092ecc14f10c45a2048499270340074b52c1cb28c3807c55f50abe63053db4eb  codex/skill/references/verification.md
 23d928dc115b922e5418db9c89057dab2f19acb7c946420a55923d3bb5148417  codex/skill/references/visual-companion.md
 30d8cdcb9d7ab6396cab09cd9f5cf6b8003f5490fb5c0ffe9f5acffbb0534978  codex/skill/runtime/adapters/claude.mjs
 d30d118d3b42b805195ed05a3dea0ed3cf939eac811cf0228ca0b0cafeda7969  codex/skill/runtime/adapters/codex.mjs
@@ -59,7 +59,7 @@ b210df233983ffef326d65ae41a096fdef1b53d1e300ada3b217de3524686701  codex/skill/ru
 494470cf70121ddac8d716586b0c05b1f0977f3eada8c0323ed34dc157b0db8e  codex/skill/runtime/git-query.mjs
 cde1d91eb252e212e1985cee4bac0753964ba1c507202c711adab88f020e474d  codex/skill/runtime/identity.mjs
 23339b1d2ac83c673ded090f993dee7985c785442cababdb6a3a224163451eef  codex/skill/runtime/operations.mjs
-c93f08cf6cafb5d96007df33d00dadda676c54b074fb998c2e523ecfc5e23d30  codex/skill/runtime/role-policy.json
+46b4e793c538f858b3a3e46087cd140a5a34154e6ecf5381c22b71250f289904  codex/skill/runtime/role-policy.json
 71d5696e0523f2f915a2de02cf3ded453b27783b9e09d2b98ec4aef1958a26a4  codex/skill/runtime/schema.mjs
 aa1361419c0137f74793847805a3abc076a8d782c6f590e2d28b8eee5c35065d  codex/skill/runtime/store.mjs
 57e93213dc97465757294cb9d0ae2f4eb2f1384b955c4ca2a39f2fa38f7a9bd7  codex/skill/scripts/apply-models.py
@@ -103,7 +103,7 @@ ee81dee01b1623d95dda9b1d195ce2008811dfb54af3da8324a9e538238ac84e  lib/npm/proces
 7c36313221f36a9d08964017c79e8c7b3c848655f6a338f71a24ce508ac6e3ed  lib/policy/claude-hook.mjs
 f32fcb03201c6a73d658a6b3107376f13d03f21503c568a7b4e71ff9b71dd426  lib/policy/placement.mjs
 09b5851cdbcb88b9d4d027e2d96aadb275660354ea64eef0aaa7583ec8090c3e  lib/policy/render.mjs
-5fd21f28b7983a89de8d52033ea61003462586ae679dbf87843b8291a2a29237  lib/policy/role-policy.json
+46b4e793c538f858b3a3e46087cd140a5a34154e6ecf5381c22b71250f289904  lib/policy/role-policy.json
 80e270d526e9a9c5cac23fe6ae293c2fd25a0176e4a8060987fd19dafe2a4594  lib/release/artifact.mjs
 30d8cdcb9d7ab6396cab09cd9f5cf6b8003f5490fb5c0ffe9f5acffbb0534978  lib/runtime/adapters/claude.mjs
 d30d118d3b42b805195ed05a3dea0ed3cf939eac811cf0228ca0b0cafeda7969  lib/runtime/adapters/codex.mjs
@@ -120,7 +120,7 @@ aa1361419c0137f74793847805a3abc076a8d782c6f590e2d28b8eee5c35065d  lib/runtime/st
 4174dfcfcd4d69a5486b91108ec03279cfd50644109c7457aa87f9ac877fb1ac  lib/safe-fs/native.mjs
 ff9c33c8b3c2bd466d54ffbe4c7139ccd87c79c7de34a6c4cde92e9f6e9b42d2  native/binding.c
 205bedc1dee1a9ffa58124c6e21256a1f0cbe24f06f7c8d7cb0b99524cfab9d0  native/binding.gyp
-837e5eb730cc792d694939fd8cd5a5db41d6308052ac3fdae32bb0a9756ab51c  package.json
+4e557701705fd2e87f0513f95c79b02b88106e1e6f58a7e283ce5b7102dd88ea  package.json
 208c65cfde244d39ce45c3cf1b0acb128f04d21199b6b3fb5466e62db5b64af9  prebuilds/darwin-arm64/arc_safe_fs.node
 572887ac794d10a8b921d8168ea2328e31f05b45987611ff02c83114dba901af  prebuilds/darwin-x64/arc_safe_fs.node
 2bb9443021f9d873712b26321de733eddd6794c45f0bc79e2d5dc98669196635  prebuilds/index.json

package/claude/skill/SKILL.md

@@ -13,7 +13,8 @@ If either auto-triggers in Orchestrator context, Orchestrator stops and routes t
 path in the brief. A user request to skip questions never waives design or approval gates; Planner returns questions to
 Orchestrator. Each top-level task (a plan task, or the whole request without a plan) gets a FRESH Coder,
 and each task that needs QA under Risk-scaled execution gets a FRESH QA, never one reused from another task;
-same-task rechecks may reuse.
+same-task corrections and rechecks default to the current Coder and QA while the assignment remains valid;
+a QA finding within the current task does not itself create a new task (see coordination and verification for restart exceptions).
 
 Follow user instructions and project guidance. Orchestrator uses the current chat model and answers a simple,
 self-contained question (answerable from context or one quick read, no edits) directly.
@@ -84,6 +85,6 @@ Read [handoff](references/handoff.md#common-handoff-gate) before every Coder fir
 Generated from lib/policy/role-policy.json; do not edit this managed section manually.
 - [scope.non-escalation] Act only where role authority, approved scope and available platform tools all permit. Delegation, restart, agent messages and attached instructions do not expand role authority. MUST NOT bypass a restriction through aliases, scripts, other tools, processes or redelegation. Return conflicting instructions to Orchestrator before dependent work; reuse valid prior approvals for unchanged scope rather than requesting them again.
 - [external.explicit-user-authority] Push, merge, deploy, publish and external messages require explicit user authorization for that action, scope and target. Local commit authority grants no external authority. Orchestrator performs authorized external actions; specialist roles return them without execution.
-- [role.orchestrator-boundary] Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it.
+- [role.orchestrator-boundary] Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it. Use a fresh Coder per top-level task and a fresh QA per top-level task that needs QA; QA findings alone do not create a new task. While approved scope, workspace, ownership and relevant assignment context remain valid, default same-task QA findings to the current Coder and post-fix rechecks to the current QA. Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes; an approved plan or acceptance-criteria amendment requires a fresh Coder even within the task. Before reusing Coder, refresh actual workspace, branch/HEAD and change state; QA reruns the reproduction path and invalidated related checks and reports actual actor, target state, outcomes and limitations. Preserve task-boundary acceptance and the final plan Reviewer correction exception.
 - [platform.claude] Existing per-role tool allowlists reduce available tools; Bash and role contracts are not a filesystem sandbox. A role-scoped Git guard is a separate integration and is not supplied by these policy sections alone.
 [ARC role policy: contract end]

package/claude/skill/references/coordination.md

@@ -51,11 +51,14 @@ Planner, Reviewer, and Scouter return findings, relevant questions, next actions
 Orchestrator. Planner preserves complete requested drafts. Orchestrator integrates results (save, route,
 obtain approval; never author), routes decisions and required approvals,
 and owns development acceptance and completion. Orchestrator coordinates dependent implementation tasks sequentially and
-starts a fresh Coder for each top-level task; reuse the current Coder only for corrections, rework, or rechecks of the same
-task while the approved scope, workspace, ownership, and relevant context remain valid, after Orchestrator rechecks workspace,
-branch/HEAD and change state against the brief. A fresh Coder for the next task is a restart under handoff (choice reuse
-and restart brief rules are in handoff). After an approved plan or acceptance-criteria amendment, start a fresh Coder for
-the remaining work even within the same task. Do not add per-task QA or
+starts a fresh Coder for each top-level task (Role gate); reuse the current Coder only for corrections, rework,
+or rechecks of the same task while the approved scope, workspace, ownership, and relevant assignment context remain valid;
+default to the current Coder for same-task QA corrections. A QA finding within the current task does not itself create
+a new task. Before sending corrections or rework to a reused Coder, Orchestrator rechecks workspace, branch/HEAD and change state against the brief.
+Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes, subject to the
+amendment exception below. A fresh Coder for the next task is a restart under handoff (choice reuse and restart brief rules are in handoff).
+After an approved plan or acceptance-criteria amendment, start a fresh Coder for
+the remaining work even within the same task; it is also a restart under handoff. Do not add per-task QA or
 review gates solely because a task boundary exists; apply risk requirements and specific approved obligations. If the
 next task depends on a still-unverified risky contract, complete applicable QA at that dependency boundary and
 resolve or explicitly disposition findings before dependent implementation. This does not create a gate for every task.

package/claude/skill/references/verification.md

@@ -22,13 +22,19 @@ repairs.
 ## Reviewer timing and task acceptance
 
 Task acceptance and its focused commit need only the task's risk-scaled evidence: a FRESH QA instance per task that
-needs QA (same-task rechecks may reuse), or Orchestrator focused checks for small, low-risk tasks; Reviewer is never a
+needs QA (default to the current QA for post-fix rechecks of the same task while the approved scope, workspace,
+ownership, and relevant assignment context remain valid), or Orchestrator focused checks for small, low-risk tasks; Reviewer is never a
 plan-task acceptance prerequisite. Do not delay an independently acceptable task for final-only checks,
 and do not defer currently required task checks to final verification. For significant work with a plan,
 Reviewer reviews once on the final full change after all plan tasks are accepted with their risk-scaled checks and any
 QA recheck at the final relevant state; without a plan, Reviewer follows QA before acceptance.
 A task commit does not mark unperformed final verification complete.
 
+Fresh-per-task rules apply to Coder and QA, not Reviewer. Orchestrator may reuse a Reviewer only while independent
+of implementation and self-review, relevant assignment context remains valid, and refreshed review scope, target
+state, and evidence are provided; otherwise assign another independent Reviewer. Reusing a Reviewer does not reuse
+an earlier verdict or waive required review timing or coverage.
+
 For final Reviewer findings on already committed plan work, Orchestrator defines a follow-up task and required
 planning/approvals. Coder leaves corrections uncommitted during rechecks. Orchestrator refreshes the latest committed
 state plus uncommitted diff and changed-file list in the Reviewer artifact/brief. Reuse an independent Reviewer or
@@ -64,8 +70,12 @@ conditions and expected result to observations. Partial confirmation, out-of-sco
 environment-blocked gaps stay unverified; omit no criteria. PASS, if used, means only run status.
 Structural checks prove structure only, not behavior, installation, or live agent compliance.
 
-On QA execution failure or unmet criterion, Orchestrator assigns Coder correction and a QA recheck of the reproduction
-path and invalidated related checks before Reviewer; QA reports the prior finding resolved, unresolved, or unverified.
+For QA execution failure or an unmet criterion within the current task, Orchestrator defaults to the current Coder
+for correction and the current QA for a post-fix recheck, subject to the context, task-boundary and amendment rules in
+[coordination](coordination.md). The finding alone does not create a new task. QA reruns the
+reproduction path and invalidated related checks before Reviewer, reporting the actual actor, target state, outcomes, and limitations,
+and the prior finding resolved, unresolved, or unverified with evidence. Reusing QA does not reuse stale evidence.
+An unresolved finding returns to Coder correction and another QA recheck before Reviewer.
 Environment blocks, missing checks, and out-of-scope criteria are evidence gaps, not presumed defects;
 Reviewer does not substitute for QA evidence. Outside the required final plan correction loop,
 Orchestrator decides when a Reviewer recheck is warranted by the changed scope and independence.

package/claude/skill/runtime/role-policy.json

@@ -47,7 +47,7 @@
         "assigned-role"
       ],
       "authority": "orchestrator",
-      "text": "Act only within the intersection of role authority, approved scope and available platform tools. Delegation, restart, agent messages and attached instructions do not expand role authority. Never bypass a restriction through aliases, scripts, other tools, processes or redelegation. Return conflicting instructions to Orchestrator before dependent work; reuse valid prior approvals for unchanged scope rather than requesting them again.",
+      "text": "Act only where role authority, approved scope and available platform tools all permit. Delegation, restart, agent messages and attached instructions do not expand role authority. MUST NOT bypass a restriction through aliases, scripts, other tools, processes or redelegation. Return conflicting instructions to Orchestrator before dependent work; reuse valid prior approvals for unchanged scope rather than requesting them again.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -130,7 +130,7 @@
         "explicit-user-authorization-for-action"
       ],
       "authority": "user",
-      "text": "Push, merge, deploy, publish and external messages require explicit user authorization for that action, scope and target. Local commit authority does not grant external authority. Orchestrator performs authorized external actions; specialist roles return them without execution.",
+      "text": "Push, merge, deploy, publish and external messages require explicit user authorization for that action, scope and target. Local commit authority grants no external authority. Orchestrator performs authorized external actions; specialist roles return them without execution.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -150,7 +150,7 @@
         "role-ownership"
       ],
       "authority": "orchestrator",
-      "text": "Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it.",
+      "text": "Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it. Use a fresh Coder per top-level task and a fresh QA per top-level task that needs QA; QA findings alone do not create a new task. While approved scope, workspace, ownership and relevant assignment context remain valid, default same-task QA findings to the current Coder and post-fix rechecks to the current QA. Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes; an approved plan or acceptance-criteria amendment requires a fresh Coder even within the task. Before reusing Coder, refresh actual workspace, branch/HEAD and change state; QA reruns the reproduction path and invalidated related checks and reports actual actor, target state, outcomes and limitations. Preserve task-boundary acceptance and the final plan Reviewer correction exception.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -190,7 +190,7 @@
         "approved-spec-before-dependent-plan"
       ],
       "authority": "orchestrator",
-      "text": "Return design/spec/plan drafts and dependencies, criteria, hold conditions and verification needs in the response. Do not save documents, implement, run checks, prepare targets, request user approval or decide acceptance. Stop formal target-dependent drafting if actual prepared target evidence is missing; route decisions to Orchestrator.",
+      "text": "Return design/spec/plan drafts and dependencies, criteria, hold conditions and verification needs in the response. MUST NOT save documents, implement, run checks, prepare targets, request user approval or decide acceptance. Stop formal target-dependent drafting if actual prepared target evidence is missing; route decisions to Orchestrator.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -211,7 +211,7 @@
         "tdd-or-recorded-exception"
       ],
       "authority": "orchestrator",
-      "text": "Implement only assigned approved files and focused checks under the existing TDD contract. Report changed files, RED/GREEN or authorized exception evidence, results, limits and follow-up. Do not plan, independently QA/review your own work, accept the task or declare overall completion. Git changes remain forbidden even when implementation succeeds.",
+      "text": "Edit only assigned, approved files and run focused checks under the existing TDD contract. Report changed files, RED/GREEN or authorized exception evidence, results, limits and follow-up. Do not plan, independently QA/review your own work, accept the task or declare overall completion. Git changes remain forbidden even when implementation succeeds.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -253,7 +253,7 @@
         "relevant-qa-evidence"
       ],
       "authority": "orchestrator",
-      "text": "Independently inspect the assigned final changes and evidence and report actionable findings and limits. Remain read-only; do not execute QA tests, edit files, perform Git mutations or decide acceptance.",
+      "text": "Independently inspect the assigned final changes and evidence and report actionable findings and limits. Remain read-only. MUST NOT execute QA tests, edit files, perform Git mutations or decide acceptance.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -278,7 +278,7 @@
         "qa-rechecks"
       ],
       "authority": "orchestrator",
-      "text": "For significant/high-risk work without a plan: Coder \u2192 QA and required QA rechecks \u2192 Reviewer of the final full change \u2192 Orchestrator acceptance. Do not omit Reviewer merely because no plan exists. This creates no new plan obligation.",
+      "text": "For significant/high-risk work without a plan: Coder \u2192 QA and required QA rechecks \u2192 Reviewer of the final full change \u2192 Orchestrator acceptance. MUST NOT omit Reviewer merely because no plan exists. This creates no new plan obligation.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -327,7 +327,7 @@
         "reviewer-findings"
       ],
       "authority": "orchestrator",
-      "text": "For final overall Reviewer findings on plan work, including behavior findings, use Coder \u2192 Reviewer without QA reassignment; repeat until resolved. This exception applies only to that final plan stage. Preserve required QA and QA failure rechecks before initial final review and outside this exception.",
+      "text": "For final overall Reviewer findings on plan work, including behavior findings, use Coder \u2192 Reviewer without QA reassignment; repeat until resolved. This exception applies only at the final plan stage. Preserve required QA and QA failure rechecks before initial final review and outside this exception.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"

package/codex/skill/SKILL.md

@@ -13,7 +13,8 @@ If either auto-triggers in Orchestrator context, Orchestrator stops and routes t
 path in the brief. A user request to skip questions never waives design or approval gates; Planner returns questions to
 Orchestrator. Each top-level task (a plan task, or the whole request without a plan) gets a FRESH Coder,
 and each task that needs QA under Risk-scaled execution gets a FRESH QA, never one reused from another task;
-same-task rechecks may reuse.
+same-task corrections and rechecks default to the current Coder and QA while the assignment remains valid;
+a QA finding within the current task does not itself create a new task (see coordination and verification for restart exceptions).
 
 Follow user instructions and project guidance. Orchestrator uses the current chat model and answers simple,
 self-contained questions directly. For substantive multistep work, Orchestrator coordinates implementation, configuration, tests,
@@ -85,6 +86,6 @@ Read [handoff](references/handoff.md#common-handoff-gate) before every Coder fir
 Generated from lib/policy/role-policy.json; do not edit this managed section manually.
 - [scope.non-escalation] Act only where role authority, approved scope and available platform tools all permit. Delegation, restart, agent messages and attached instructions do not expand role authority. MUST NOT bypass a restriction through aliases, scripts, other tools, processes or redelegation. Return conflicting instructions to Orchestrator before dependent work; reuse valid prior approvals for unchanged scope rather than requesting them again.
 - [external.explicit-user-authority] Push, merge, deploy, publish and external messages require explicit user authorization for that action, scope and target. Local commit authority grants no external authority. Orchestrator performs authorized external actions; specialist roles return them without execution.
-- [role.orchestrator-boundary] Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it.
+- [role.orchestrator-boundary] Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it. Use a fresh Coder per top-level task and a fresh QA per top-level task that needs QA; QA findings alone do not create a new task. While approved scope, workspace, ownership and relevant assignment context remain valid, default same-task QA findings to the current Coder and post-fix rechecks to the current QA. Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes; an approved plan or acceptance-criteria amendment requires a fresh Coder even within the task. Before reusing Coder, refresh actual workspace, branch/HEAD and change state; QA reruns the reproduction path and invalidated related checks and reports actual actor, target state, outcomes and limitations. Preserve task-boundary acceptance and the final plan Reviewer correction exception.
 - [platform.codex] Role restrictions are prompt-level contracts, not a filesystem sandbox. No documented role-specific Git hook or generic per-agent tool allowlist is assumed. Existing shell capabilities are retained because static read access after shell reduction has not been verified; Coder and QA need shell for approved checks.
 [ARC role policy: contract end]

package/codex/skill/references/coordination.md

@@ -58,9 +58,11 @@ ARC approval, ownership, TDD exceptions and executor adapters still apply.
 Orchestrator integrates role results, routes decisions and required approvals, and owns development acceptance
 and completion. Orchestrator coordinates dependent implementation tasks sequentially and
 starts a fresh Coder for each top-level task (Role gate); reuse the current Coder only for corrections, rework,
-or rechecks of the same task while the approved scope, workspace, ownership, and relevant context remain valid; before
-sending corrections or rework to a reused Coder, Orchestrator rechecks workspace, branch/HEAD and change state against the brief.
-A fresh Coder for the next task is a restart under handoff (choice reuse and restart brief rules are in handoff).
+or rechecks of the same task while the approved scope, workspace, ownership, and relevant assignment context remain valid;
+default to the current Coder for same-task QA corrections. A QA finding within the current task does not itself create
+a new task. Before sending corrections or rework to a reused Coder, Orchestrator rechecks workspace, branch/HEAD and change state against the brief.
+Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes, subject to the
+amendment exception below. A fresh Coder for the next task is a restart under handoff (choice reuse and restart brief rules are in handoff).
 After an approved plan or acceptance-criteria amendment, start a fresh Coder for
 the remaining work even within the same task; it is also a restart under handoff. Task-boundary gates
 follow [Risk-scaled execution](verification.md#risk-scaled-execution).

package/codex/skill/references/verification.md

@@ -40,6 +40,11 @@ explicitly dispositioned.
 
 Criterion verdicts follow the Evidence verdict.
 
+Fresh-per-task rules apply to Coder and QA, not Reviewer. Orchestrator may reuse a Reviewer only while independent
+of implementation and self-review, relevant assignment context remains valid, and refreshed review scope, target
+state, and evidence are provided; otherwise assign another independent Reviewer. Reusing a Reviewer does not reuse
+an earlier verdict or waive required review timing or coverage.
+
 ### Final plan Reviewer correction loop
 
 For a plan's final overall Reviewer findings, including behavior findings, Orchestrator assigns
@@ -95,7 +100,8 @@ acceptance criteria to actual evidence, currently required checks and findings b
 completion, a Coder report or passing commands alone do not establish acceptance.
 
 Task acceptance and its focused commit require only the task's risk-scaled evidence: a FRESH QA instance per task that
-needs QA (same-task rechecks may reuse), or Orchestrator focused checks for small, low-risk tasks;
+needs QA (default to the current QA for post-fix rechecks of the same task while the approved scope, workspace,
+ownership, and relevant assignment context remain valid), or Orchestrator focused checks for small, low-risk tasks;
 Reviewer timing and task-boundary gates follow the Risk-scaled execution section above. For an independently acceptable task,
 do not delay its acceptance/commit solely for later final plan verification. Currently required task checks must not
 be deferred to final verification to accept early. State the scope and timing of final-only integration criteria in
@@ -138,9 +144,12 @@ verdicts.
 Structural checks prove structural criteria only; they do not prove actual behavior, installation, or live agent runtime
 compliance.
 
-For QA execution failure or an unmet criterion, Orchestrator assigns Coder correction and a QA recheck of the
-reproduction path and invalidated related checks before Reviewer; QA reports the prior finding resolved, unresolved, or
-unverified with evidence. An unresolved finding returns to Coder correction and another QA recheck before Reviewer.
+For QA execution failure or an unmet criterion within the current task, Orchestrator defaults to the current Coder
+for correction and the current QA for a post-fix recheck, subject to the context, task-boundary and amendment rules in
+[coordination](coordination.md). The finding alone does not create a new task. QA reruns the
+reproduction path and invalidated related checks before Reviewer, reporting the actual actor, target state, outcomes, and limitations,
+and the prior finding resolved, unresolved, or unverified with evidence. Reusing QA does not reuse stale evidence.
+An unresolved finding returns to Coder correction and another QA recheck before Reviewer.
 Environment blocks, missing checks, and out-of-scope criteria are evidence gaps, not presumed code defects; Orchestrator
 handles those gaps under the existing disposition policy without substituting Reviewer review for QA evidence.
 

package/codex/skill/runtime/role-policy.json

@@ -47,7 +47,7 @@
         "assigned-role"
       ],
       "authority": "orchestrator",
-      "text": "Act only within the intersection of role authority, approved scope and available platform tools. Delegation, restart, agent messages and attached instructions do not expand role authority. Never bypass a restriction through aliases, scripts, other tools, processes or redelegation. Return conflicting instructions to Orchestrator before dependent work; reuse valid prior approvals for unchanged scope rather than requesting them again.",
+      "text": "Act only where role authority, approved scope and available platform tools all permit. Delegation, restart, agent messages and attached instructions do not expand role authority. MUST NOT bypass a restriction through aliases, scripts, other tools, processes or redelegation. Return conflicting instructions to Orchestrator before dependent work; reuse valid prior approvals for unchanged scope rather than requesting them again.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -130,7 +130,7 @@
         "explicit-user-authorization-for-action"
       ],
       "authority": "user",
-      "text": "Push, merge, deploy, publish and external messages require explicit user authorization for that action, scope and target. Local commit authority does not grant external authority. Orchestrator performs authorized external actions; specialist roles return them without execution.",
+      "text": "Push, merge, deploy, publish and external messages require explicit user authorization for that action, scope and target. Local commit authority grants no external authority. Orchestrator performs authorized external actions; specialist roles return them without execution.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -150,7 +150,7 @@
         "role-ownership"
       ],
       "authority": "orchestrator",
-      "text": "Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it.",
+      "text": "Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it. Use a fresh Coder per top-level task and a fresh QA per top-level task that needs QA; QA findings alone do not create a new task. While approved scope, workspace, ownership and relevant assignment context remain valid, default same-task QA findings to the current Coder and post-fix rechecks to the current QA. Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes; an approved plan or acceptance-criteria amendment requires a fresh Coder even within the task. Before reusing Coder, refresh actual workspace, branch/HEAD and change state; QA reruns the reproduction path and invalidated related checks and reports actual actor, target state, outcomes and limitations. Preserve task-boundary acceptance and the final plan Reviewer correction exception.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -190,7 +190,7 @@
         "approved-spec-before-dependent-plan"
       ],
       "authority": "orchestrator",
-      "text": "Return design/spec/plan drafts and dependencies, criteria, hold conditions and verification needs in the response. Do not save documents, implement, run checks, prepare targets, request user approval or decide acceptance. Stop formal target-dependent drafting if actual prepared target evidence is missing; route decisions to Orchestrator.",
+      "text": "Return design/spec/plan drafts and dependencies, criteria, hold conditions and verification needs in the response. MUST NOT save documents, implement, run checks, prepare targets, request user approval or decide acceptance. Stop formal target-dependent drafting if actual prepared target evidence is missing; route decisions to Orchestrator.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -211,7 +211,7 @@
         "tdd-or-recorded-exception"
       ],
       "authority": "orchestrator",
-      "text": "Implement only assigned approved files and focused checks under the existing TDD contract. Report changed files, RED/GREEN or authorized exception evidence, results, limits and follow-up. Do not plan, independently QA/review your own work, accept the task or declare overall completion. Git changes remain forbidden even when implementation succeeds.",
+      "text": "Edit only assigned, approved files and run focused checks under the existing TDD contract. Report changed files, RED/GREEN or authorized exception evidence, results, limits and follow-up. Do not plan, independently QA/review your own work, accept the task or declare overall completion. Git changes remain forbidden even when implementation succeeds.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -253,7 +253,7 @@
         "relevant-qa-evidence"
       ],
       "authority": "orchestrator",
-      "text": "Independently inspect the assigned final changes and evidence and report actionable findings and limits. Remain read-only; do not execute QA tests, edit files, perform Git mutations or decide acceptance.",
+      "text": "Independently inspect the assigned final changes and evidence and report actionable findings and limits. Remain read-only. MUST NOT execute QA tests, edit files, perform Git mutations or decide acceptance.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -278,7 +278,7 @@
         "qa-rechecks"
       ],
       "authority": "orchestrator",
-      "text": "For significant/high-risk work without a plan: Coder \u2192 QA and required QA rechecks \u2192 Reviewer of the final full change \u2192 Orchestrator acceptance. Do not omit Reviewer merely because no plan exists. This creates no new plan obligation.",
+      "text": "For significant/high-risk work without a plan: Coder \u2192 QA and required QA rechecks \u2192 Reviewer of the final full change \u2192 Orchestrator acceptance. MUST NOT omit Reviewer merely because no plan exists. This creates no new plan obligation.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"
@@ -327,7 +327,7 @@
         "reviewer-findings"
       ],
       "authority": "orchestrator",
-      "text": "For final overall Reviewer findings on plan work, including behavior findings, use Coder \u2192 Reviewer without QA reassignment; repeat until resolved. This exception applies only to that final plan stage. Preserve required QA and QA failure rechecks before initial final review and outside this exception.",
+      "text": "For final overall Reviewer findings on plan work, including behavior findings, use Coder \u2192 Reviewer without QA reassignment; repeat until resolved. This exception applies only at the final plan stage. Preserve required QA and QA failure rechecks before initial final review and outside this exception.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"

package/lib/policy/role-policy.json

@@ -150,7 +150,7 @@
         "role-ownership"
       ],
       "authority": "orchestrator",
-      "text": "Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it.",
+      "text": "Assign design/spec/plan/brainstorming drafts ONLY to Planner and implementation/configuration/test edits to Coder. Orchestrator saves complete drafts and owns approval requests, preparation, scheduling, evidence, acceptance and completion. Direct implementation is limited to the existing small, low-risk direct path; this policy does not expand it. Use a fresh Coder per top-level task and a fresh QA per top-level task that needs QA; QA findings alone do not create a new task. While approved scope, workspace, ownership and relevant assignment context remain valid, default same-task QA findings to the current Coder and post-fix rechecks to the current QA. Replace or restart a role only when its context is invalid or unavailable, or the task boundary changes; an approved plan or acceptance-criteria amendment requires a fresh Coder even within the task. Before reusing Coder, refresh actual workspace, branch/HEAD and change state; QA reruns the reproduction path and invalidated related checks and reports actual actor, target state, outcomes and limitations. Preserve task-boundary acceptance and the final plan Reviewer correction exception.",
       "controls": {
         "codex": "prompt",
         "claude": "prompt"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yunhozz/arc",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org/"