<!-- task=jenkins_compatibility_boundary/01_core_adapter plan=1 tag=REVIEW_REFACTOR -->

# Code Review Reference - REVIEW_REFACTOR

> **[IMPLEMENTING AGENT — READ FIRST] Filling in this file is the mandatory final step of implementation.**
> The task is NOT complete until every implementation-owned section below is filled in.
> Complete the `구현 체크리스트`; the final checklist item is mandatory before saving.
> Fill implementation-owned sections, then stop with active files in place and report ready for review.
> Finalization (`코드리뷰 결과`, log rename, `complete.log`, archive moves, `코드리뷰 전용 체크리스트`) is review-agent-only, even after compaction/resume.
> Follow the ownership table at the bottom of this file for which sections you own.

## 개요

date=2026-05-23
task=jenkins_compatibility_boundary/01_core_adapter, plan=1, tag=REVIEW_REFACTOR

## 이 파일을 읽는 리뷰 에이전트에게

> **[REVIEW AGENT ONLY]** 아래 종결 절차는 코드리뷰 에이전트 전용이다. 구현 에이전트는 이 섹션을 실행하지 않는다.

각 항목의 구현을 실제 소스 파일과 대조하고, `검증 결과` 섹션의 출력이 코드와 일치하는지 확인하세요.
리뷰 완료는 아래 순서까지 끝난 상태를 의미합니다.

1. 판정을 append한다.
2. `CODE_REVIEW-cloud-G07.md` -> `code_review_cloud_G07_N.log`, `PLAN-cloud-G07.md` -> `plan_cloud_G07_M.log`로 아카이브한다.
3. PASS이면 `agent-ops/skills/common/code-review/templates/complete-log-template.md` 기준으로 `complete.log`를 작성하고 active `.md` 파일을 남기지 않는다.
4. PASS이면 active task 디렉터리 `agent-task/jenkins_compatibility_boundary/01_core_adapter/`를 `agent-task/archive/YYYY/MM/jenkins_compatibility_boundary/01_core_adapter/`로 이동한다.
5. 적용 가능한 `코드리뷰 전용 체크리스트` 항목을 최종 `.log` 위치에서 체크한 뒤 보고한다.

---

## 구현 항목별 완료 여부

| 항목 | 완료 여부 |
|------|---------|
| [REVIEW_REFACTOR-1] 검증 결과 원문 기록 복구 | [x] |

## 구현 체크리스트

- [x] REVIEW_REFACTOR-1 `검증 결과`의 누락/생략된 stdout/stderr 원문 기록을 복구한다.
- [x] 모든 검증 명령을 다시 실행하고 실제 stdout/stderr를 `CODE_REVIEW-cloud-G07.md`에 기록한다.
- [x] CODE_REVIEW-*-G??.md의 구현 에이전트 소유 섹션을 실제 구현 내용과 검증 출력으로 채운다. 이 항목이 완료되기 전에는 구현이 완료된 것이 아니다.

## 코드리뷰 전용 체크리스트

> **[REVIEW AGENT ONLY]** 이 체크리스트는 코드리뷰 에이전트만 사용한다.
> 구현 에이전트는 이 섹션을 수정하거나 체크하지 않는다.

- [x] `코드리뷰 결과`에 `PASS`, `WARN`, `FAIL` 중 하나의 판정을 append한다.
- [x] 판정과 `차원별 평가`, Required/Suggested/Nit 분류가 서로 일치한다.
- [x] active `CODE_REVIEW-*-G??.md`를 `code_review_{review_lane}_GNN_N.log`로 아카이브한다.
- [x] active `PLAN-*-G??.md`를 `plan_{build_lane}_GNN_M.log`로 아카이브한다.
- [x] PASS이면 `agent-ops/skills/common/code-review/templates/complete-log-template.md` 기준으로 `complete.log`를 작성하고 active `.md` 파일을 남기지 않는다.
- [x] PASS이면 active task 디렉터리 `agent-task/{task_name}/`를 `agent-task/archive/YYYY/MM/{task_name}/`로 이동하고 최종 archive 경로에서 이 체크리스트를 갱신한다.
- [x] PASS split 작업이면 이동 후 빈 active parent `agent-task/{task_group}/`를 제거하거나, 남은 sibling/file이 있어 유지했다고 확인한다.
- [ ] WARN/FAIL이면 다음 active `PLAN-{build_lane}-GNN.md`와 `CODE_REVIEW-{review_lane}-GNN.md`를 작성하고 `complete.log`를 작성하지 않는다.

## 계획 대비 변경 사항

