sync: to agentic-framework v1.1.116

agent-ops/.version

@@ -1 +1 @@
-1.1.115
+1.1.116

agent-ops/skills/common/plan/SKILL.md

@@ -45,6 +45,7 @@ Role boundary rules:
 
 - Implementing agents fill implementation-owned `CODE_REVIEW-*-G??.md` sections, keep active files in place, and report ready for review.
 - If implementation cannot continue without user input, implementing agents fill the review stub's `사용자 리뷰 요청` section with the exact decision needed, evidence, commands/output, and resume condition, then stop with active files in place. Evidence gaps that a follow-up agent can close by rerunning commands or collecting artifacts should be recorded in `검증 결과` or `계획 대비 변경 사항`, not escalated to user review.
+- If required UI evidence capture needs a user-owned device, emulator, permission, secret, or interactive access unavailable to the agent, fill `사용자 리뷰 요청` with attempted commands, blocker evidence, and resume condition.
 - Finalization (`코드리뷰 결과`, log rename, `complete.log`, archive moves, review-only checklist) is code-review-skill only.
 
 Split decision policy:
@@ -62,6 +63,7 @@ Split gates:
 - Split when different parts can be verified with different focused tests or have different risk profiles.
 - Split when a likely failure in one part would force rewriting unrelated parts of the plan.
 - Split when one part can produce a useful `complete.log` before another part starts.
+- Split when mobile/UI verification can hang on emulator/device state, modal, permission dialog, animation, or external runner; isolate evidence recovery from feature implementation.
 
 Task directory naming rules:
 
@@ -287,6 +289,7 @@ Verification fidelity rules:
 - Do not download, generate, or leave verification tools inside the repository. Temporary tools belong outside the repo, such as under `/tmp`, and must not become task artifacts.
 - For search commands whose output order may vary, specify deterministic options in the plan, for example `rg --sort path`.
 - `검증 결과` must contain actual stdout/stderr, not summarized or reconstructed output. If output is too long, record the saved output file path and the exact command used to create it.
+- If mobile/UI verification has no progress for 2 minutes or times out, stop blind retries; collect focused stdout plus screenshot/window/UI-tree evidence when available, or record why capture is impossible.
 - If the plan's pass condition says all leftovers must be intentional exceptions, any `변경 필요` item forces FAIL until resolved or explicitly reclassified with evidence.
 - Decide in the plan whether Go test cache output is acceptable. If fresh execution matters, use `go test -count=1 ...`.
 
@@ -392,6 +395,7 @@ _구현 에이전트가 각 중간 검증 및 최종 검증 명령 실행 후
 - 대체가 필요하면 `계획 대비 변경 사항`에 이유와 대체 명령을 기록한다.
 - `검증 결과`에는 실제 stdout/stderr를 붙여 넣는다.
 - 사용자 리뷰 요청으로 명령을 끝까지 실행하지 못했다면 `사용자 리뷰 요청`에 실행한 명령, 실제 출력, 미실행 명령의 사유를 기록한다.
+- mobile/UI hang 또는 timeout은 focused rerun 명령과 screenshot/window/UI-tree evidence path를 남기고, 불가능하면 정확한 사유를 남긴다.
 
 ### {TAG}-1 중간 검증
 ```