okstra 0.209.2 → 0.209.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "okstra",
-  "version": "0.209.2",
+  "version": "0.209.3",
   "description": "Host-aware multi-provider cross-verification orchestrator runtime and agent skills.",
   "license": "MIT",
   "author": "devonshin",

package/runtime/BUILD.json

@@ -1,5 +1,5 @@
 {
-  "package": "0.209.2",
-  "builtAt": "2026-10-05T05:48:33.643Z",
+  "package": "0.209.3",
+  "builtAt": "2026-10-05T06:23:58.308Z",
   "repoRoot": "/home/runner/work/okstra/okstra"
 }

package/runtime/prompts/lead/adapters/cmux.md

@@ -33,7 +33,7 @@ Keep the selected host relay's dispatch permission guidance when calling `okstra
 | `await_workers` | Run `okstra team await --project-root <root> --run-manifest <path>` through the host's asynchronous shell facility. |
 | `redispatch_worker` | Create the core-specified fresh jobs file and dispatch it with a new `dispatchKind`; never reuse a live worker conversation. |
 | `shutdown_workers` | Run `okstra team teardown --project-root <root> --run-manifest <path>` only after the user-approved cleanup gate. |
-| `record_lead_event` | Append progress and activity records to the manifest-provided `leadEventsPath`. Use `okstra lead-progress append --project-root <dir> --run-manifest <path> --phase <phase-id>` for a checkpoint the command performing that step does not record itself (the lead contract "Progress reporting" lists the ones `team dispatch`, `team await`, `team reclaim`, `worker-dispatch` and `report-finalize` record; emit the `PROGRESS:` lines they print instead) and `okstra agent-activity append --project-root <dir> --run-manifest <path> --kind <kind> ...` for an activity record; both resolve the ledger path from the run manifest. Emit the matching `PROGRESS:` line — the command prints it as `progressLine` — and, when an activity record is required, the immediately following `ACTIVITY:` line from the same structured fields. |
+| `record_lead_event` | Append progress and activity records to the manifest-provided `leadEventsPath`. Use `okstra lead-progress append --project-root <dir> --run-manifest <path> --phase <phase-id>` for a checkpoint the command performing that step does not record itself (the lead contract "Progress reporting" lists the ones `team dispatch`, `team await`, `team reclaim`, `worker-dispatch` and `report-finalize` record; emit the `PROGRESS:` lines they print instead) and `okstra agent-activity append --project-root <dir> --run-manifest <path> --kind <kind> ...` for an activity record — never for the `worker-dispatched` / `worker-completed` rows `team dispatch` and `team await` append themselves; both resolve the ledger path from the run manifest. Emit the matching `PROGRESS:` line — the command prints it as `progressLine` — and, when an activity record is required, the immediately following `ACTIVITY:` line from the same structured fields. |
 | `collect_usage` | Collect artifact/CLI-log-backed usage through the existing Okstra token-usage path; never substitute another runtime's session log. |
 
 An `implementation` run calls `dispatch_worker` twice: once for the Executor, then — after `await_workers` settles it — once for the verifiers. That second call's `--workers` list must omit the Executor's worker ID: it is materialized as the Executor on every dispatch, so a batch still carrying it is refused again. A verifier started beside the Executor observes base HEAD instead of the stage diff, so a single batch holding both is refused by `scripts/okstra_ctl/dispatch_core.py` `_validate_implementation_phase_order`, `--dry-run` included.

package/runtime/prompts/lead/okstra-lead-contract.md

@@ -66,7 +66,7 @@ Every `okstra` command the lead documents cite, grouped by phase, each spelled w
 | Command | Use when | Procedure |
 |---|---|---|
 | `okstra lead-progress append --project-root <dir> --run-manifest <path> --phase <phase-id>` | Every `PROGRESS` checkpoint the command performing that step does not record itself; print the `progressLine` it returns. `--phase` accepts only the listed phase ids; use `--worker`, `--field NAME=VALUE`, and `--detail <text>` for the rest | this contract "Progress reporting" |
