okstra 0.201.2 → 0.202.0

package/runtime/python/okstra_ctl/verification_target.py

@@ -13,13 +13,14 @@ import hashlib
 import argparse
 import json
 import re
+import shlex
 import subprocess
 from pathlib import Path
 
 from .execution_mutation_audit import source_content_snapshot
 from .json_boundary import load_owned_object
 from .path_hints import hydrate_active_run_context
-from .qa_commands import verification_command_defects
+from .qa_commands import split_verification_command, verification_command_defects
 
 TARGET_FIELD_RES = {
     "scope": re.compile(r"\*\*Verification scope:\*\*\s*`([^`]*)`"),
@@ -95,6 +96,13 @@ def capture_verification_target(
     if not target or not Path(target).is_absolute():
         raise ValueError("active run context has no absolute verification worktree")
     worktree = Path(target).resolve()
+    declared_command = command
+    command, annotation = split_verification_command(command)
+    prefix = re.match(r"^\s*cd\s+('[^']*'|\"[^\"]*\"|[^\s;&|]+)\s*&&\s*", command)
+    if prefix is not None:
+        directory = shlex.split(prefix.group(1))[0]
+        if Path(directory).is_absolute() and Path(directory).resolve() == worktree:
+            command = command[prefix.end():]
     defects = verification_command_defects(command)
     if defects:
         raise ValueError("; ".join(defects))
@@ -105,11 +113,14 @@ def capture_verification_target(
         raise ValueError(f"verification target mismatch: expected HEAD {expected_head}, actual {head}, root {actual_root}")
     files = source_content_snapshot(worktree, frozenset({".okstra"}))
     digest = hashlib.sha256(json.dumps(files, sort_keys=True).encode()).hexdigest()
-    return {
+    result = {
         "schemaVersion": "1.0", "runManifest": str(manifest_path),
         "taskKey": manifest["taskKey"], "cwd": str(worktree),
         "head": head, "sourceDigest": digest, "command": command,
     }
+    if declared_command != command:
+        result.update(declaredCommand=declared_command, commandAnnotation=annotation)
+    return result
 
 
 def main(argv: list[str] | None = None) -> int:

package/runtime/skills/okstra-manager/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: okstra-manager
-description: Use when the user wants to manage okstra work across multiple project roots, register or discover projects under a manager, create or update a shared manager task, sync project child-task status into manager state, or launch a child task from manager context. Trigger words include "okstra manager", "okstra-manager", "multiple projects", "cross-project", "group projects together", "manager task".
+description: Use when the user wants to manage okstra work across multiple project roots, register or discover projects under a manager, create or update a shared manager task, sync project child-task status into manager state, split a Linear project or issue into per-project scoped briefs, or launch a child task from manager context. Trigger words include "okstra manager", "okstra-manager", "multiple projects", "cross-project", "group projects together", "manager task", "split this Linear project", "brief per project".
 ---
 
 # OKSTRA Manager
@@ -28,19 +28,68 @@ okstra manager task sync --manager-id <manager-id> --task-group <task-group> --t
 okstra manager task assign --manager-id <manager-id> --task-group <task-group> --task-id <task-id> --project-id <project-id> [--child-task-id <child-task-id>] [--role <role>] [--tag <tag>] [--assignment <text>]
 okstra manager task note --manager-id <manager-id> --task-group <task-group> --task-id <task-id> --scope <shared|project> [--project-id <project-id>] --body <text>
 okstra manager task run --manager-id <manager-id> --project-id <project-id> --task-group <task-group> --task-id <task-id> [--child-task-id <child-task-id>]
+okstra manager task split --manager-id <manager-id> --task-group <task-group> --task-id <task-id> --plan <split-plan.json> [--overwrite]
+okstra manager list managers
+okstra manager list projects --manager-id <manager-id>
+okstra manager list tasks --manager-id <manager-id>
+okstra manager view --manager-id <manager-id>
 ```
 
 - Public child task identity is `project-id:task-group:task-id`.
 - `okstra manager new task --task ...` should prefer the full child key form above. The CLI also accepts shorthand under the command's `--task-group`, but the full key is the public form to show users.
 - When a manager task id differs from the actual child task id for a specific project, pass `--child-task-id <child-task-id>` to `task assign` and `task run`.
 
+## Tracker Split
+
+Use this when one Linear project, or one parent issue, covers work in several registered projects and each project needs its own brief. A Linear project can point at several projects, and one issue can too; every (issue, project) pair gets its own brief and child task.
+
+1. Run `okstra manager list projects --manager-id <manager-id>`. These are the only valid targets. Register a missing repo with `okstra manager new project ...` first.
+2. Fetch from the Linear MCP: the project (`get_project`) and its issues (`list_issues` filtered by that project), then each issue with `get_issue`, including sub-issues and blocking or related links. If the Linear tools are missing, load them once with `ToolSearch`; if they are still missing, ask the user to paste the bodies. Never invent ticket content.
+3. For each issue, propose target projects from evidence: labels, team, repository names or paths in the body. Confirm with `AskUserQuestion` (multi-select, recommended projects first, reason in each description).
+4. For each (issue, project) pair, draft the scope: the part of the issue this project implements. Confirm it with `AskUserQuestion` offering one or two drafts plus a custom-input option. A pair without scope is rejected by the CLI.
+5. Author each pair's brief fields under the okstra-brief-gen brief contract: bodies verbatim, `EB-NNN` / `PB-NNN` / `EO-NNN` items as `<id> <observable condition> — verify: <how>`, anything without an observation method under `externalGates`, and `openQuestions` rows prefixed `general:`, `terminology:`, `intent-check:`, `conversion-block:` or `adr-candidate:`.
+6. Write the plan JSON below with the Write tool to a scratch path outside the project roots, then run `okstra manager task split ... --plan <path>`.
+   - `split plan rejected` or `rendered briefs failed validate-brief`: fix the named fields and run it again. Nothing was written.
+   - `briefs already exist with different content`: show the listed paths and ask before adding `--overwrite`, which replaces hand edits. Adding issues to an earlier split changes every brief's Related Task Graph, so existing briefs are listed too.
+7. Each `Brief N task key` is `<project-id>:<task-group>:<child-task-id>`. Start one with `okstra manager task run ... --project-id <project-id> --child-task-id <child-task-id>` and follow the Child Launch Rule. The packet already carries `--task-brief`, and `--task-type` until the child task exists.
+
+Plan JSON (`schemaVersion` 1). `source.kind` is `project` or `issue`; `recommendedPhase` is `requirements-discovery` (default), `error-analysis` or `improvement-discovery`; `relations[].relation` uses the brief Related Task Graph values; list fields may be omitted.
+
+```json
+{
+  "schemaVersion": 1,
+  "source": {"kind": "project", "ref": "<Linear URL>", "title": "<title>", "fetchedVia": "<tool>", "fetchedAt": "YYYY-MM-DD HH:MM", "body": "<verbatim>"},
+  "issues": [
+    {
+      "ticketId": "LIN-12", "title": "<title>", "url": "<Linear URL>", "fetchedVia": "<tool>", "fetchedAt": "YYYY-MM-DD HH:MM", "body": "<verbatim>",
+      "relations": [{"relation": "blocked-by", "to": "LIN-11", "source": "<where the link came from>", "impact": "<what the next phase must keep>"}],
+      "assignments": [
+        {
+          "projectId": "<registered project id>", "scope": ["<work in this project>"], "outOfScope": [],
+          "recommendedPhase": "requirements-discovery",
+          "context": "<text>", "problem": "<text>", "desiredOutcome": "<text>",
+          "expectedBehavior": [], "preservedBehavior": [], "expectedOutcome": [],
+          "externalGates": [], "constraints": [], "openQuestions": []
+        }
+      ]
+    }
+  ]
+}
+```
+
+The CLI writes each brief to `<projectRoot>/.okstra/briefs/<task-group>/<ticketId>-<file-title>.md` with a `## Project Scope` section: this project's scope, `outOfScope`, and the scope of every other project the same issue went to. It validates every brief with the brief validator before writing any file, registers the child tasks, and keeps the plan at `split-plan.json` in the manager task directory.
+
+## Overview Page
+
+When the user wants to see a manager at a glance, run `okstra manager task sync ...` for each task listed by `okstra manager list tasks ...` whose snapshot must be current, then run `okstra manager view --manager-id <manager-id>` and give the user the returned `View URL`. The page reads manager files only, so each task shows the state of its last sync and prints its own sync command.
+
 ## Child Launch Rule
 
 For launching child work:
 
 1. Run `okstra manager task sync ...` if the manager snapshot must be refreshed first.
 2. Run `okstra manager task run ...`.
-3. Read the returned fixed fields `Backend`, `Worker dispatch backend`, `Project root`, `Context path`, and every numbered `Run arg N`.
-4. Use that launch packet for the host-native child lead handoff.
+3. Read the returned fixed fields `Backend`, `Worker dispatch backend`, `Project root`, `Context path`, `Run command`, every numbered `Run arg N`, and `Shell command`.
+4. Give the user the `Shell command` line verbatim and tell them to run it in a new terminal. It starts the installed launcher in the child project: the launcher fills the task type and brief from the child task manifest or asks for them, prepares the run with the manager context directive, and starts the child lead as a separate host process (`Backend` `spawn-process`).
 
-The launch packet remains the source of truth. Do not rebuild child args by hand.
+Do not run the `Shell command` through this session's Bash tool: it opens an interactive host session. Do not rebuild it from `Run arg N` or swap in `okstra run`, which drops the task inputs and the directive for a lead host.

package/runtime/skills/okstra-run/SKILL.md

@@ -244,6 +244,8 @@ Output: `{ok: true, outcome: {renderArgv: ["--lead-runtime", "...", ...], render
 
 `userAuthorization`, when present, preserves the confirmation prompt actually emitted by this wizard and the relayed `proceed` response. Its `--user-authorization-json` token carries that record into the run manifest; preserve it unchanged. Do not synthesize a receipt for older confirmed states. Include the translator's disclosed provider/model and report material when citing this record in host execution requests, including `report-finalize`. The record documents task scope; it does not grant host execution privileges.
 
+Before retrying a worker in an existing run, inspect its last invocation attempt: await running work; append an attempt only after `failed-no-mutation` within the retry budget. Preserve every other terminal attempt. `okstra team dispatch` routes the legacy declaration-only implementer failure to a separate same-model evidence-recovery invocation; collect its result before independent verification. Other terminal failures need `okstra agent-prompt materialize` with a new `--invocation-id`, distinct `--prompt`/`--result` paths, and unchanged assignment/model for a bounded correction. Do not restart completed implementation or request renewed approval for unchanged scope. Enforcement: `dispatch_core._next_attempt` and `execution_manifest._validate_next_attempt`.
+
 Run every `outcome.persistActions[]` entry BEFORE `render-bundle`. The only supported action is:
 
 ```json
@@ -489,6 +491,6 @@ Follow the rendered launch prompt's "Progress, remaining work, and recommendatio
 ## Output Rules
 
 - Echo each captured answer (`result.echo`) on one short line so the user sees what was registered.
-- Name every file you show the user as a markdown link — `[<what it is>](<path>)`, with the path inside the parentheses. That is the only form the host renders as clickable; a path in backticks is text the user has to copy out. The `report-finalize` result's `reportPaths.markdown` carries the run's report, report record, and team state already in that form. Commands stay in backticks — a link is for a file, not for something to run.
+- Name every file you show the user as a markdown link — `[<short label>](<absolute path>)`, with the absolute path inside the parentheses and a short label naming what the file is. A relative destination does not open from an external program. That is the only form the host renders as clickable; a path in backticks is text the user has to copy out. The `report-finalize` result's `reportPaths.markdown` carries the run's report, report record, and team state already in that form. Commands stay in backticks — a link is for a file, not for something to run.
 - Never invent identity; if a `text` prompt returns an empty answer where the wizard rejects it, the user must retry.
 - After Step 6, begin the lead workflow without re-summarizing the skill itself. For a single run, finish after Step 6 and any same-run recovery, unless the user has already authorized continuing the task through further phases. In an unattended chain where `orchestration.chainStages` has 2+ elements, repeat Step 6 per stage until Step 7's queue is empty (or it stops at a "not ready" / exception gate), then finish. When `report-finalize` returns `recovery.mode: same-run`, continue the authorized corrections in this run and execute `recovery.resumeCommand` before closeout; preserve approvals and model choices without reopening the wizard. The command and owner issues are supplied by `report_finalize._finalize_recovery`. When the lead (or this skill, after the lead returns) reports a successfully finalized run over, close with the user's next action — one command they can run now. A prohibition is not a next action. Take the pointer from the `report-finalize` result's top-level `nextRecommendedPhase` (`phase`, `status`, `rationale`; also on stderr as `next phase status:` / `next phase:` / `next phase rationale:`) — do not re-derive it from the report, and treat a `nextRecommendedPhaseError` as "pointer unreadable", said in one line before the `validate-run` branch. The same result also carries `nextCommand` — `{command, note}`, the table below already applied to this run. When `command` is non-empty it is the close; when it is empty the `note` says what to do with the `rationale` instead. After `implementation-planning`, open `blocks: approval` rows → `/okstra-user-response`. A recorded `accept-risk` / `select` / `answer` is not an open blocker. No open approval blocker → `/okstra-run` → `implementation` or `--approve` (do not start another planning run; do not say `/okstra-inspect`). For every other task type, quote the pointer's `rationale` in every branch — that sentence is the report's own reason and it is what the user asked to be analysed. Pointer `status: ready` → `/okstra-run` for that phase; `status: terminal` → say the task is finished, name any follow-up tasks this run registered, and do not say `/okstra-inspect`; `status: blocked` → issue the command the `rationale` calls for (`/okstra-user-response` for the `C-NNN` ids, `/okstra-run` for the phase it names); `validate-run` failed with `recovery.mode: phase-reentry` → name the cause and use `nextCommand` for the recorded earlier phase; otherwise `/okstra-inspect status`.

package/runtime/skills/okstra-setup/SKILL.md

@@ -140,6 +140,15 @@ Then create the file — paste the literal `projectRoot` from Step 2 and the lit
 okstra setup --yes --project-root /abs/path/to/projectRoot --project-id my-project-id
 ```
 
+`okstra setup` also refreshes the okstra-managed citation-guidance block in
+`<PROJECT_ROOT>/CLAUDE.md` and `AGENTS.md` when those files already exist (it never
+creates them). The block tells agents not to carry okstra-internal references — report
+section numbers, `C-NNN` clarification ids, run/stage ids, `.okstra/...` paths — into
+writing that is not an okstra report, where the reader cannot resolve them. The command
+reports the files it touched in its JSON `citationGuidance` array; a failure there is a
+`warning:` line, not a non-zero exit. Tell the user which guidance files were updated so
+they can review the appended block.
+
 ## Step 3.5 (optional): project customisation
 
 The built-in defaults work for most projects — skip straight to Step 4

package/runtime/templates/manager/view.template.html

@@ -0,0 +1,108 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>{{TITLE}}</title>
+<style>
+:root {
+  --bg: #f7f7f5;
+  --panel: #ffffff;
+  --text: #1f2328;
+  --muted: #5f6670;
+  --line: #d9dbde;
+  --planned: #6e7781;
+  --missing: #9a6700;
+  --running: #0969da;
+  --done: #1a7f37;
+  --blocked: #cf222e;
+}
+@media (prefers-color-scheme: dark) {
+  :root {
+    --bg: #111418;
+    --panel: #1a1f25;
+    --text: #e6e8eb;
+    --muted: #9aa3ad;
+    --line: #2f363e;
+    --planned: #8b949e;
+    --missing: #d29922;
+    --running: #58a6ff;
+    --done: #3fb950;
+    --blocked: #f85149;
+  }
+}
+* { box-sizing: border-box; }
+body {
+  margin: 0;
+  background: var(--bg);
+  color: var(--text);
+  font: 14px/1.5 -apple-system, BlinkMacSystemFont, "Segoe UI", "Apple SD Gothic Neo", "Noto Sans KR", sans-serif;
+}
+main { max-width: 1200px; margin: 0 auto; padding: 24px 16px 48px; }
+header h1 { margin: 0 0 4px; font-size: 22px; }
+.meta { color: var(--muted); font-size: 13px; }
+section { margin-top: 28px; }
+h2 { font-size: 17px; margin: 0 0 10px; }
+h3 { font-size: 15px; margin: 0; }
+.panel {
+  background: var(--panel);
+  border: 1px solid var(--line);
+  border-radius: 8px;
+  padding: 16px;
+  margin-bottom: 16px;
+}
+.tiles { display: grid; grid-template-columns: repeat(auto-fit, minmax(120px, 1fr)); gap: 10px; }
+.tile { background: var(--panel); border: 1px solid var(--line); border-radius: 8px; padding: 10px 12px; }
+.tile .count { font-size: 24px; font-weight: 600; }
+.tile .label { color: var(--muted); font-size: 12px; text-transform: uppercase; letter-spacing: 0.04em; }
+.scroll { overflow-x: auto; }
+table { width: 100%; border-collapse: collapse; }
+th, td { text-align: left; padding: 7px 10px; border-bottom: 1px solid var(--line); vertical-align: top; }
+th { color: var(--muted); font-weight: 600; font-size: 12px; white-space: nowrap; }
+.wrap { display: inline-block; min-width: 220px; }
+code.id { white-space: nowrap; word-break: normal; }
+code { font: 12px/1.4 ui-monospace, SFMono-Regular, Menlo, monospace; word-break: break-all; }
+.chip {
+  display: inline-block;
+  padding: 1px 8px;
+  border-radius: 999px;
+  border: 1px solid currentColor;
+  font-size: 12px;
+  white-space: nowrap;
+}
+.chip.planned { color: var(--planned); }
+.chip.missing { color: var(--missing); }
+.chip.running { color: var(--running); }
+.chip.done { color: var(--done); }
+.chip.blocked { color: var(--blocked); }
+.task-head { display: flex; flex-wrap: wrap; gap: 8px 16px; align-items: baseline; margin-bottom: 8px; }
+.counts { display: flex; flex-wrap: wrap; gap: 6px; }
+.hint { color: var(--muted); font-size: 12px; margin: 6px 0 12px; }
+details { margin-top: 10px; }
+summary { cursor: pointer; color: var(--muted); }
+ul.plain { margin: 6px 0 0; padding-left: 18px; }
+.empty { color: var(--muted); }
+a { color: var(--running); }
+</style>
+</head>
+<body>
+<main>
+<header>
+<h1>{{TITLE}}</h1>
+<div class="meta">{{META}}</div>
+</header>
+<section>
+<h2>Summary</h2>
+{{SUMMARY}}
+</section>
+<section>
+<h2>Projects</h2>
+{{PROJECTS}}
+</section>
+<section>
+<h2>Manager tasks</h2>
+{{TASKS}}
+</section>
+</main>
+</body>
+</html>

package/runtime/templates/reports/html/i18n/en.json

@@ -371,6 +371,8 @@
     "final-verification": {
       "verification-verdict": "Verification verdict",
       "result-per-requirement": "Result per requirement",
+      "requirement": "Requirement",
+      "evidence": "Evidence",
       "what-the-change-added": "What the change added",
       "traced-to": "Serves",
       "callers": "Callers",

package/runtime/templates/reports/html/i18n/ko.json

@@ -371,6 +371,8 @@
     "final-verification": {
       "verification-verdict": "검증 판정",
       "result-per-requirement": "요구사항별 결과",
+      "requirement": "요구사항",
+      "evidence": "근거",
       "what-the-change-added": "이 변경이 추가한 것",
       "traced-to": "봉사하는 요구사항",
       "callers": "호출자",

package/runtime/templates/reports/html/tasks/final-verification.template.html

@@ -1,6 +1,5 @@
 {% extends "html/base.template.html" %}
 {% from "html/macros/layout.html" import narrative as render_narrative, row_key %}
-{% from "html/macros/visualizations.html" import figure %}
 
 {% block human_content %}
 <section data-report-section="verification-verdict">
@@ -22,7 +21,8 @@
 <section data-report-section="requirement-results" data-report-field="finalVerification.validationEvidence">
   <h2>{{ t('tasks.final-verification.result-per-requirement') }}</h2>
   {{ render_narrative(narrative.coverageExplanation, "finalVerification.userNarrative.coverageExplanation") }}
-  {{ figure(coverageFigure, anchor_nodes=true) }}
+  <div class="table-scroll"><table><thead><tr><th>{{ t('macros.layout.id') }}</th><th>{{ t('tasks.final-verification.requirement') }}</th><th>{{ t('macros.layout.status') }}</th><th>{{ t('tasks.final-verification.evidence') }}</th></tr></thead>
+  <tbody>{% for row in final.validationEvidence %}<tr id="id-{{ row.id }}"><td>{{ row.id | inline_code }}</td><td>{{ row.requirement | inline_code }}</td><td><span class="status status-{{ row.status }}">{{ row.status }}</span></td><td>{{ row.artifact | inline_code }}</td></tr>{% endfor %}</tbody></table></div>
 </section>
 
 <section data-report-section="added-surface" data-report-field="finalVerification.addedSurfaceAudit">

package/runtime/validators/validate-brief.py

@@ -104,6 +104,10 @@ AUGMENTATION_LABELS = {
 
 REPORTER_CONFIRMATION_VALUES = {"complete", "partial", "pending", "skipped"}
 
+# okstra-manager `task split` renders the same brief contract for each project
+# it splits a tracker issue into.
+GENERATORS = {"okstra-brief-gen", "okstra-manager"}
+
 SCOPE_VALUES = {"reporter-input", "codebase"}
 
 TASK_GRAPH_HEADER = ["From", "Relation", "To", "Direction", "Source", "Impact"]
@@ -693,9 +697,10 @@ def validate_brief(path: Path, briefs_root: Path) -> list[str]:
     if fm.get("type") != "brief":
         errors.append(f"frontmatter type must be 'brief', got {fm.get('type')!r}")
 
-    if fm.get("generator") != "okstra-brief-gen":
+    if fm.get("generator") not in GENERATORS:
         errors.append(
-            f"frontmatter generator must be 'okstra-brief-gen', got {fm.get('generator')!r}"
+            f"frontmatter generator must be one of {sorted(GENERATORS)}, "
+            f"got {fm.get('generator')!r}"
         )
 
     if fm.get("reporter-confirmations") not in REPORTER_CONFIRMATION_VALUES:

package/runtime/validators/validate-run.py

@@ -5443,19 +5443,8 @@ def _validate_plan_body_state_rounds(
         )
 
 
-def _validate_out_of_plan_edits_are_real(data: dict, failures: list[str]) -> None:
-    """선언한 out-of-plan 편집은 실제로 바뀐 파일이어야 한다.
-
-    입력 템플릿의 §"Forbidden In This Run" 은 계획 목록 밖에서 건드린 파일을 전부
-    `Out-of-plan edits` 에 적으라고 요구한다. 그 목록이 실제 diff 와 무관하면 기록은
-    검토자에게 성실해 보이는 문자열일 뿐이다 — 실제로 바꾼 적 없는 파일이 적혀
-    있으면 나머지 행도 믿을 근거가 없다.
-
-    계획 목록 자체와의 대조(계획 밖 파일이 여기 빠졌는지)는 하지 않는다. 그러려면
-    `approvedPlanReference.planFile` 이 가리키는 다른 리포트를 열어 stage 범위까지
-    풀어야 하고, 그 경로 해소를 검증할 실물 run 이 저장소에 없다. 여기서는 리포트
-    안에서 닫히는 방향만 본다.
-    """
+def _warn_out_of_plan_edits_not_in_diff(data: dict, warnings: list[str]) -> None:
+    """소스 차이 목록은 별도 QA 산출물의 변경 여부를 증명하지 못한다."""
     implementation = data.get("implementation")
     if not isinstance(implementation, dict):
         return
@@ -5470,7 +5459,7 @@ def _validate_out_of_plan_edits_are_real(data: dict, failures: list[str]) -> Non
             continue
         target = row.get("file")
         if isinstance(target, str) and target and target not in changed:
-            failures.append(
+            warnings.append(
                 f"out-of-plan-edit: {row.get('id') or 'OOP-???'} 가 `{target}` 을 "
                 "계획 밖 편집으로 신고했지만 diffSummary 에 그 파일이 없다"
             )
@@ -9755,7 +9744,10 @@ def main() -> int:
         _validate_verifier_command_log_is_read_only(validation_data, failures)
         _validate_verifier_reran_independently(validation_data, failures)
         _validate_verifier_discrepancy_is_not_passed(validation_data, failures)
-        _validate_out_of_plan_edits_are_real(validation_data, failures)
+        declaration_warnings: list[str] = []
+        _warn_out_of_plan_edits_not_in_diff(validation_data, declaration_warnings)
+        for warning in declaration_warnings:
+            print(f"validate-run: warning: {warning}", file=sys.stderr)
     if task_type == "implementation-planning":
         _validate_plan_body_state_file(
             validation_data,