@walwal-harness/cli 7.1.13 → 7.1.14

package/HR-Resource/cdo/SKILL.md

@@ -25,6 +25,10 @@ Own design strategy for the mission.
 Design output must be usable by implementation teams, not just descriptive.
 CDO must not directly produce palettes, typography, layouts, mockups, interaction specs, or design-review findings. CDO may only brief workers, compare their outputs, decide, and document the accepted direction with worker names and report paths.
 
+## Owner Handoff Gate
+
+Owner is the final acceptance reviewer, not a design QA substitute. CDO must use design/review workers to validate UI/UX readiness, accessibility concerns, responsive behavior assumptions, and visual acceptance risks before handoff. Do not ask the Owner to discover whether the UI is usable or visually broken; ask only for final product or brand acceptance after worker-backed review.
+
 Required output sections:
 
 1. Worker Task Briefs — task, capability needed, selected worker or hiring request, acceptance criteria.

package/HR-Resource/ceo/SKILL.md

@@ -35,6 +35,8 @@ You are the only direct conversation channel with the Owner.
 - After writing `.env`, verify with `grep '^HARNESS_BASE_PORT=' .env` before routing service work.
 - For service monitoring, collect the Owner's server mapping first: local PC, Docker, VM, AWS/cloud, host, port, health path, log path, and contact/source.
 - Every CEO and CXX mission document must include an English `## Implementation Notes` section with the required subsections below. CEO must reject CXX reports that omit it.
+- Owner is the final acceptance reviewer, not a tester, QA substitute, debugger, or deployment verifier. CEO must not send "done, please check" reports while core functionality, regression, account setup, browser flows, logs, or runtime health remain unverified by workers.
+- Before requesting Owner acceptance, CEO must collect and summarize CXX-backed completion evidence: CTO implementation evidence, CQO evaluator/tester evidence, and OPS runtime evidence when services are involved. The final Owner report may request acceptance review or business/product judgment, but must not ask the Owner to discover whether the software works.
 
 ## Required Mission Note Format
 

package/HR-Resource/coo/SKILL.md

@@ -24,6 +24,10 @@ Own mission planning, research, references, hypotheses, and goal fit.
 
 COO must not directly produce research findings, sprint plans, feed lists, market conclusions, backtest scripts, or documentation deliverables. COO may only frame the question, select and brief workers, evaluate worker output, and record the accepted decision.
 
+## Owner Handoff Gate
+
+Owner is the final acceptance reviewer, not a tester or discovery worker. COO must define verifiable success criteria and worker-backed validation plans before work reaches implementation. Do not propose Owner manual checking as the way to discover whether the goal works; unresolved validation gaps must be reported to CEO as blockers or risks.
+
 ## Output
 
 Return planning decisions, evidence, rejected options, mission fit, worker names used, worker report paths, and the next CXX that should receive the work.

package/HR-Resource/cqo/SKILL.md

@@ -30,6 +30,8 @@ CQO must not directly execute QA, visual review, security review, performance te
 
 Every evaluator/tester dispatched by CQO must write its report under `.harness/documents/{goal-or-child-mission}/cqo/workers/{worker-name}.md`.
 
+**Owner is not the QA tester.** CQO must not approve a handoff that asks the Owner to verify basic functionality, regression safety, browser behavior, account setup, logs, or runtime health. CQO must use evaluator/tester workers to collect the evidence, including E2E/Playwright/browser checks, regression commands, test-account or seeded-data validation, screenshots, logs, and risk notes when relevant. If evidence is missing, CQO verdict is BLOCKED or FAIL, not "ask Owner to check."
+
 Required output sections in `cqo.md`:
 
 1. Worker Task Briefs — gate, capability needed, selected evaluator or hiring request, acceptance criteria.

package/HR-Resource/cto/SKILL.md

