okstra 0.60.3 → 0.61.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "okstra",
3
- "version": "0.60.3",
3
+ "version": "0.61.0",
4
4
  "description": "Multi-agent cross-verification orchestrator runtime + Claude Code skills.",
5
5
  "license": "MIT",
6
6
  "author": "devonshin",
@@ -1,5 +1,5 @@
1
1
  {
2
- "package": "0.60.3",
3
- "builtAt": "2026-06-09T06:44:22.023Z",
2
+ "package": "0.61.0",
3
+ "builtAt": "2026-06-09T07:19:02.278Z",
4
4
  "repoRoot": "/home/runner/work/okstra/okstra"
5
5
  }
@@ -357,10 +357,16 @@ run_resume_clarification() {
357
357
  local report_path="${lookup_result%$'\t'*}"
358
358
  local resolved_type="${lookup_result##*$'\t'}"
359
359
 
360
+ # implementation-planning 도 §1 Clarification Items(plan-body 결정: 예 C-205
361
+ # tx-배관 step 누락)를 가지므로, 사용자가 결정란을 채운 뒤 같은 phase 를
362
+ # clarification-response 자동공급으로 재실행해 plan 을 재생성·gate 재판정할 수
363
+ # 있다. 자동검색(task_type_filter 없음)은 파일명 사전순 max 라 implementation-
364
+ # planning 이 requirements-discovery 에 밀리므로, 이 경로는 --task-type
365
+ # implementation-planning 을 명시했을 때만 해소된다.
360
366
  case "$resolved_type" in
361
- requirements-discovery|error-analysis) ;;
367
+ requirements-discovery|error-analysis|implementation-planning) ;;
362
368
  *)
363
- printf '%s (resolved task-type: %s)\n' '--resume-clarification only applies to requirements-discovery or error-analysis runs' "$resolved_type" >&2
369
+ printf '%s (resolved task-type: %s)\n' '--resume-clarification only applies to requirements-discovery, error-analysis, or implementation-planning runs' "$resolved_type" >&2
364
370
  exit 1
365
371
  ;;
366
372
  esac
@@ -35,8 +35,9 @@ implementation-option: {{ frontmatter.implementationOption | yaml_scalar }}
35
35
  {% if clarificationCarryIn and clarificationCarryIn.sourceFile %}
36
36
  ## 0. Clarification Response Carried In From Previous Run
37
37
 
38
+ {{ t("sectionIntro.clarificationCarryIn") }}
39
+
38
40
  - Source file: `{{ clarificationCarryIn.sourceFile }}`
39
- - {{ t("sectionIntro.clarificationCarryIn") }}
40
41
 
41
42
  {% endif %}
42
43
  ## Summary of the Problem or Verification Target
@@ -78,12 +79,6 @@ implementation-option: {{ frontmatter.implementationOption | yaml_scalar }}
78
79
  {% for row in clarificationItems -%}
79
80
  | **{{ row.id }}**<br>Ticket: `{{ row.ticketId }}`<br>Kind: `{{ row.kind }}`<br>Blocks: `{{ row.blocks }}`<br>Status: {{ row.status }} | {{ row.statement }} | {{ row.expectedForm }} | {{ row.userInput or '' }} |
80
81
  {% endfor %}
81
-
82
- {{ t("clarification.columnGuide") }}
83
-
84
- - **`Kind`** ∈ `{material, decision, data-point}`.
85
- - **`Blocks`** ∈ `{approval, next-phase, none}`.
86
- - **`Status`** ∈ `{open, answered, resolved, obsolete}`.
87
82
  {%- endif %}
88
83
 
89
84
  ## 2. Evidence and Detailed Analysis
@@ -126,8 +126,7 @@
126
126
  },
127
127
  "clarification": {
128
128
  "fillAndRerun": "Fill in your answers then re-run the same phase:",
129
- "separateTerminalLabel": "Separate terminal",
130
- "columnGuide": "Record cell field values:"
129
+ "separateTerminalLabel": "Separate terminal"
131
130
  },
132
131
  "followUpTasks": {
133
132
  "headingAside": "Follow-up Tasks"
@@ -126,8 +126,7 @@
126
126
  },
127
127
  "clarification": {
128
128
  "fillAndRerun": "답을 채우신 뒤 같은 phase 를 다시 실행:",
129
- "separateTerminalLabel": "별도 터미널",
130
- "columnGuide": "항목 칸 안의 값 설명:"
129
+ "separateTerminalLabel": "별도 터미널"
131
130
  },
132
131
  "followUpTasks": {
133
132
  "headingAside": "후속 작업"