-| `okstra agent-activity append --project-root <dir> --run-manifest <path> --kind <kind> --agent <agent> --outcome <outcome> --summary <text>` | Before each activity boundary when the run manifest declares `activityContractVersion: 1` | launch prompt "Progress reporting" |
+| `okstra agent-activity append --project-root <dir> --run-manifest <path> --kind <kind> --agent <agent> --outcome <outcome> --summary <text>` | Before each activity boundary when the run manifest declares `activityContractVersion: 1`, except a `worker-dispatched` / `worker-completed` row the dispatching command already appended (see "Progress reporting") | launch prompt "Progress reporting" |
 | `okstra error-log append-observed --out <errors-path> --task-key <key> --phase <phase> --agent <provider-worker> --agent-role <role> --model <model> --error-type <type> --command-kind <kind> --command <command> --message <text>` | Record an observed failure. `--agent` takes the provider worker id (`codex-worker`); an execution label goes in `--execution-label` | this contract "Errors log path wiring"; `team-contract` "Worker error-log command" |
 | `okstra approval-decision open --ledger <path> --task-key <key> --task-type <type> --run-seq <seq> --clarification-id <C-NNN> --ticket-id <id> --statement <text> --expected-form <form> --classification <class> --origin <origin> --user-confirmation <text> --unblock-condition <text> --recommended-disposition <disposition> [--supersedes <C-NNN>]` | Open an approval blocker after the user confirmed it | this contract "User confirmation before an approval blocker" |
 | `okstra approval-decision carry --ledger <path> --clarification-id <C-NNN> --from-responses <path>` | Carry a decision answered in an earlier run | `report-writer` "Role-owned inputs" |

package/runtime/python/okstra_ctl/agent/activity.py

@@ -166,6 +166,9 @@ def _activity_row(event: LeadEvent) -> dict[str, Any]:
     from okstra_ctl.execution_identity import stored_identity
 
     row = {key: details[key] for key in ACTIVITY_FIELDS}
+    if row["resultPath"] is None:
+        # 0.209.1 의 team dispatch/await 가 null 로 기록한 행. 원장은 고치지 않고 읽을 때 맞춘다.
+        row["resultPath"] = ""
     if "clarificationRefs" in details:
         refs = details["clarificationRefs"]
         if not isinstance(refs, list) or any(
@@ -201,6 +204,8 @@ def record_activity(
         raise ActivityProjectionError(
             "run manifest does not declare activityContractVersion 1"
         )
+    if not isinstance(details.get("resultPath"), str):
+        raise ActivityProjectionError("activity resultPath must be a string")
     _validate_activity_ownership(project_root, manifest, details)
     event = LeadEvent(
         event_type="activity",

package/runtime/python/okstra_ctl/dispatch_checkpoints.py

@@ -74,7 +74,8 @@ def record_dispatch_checkpoints(
                     project_root, run_manifest, source=source,
                     kind="worker-dispatched", agent=job.worker_id,
                     summary=f"Dispatched {job.worker_id} as an initial worker",
-                    result_path=None, outcome="pending",
+                    result_path=_project_relative(project_root, str(job.worker_result_path)),
+                    outcome="pending",
                 ))
     dispatches_writer = any(job.worker_id == REPORT_WRITER_WORKER_ID for job in jobs)
     writer_dispatched_before = bool(
@@ -165,9 +166,10 @@ def _declares_activity_contract(
     return manifest.get("activityContractVersion") == 1
 
 
-def _project_relative(project_root: Path, value: Any) -> str | None:
+def _project_relative(project_root: Path, value: Any) -> str:
+    # 보고서 스키마의 resultPath 는 문자열이다. 리드 CLI 도 경로가 없으면 "" 를 쓴다.
     if not isinstance(value, str) or not value:
-        return None
+        return ""
     path = Path(value)
     root = project_root.resolve()
     return str(path.relative_to(root)) if path.is_relative_to(root) else value
@@ -181,7 +183,7 @@ def _record_worker_activity(
     kind: str,
     agent: str,
     summary: str,
-    result_path: str | None,
+    result_path: str,
     outcome: str,
 ) -> str | None:
     """실패 처리는 `record_checkpoint` 와 같다: stderr 에만 남기고, 누락은 검증기가 보고한다."""