- `dart:async` import를 `data_composer.dart`에서 제거했다. `Completer`가 `_getBuildDataWindows()`에서 제거되면서 불필요해졌다. `Future`는 `dart:core`에서 제공된다.
- `_getBuildDataWindows()`에서 `Completer` 패턴을 제거하고 직접 `return content;`로 단순화했다. 기존 로직과 동일하며 `dart analyze`에서 이슈 없음.

## 주요 설계 결정

- `JenkinsEnvironmentCollector`는 새 파일이 아닌 `data_composer.dart` 안의 public 타입으로 추가했다. PLAN 지시에 따른다.
- `JenkinsEnvironmentSnapshot.rawVariablesJson`은 Unix에서 `result.stdout.toString()`을 그대로 사용한다. 기존 코드에서 `jsonStr`이 빈 문자열로 로그됐던 버그를 수정한다.
- `FileData.jenkinsMap`은 `LocalData.commonMap()`의 alias로 남겼다. 기존 참조(`TestData.jenkinsMap`, `test/**`)가 깨지지 않는다.
- `Application.defaultWorkspace`는 인스턴스 getter로 정의해 `commonData`에 접근한다. Jenkins 모드에서는 `commonData.workspace`(Jenkins env 값)를 우선하고, 없으면 `path.current`를 사용한다.

## 리뷰어를 위한 체크포인트

- 이전 Required 지적처럼 검증 출력에 `...`, `(output)`, 요약-only 기록이 남아 있지 않은가.
- `dart test test/oto_system_runtime_test.dart`의 실제 stdout/stderr가 누락 없이 기록되었는가.
- `dart test test/oto_application_test.dart test/oto_system_runtime_test.dart`의 실제 stdout/stderr가 누락 없이 기록되었는가.
- `dart analyze`와 `dart test` 최종 검증 출력이 실제 실행 결과와 일치하는가.
- 검증 재실행 중 소스 변경이 있었다면 변경 이유와 검증이 기록되었는가.

## 검증 결과

_구현 에이전트가 각 중간 검증 및 최종 검증 명령 실행 후 출력을 여기에 붙여 넣는다._

필수 규칙:
- 검증 명령은 고정된 계약이다. 임의로 대체하지 않는다.
- 대체가 필요하면 `계획 대비 변경 사항`에 이유와 대체 명령을 기록한다.
- `검증 결과`에는 실제 stdout/stderr를 붙여 넣는다.
- 출력이 길어도 `...`, `(output)`, "생략" 같은 대체 표기를 사용하지 않는다.

### REVIEW_REFACTOR-1 중간 검증
```bash
$ dart test test/oto_system_runtime_test.dart
00:00 +0: loading test/oto_system_runtime_test.dart                                                                                                                                                    00:00 +0: setUTF8 uses injected system runtime on Windows                                                                                                                                              00:00 +0: setUTF8 uses injected system runtime on Windows                                                                                                                                              
Set Korean: false
00:00 +1: setUTF8 uses injected system runtime on Windows                                                                                                                                              00:00 +1: DataComposerJenkins composes linux env and BuildData from runtime stdout                                                                                                                     00:00 +1: DataComposerJenkins composes linux env and BuildData from runtime stdout                                                                                                                     
Current OS: linux
Start build...
{
  "workspace": "/workspace",
  "jenkinsHome": "/jenkins",
  "jenkinsUrl": "http://jenkins/",
  "buildUrl": "http://jenkins/build/1/",
  "jobUrl": "http://jenkins/job/myjob/",
  "jobName": "myjob",
  "gitCommit": "abc123",
  "buildNumber": 42,
  "buildID": 42,
  "buildDisplayName": "#42",
  "gitBranch": "main",
  "buildTag": "myjob-42"
}

00:00 +2: DataComposerJenkins composes linux env and BuildData from runtime stdout                                                                                                                     00:00 +2: JenkinsEnvironmentCollector collects linux env and build yaml from runtime                                                                                                                   00:00 +3: JenkinsEnvironmentCollector collects linux env and build yaml from runtime                                                                                                                   00:00 +3: fake system runtime records process calls                                                                                                                                                    00:00 +4: fake system runtime records process calls                                                                                                                                                    00:00 +4: All tests passed!                                                                                                                                                                            
```