@@ -30,6 +30,8 @@ CTO must not directly write code, create build scripts, choose detailed implemen
 
 Every worker dispatched by CTO must be listed in the Worker Evidence Manifest section of `cto.md` with their report path and status. The report path must be `.harness/documents/{goal-or-child-mission}/cto/workers/{worker-name}.md`. Workers not listed there are invisible to the harness and their output cannot be accepted.
 
+**Owner is not the technical tester.** CTO must not hand unfinished software to CEO/Owner with "please check" as the validation plan. CTO must require workers to prove implementation readiness with appropriate unit tests, integration checks, build/run commands, seeded data or test account setup, browser/E2E checks when applicable, and changed-file evidence. If verification cannot be completed, CTO reports BLOCKED with the missing evidence instead of asking the Owner to test it.
+
 Required output sections in `cto.md`:
 
 1. Worker Task Briefs — task, capability needed, selected worker or hiring request, acceptance criteria.

package/HR-Resource/ops/SKILL.md

@@ -17,6 +17,10 @@ OPS owns two environment classes:
 OPS is not the implementation owner. CTO/DevOps workers start or change systems; OPS observes whether the declared build/service environments are healthy and raises evidence-backed events.
 OPS must not directly perform DevOps implementation, service fixes, config rewrites, deployment changes, or recovery work. OPS may only monitor, classify, brief hired Ops/DevOps workers, review their reports, and escalate evidence-backed events.
 
+## Owner Handoff Gate
+
+Owner is the final acceptance reviewer, not the runtime monitor. OPS must provide build/service evidence through logs, health checks, port checks, process status, and worker-backed recovery reports when needed. Do not ask the Owner to verify that a server is running, a port is correct, or logs are clean; report BLOCKED or INCIDENT to CEO when runtime evidence is missing.
+
 ## Port Policy
 
 - CEO must agree on a `{xx}000` base port with the Owner before CXX services are allocated.

package/README.md

@@ -181,12 +181,13 @@ npx walwal-harness init --force --project-root /path/to/project
 Features:
 
 - **Split Workspace** — full-viewport left/right panes keep Org Tree + Mission Timeline beside the selected mission detail; both panes scroll independently with hidden scrollbars, and the detail pane resets to top on selection changes
-- **Org Tree** — live status of Owner → CEO → CXX → Workers hierarchy, with worker cards grouped under their owning CXX
+- **Org Tree** — live status of Owner → CEO → CXX → Workers hierarchy, with worker cards grouped under their owning CXX; clicking any node initializes the right pane to the relevant history, CXX document, or worker report
 - **Mission Timeline** — clickable history of goal/submission/hot-fix missions showing the full dispatch chain
 - **Mission Flow tab** — per-mission flow: Owner prompt → CEO routing → CXX → owner-specific worker evidence → CQO verdict
 - **History tab** — mission-specific Owner request (from CEO summary + closest progress.log match)
 - **Gotchas tab** — searchable `.harness/gotchas/*.md` knowledge base, click to read full markdown
 - **Document tab** — per-CXX markdown doc viewer
+- **Owner Acceptance Gate** — Owner is final acceptance only; CEO/CXX must complete worker-backed verification before asking for Owner review
 
 ---
 
@@ -222,6 +223,7 @@ harness-hiring           → register and onboard worker
 
 | Version | Summary |
 |---|---|
+| 7.1.14 | Owner acceptance gate: Owner is final reviewer, not tester; dashboard org-node clicks initialize the detail pane |
 | 7.1.13 | Dashboard: full-viewport split workspace, hidden pane scrollbars, and detail scroll reset on selection |
 | 7.1.12 | Dashboard: split workspace panes now scroll independently |
 | 7.1.11 | Dashboard: persistent 50/50 split workspace and CXX-owned worker grouping in the org tree |

package/apps/harness-dashboard/components/Scene.tsx

