okstra 0.34.1 → 0.36.0

package/docs/task-process/error-analysis.md

@@ -0,0 +1,101 @@
+# error-analysis process
+
+## Index
+
+- [1. 목적](#1-목적)
+- [2. okstra-run wizard 흐름](#2-okstra-run-wizard-흐름)
+- [3. prepare_task_bundle 처리](#3-prepare_task_bundle-처리)
+- [4. lead 실행 흐름](#4-lead-실행-흐름)
+- [5. 산출물과 금지선](#5-산출물과-금지선)
+- [6. 확인한 코드](#6-확인한-코드)
+
+## 1. 목적
+
+`error-analysis`는 보고된 error 또는 incident를 분석해 symptom, trigger, root-cause candidate, reproduction gap, validation path를 정리한다. fix 자체나 implementation design을 만드는 phase가 아니다.
+
+## 2. okstra-run wizard 흐름
+
+```mermaid
+flowchart TD
+    Start[/okstra-run/] --> Common[공통 task identity flow]
+    Common --> Type[task-type = error-analysis]
+    Type --> Worktree{active worktree exists?}
+    Worktree -->|yes| Defaults[Use defaults / Customize]
+    Worktree -->|no| BaseRef[base-ref pick/text<br/>main recommended]
+    BaseRef --> Defaults
+    Defaults --> Workers[analysis worker multi-pick]
+    Workers --> D{Use defaults?}
+    D -->|yes| Confirm
+    D -->|customize| M[lead/worker model prompts]
+    M --> X[directive, related tasks, clarification]
+    X --> Confirm
+    Confirm --> Render[render-bundle --render-only]
+```
+
+기본 required roster는 `claude`, `codex`, `report-writer`다. `gemini`는 optional worker이고, 선택하면 analyser set에 들어간다.
+
+## 3. prepare_task_bundle 처리
+
+```mermaid
+sequenceDiagram
+    participant Skill as okstra-run
+    participant Wizard as wizard.py
+    participant Run as prepare_task_bundle
+    participant WT as worktree.py
+    participant Art as artifacts
+
+    Skill->>Wizard: task-type error-analysis selected
+    Wizard-->>Skill: workers/base-ref/model args
+    Skill->>Run: render-bundle --render-only
+    Run->>Run: validate brief/profile
+    Run->>Run: resolve worker roster
+    Run->>WT: provision/reuse worktree
+    Run->>Art: analysis-profile.md includes common contract
+    Run->>Art: task-manifest workflow next=implementation-planning
+```
+
+`workflow.py`의 static next phase는 `implementation-planning`이다. 실제 final report는 더 조사해야 한다고 할 수 있지만, lifecycle상 fix는 바로 가지 않고 planning으로 넘어간다.
+
+## 4. lead 실행 흐름
+
+```mermaid
+flowchart TD
+    Intake[Phase 1 intake] --> Prompts[Phase 2 worker prompts]
+    Prompts --> Team[Phase 3 TeamCreate]
+    Team --> Dispatch[Phase 4/5 dispatch analysers]
+    Dispatch --> Evidence[worker outputs<br/>root-cause hypotheses]
+    Evidence --> Conv[Phase 5.5 convergence<br/>default maxRounds = 2]
+    Conv --> Report[Phase 6 report-writer final report]
+    Report --> Persist[Phase 7 persist + validate]
+```
+
+worker들은 symptom과 evidence를 독립적으로 분석한다. report-writer는 Phase 4/5에 분석하지 않고 Phase 6에서 final report를 작성한다.
+
+## 5. 산출물과 금지선
+
+```mermaid
+flowchart LR
+    Symptom[Symptom] --> Hyp[Root-cause candidates]
+    Hyp --> Gap[Reproduction gaps]
+    Gap --> Validate[Validation path]
+    Validate --> Next[Recommended next diagnostic/planning step]
+    Hyp -. forbidden .-> Fix[Code fix in this run]
+```
+
+final report는 다음을 담아야 한다.
+
+- evidence-backed cause analysis
+- uncertainty boundary
+- practical next diagnostic steps
+- blocking uncertainty가 있으면 `## 5. Clarification Items`, 보통 `Blocks=next-phase`
+
+금지되는 것은 source edit, refactor, fix attempt, implementation design artifact, build/migration/deploy 실행이다. code나 log로 답할 수 있는 ambiguity를 사용자 질문으로 넘기는 것도 profile상 defect다.
+
+## 6. 확인한 코드
+
+- [`prompts/profiles/error-analysis.md`](../../prompts/profiles/error-analysis.md)
+- [`templates/reports/error-analysis-input.template.md`](../../templates/reports/error-analysis-input.template.md)
+- [`scripts/okstra_ctl/workflow.py`](../../scripts/okstra_ctl/workflow.py)
+- [`scripts/okstra_ctl/wizard.py`](../../scripts/okstra_ctl/wizard.py)
+- [`agents/SKILL.md`](../../agents/SKILL.md)
+

package/docs/task-process/final-verification.md

@@ -0,0 +1,167 @@
+# final-verification process
+
+## Index
+
+- [1. 목적](#1-목적)
+- [2. okstra-run wizard 흐름](#2-okstra-run-wizard-흐름)
+- [3. entry gate](#3-entry-gate)
+- [4. 검증 실행 흐름](#4-검증-실행-흐름)
+- [5. verdict와 routing](#5-verdict와-routing)
+- [6. 산출물](#6-산출물)
+- [7. 금지선](#7-금지선)
+- [8. 확인한 코드](#8-확인한-코드)
+
+## 1. 목적
+
+`final-verification`은 `implementation`이 만든 committed diff를 최종 수락할 수 있는지 판정한다. source edit나 follow-up fix를 수행하지 않고, 구현 report와 실제 checkout이 일치하는지 확인한 뒤 acceptance blocker, residual risk, release recommendation을 남긴다.
+
+## 2. okstra-run wizard 흐름
+
+```mermaid
+flowchart TD
+    Start[/okstra-run/] --> Common[공통 task identity flow]
+    Common --> Type[task-type = final-verification]
+    Type --> Worktree{active task worktree?}
+    Worktree -->|yes| Defaults[Use defaults / Customize]
+    Worktree -->|no| BaseRef[base-ref pick/text]
+    BaseRef --> Defaults
+    Defaults -->|defaults| Workers[worker roster pick<br/>claude/codex/report-writer default]
+    Defaults -->|customize| Models[lead + worker model prompts]
+    Models --> Extras[directive, related tasks, clarification]
+    Extras --> Workers
+    Workers --> Confirm[confirmation]
+    Confirm --> Render[render-bundle]
+```
+
+`final-verification`은 analyser roster가 있는 non-implementation phase다. 따라서 `Use defaults`를 골라도 worker roster prompt는 계속 나온다. 기본 required workers는 `claude`, `codex`, `report-writer`이고, `gemini`는 opt-in이다.
+
+## 3. entry gate
+
+```mermaid
+sequenceDiagram
+    participant Lead as Claude lead
+    participant Brief as task brief
+    participant Impl as implementation final-report
+    participant Git as verification worktree
+
+    Lead->>Brief: Source Implementation Report section read
+    Lead->>Impl: required sections present?
+    Lead->>Git: inspect same worktree named by report
+    Lead->>Git: git rev-parse HEAD
+    Lead->>Git: git status --short
+    Lead->>Git: git diff --stat <implementation-base>..HEAD
+    Git-->>Lead: verification target snapshot
+    Lead->>Lead: commit list and diff summary match?
+```
+
+lead는 worker dispatch 전에 verification target을 고정한다. 다음 중 하나라도 실패하면 검증하지 않고 `blocked`로 끝내며 `implementation` 또는 `implementation-planning`으로 되돌린다.
+
+- task brief에 `## Source Implementation Report`가 없다.
+- 인용된 implementation final report가 없거나 필수 section이 빠져 있다.
+- report가 named worktree를 가리키는데 lead가 다른 checkout을 보고 있다.
+- implementation report의 commit list / diff summary와 현재 checkout이 맞지 않는다.
+- delivered code change commit이 없다.
+
+## 4. 검증 실행 흐름
+
+```mermaid
+flowchart TD
+    Gate[entry gate passed] --> Lead[Claude lead fixes target snapshot]
+    Lead --> CW[Claude verifier<br/>read-only]
+    Lead --> XW[Codex verifier<br/>read-only]
+    Lead --> GW{Gemini opt-in?}
+    GW -->|yes| Gemini[Gemini verifier<br/>read-only]
+    GW -->|no| Collect
+    CW --> Collect[collect independent findings]
+    XW --> Collect
+    Gemini --> Collect
+    Collect --> Conv[convergence<br/>default max rounds = 2]
+    Conv --> Writer[report-writer final synthesis]
+    Writer --> SelfReview[lead self-review<br/>verdict, blockers, coverage, no-mutation]
+    SelfReview --> Persist[final report + manifests]
+```
+
+검증 command는 자동 추측하지 않는다. 독립 재검증이 필요하면 command source는 두 tier뿐이다.
+
+```mermaid
+flowchart LR
+    Need[needs validation command] --> Tier1{task brief / approved plan<br/>validation set?}
+    Tier1 -->|yes| Deny[Deny-list self-check]
+    Tier1 -->|no| Tier2{project.json<br/>qaCommands?}
+    Tier2 -->|yes| Deny
+    Tier2 -->|no| Missing[record<br/>qa-command not configured]
+    Deny -->|clean| Run[execute read-only command]
+    Deny -->|denied token| Reject[record rejected command<br/>do not execute]
+```
+
+`implementation` runtime은 `qaCommands` deny-list를 prepare 단계에서 검증하지만, `final-verification`은 그 fail-fast gate가 없다. profile contract상 lead가 실행 직전에 직접 deny-list를 self-check해야 한다.
+
+## 5. verdict와 routing
+
+```mermaid
+flowchart TD
+    Verdict{Verdict Token}
+    Verdict -->|accepted| Release[route to release-handoff or done]
+    Verdict -->|conditional-accept| Conditions[conditions listed exhaustively]
+    Conditions --> Followup[route to error-analysis or implementation-planning]
+    Verdict -->|blocked| Blockers[acceptance blockers with evidence]
+    Blockers --> Followup
+```
+
+`## 2. Final Verdict`에는 `Verdict Token` field가 정확히 하나 들어가야 하며 값은 다음 셋 중 하나다.
+
+- `accepted`: release-handoff로 넘겨도 되는 상태
+- `conditional-accept`: 조건을 모두 명시해야 하며, 조건이 gate면 다음 phase를 막는다
+- `blocked`: acceptance blocker가 있어 release-handoff로 갈 수 없는 상태
+
+애매한 표현인 "looks good", "mostly ready"는 허용되지 않는다.
+
+## 6. 산출물
+
+```mermaid
+flowchart TD
+    Snapshot[base/head SHA<br/>status + diff stat] --> Report[final-verification final report]
+    Source[Source Implementation Report<br/>path + quoted commit/diff] --> Report
+    Coverage[requirement coverage<br/>artifact per requirement] --> Report
+    Blockers[acceptance blockers] --> Report
+    Risks[residual risks] --> Report
+    Commands[read-only command log] --> Report
+    Report --> Route[routing recommendation]
+```
+
+final report에는 최소 다음이 필요하다.
+
+- originating implementation final-report path
+- inspected worktree path
+- implementation base ref와 run start head SHA
+- quoted commit list / diff summary
+- `Verdict Token`
+- blocker table 또는 `No acceptance blockers found.`
+- residual risk와 escalation trigger
+- requirement별 coverage artifact
+- read-only command log와 exit code
+- 다음 safe phase recommendation
+
+## 7. 금지선
+
+```mermaid
+flowchart TD
+    FV[final-verification] --> Allowed[read-only inspect/test/validate]
+    FV -. forbidden .-> Edit[source edit or config edit]
+    FV -. forbidden .-> Fix[in-run bug fix]
+    FV -. forbidden .-> Mutate[mutating command]
+    FV -. forbidden .-> Expand[scope expansion]
+    FV -. forbidden .-> Hide[hide verifier dissent]
+```
+
+source edit, follow-up fix, scope expansion은 전부 금지다. 결함을 발견하면 현재 run 안에서 고치지 않고 final report에 blocker로 기록한 뒤 새 `error-analysis` 또는 `implementation-planning` 입력으로 넘긴다.
+
+## 8. 확인한 코드
+
+- [`prompts/profiles/final-verification.md`](../../prompts/profiles/final-verification.md)
+- [`templates/reports/final-verification-input.template.md`](../../templates/reports/final-verification-input.template.md)
+- [`scripts/okstra_ctl/wizard.py`](../../scripts/okstra_ctl/wizard.py)
+- [`scripts/okstra_ctl/run.py`](../../scripts/okstra_ctl/run.py)
+- [`scripts/okstra_ctl/workflow.py`](../../scripts/okstra_ctl/workflow.py)
+- [`scripts/okstra_ctl/render.py`](../../scripts/okstra_ctl/render.py)
+- [`agents/SKILL.md`](../../agents/SKILL.md)

package/docs/task-process/implementation-planning.md

@@ -0,0 +1,128 @@
+# implementation-planning process
+
+## Index
+
+- [1. 목적](#1-목적)
+- [2. okstra-run wizard 흐름](#2-okstra-run-wizard-흐름)
+- [3. prepare_task_bundle 처리](#3-prepare_task_bundle-처리)
+- [4. lead 실행 흐름](#4-lead-실행-흐름)
+- [5. final report gate](#5-final-report-gate)
+- [6. 금지선](#6-금지선)
+- [7. 확인한 코드](#7-확인한-코드)
+
+## 1. 목적
+
+`implementation-planning`은 coding 전에 구현 방향을 정하는 phase다. 최소 두 개의 implementation option, trade-off, recommended option, stepwise execution order, validation checklist, rollback strategy를 만들고 사용자 approval gate를 둔다.
+
+## 2. okstra-run wizard 흐름
+
+```mermaid
+flowchart TD
+    Start[/okstra-run/] --> Common[공통 task identity flow]
+    Common --> Type[task-type = implementation-planning]
+    Type --> Worktree{active task worktree?}
+    Worktree -->|yes| Defaults[Use defaults / Customize]
+    Worktree -->|no| BaseRef[base-ref pick/text]
+    BaseRef --> Defaults
+    Defaults --> Workers[worker multi-pick<br/>claude/codex + optional gemini]
+    Workers --> Branch{customize?}
+    Branch -->|no| Confirm
+    Branch -->|yes| Models[lead, claude, codex, gemini if selected, report-writer models]
+    Models --> Extras[directive, related tasks, clarification]
+    Extras --> Confirm
+    Confirm --> Render[render-bundle]
+```
+
+wizard는 현재 `--no-plan-verification`을 묻지 않는다. okstra-run 경로에서는 plan-body verification이 기본 enabled로 준비된다. shell/CLI 경로에는 `--no-plan-verification` flag가 있다.
+
+## 3. prepare_task_bundle 처리
+
+```mermaid
+sequenceDiagram
+    participant W as wizard/render-bundle
+    participant P as prepare_task_bundle
+    participant R as render.py
+    participant M as manifests
+
+    W->>P: task-type=implementation-planning
+    P->>P: validate profile/brief/base-ref
+    P->>P: resolve profile workers + optional override
+    P->>P: resolve model metadata
+    P->>P: provision/reuse task worktree
+    P->>R: _build_convergence_block()
+    R-->>M: convergence.planBodyVerification.enabled=true
+    P->>M: workflow nextRecommendedPhase=implementation
+    P-->>W: prepared lead prompt
+```
+
+runtime prepare 단계는 source edit를 막는 것이 아니라 "현재 phase boundary를 lead prompt와 manifest에 박아 넣는" 방식이다. 실제 no-edit/no-build 규칙은 lead와 worker가 profile을 읽고 지켜야 한다.
+
+## 4. lead 실행 흐름
+
+```mermaid
+flowchart TD
+    P1[Phase 1 intake] --> P2[Phase 2 prompts]
+    P2 --> P3[Phase 3 TeamCreate]
+    P3 --> P4[Phase 4/5 analyser dispatch]
+    P4 --> C[Phase 5.5 finding convergence]
+    C --> RW[Phase 6 report-writer writes draft]
+    RW --> PBV[Phase 6 sub-step<br/>Plan Body Verification]
+    PBV --> Gate{gate result}
+    Gate -->|passed / passed-with-dissent| Approval[render top Approval checkbox]
+    Gate -->|blocked-by-disagreement / aborted-non-result| NoApproval[render block without checkbox]
+    Approval --> P7[Phase 7 persist]
+    NoApproval --> P7
+```
+
+Plan-body verification은 Phase 5.5와 다른 queue를 쓴다. Phase 5.5는 worker finding을 검증하고, Phase 6 sub-step은 report-writer가 만든 consolidated plan body를 `P-*` plan item 단위로 다시 검증한다.
+
+## 5. final report gate
+
+```mermaid
+flowchart LR
+    Options[Option Candidates] --> Matrix[Trade-off Matrix]
+    Matrix --> Rec[Recommended Option]
+    Rec --> Steps[Stepwise Execution Order]
+    Steps --> Dep[Dependency / Migration Risk]
+    Dep --> Val[Validation Checklist]
+    Val --> Rb[Rollback Strategy]
+    Rb --> Verify[Plan Body Verification]
+    Verify --> Approval[User Approval Request]
+    Approval --> Impl[Next run: implementation]
+```
+
+validator가 section heading의 영문 substring을 찾기 때문에 다음 문자열은 heading line에 그대로 남아야 한다.
+
+- `Option Candidates`
+- `Trade-off`
+- `Recommended Option`
+- `Stepwise Execution Order`
+- `Dependency`
+- `Validation Checklist`
+- `Rollback`
+- `User Approval Request`
+
+approval marker는 top-of-report `User Approval Request` block의 `- [ ] Approved` line이다. 사용자가 `- [x] Approved`로 바꿔야 implementation run이 시작된다. `Blocks=approval` clarification row가 unresolved이면 approved marker가 있어도 implementation prepare에서 거부된다.
+
+## 6. 금지선
+
+```mermaid
+flowchart TD
+    Plan[planning output] --> OK[reports/prompts/state/manifests only]
+    Plan -. forbidden .-> Code[source code edit]
+    Plan -. forbidden .-> Build[build/test/migration/deploy execution]
+    Plan -. forbidden .-> ExternalDocs[docs/superpowers plans/specs write]
+    Plan -. forbidden .-> NextPhase[start implementation in same run]
+```
+
+이 phase는 plan document만 만든다. code-level micro-optimization, source edit, build, migration, deployment, run artifact directory 밖 write는 금지된다.
+
+## 7. 확인한 코드
+
+- [`prompts/profiles/implementation-planning.md`](../../prompts/profiles/implementation-planning.md)
+- [`templates/reports/implementation-planning-input.template.md`](../../templates/reports/implementation-planning-input.template.md)
+- [`templates/reports/final-report.template.md`](../../templates/reports/final-report.template.md)
+- [`scripts/okstra_ctl/render.py`](../../scripts/okstra_ctl/render.py)
+- [`validators/validate-run.py`](../../validators/validate-run.py)
+- [`agents/SKILL.md`](../../agents/SKILL.md)
+

package/docs/task-process/implementation.md

@@ -0,0 +1,149 @@
+# implementation process
+
+## Index
+
+- [1. 목적](#1-목적)
+- [2. okstra-run wizard 흐름](#2-okstra-run-wizard-흐름)
+- [3. runtime gate](#3-runtime-gate)
+- [4. executor와 verifier](#4-executor와-verifier)
+- [5. stage와 consumers](#5-stage와-consumers)
+- [6. 산출물](#6-산출물)
+- [7. 금지선](#7-금지선)
+- [8. 확인한 코드](#8-확인한-코드)
+
+## 1. 목적
+
+`implementation`은 승인된 `implementation-planning` final report를 실제 code change와 local commit으로 실행한다. 이 phase에서만 source edit가 허용되지만, scope는 approved plan과 recorded out-of-plan justification으로 제한된다.
+
+## 2. okstra-run wizard 흐름
+
+```mermaid
+flowchart TD
+    Start[/okstra-run/] --> Common[공통 task identity flow]
+    Common --> Type[task-type = implementation]
+    Type --> Worktree{active task worktree?}
+    Worktree -->|yes| PlanPick[approved plan pick/text]
+    Worktree -->|no| BaseRef[base-ref pick/text]
+    BaseRef --> PlanPick
+    PlanPick --> Approved{APPROVED marker present?}
+    Approved -->|no| Retry[re-prompt same step]
+    Approved -->|yes| Stage[stage pick<br/>auto or number]
+    Stage --> Executor[executor pick<br/>claude/codex/gemini]
+    Executor --> Defaults[Use defaults / Customize]
+    Defaults -->|defaults| Confirm
+    Defaults -->|customize| Models[lead + executor model + report-writer model]
+    Models --> Extras[directive, related tasks, clarification]
+    Extras --> Confirm
+    Confirm --> Render[render-bundle]
+```
+
+`implementation`은 worker override 질문이 없다. wizard `render_args()`가 `workers`를 빈 문자열로 내보내고, runtime이 profile default roster를 사용한다. 현재 okstra-run wizard 경로는 승인 checkbox를 직접 flip하는 `--approve`를 노출하지 않는다. plan file에는 이미 recognized approval marker가 있어야 한다.
+
+## 3. runtime gate
+
+```mermaid
+sequenceDiagram
+    participant W as okstra-run
+    participant P as prepare_task_bundle
+    participant Plan as approved final-report
+    participant QA as project.json qaCommands
+    participant Stage as stage validator
+
+    W->>P: task-type=implementation, approved-plan, stage, executor
+    P->>Plan: file exists?
+    P->>Plan: approval marker regex matches?
+    P->>Plan: unresolved Blocks=approval rows?
+    P->>Stage: validate stage structure
+    P->>QA: validate qaCommands deny-list
+    P->>P: executor provider in resolved roster?
+    P->>P: provision/reuse worktree
+    P-->>W: prepared implementation prompt or PrepareError
+```
+
+`--approve`는 Python runtime에 존재하지만 okstra-run wizard가 args로 내보내지 않는다. shell path에서는 `--approve`가 unchecked approval line을 flip하고 audit line을 붙인 뒤 같은 validation path를 탄다.
+
+## 4. executor와 verifier
+
+```mermaid
+flowchart TD
+    Lead[Claude lead] --> Exec[Executor<br/>selected provider]
+    Lead --> CV[Claude verifier<br/>read-only]
+    Lead --> XV[Codex verifier<br/>read-only]
+    Lead --> GV{Gemini in roster?}
+    GV -->|yes| Gem[Gemini verifier<br/>read-only]
+    Exec --> Diff[Source edits + local commits]
+    CV --> QA[Independent QA rerun]
+    XV --> QA
+    Gem --> QA
+    QA --> Verdict[PASS / CONCERNS / FAIL]
+    Verdict --> Report[Final report preserves dissent]
+```
+
+Executor만 project file을 mutate할 수 있다. verifier는 같은 worktree에서 read-only로 diff와 validation command를 독립 재실행한다. executor와 같은 provider도 verifier로 별도 fresh CLI session에서 다시 실행된다. 같은 session이 쓴 diff를 같은 session이 승인하는 구조를 막기 위함이다.
+
+## 5. stage와 consumers
+
+```mermaid
+flowchart LR
+    Plan[approved plan<br/>Stage Map] --> Parse[parse stage map]
+    Parse --> Done[read consumers.jsonl<br/>done stages]
+    Done --> Resolve{stage arg}
+    Resolve -->|auto| Next[lowest unblocked unfinished stage]
+    Resolve -->|number| Forced[selected stage]
+    Next --> Started[append consumer status=started]
+    Forced --> Started
+    Started --> Run[implementation executes selected stage]
+```
+
+stage 선택은 `auto` 또는 숫자다. 다른 task-type에서 `--stage`가 오면 `PrepareError`다. wizard는 approved plan에서 Stage Map을 parse해 stage picker에 `auto`와 각 stage를 보여준다.
+
+## 6. 산출물
+
+```mermaid
+flowchart TD
+    Code[Commits] --> Report[implementation final report]
+    Diff[git diff --stat base..HEAD] --> Report
+    TDD[TDD evidence] --> Report
+    Validation[Validation evidence<br/>actual output + exit code] --> Report
+    Verifiers[Verifier results<br/>command logs + verdicts] --> Report
+    Rollback[Rollback verification] --> Report
+    Report --> Next[Routing recommendation<br/>final-verification or loop back]
+```
+
+final report에는 최소 다음이 필요하다.
+
+- approved plan path와 quoted approval marker
+- commit SHA, message, plan step mapping
+- diff summary와 per-file summary
+- out-of-plan edits block
+- plan validation command의 실제 stdout/stderr와 exit code
+- TDD failing-then-passing evidence
+- verifier별 independent validation rerun result
+- rollback verification
+- follow-up tasks table
+
+## 7. 금지선
+
+```mermaid
+flowchart TD
+    Impl[implementation] --> Allowed[local edit/write/build/test/git add/git commit]
+    Impl -. forbidden .-> Push[git push]
+    Impl -. forbidden .-> Publish[publish/release/deploy]
+    Impl -. forbidden .-> RealDB[real DB migration or non-local datastore write]
+    Impl -. forbidden .-> VerifierWrite[verifier edit/write]
+    Impl -. forbidden .-> Scope[silent scope expansion]
+    Impl -. forbidden .-> Acceptance[declaring final acceptance]
+```
+
+이 phase는 final acceptance를 선언하지 않는다. ready for final-verification 또는 needs new loop만 말한다.
+
+## 8. 확인한 코드
+
+- [`prompts/profiles/implementation.md`](../../prompts/profiles/implementation.md)
+- [`templates/reports/implementation-input.template.md`](../../templates/reports/implementation-input.template.md)
+- [`scripts/okstra_ctl/run.py`](../../scripts/okstra_ctl/run.py)
+- [`scripts/okstra_ctl/wizard.py`](../../scripts/okstra_ctl/wizard.py)
+- [`validators/validate-implementation-plan-stages.py`](../../validators/validate-implementation-plan-stages.py)
+- [`scripts/okstra_ctl/qa_commands.py`](../../scripts/okstra_ctl/qa_commands.py)
+- [`agents/SKILL.md`](../../agents/SKILL.md)
+