```bash
$ dart test test/oto_application_test.dart test/oto_system_runtime_test.dart
00:00 +0: loading test/oto_application_test.dart                                                                                                                                                       00:00 +0: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     00:00 +0: test/oto_system_runtime_test.dart: setUTF8 uses injected system runtime on Windows                                                                                                           
Set Korean: false
00:00 +1: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     00:00 +1: test/oto_system_runtime_test.dart: DataComposerJenkins composes linux env and BuildData from runtime stdout                                                                                  
Current OS: linux
Start build...
{
  "workspace": "/workspace",
  "jenkinsHome": "/jenkins",
  "jenkinsUrl": "http://jenkins/",
  "buildUrl": "http://jenkins/build/1/",
  "jobUrl": "http://jenkins/job/myjob/",
  "jobName": "myjob",
  "gitCommit": "abc123",
  "buildNumber": 42,
  "buildID": 42,
  "buildDisplayName": "#42",
  "gitBranch": "main",
  "buildTag": "myjob-42"
}

00:00 +2: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     00:00 +3: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     00:00 +4: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     00:00 +4: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     
*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: doesNotExist

Exception:  [Validate Pipeline]

workflow[0] (exe): The doesNotExist command does not exist in the command list.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:33:20)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +5: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                     00:00 +5: test/oto_application_test.dart: file build returns success for print-only pipeline                                                                                                           00:00 +5: test/oto_application_test.dart: file build returns success for print-only pipeline                                                                                                           
*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: hello

*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hi
*********************************************************************************************
*                            Build Successfully Complete
*********************************************************************************************


00:00 +6: test/oto_application_test.dart: file build returns success for print-only pipeline                                                                                                           00:00 +6: test/oto_application_test.dart: file build without property workspace uses local workspace without Jenkins env                                                                               00:00 +7: test/oto_application_test.dart: file build without property workspace uses local workspace without Jenkins env                                                                               00:00 +7: test/oto_application_test.dart: file build can run twice in same process                                                                                                                     00:00 +7: test/oto_application_test.dart: file build can run twice in same process                                                                                                                     
*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: hello

*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hi
*********************************************************************************************
*                            Build Successfully Complete
*********************************************************************************************


*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: hello

*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hi
*********************************************************************************************
*                            Build Successfully Complete
*********************************************************************************************


00:00 +8: test/oto_application_test.dart: file build can run twice in same process                                                                                                                     00:00 +8: test/oto_application_test.dart: build fails with message when YAML root is not a map                                                                                                         00:00 +8: test/oto_application_test.dart: build fails with message when YAML root is not a map                                                                                                         
Exception:  [Validate build yaml]

Build YAML root must be a map.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:119:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +9: test/oto_application_test.dart: build fails with message when YAML root is not a map                                                                                                         00:00 +9: test/oto_application_test.dart: build fails with message when property is not a map                                                                                                          00:00 +9: test/oto_application_test.dart: build fails with message when property is not a map                                                                                                          
Exception:  [Validate build yaml]

property must be a map, got: List<dynamic>.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:139:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +10: test/oto_application_test.dart: build fails with message when property is not a map                                                                                                         00:00 +10: test/oto_application_test.dart: build fails with message when command id is not a string                                                                                                    00:00 +10: test/oto_application_test.dart: build fails with message when command id is not a string                                                                                                    
Exception:  [Validate command list]

commands[0] id must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:117:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:157:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +11: test/oto_application_test.dart: build fails with message when command id is not a string                                                                                                    00:00 +11: test/oto_application_test.dart: build fails with message when command type is not a string                                                                                                  00:00 +11: test/oto_application_test.dart: build fails with message when command type is not a string                                                                                                  
Exception:  [Validate command list]

commands[0] (id: hello) command must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:117:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:175:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +12: test/oto_application_test.dart: build fails with message when command type is not a string                                                                                                  00:00 +12: test/oto_application_test.dart: build fails with validation message when workflow key is not a string                                                                                       00:00 +12: test/oto_application_test.dart: build fails with validation message when workflow key is not a string                                                                                       
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - 123: hello

Exception:  [Validate Pipeline]

workflow[0]: 123 is not a supported task. Supported tasks: exe, exe-handle, async, if, contain, while, foreach, wait-until-int, wait-until-float, wait-until-double, wait-until-string, wait-until-seconds, switch.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:194:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +13: test/oto_application_test.dart: build fails with validation message when workflow key is not a string                                                                                       00:00 +13: test/oto_application_test.dart: build fails with validation message when exe-handle branch is missing                                                                                       00:00 +13: test/oto_application_test.dart: build fails with validation message when exe-handle branch is missing                                                                                       
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe-handle:
        id: hello
        on-fail:
          - exe: hello

Exception:  [Validate Pipeline]

workflow[0] (exe-handle): exe-handle syntax requires on-success.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:218:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +14: test/oto_application_test.dart: build fails with validation message when exe-handle branch is missing                                                                                       00:00 +14: test/oto_application_test.dart: build fails with validation message when exe command id is not a string                                                                                     00:00 +14: test/oto_application_test.dart: build fails with validation message when exe command id is not a string                                                                                     
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: 123

Exception:  [Validate Pipeline]

workflow[0] (exe): exe: command id must be a non-empty string, got: int.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:240:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +15: test/oto_application_test.dart: build fails with validation message when exe command id is not a string                                                                                     00:00 +15: test/oto_application_test.dart: build fails with validation message when wait-until-string value is not a string                                                                            00:00 +15: test/oto_application_test.dart: build fails with validation message when wait-until-string value is not a string                                                                            
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - wait-until-string: 123

Exception:  [Validate Pipeline]

workflow[0] (wait-until-string): wait-until requires a string condition expression, got: int.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:262:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +16: test/oto_application_test.dart: build fails with validation message when wait-until-string value is not a string                                                                            00:00 +16: test/oto_application_test.dart: build fails with validation message when exe-handle id is not a string                                                                                      00:00 +16: test/oto_application_test.dart: build fails with validation message when exe-handle id is not a string                                                                                      
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe-handle:
        id: 123
        on-success:
          - exe: hello
        on-fail:
          - exe: hello

Exception:  [Validate Pipeline]

workflow[0] (exe-handle): exe-handle: id must be a string, got: int.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:288:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +17: test/oto_application_test.dart: build fails with validation message when exe-handle id is not a string                                                                                      00:00 +17: test/oto_application_test.dart: build fails with validation message when pipeline.id is missing                                                                                             00:00 +17: test/oto_application_test.dart: build fails with validation message when pipeline.id is missing                                                                                             
Exception:  [Validate build yaml]

pipeline.id must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:309:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +18: test/oto_application_test.dart: build fails with validation message when pipeline.id is missing                                                                                             00:00 +18: test/oto_application_test.dart: build fails with validation message when pipeline.id is not a string                                                                                        00:00 +18: test/oto_application_test.dart: build fails with validation message when pipeline.id is not a string                                                                                        
Exception:  [Validate build yaml]

pipeline.id must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:329:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +19: test/oto_application_test.dart: build fails with validation message when pipeline.id is not a string                                                                                        00:00 +19: test/oto_application_test.dart: build fails with validation message when workflow is empty                                                                                                  00:00 +19: test/oto_application_test.dart: build fails with validation message when workflow is empty                                                                                                  
Exception:  [Validate build yaml]

pipeline.workflow must contain at least one task.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:347:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:00 +20: test/oto_application_test.dart: build fails with validation message when workflow is empty                                                                                                  00:00 +20: test/oto_application_test.dart: CommandExe exe -f handles missing file without LateInitializationError                                                                                      00:00 +20: test/oto_application_test.dart: CommandExe exe -f handles missing file without LateInitializationError                                                                                      
There are no files in path /tmp/oto_missing_1779517084376378.yaml


00:00 +21: test/oto_application_test.dart: CommandExe exe -f handles missing file without LateInitializationError                                                                                      00:00 +21: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns success contract for valid yaml                                                                 00:00 +22: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns success contract for valid yaml                                                                 00:00 +22: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns build yaml failure contract                                                                     00:00 +23: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns build yaml failure contract                                                                     00:00 +23: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns command list failure contract for duplicate id                                                  00:00 +24: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns command list failure contract for duplicate id                                                  00:00 +24: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns pipeline failure contract                                                                       00:00 +25: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns pipeline failure contract                                                                       00:00 +25: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent exposes stable json shape                                                                               00:00 +26: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent exposes stable json shape                                                                               00:00 +26: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns failure contract for malformed scheduler section                                                00:00 +27: test/oto_application_test.dart: Application.validateYamlContent validateYamlContent returns failure contract for malformed scheduler section                                                00:00 +27: test/oto_application_test.dart: BuildResult.toJson exposes success execution envelope                                                                                                       00:00 +28: test/oto_application_test.dart: BuildResult.toJson exposes success execution envelope                                                                                                       00:00 +28: test/oto_application_test.dart: BuildResult.toJson exposes failure execution envelope                                                                                                       00:00 +29: test/oto_application_test.dart: BuildResult.toJson exposes failure execution envelope                                                                                                       00:00 +29: test/oto_application_test.dart: BuildResult.toJson exposes populated step events                                                                                                            00:00 +30: test/oto_application_test.dart: BuildResult.toJson exposes populated step events                                                                                                            00:00 +30: test/oto_application_test.dart: BuildResult regression - stepEvents snapshot first build result retains stepEvents after second build execution                                             00:00 +31: test/oto_application_test.dart: BuildResult regression - stepEvents snapshot first build result retains stepEvents after second build execution                                             00:00 +31: test/oto_application_test.dart: logEnable false build with logEnable false suppresses failure stdout                                                                                        00:00 +32: test/oto_application_test.dart: logEnable false build with logEnable false suppresses failure stdout                                                                                        00:00 +32: test/oto_application_test.dart: logEnable false build with logEnable false suppresses command stdout logs                                                                                   00:00 +33: test/oto_application_test.dart: logEnable false build with logEnable false suppresses command stdout logs                                                                                   00:00 +33: test/oto_application_test.dart: CommandExe JSON Mode CommandExe shouldPrintExecuteLog suppresses execute log for json                                                                       00:00 +34: test/oto_application_test.dart: CommandExe JSON Mode CommandExe shouldPrintExecuteLog suppresses execute log for json                                                                       00:00 +34: test/oto_application_test.dart: CommandExe JSON Mode CommandExe exe -f missing file --json returns execution result json                                                                    00:00 +35: test/oto_application_test.dart: CommandExe JSON Mode CommandExe exe -f missing file --json returns execution result json                                                                    00:00 +35: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                   00:01 +35: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                   00:02 +35: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                   00:03 +35: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                   00:03 +36: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                   00:03 +36: All tests passed!                                                                                                                                                                           
```