@@ -40,18 +40,18 @@ export function Scene({ snapshot: initial, lang = "ko" }: SceneProps) {
   };
 
   const handleNodeClick = (node: OrgNodeDef) => {
+    const currentMission = snapshot.missions?.[0] ?? null;
     setSelectedNode(node);
     setSelectedAgent(null);
-    // Auto-select current mission for non-owner nodes
-    if (!selectedMission && snapshot.missions?.[0]) {
-      setSelectedMission(snapshot.missions[0]);
+    if (currentMission) {
+      setSelectedMission(currentMission);
     }
     if (node.id === "owner") {
       setDrawerTab("history");
     } else if (node.id.startsWith("worker-")) {
-      setDrawerTab("mission-flow");
+      setDrawerTab("mission-doc");
     } else {
-      setDrawerTab("mission-flow");
+      setDrawerTab("mission-doc");
     }
   };
 
@@ -76,6 +76,14 @@ export function Scene({ snapshot: initial, lang = "ko" }: SceneProps) {
     selectedNode?.id ?? "",
     selectedAgent?.id ?? "",
   ].join(":");
+  const selectedWorkerName = selectedNode?.id.startsWith("worker-")
+    ? selectedNode.label
+    : undefined;
+  const selectedDocumentRole = selectedWorkerName
+    ? "worker"
+    : selectedNode?.role === "owner"
+    ? "ceo"
+    : selectedNode?.role;
 
   // Suppress unused lang warning — kept for future i18n
   void lang;
@@ -161,14 +169,19 @@ export function Scene({ snapshot: initial, lang = "ko" }: SceneProps) {
             {drawerTab === "mission-doc" && selectedNode && (
               <MissionDocTab
                 missions={snapshot.missions ?? []}
-                role={
-                  selectedNode.role === "owner"
-                    ? "ceo"
-                    : (selectedNode.role as "ceo" | "cto" | "cqo" | "coo" | "cdo" | "ops")
+                role={selectedDocumentRole as "ceo" | "cto" | "cqo" | "coo" | "cdo" | "ops" | "worker"}
+                workerName={selectedWorkerName}
+                fromLabel={
+                  selectedWorkerName
+                    ? selectedNode.role.toUpperCase()
+                    : selectedNode.role === "ceo"
+                    ? "Owner"
+                    : "CEO"
                 }
-                fromLabel={selectedNode.role === "ceo" ? "Owner" : "CEO"}
                 toLabel={
-                  selectedNode.role === "cto"
+                  selectedWorkerName
+                    ? "Evidence"
+                    : selectedNode.role === "cto"
                     ? "Workers"
                     : selectedNode.role === "cqo"
                     ? "Owner Report"

package/assets/templates/AGENTS-ko.md.template

@@ -106,7 +106,17 @@ Owner
 
 CEO는 worker 기록 없이 완료된 산출물을 포함한 CXX 보고서를 거부한다.
 
-## 7. 미션 플로우
+## 7. Owner 역할
+
+Owner는 최종 검수자다. Tester, QA worker, debugger, 배포 확인 담당자가 아니다.
+
+- 동작하지 않거나 검증되지 않았거나 부분적으로만 실행되는 소프트웨어를 Owner에게 전달하며 "확인해 주세요"를 다음 액션으로 삼지 않는다.
+- Owner에게 개발자 테스트, 회귀 확인, 계정 생성/로그인 확인, Playwright 확인, E2E 순회, 로그 점검, 기본 기능 검증을 요구하지 않는다.
+- CEO와 CXX는 worker를 통해 자체 검증을 계획하고 실행한다: unit test, E2E test, Playwright/browser check, test account, seed data, build/run check, log evidence.
+- Owner 검수는 CEO가 CXX 완료 기록, CTO 구현 증거, CQO evaluator 증거, 필요한 OPS 런타임 증거를 모아 goal이 실제로 완수되었음을 보인 뒤에만 요청한다.
+- 최종 Owner 보고는 acceptance review, 제품 판단, 비즈니스 승인을 요청할 수 있다. 소프트웨어가 동작하는지 발견해 달라고 요청해서는 안 된다.
+
+## 8. 미션 플로우
 
 ### Goal
 
@@ -139,7 +149,7 @@ CEO는 worker 기록 없이 완료된 산출물을 포함한 CXX 보고서를
 
 주의: harness 문서(ceo.md, cto.md, cqo.md, worker 보고서)에 대한 docmeta skip 판단은 미션 프로토콜 단계를 건너뛸 권한을 부여하지 않는다. 이 파일들은 분석 산출물이 아니라 미션 기록이다.
 
-## 8. 하네스 런타임
+## 9. 하네스 런타임
 
 | 경로 | 역할 |
 |---|---|
@@ -155,7 +165,7 @@ CEO는 worker 기록 없이 완료된 산출물을 포함한 CXX 보고서를
 
 `.harness/`는 미션 상태 저장소다. 빌드 산출물이 아니다. 삭제하지 않는다.
 
-## 9. 금지 규칙
+## 10. 금지 규칙
 
 1. **`{mission}/cto.md` 없이 소스 코드 편집 금지** — CTO의 범위 승인이 있어야 소스 파일을 수정할 수 있다.
 2. **CXX 사칭 금지** — 현재 모델이 CEO/CTO/CQO를 인라인으로 대행하지 않는다. 설치된 harness skill을 fresh session에서 사용한다.
@@ -163,10 +173,11 @@ CEO는 worker 기록 없이 완료된 산출물을 포함한 CXX 보고서를
 4. **CQO 판정 없이 archive 금지** — 명시적 PASS가 담긴 `{mission}/cqo.md`가 존재해야 한다.
 5. **gotcha 등록 생략 금지** — 모든 hot-fix는 `.harness/gotchas/` 또는 `.harness/conventions/`에 최소 하나의 항목을 만든다.
 6. **미션 중 이 파일 편집 금지** — AGENTS.md를 수정하려면 별도 `/goal`을 제출한다.
+7. **Owner는 최종 검수만 수행** — Owner는 tester나 QA 대체자가 아니다. CEO/CXX는 worker-backed verification으로 goal 완료 가능성을 증명하기 전까지 "완료했습니다, 확인해 주세요"라고 보고하지 않는다.
 
 ---
 
-## 10. 프로젝트 컨텍스트
+## 11. 프로젝트 컨텍스트
 
 - **기술 스택**: {{TECH_STACK}}
 - **프로젝트 구조**: {{PROJECT_STRUCTURE}}

package/assets/templates/AGENTS.md.template

@@ -54,9 +54,19 @@ Each CXX:
 
 CEO rejects any CXX report that contains completed deliverables without matching worker records.
 
+## 4. Owner Role
+
+The Owner is the final acceptance reviewer, not a tester, QA worker, debugger, or deployment verifier.
+
+- Do not hand the Owner broken, unverified, or partially runnable software with "please check this" as the next action.
+- Do not ask the Owner to perform developer testing, regression checks, account setup checks, Playwright review, E2E traversal, log inspection, or basic functionality verification.
+- CEO and CXX must plan and execute self-verification through workers: unit tests, E2E tests, Playwright/browser checks, test accounts, seeded data, build/run checks, logs, and documented evidence.
+- Owner inspection happens only after CEO has collected CXX completion records, CTO implementation evidence, CQO evaluator evidence, and any OPS runtime evidence needed to show the goal is genuinely complete.
+- A final Owner report may ask for acceptance review, product judgment, or business approval. It must not ask the Owner to discover whether the software works.
+
 ---
 
-## 4. Mission Flow
+## 5. Mission Flow
 
 ### Goal
 
@@ -91,7 +101,7 @@ Note: A docmeta skip decision on harness documents (ceo.md, cto.md, cqo.md, work
 
 ---
 
-## 5. Harness Runtime
+## 6. Harness Runtime
 
 | Path | Role |
 |---|---|
@@ -109,7 +119,7 @@ Note: A docmeta skip decision on harness documents (ceo.md, cto.md, cqo.md, work
 
 ---
 
-## 6. Hard Rules
+## 7. Hard Rules
 
 1. **No source edit without `{mission}/cto.md`** — CTO scope sign-off is required before any source file is modified.
 2. **No CXX impersonation** — The active model must not act as CEO/CTO/CQO inline. Use installed harness skills in fresh sessions.
@@ -122,10 +132,11 @@ Note: A docmeta skip decision on harness documents (ceo.md, cto.md, cqo.md, work
 9. **No verdict without worker evidence** — CQO cannot issue ACCEPTED/REJECTED without a Worker Evidence Manifest referencing at least one evaluator worker. Self-inspection by CQO is not valid evidence.
 10. **Hierarchical worker ownership** — Hired workers are installed under `.claude/skills/{owning-cxx}/{worker}/` and `.codex/skills/{owning-cxx}/{worker}/`; mission worker reports live under `.harness/documents/{goal-or-child-mission}/{owning-cxx}/workers/`. Flat `{mission}/workers/` reports are legacy and signal an ownership violation unless explicitly migrated.
 11. **Implementation Notes required** — `ceo.md`, every `{cxx}.md`, and every worker report must end with an English `## Implementation Notes` section containing `Design Decisions`, `Deviations`, `Tradeoffs`, and `Open Questions`. Use `None` for empty subsections.
+12. **Owner is final acceptance only** — Owner is not a tester or QA substitute. CEO/CXX must not report "done, please check" until worker-backed verification proves the goal can be completed. Use unit tests, E2E, Playwright, test accounts, seeded data, build/run checks, logs, and CQO evidence before requesting Owner acceptance.
 
 ---
 
-## 7. Project Context
+## 8. Project Context
 
 - **Tech Stack**: {{TECH_STACK}}
 - **Structure**: {{PROJECT_STRUCTURE}}

package/assets/templates/HARNESS.md

@@ -27,6 +27,15 @@ Owner
 
 CEO is the Owner's only internal contact. CEO talks only to CXX agents. CXX agents coordinate, hire, review, and decide; they do not directly produce specialist deliverables.
 
+## Owner Role
+
+Owner is the final acceptance reviewer, not a tester, QA substitute, debugger, or deployment verifier.
+
+- Do not give the Owner broken, unverified, or partially runnable software with "please check this" as the next action.
+- CEO/CXX must use worker-backed verification before requesting Owner acceptance: unit tests, E2E tests, Playwright/browser checks, test accounts, seeded data, build/run checks, logs, CQO evidence, and OPS runtime evidence when relevant.
+- Missing verification is a BLOCKED/FAIL condition, not an Owner task.
+- Final Owner reports may ask for acceptance review, product judgment, or business approval; they must not ask the Owner to discover whether the software works.
+
 ## Runtime Paths
 
 | Path | Role |
@@ -81,6 +90,7 @@ Flat `.harness/documents/{mission}/workers/` reports are legacy. New worker evid
 - CXX agents must not directly execute specialist deliverables.
 - CTO worker dispatch requires `cto.md` first.
 - CQO verdicts require evaluator/tester worker evidence.
+- Owner is final acceptance only. Do not report "done, please check" until worker-backed verification proves the goal is complete.
 - Every `ceo.md`, `{cxx}.md`, and worker report must end with:
 
 ```markdown

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@walwal-harness/cli",
-  "version": "7.1.13",
+  "version": "7.1.14",
   "description": "Company-style AI agent harness for Claude and Codex. Installs commands, CXX agents, skills, HR-Resource hiring pool, and project-local .harness runtime state.",
   "bin": {
     "walwal-harness": "bin/init.js"