Follow blocked work through to verified progress

VERSION

@@ -1 +1 @@
-0.1.16
+0.1.17

agent-ops/factory-agent-ops/SKILL.md

@@ -3,7 +3,7 @@ name: factory-agent-ops
 description: Act as a project's lead for ideas, research, accepted tasks or an approved backlog; coordinate native workers, independent review and authorized delivery.
 license: MIT
 metadata:
-  version: "0.1.16"
+  version: "0.1.17"
   updated: "2026-10-15"
 ---
 
@@ -101,6 +101,14 @@ the concrete candidate, evidence, recommendation and consequence. Batch closely
 related questions. A refusal, uncertain write or lost connection requires reading
 actual state before retry; never blind-replay a creation, merge or release.
 
+Blocked work stays your responsibility until it actually moves. Name the responder
+actually able to settle the block and the concrete next action; a handoff or a
+queued correction is not recovery. Verify the request's current disposition, that
+the correction reached the worker at a supported safe checkpoint, and that the
+worker then made useful progress. If it stays blocked, keep the gap visible with
+its responsible holder while continuing other accepted work; bring only a real
+owner decision, missing information or authority to the owner.
+
 Report the outcome plainly: decided, implemented, reviewed, merged, published,
 installed and still open are different states. Include useful links and material
 limits. Research-only work ends with its decision; a backlog mandate ends at its

agent-ops/factory-agent-ops/references/t3.md

@@ -1,6 +1,6 @@
 # Operating through T3 Code
 
-Revision: 0.1.16 · Updated: 2026-10-15
+Revision: 0.1.17 · Updated: 2026-10-15
 
 Use the tools actually exposed by the installed T3/provider versions. This guide
 was written for **0.0.46-nightly.20261009.2861** (V2), with upstream source checked
@@ -86,7 +86,22 @@ parent wait notifications are tracked upstream in
 than filing another issue. Only a holder already authorized for that decision
 may answer, after freshly checking the environment, project, thread, run, request,
 full input and live callback. Never late-approve an aborted or resolved request.
-Report one concrete handoff instead of polling or auto-confirming.
+Report one concrete handoff instead of polling or auto-confirming, then follow it
+through.
+
+Identify the actual authorized native responder and have the current request
+settled with its real meaning. Deliver an already-accepted correction at a verified
+supported checkpoint, then read the same bound worker's native activity for useful
+progress. A handoff, resolved card, successful send or queued message is not
+recovery. A blanket Decline can leave the run free to propose another call before
+the correction arrives; it is not a recovery technique. Cancel may interrupt the
+run and is not a neutral withdrawal: use it only when ending that blocked attempt
+is authorized and its checkpoint is preserved, never on healthy work. Native state
+can change during a handoff, so reconcile before each effect instead of declining
+or replaying in a loop. Refused actions stay refused; do not route them through
+another actor or tool. If the current tools provide no capable responder, wake or
+continuation, record that limitation and the next responsible holder in the
+existing issue rather than building a custom layer.
 
 A completed run need not end a worker's task: a harness background command,
 monitor or child notification can start another turn in the same thread. Before

docs/qualification.md

@@ -1,6 +1,6 @@
 # Qualification
 
-Revision: 0.1.16 · Updated: 2026-10-15
+Revision: 0.1.17 · Updated: 2026-10-15
 
 This record distinguishes source review, disposable exercises and observed native
 operation. A package release does not qualify another host, every future update
@@ -10,6 +10,7 @@ remain with the installation; public issues track the remaining acceptance work.
 | Boundary | Observed evidence | Limit / next check |
 | --- | --- | --- |
 | Package | Eight portable skills, metadata/link checks and staging tests | Mechanical checks do not establish agent decisions |
+| Blocked-request follow-through (0.1.17 candidate) | 2026-10-15, after the held OPD request recorded below ([Factory #32](https://github.com/arcitai/factory/issues/32); coordinator native UI actions plus Factory native readback). Declining the held compound shell call failed it without running it, but the run stayed active and proposed a second shell change before the prepared text-only correction arrived. The coordinator then cancelled that held call: neither call ran, the run was interrupted and ended with nothing pending, and its pre-recovery checkpoint was kept. The OPD lead sent its accepted native-file-only instruction to the same worker at that checkpoint; the next run completed native file changes with no shell or approval items and nothing pending while still active | Operator-assisted progress after an interrupted blocked attempt, not an automatic wake, autonomous responder, uninterrupted run, completed diagnostic checks, review or product delivery, or OS isolation. The two settled requests are not to be re-disposed. The source guidance followed this event and did not cause it. Source checks and independent review are recorded in the delivery PR |
 | Lead-prepared inputs (0.1.16 candidate) | 2026-10-15: separately, an OPD worker's archive preparation waited 15 m 12 s for approval and was resolved once in the native UI (operator report, not reproduced here). In this [Factory #32](https://github.com/arcitai/factory/issues/32) trial the lead prepared harmless inputs in the worker's task worktree; the same Claude worker used native Read and Edit for one result-file change and the AgentOps text change. The lead independently verified the inputs unchanged and the expected result hash; the run ended terminal with nothing pending, and its native timeline showed no approval request or worker shell command | One same-worker prepared-input text task, not a fresh-context comparison, measured wait reduction, general prompt-free operation, worker build/test permission, permission wake or decision authority, or isolation. A separate compound Python edit and Node/shell check request in that same OPD run remains held at this observation; its lead has a recovery handoff, not a passing recovery. Source checks and independent review are recorded in the delivery PR |
 | Foundation readiness handoff (0.1.12 candidate) | 2026-10-11: [Factory #27](https://github.com/arcitai/factory/issues/27) source change after an AIOS assessment accepted a stale mandatory authoring self-dependency, its disabled private reporting was found only by readback, its lead could not read its private record, and Project1's current README kept stale pre-delivery claims (coordinator observations, not reproduced here). Package, unit and staging checks only | Behavioral evidence and independent review are pending in the delivery PR. Native binding/authentication behavior stays with [Factory #3](https://github.com/arcitai/factory/issues/3); Markdown does not repair it |
 | English deliverables (0.1.15 candidate) | 2026-10-15: owner instruction that GitHub issues, PRs and Factory documentation default to English, and that Danish brainstorming does not request Danish deliverables. AgentOps and the Implement review handoff now state this default and its explicit-request exception. On the same owner instruction the lead published the runtime audit in English as [Factory #39](https://github.com/arcitai/factory/issues/39) and rewrote the [#32](https://github.com/arcitai/factory/issues/32) and [#34](https://github.com/arcitai/factory/issues/34) descriptions in English, each independently read back in English | Source change plus real reporting corrections made on owner instruction; not proof that a model applies the rule on its own. Source checks and independent review are recorded in the delivery PR |