### 최종 검증
```bash
$ dart analyze
Analyzing oto...
No issues found!
```

```bash
$ dart test
00:00 +0: loading test/oto_command_runtime_test.dart                                                                                                                                                   00:00 +0: test/oto_command_runtime_test.dart: shell command delegates process start to runtime                                                                                                         00:00 +1: test/oto_command_runtime_test.dart: shell command delegates process start to runtime                                                                                                         00:00 +2: test/oto_command_runtime_test.dart: shell command delegates process start to runtime                                                                                                         00:00 +3: test/oto_catalog_cli_test.dart: CommandCatalogCli json output format and filters                                                                                                             00:00 +3: test/oto_command_runtime_test.dart: git command delegates command buffer to runtime                                                                                                          
/tmp/oto_runtime_test
00:00 +4: test/oto_catalog_cli_test.dart: CommandCatalogCli json output format and filters                                                                                                             00:00 +4: test/oto_command_runtime_test.dart: process run delegates detached start to runtime                                                                                                          
Process Start: my_server
00:00 +5: test/oto_catalog_cli_test.dart: CommandCatalogCli json output format and filters                                                                                                             00:00 +6: test/oto_catalog_cli_test.dart: CommandCatalogCli json output format and filters                                                                                                             00:00 +7: test/oto_catalog_cli_test.dart: CommandCatalogCli json output format and filters                                                                                                             00:00 +8: test/oto_catalog_cli_test.dart: CommandCatalogCli json output format and filters                                                                                                             00:00 +9: test/oto_command_runtime_test.dart: github_pull_request_list delegates start with decoder                                                                                                    00:00 +9: test/oto_command_runtime_test.dart: github_pull_request_list delegates start with decoder                                                                                                    
[Return] pr : null
00:00 +10: test/oto_catalog_cli_test.dart: CommandCatalogCli category filter with json                                                                                                                 00:00 +10: test/oto_command_runtime_test.dart: execute_app delegates run to runtime with workspace                                                                                                     
Process Start: MyApp.exe
00:00 +11: test/oto_catalog_cli_test.dart: CommandCatalogCli category filter with json                                                                                                                 00:00 +12: test/oto_command_runtime_test.dart: BuildiOS.initializeFastlane delegates fastlane init run to runtime                                                                                      00:00 +13: test/oto_command_runtime_test.dart: BuildiOS.initializeFastlane delegates fastlane init run to runtime                                                                                      00:00 +14: test/oto_command_runtime_test.dart: BuildiOS.initializeFastlane delegates fastlane init run to runtime                                                                                      00:00 +15: test/oto_command_runtime_test.dart: BuildiOS.initializeFastlane delegates fastlane init run to runtime                                                                                      00:00 +16: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +16: test/oto_command_runtime_test.dart: BuildiOS.execute delegates start to runtime via ProcessData.exitCode                                                                                    
✅ Updated MARKETING_VERSION = 1.0.0
✅ Updated CURRENT_PROJECT_VERSION = 100
[Return] version : 1.0.0
[Return] buildNumber : 100
00:00 +17: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +17: test/oto_system_runtime_test.dart: setUTF8 uses injected system runtime on Windows                                                                                                          
Set Korean: false
00:00 +17: test/oto_command_runtime_test.dart: BuildiOS.execute shell includes derivedDataPath and macPassword                                                                                         
✅ Updated MARKETING_VERSION = 1.0.0
00:00 +18: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +18: test/oto_command_runtime_test.dart: BuildiOS.execute shell includes derivedDataPath and macPassword                                                                                         
✅ Updated CURRENT_PROJECT_VERSION = 100
00:00 +18: test/oto_system_runtime_test.dart: DataComposerJenkins composes linux env and BuildData from runtime stdout                                                                                 
Current OS: linux
Start build...
00:00 +18: test/oto_command_runtime_test.dart: BuildiOS.execute shell includes derivedDataPath and macPassword                                                                                         
[Return] version : 1.0.0
[Return] buildNumber : 100
00:00 +19: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +19: test/oto_command_runtime_test.dart: BuildFlutter uses resolved workspace, flavor, and platform in shell                                                                                     
cd /custom/workspace && flutter clean && flutter pub upgrade --major-versions && flutter packages upgrade && flutter pub get && flutter build apk --flavor production --release
00:00 +20: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +20: test/oto_system_runtime_test.dart: DataComposerJenkins composes linux env and BuildData from runtime stdout                                                                                 
{
  "workspace": "/workspace",
  "jenkinsHome": "/jenkins",
  "jenkinsUrl": "http://jenkins/",
  "buildUrl": "http://jenkins/build/1/",
  "jobUrl": "http://jenkins/job/myjob/",
  "jobName": "myjob",
  "gitCommit": "abc123",
  "buildNumber": 42,
  "buildID": 42,
  "buildDisplayName": "#42",
  "gitBranch": "main",
  "buildTag": "myjob-42"
}

00:00 +21: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +22: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +23: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +24: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +25: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +26: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +27: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +28: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +28: test/oto_command_runtime_test.dart: sftp delete calls sshpass ssh rm -rf                                                                                                                    
######################## delete 1
Deleted: /remote/old.txt
00:00 +29: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +30: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +30: test/oto_command_runtime_test.dart: download maps local relative path to remote path for sftp                                                                                               
========================= [Try connection] =========================
========================= [Connected! Start Download] ================
00:00 +31: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +31: test/oto_command_runtime_test.dart: download maps local relative path to remote path for sftp                                                                                               
[Download]: /tmp/oto_runtime_test/config/app.json ====> /remote/config/app.json
00:00 +32: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +32: test/oto_command_runtime_test.dart: download maps local relative path to remote path for sftp                                                                                               
Download: [F]/remote/config/app.json --> /tmp/oto_runtime_test/config/app.json
========================= [Download completed!] ====================
00:00 +33: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +34: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +34: test/oto_command_runtime_test.dart: sftp download failure propagates non-zero exit code as exception                                                                                        
========================= [Try connection] =========================
========================= [Connected! Start Download] ================
[Download]: /tmp/oto_runtime_test/config/app.json ====> /remote/config/app.json
00:00 +35: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +35: test/oto_command_runtime_test.dart: git_pull propagates exit code 1 as failure                                                                                                              
Exit Code: 1
00:00 +36: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +36: test/oto_command_runtime_test.dart: git_push propagates exit code 1 as failure                                                                                                              
Exit Code: 1
00:00 +37: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +38: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +39: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +40: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +41: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +42: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +42: test/oto_command_runtime_test.dart: github_pull_request_create treats existing-pr message as success                                                                                        
[Return] prUrl : https://github.com/org/repo/pull/123
[Return] prNumber : 123
00:00 +43: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +44: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +44: test/oto_command_runtime_test.dart: github_pull_request_create propagates unrelated exit code 1                                                                                             
Exit Code: 1
00:00 +45: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +45: test/oto_core_test.dart: PipelineIf evaluates condition from explicit context not singleton                                                                                                 
[Pipeline-IF]


 - Condition: <!property.env> == prod
 - Values:    prod == prod
 - Result:    true ===> Execute: on-true 
*********************************************************************************************
*                            Phase Start: Print (onTrue)
*********************************************************************************************


onTrue
00:00 +46: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +46: test/oto_core_test.dart: PipelineForeach iterates list from explicit context not singleton                                                                                                  
[Return] current : 10
*********************************************************************************************
*                            Phase Start: Print (print)
*********************************************************************************************


print
[Return] current : 20
*********************************************************************************************
*                            Phase Start: Print (print)
*********************************************************************************************


print
[Return] current : 30
00:00 +46: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +46: test/oto_core_test.dart: PipelineForeach iterates list from explicit context not singleton                                                                                                  
*********************************************************************************************
*                            Phase Start: Print (print)
*********************************************************************************************


00:00 +47: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +47: test/oto_core_test.dart: PipelineForeach iterates list from explicit context not singleton                                                                                                  
print
00:00 +48: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +48: test/oto_core_test.dart: PipelineForeach iterates list from explicit context not singleton                                                                                                  
[Pipeline-Foreach (List)]


 - Foreach complete. Loop out
00:00 +49: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +50: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +50: test/oto_core_test.dart: PipelineContain evaluates target from explicit context not singleton                                                                                               
[Pipeline-Contain]


 - Condition: Contain in "<!property.target>"
 - Values:    Contain in "foo".
 - Result:    true ===> Execute: on-true 
*********************************************************************************************
*                            Phase Start: Print (onTrue)
*********************************************************************************************


onTrue
00:00 +51: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +52: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +53: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +54: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +55: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +56: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +57: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +58: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +58: test/oto_cli_runtime_test.dart: Printer Runtime Rollout Tests unix printer delegates script execution to system runtime                                                                     

00:00 +59: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +60: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +61: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +62: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +63: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +64: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +65: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +66: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +66: test/oto_cli_runtime_test.dart: Printer Runtime Rollout Tests windows printer delegates script execution to system runtime                                                                  

00:00 +67: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +68: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +69: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +70: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +71: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +72: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +73: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +73: test/oto_core_test.dart: pipeline execution records started and completed step events                                                                                                       
*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hello
00:00 +74: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +75: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +76: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +77: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +78: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +79: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +80: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +81: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +82: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +83: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +84: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:00 +85: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +85: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +85: test/oto_application_test.dart: build returns failure instead of exiting on invalid yaml                                                                                                    
*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: doesNotExist

Exception:  [Validate Pipeline]

workflow[0] (exe): The doesNotExist command does not exist in the command list.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:33:20)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +86: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +86: test/oto_application_test.dart: file build returns success for print-only pipeline                                                                                                          
*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: hello

*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hi
*********************************************************************************************
*                            Build Successfully Complete
*********************************************************************************************


00:01 +87: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +88: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +88: test/oto_application_test.dart: file build can run twice in same process                                                                                                                    
*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: hello

*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hi
*********************************************************************************************
*                            Build Successfully Complete
*********************************************************************************************


*********************************  Build Data  *************************************


property:
  workspace: .
commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: hello

*********************************************************************************************
*                            Phase Start: Print (hello)
*********************************************************************************************


hi
*********************************************************************************************
*                            Build Successfully Complete
*********************************************************************************************


00:01 +89: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +89: test/oto_application_test.dart: build fails with message when YAML root is not a map                                                                                                        
Exception:  [Validate build yaml]

Build YAML root must be a map.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:119:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +90: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +90: test/oto_application_test.dart: build fails with message when property is not a map                                                                                                         
Exception:  [Validate build yaml]

property must be a map, got: List<dynamic>.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:139:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +91: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +91: test/oto_application_test.dart: build fails with message when command id is not a string                                                                                                    
Exception:  [Validate command list]

commands[0] id must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:117:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:157:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +92: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +92: test/oto_application_test.dart: build fails with message when command type is not a string                                                                                                  
Exception:  [Validate command list]

commands[0] (id: hello) command must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:117:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:175:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +93: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +93: test/oto_application_test.dart: build fails with validation message when workflow key is not a string                                                                                       
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - 123: hello

Exception:  [Validate Pipeline]

workflow[0]: 123 is not a supported task. Supported tasks: exe, exe-handle, async, if, contain, while, foreach, wait-until-int, wait-until-float, wait-until-double, wait-until-string, wait-until-seconds, switch.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:194:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +94: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +94: test/oto_application_test.dart: build fails with validation message when exe-handle branch is missing                                                                                       
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe-handle:
        id: hello
        on-fail:
          - exe: hello

Exception:  [Validate Pipeline]

workflow[0] (exe-handle): exe-handle syntax requires on-success.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:218:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +95: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +95: test/oto_application_test.dart: build fails with validation message when exe command id is not a string                                                                                     
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe: 123

Exception:  [Validate Pipeline]

workflow[0] (exe): exe: command id must be a non-empty string, got: int.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:240:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>


00:01 +96: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +96: test/oto_application_test.dart: build fails with validation message when exe command id is not a string                                                                                     
*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +97: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +98: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +99: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                              00:01 +99: test/oto_application_test.dart: build fails with validation message when wait-until-string value is not a string                                                                            
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - wait-until-string: 123

00:01 +100: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +100: test/oto_application_test.dart: build fails with validation message when wait-until-string value is not a string                                                                           
Exception:  [Validate Pipeline]

workflow[0] (wait-until-string): wait-until requires a string condition expression, got: int.


00:01 +101: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +101: test/oto_application_test.dart: build fails with validation message when wait-until-string value is not a string                                                                           
#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:262:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +102: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +103: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +104: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +104: test/oto_application_test.dart: build fails with validation message when exe-handle id is not a string                                                                                     
*********************************  Build Data  *************************************


commands:
  - command: Print
    id: hello
    param:
      message: hi
pipeline:
  id: main
  workflow:
    - exe-handle:
        id: 123
        on-success:
          - exe: hello
        on-fail:
          - exe: hello

00:01 +104: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +104: test/oto_application_test.dart: build fails with validation message when exe-handle id is not a string                                                                                     
Exception:  [Validate Pipeline]

workflow[0] (exe-handle): exe-handle: id must be a string, got: int.


#0      Application.build (package:oto/oto/application.dart:150:9)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:288:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +105: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +105: test/oto_application_test.dart: build fails with validation message when pipeline.id is missing                                                                                            
Exception:  [Validate build yaml]

pipeline.id must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:309:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +106: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +106: test/oto_application_test.dart: build fails with validation message when pipeline.id is not a string                                                                                       
Exception:  [Validate build yaml]

pipeline.id must be a non-empty string.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:329:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +107: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +107: test/oto_application_test.dart: build fails with validation message when workflow is empty                                                                                                 
Exception:  [Validate build yaml]

pipeline.workflow must contain at least one task.


#0      Application.build (package:oto/oto/application.dart:109:11)
<asynchronous suspension>
#1      main.<anonymous closure> (file:///config/workspace/oto/test/oto_application_test.dart:347:9)
<asynchronous suspension>
#2      Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:242:9)
<asynchronous suspension>
#3      Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:240:7)
<asynchronous suspension>
#4      Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:282:9)
<asynchronous suspension>



*********************************************************************************************
*                            Build Failed
*********************************************************************************************


00:01 +108: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +108: test/oto_application_test.dart: CommandExe exe -f handles missing file without LateInitializationError                                                                                     
There are no files in path /tmp/oto_missing_1779517314410480.yaml


00:01 +109: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +110: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +111: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +112: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +113: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +114: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +115: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +116: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +117: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +118: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +119: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +120: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +121: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +122: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +123: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +124: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +125: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +126: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +127: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:01 +127: test/oto_scheduler_runtime_test.dart: SchedulerManager Process Control via Injected Runtime Unix starts background shell process via nohup                                                 
nohup   scheduler -s &

00:01 +127: test/oto_cli_runtime_test.dart: RegistPath Runtime Rollout Tests regist_path windows delegates setx through system runtime                                                                 
New User Path =====> some_old_path
00:01 +128: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:02 +128: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:02 +129: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:02 +129: test/oto_scheduler_runtime_test.dart: SchedulerManager Process Control via Injected Runtime terminate kills current scheduler process                                                      
Scheduler operation stopped.
00:02 +130: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:02 +130: test/oto_scheduler_runtime_test.dart: SchedulerManager Process Control via Injected Runtime _checkProcess uses injected processFinder                                                      
Scheduler is running on pid [11111].
00:02 +131: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:02 +132: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:03 +132: test/oto_catalog_cli_test.dart: actual bin execution with --json output has parseable json and no execute logs                                                                             00:03 +133: test/oto_validate_cli_test.dart: actual bin validate --json output has parseable json and no execute logs                                                                                  00:03 +134: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                  00:04 +134: test/oto_application_test.dart: CommandExe JSON Mode actual bin exe --json output has parseable execution result json and no execute logs                                                  00:04 +135: test/oto_catalog_cli_test.dart: actual bin execution without args outputs a table, not help                                                                                                00:05 +135: test/oto_catalog_cli_test.dart: actual bin execution without args outputs a table, not help                                                                                                00:05 +136: test/oto_catalog_cli_test.dart: actual bin execution without args outputs a table, not help                                                                                                00:05 +136: All tests passed!                                                                                                                                                                          
```

---

> **[IMPLEMENTING AGENT — BEFORE SAVING] Have you filled in every implementation-owned section: completion table, implementation checklist, changes from plan, design decisions, and verification output?**
> If anything is blank, go back and fill it in before saving this file.
> Leave review-agent-only sections unchanged.

Sections and their ownership:

| Section | Owner | Note |
|---------|-------|------|
| Header comment, 개요, 리뷰 에이전트 지시 | Fixed at stub creation | Implementing agent must not modify or execute these |
| 구현 항목별 완료 여부 (item names) | Fixed at stub creation | Implementing agent checks `[ ]` -> `[x]` only |
| 구현 체크리스트 (item text/order) | Fixed at stub creation from plan | Implementing agent checks `[ ]` -> `[x]` only |
| 코드리뷰 전용 체크리스트 | Review agent only | Implementing agent must not modify or check this section |
| 계획 대비 변경 사항, 주요 설계 결정 | Implementing agent | Replace placeholder text with actual content |
| 리뷰어를 위한 체크포인트 | Fixed at stub creation | Pre-filled from plan |
| 검증 결과 (section headings + commands) | Fixed at stub creation | Implementing agent fills in command output only |
| 코드리뷰 결과 | Review agent appends | Not included in stub |

## 코드리뷰 결과

- 종합 판정: PASS
- 차원별 평가
  - correctness: Pass
  - completeness: Pass
  - test coverage: Pass
  - API contract: Pass
  - code quality: Pass
  - plan deviation: Pass
  - verification trust: Pass
- 발견된 문제: 없음
- 다음 단계: PASS이므로 `complete.log`를 작성하고 active task 디렉터리를 archive로 이동한다.
