@kodevibe/harness 0.9.1 → 0.9.5

package/README.ko.md

@@ -93,7 +93,7 @@ kode:harness는 세 가지 메커니즘으로 해결합니다:
 | 🧭 **Navigation Dispatcher** | 5개 파이프라인을 따라 다음 단계 프롬프트를 자동 안내 |
 | 📝 **상태 영속성** | LLM 세션 간 프로젝트 지식을 유지하는 5개 마크다운 파일 |
 | 🔄 **5개 파이프라인** | 🟢 신규 → 🔵 계속 → 🔴 버그 수정 → 🟡 방향 전환 → 🟣 Crew 기반 |
-| 🛠️ **10개 스킬** | 단계별 절차: setup, debug, breakdown, review, pivot 등 |
+| 🛠️ **11개 스킬** | 단계별 절차: setup, debug, breakdown, review, pivot, state-check 등 |
 | 🤖 **4개 에이전트** | 역할 기반 페르소나: pm, reviewer, lead, architect |
 | ⚠️ **실패 패턴** | 세션 간 같은 실수를 방지하는 프로젝트별 실패 기록 |
 | 📋 **Decision Log** | 결정의 이유를 기록해 LLM이 확정된 사항을 재논의하지 않도록 방지 |
@@ -115,11 +115,11 @@ npx @kodevibe/harness validate  # state 파일에 실제 내용 확인
 | IDE | 디스패처 (always-on) | 스킬 | 에이전트 |
 |-----|---------------------|------|----------|
 | **VS Code Copilot** | `.github/copilot-instructions.md` | `.github/skills/*/SKILL.md` | `.github/agents/*.agent.md` |
-| **Claude Code** | `.claude/rules/core.md` | `.claude/skills/*/SKILL.md` | `.claude/agents/*.md` |
-| **Cursor** | `.cursor/rules/core.mdc` | `.cursor/skills/*/SKILL.md` | `.cursor/agents/*.md` |
+| **Claude Code** | `CLAUDE.md` (+ `.claude/rules/core.md`) | `.claude/skills/*/SKILL.md` | `.claude/agents/*.md` |
+| **Cursor** | `.cursor/rules/core.mdc` (+ `AGENTS.md`) | `.agents/skills/*/SKILL.md` (cross-tool) | `.cursor/rules/<agent>.mdc` |
 | **Codex** | `AGENTS.md` | `.agents/skills/*/SKILL.md` | `.codex/agents/*.toml` |
 | **Windsurf** | `.windsurf/rules/core.md` | `.windsurf/skills/*/SKILL.md` | *(스킬로 설치)* |
-| **Antigravity** | `GEMINI.md` | `.gemini/skills/*/SKILL.md` | `.gemini/agents/*.md` |
+| **Antigravity** | `AGENTS.md` | `.agents/skills/*/SKILL.md` (cross-tool) | `.agents/rules/<agent>.md` |
 
 모든 IDE에 `docs/` 디렉토리에 State 파일(`project-state.md`, `project-brief.md`, `features.md`, `failure-patterns.md`, `dependency-map.md`)도 함께 설치됩니다.
 
@@ -244,7 +244,7 @@ npx @kodevibe/harness init --team
 
 ## Iron Laws
 
-8개 규칙이 모든 스킬과 에이전트에 적용됩니다. kode:harness로 관리되는 프로젝트의 품질 근간을 형성합니다.
+10개 규칙이 모든 스킬과 에이전트에 적용됩니다. kode:harness로 관리되는 프로젝트의 품질 근간을 형성합니다.
 
 | # | 규칙 | 적용 대상 |
 |---|------|----------|
@@ -292,7 +292,7 @@ Bootstrap이 `docs/crew/`, `docs/PM/`, `docs/Analyst/`, `docs/ARB/`에서 crew
 | 의존성 | Node 20+ | Bun + Node + Playwright | Node 18+ | **Zero** |
 | IDE 지원 | 20+ (installer) | 5 (setup --host) | 13 (runtime select) | 6 (네이티브 포맷) |
 | 방향 관리 | ❌ | ❌ | ❌ | ✅ (Direction Guard + pivot + Decision Log) |
-| Iron Laws (코드 품질 규칙) | ❌ | ❌ | ❌ | ✅ (8개 규칙이 스킬에 임베딩) |
+| Iron Laws (코드 품질 규칙) | ❌ | ❌ | ❌ | ✅ (10개 규칙이 스킬에 임베딩) |
 | Cold start | ❌ | ❌ | `/gsd-new-project` | ✅ (`setup` 스킬) |
 | 태스크당 컨텍스트 | 4-6 파일 | 1 파일 | 매번 200k 플랜 | **2-3 파일 (136줄 디스패처)** |
 
@@ -300,7 +300,7 @@ Bootstrap이 `docs/crew/`, `docs/PM/`, `docs/Analyst/`, `docs/ARB/`에서 crew
 
 ## 로드맵
 
-kode:harness는 현재 **v0.9.0** — 네이밍 재설계 완료, 6개 IDE 지원, Navigation Dispatcher와 Crew Artifact Integration 안정화.
+kode:harness는 현재 **v0.9.5** — 경량성 예산 재교정(40K/1500/2500), reviewer.md의 Iron Laws 정합성 수정, `harness/core-rules.md` ↔ `.github/copilot-instructions.md` 디스패처 동기화. v0.9.4는 6개 IDE 어댑터 공식 문서 정합(Antigravity `.agents/`, Codex `.toml`, Cursor `.cursor/rules/`).
 
 | 단계 | 버전 | 상태 | 초점 |
 |------|------|------|------|
@@ -308,7 +308,10 @@ kode:harness는 현재 **v0.9.0** — 네이밍 재설계 완료, 6개 IDE 지
 | **Hardening** | v0.6.5 | ✅ 완료 | 10 스킬, 4 에이전트, Iron Laws, CLI batch/doctor/validate, 방향 드리프트 감지 |
 | **Flexibility** | v0.7.x | ✅ 완료 | 팀 컨벤션을 project-brief.md에 위임, prescriptive 규칙 제거 |
 | **Navigation** | v0.8.x | ✅ 완료 | 🧭 Navigation Dispatcher, 5개 파이프라인, Crew Artifact Integration, 100점 품질 감사, Confirm-First 게이트, Wave-Level Pacing, Recalculating Mode |
-| **Naming** | v0.9.0 | ✅ 현재 | 스킬/에이전트 네이밍 재설계 — 직관성과 발견성 강화 |
+| **Naming** | v0.9.0 | ✅ 완료 | 스킬/에이전트 네이밍 재설계 — 직관성과 발견성 강화 |
+| **Self-Verify** | v0.9.2 | ✅ 완료 | state-check 스킬, Iron Law #10, Confirmation Gate Defaults, 멀티 IDE 수정, CI Artifact Index |
+| **IDE Realignment** | v0.9.4 | ✅ 완료 | 6개 IDE 어댑터 공식 문서 정합; Antigravity `.agents/`, Codex `.toml`, Cursor `.cursor/rules/`; release 스킬 Step 6.5 + qa-check.sh §10 회귀 가드 |
+| **Consistency & Budget** | v0.9.5 | ✅ 현재 | reviewer.md Iron Laws stale 수정, 디스패처 동기화, 경량성 예산 재교정(40K/1500/2500) 및 근거 기록 |
 | **Validation** | v1.0 | 🔜 다음 | 실사용 검증, 사용자 피드백 수집 |
 
 ### 다음 단계

package/README.md

@@ -93,7 +93,7 @@ kode:harness solves this with three mechanisms:
 | 🧭 **Navigation Dispatcher** | Turn-by-Turn navigation through 5 pipelines with copy-paste next-step prompts |
 | 📝 **State Persistence** | 5 markdown files that persist project knowledge across LLM sessions |
 | 🔄 **5 Pipelines** | 🟢 New Dev → 🔵 Continue → 🔴 Bug Fix → 🟡 Direction Change → 🟣 Crew-Driven |
-| 🛠️ **10 Skills** | Step-by-step procedures: setup, debug, breakdown, review, pivot, and more |
+| 🛠️ **11 Skills** | Step-by-step procedures: setup, debug, breakdown, review, pivot, state-check, and more |
 | 🤖 **4 Agents** | Role-based personas: pm, reviewer, lead, architect |
 | ⚠️ **Failure Patterns** | Project-specific failure log that prevents repeat mistakes across sessions |
 | 📋 **Decision Log** | Records why decisions were made so LLMs don't re-debate settled choices |
@@ -113,11 +113,11 @@ npx @kodevibe/harness validate  # verify state files have real content
 | IDE | Dispatcher (always-on) | Skills | Agents |
 |-----|----------------------|--------|--------|
 | **VS Code Copilot** | `.github/copilot-instructions.md` | `.github/skills/*/SKILL.md` | `.github/agents/*.agent.md` |
-| **Claude Code** | `.claude/rules/core.md` | `.claude/skills/*/SKILL.md` | `.claude/agents/*.md` |
-| **Cursor** | `.cursor/rules/core.mdc` | `.cursor/skills/*/SKILL.md` | `.cursor/agents/*.md` |
+| **Claude Code** | `CLAUDE.md` (+ `.claude/rules/core.md`) | `.claude/skills/*/SKILL.md` | `.claude/agents/*.md` |
+| **Cursor** | `.cursor/rules/core.mdc` (+ `AGENTS.md`) | `.agents/skills/*/SKILL.md` (cross-tool) | `.cursor/rules/<agent>.mdc` |
 | **Codex** | `AGENTS.md` | `.agents/skills/*/SKILL.md` | `.codex/agents/*.toml` |
 | **Windsurf** | `.windsurf/rules/core.md` | `.windsurf/skills/*/SKILL.md` | *(agents installed as skills)* |
-| **Antigravity** | `GEMINI.md` | `.gemini/skills/*/SKILL.md` | `.gemini/agents/*.md` |
+| **Antigravity** | `AGENTS.md` | `.agents/skills/*/SKILL.md` (cross-tool) | `.agents/rules/<agent>.md` |
 
 All IDEs also get state files (`project-state.md`, `project-brief.md`, `features.md`, `failure-patterns.md`, `dependency-map.md`) in the `docs/` directory.
 
@@ -218,7 +218,7 @@ npx @kodevibe/harness init --team
 
 ## Iron Laws
 
-These 8 rules are enforced across all skills and agents. They form the quality backbone of every kode:harness project managed with harness engineering.
+These 10 rules are enforced across all skills and agents. They form the quality backbone of every kode:harness project managed with harness engineering.
 
 | # | Law | Enforced By |
 |---|-----|-------------|
@@ -268,13 +268,13 @@ Original crew documents are **never modified**. Only the index and tracker are c
 | Dependencies | Node 20+ | Bun + Node + Playwright | Node 18+ | Zero |
 | IDE support | 20+ (installer) | 5 (setup --host) | 13 (runtime select) | 6 (native format) |
 | Direction management | ❌ | ❌ | ❌ | ✅ (Direction Guard + pivot + Decision Log) |
-| Iron Laws (code quality rules) | ❌ | ❌ | ❌ | ✅ (8 laws embedded in skills) |
+| Iron Laws (code quality rules) | ❌ | ❌ | ❌ | ✅ (10 laws embedded in skills) |
 | Cold start | ❌ | ❌ | `/gsd-new-project` | ✅ (`setup` skill) |
 | Context per task | 4-6 files | 1 file | Fresh 200k per plan | 2-3 files (136-line dispatcher) |
 
 ## Roadmap
 
-kode:harness is at **v0.9.0** — naming redesign complete, 6 IDE support, Navigation Dispatcher and Crew Artifact Integration stable.
+kode:harness is at **v0.9.5** — lightness budget recalibrated (40K/1500/2500), Iron Laws consistency fix in reviewer.md, dispatcher synchronization between `harness/core-rules.md` and `.github/copilot-instructions.md`. v0.9.4 brought all 6 IDE adapters into alignment with official documentation (Antigravity `.agents/`, Codex `.toml`, Cursor `.cursor/rules/`).
 
 | Phase | Version | Status | Focus |
 |---|---|---|---|
@@ -282,7 +282,10 @@ kode:harness is at **v0.9.0** — naming redesign complete, 6 IDE support, Navig
 | **Hardening** | v0.6.5 | ✅ Done | 10 skills, 4 agents, Iron Laws, CLI batch/doctor/validate, merge conflict SOP, direction drift detection |
 | **Flexibility** | v0.7.x | ✅ Done | Delegate team conventions to project-brief.md, remove prescriptive rules |
 | **Navigation** | v0.8.x | ✅ Done | 🧭 Navigation Dispatcher, 5 Pipelines, Crew Artifact Integration, 100-point quality audit, Confirm-First gate, Wave-Level Pacing, Recalculating Mode |
-| **Naming** | v0.9.0 | ✅ Current | Skill/agent naming redesign for clarity and discoverability |
+| **Naming** | v0.9.0 | ✅ Done | Skill/agent naming redesign for clarity and discoverability |
+| **Self-Verify** | v0.9.2 | ✅ Done | state-check skill, Iron Law #10, Confirmation Gate Defaults, multi-IDE fix, CI Artifact Index |
+| **IDE Realignment** | v0.9.4 | ✅ Done | All 6 IDE adapters aligned with official docs; Antigravity `.agents/`, Codex `.toml`, Cursor `.cursor/rules/`; release skill Step 6.5 + qa-check.sh §10 regression guards |
+| **Consistency & Budget** | v0.9.5 | ✅ Current | Iron Laws stale-copy fix (reviewer.md), dispatcher sync (core-rules.md ↔ copilot-instructions.md), lightness budgets recalibrated (40K/1500/2500) with rationale |
 | **Validation** | v1.0 | 🔜 Next | Real-world project adoption, user feedback collection |
 
 ### What's Next

package/harness/agents/pm.md

@@ -61,8 +61,6 @@ Read `docs/agent-memory/pm.md` for past learnings:
 
 Apply these insights when creating the implementation plan. If the memory file is empty or contains only placeholders, skip this step.
 
-> **Team Mode**: In Team mode, agent memory is personal (`.harness/agent-memory/`). Each developer accumulates their own planning insights.
-
 ### Step 0.7: Feature Roadmap Planning (Draft & Correct)
 
 **Trigger**: `docs/project-brief.md`에 `## Feature Roadmap` 섹션이 없을 때
@@ -87,12 +85,9 @@ Apply these insights when creating the implementation plan. If the memory file i
    - [ ] F-004: ...
    ```
 3. 사용자에게 초안을 제시한다: **"이 Feature Roadmap을 검토하고, 추가/삭제/순서 변경을 알려주세요."**
-   > **물어보지 말고, 초안을 만들어서 교정받는다.** 빈 칸을 채우는 것보다 틀린 것을 고치는 것이 쉽다.
 4. 사용자 교정을 반영한 최종 Roadmap을 `docs/project-brief.md`에 `## Feature Roadmap` 섹션으로 기록한다
 5. Feature Roadmap이 확정되면 아래 "For New Feature" 절차로 진행한다
 
-> **pivot 이후**: pivot이 `project-brief.md`를 업데이트하면, pm은 변경된 Roadmap을 읽고 Checkpoint에서 반영한다.
-
 ### For New Feature
 
 1. Read `docs/project-brief.md` to understand project vision, goals, **non-goals**, and **Decision Log**
@@ -133,12 +128,11 @@ Apply these insights when creating the implementation plan. If the memory file i
    If no Crew Artifact Index → proceed with normal user-driven planning below.
 <!-- CREW_MODE_END -->
 
-3. **Direction Alignment**: Verify the requested feature against three checkpoints.
-   > This check intentionally duplicates architect’s direction validation (Step 2). The redundancy is by design: architect validates STRUCTURAL proposals (module boundaries, layer rules), while pm validates FEATURE-level alignment (goals, non-goals, decisions). When both are used in the same session, this provides defense-in-depth.
-   - **Goal Alignment**: Does it serve a listed Goal? If no clear link → **warn but proceed**. Include the warning in the plan output under a `### Direction Alignment` section: `⚠️ Goal Alignment: [feature] does not directly map to listed goals`.
-   - **Non-Goal Violation**: Does it fall into Non-Goals? If yes → **stop and ask the user**. Do not proceed until the user confirms this is intentional (may need `pivot` skill).
-   - **Decision Consistency**: Does it contradict any Decision Log entry? If yes → **stop and warn**. Recommend running the `pivot` skill before proceeding.
-   If the request represents a clear direction change → **stop and require the `pivot` skill** before proceeding with any planning. Do not proceed even if the user insists — direction changes must be formally tracked.
+3. **Direction Alignment**: Verify against three checkpoints (architect validates STRUCTURE; pm validates FEATURE-level alignment):
+   - **Goal Alignment**: Serves a listed Goal? If no clear link → **warn but proceed**. Add `⚠️ Goal Alignment: [feature] does not directly map to listed goals` under `### Direction Alignment` in the plan output.
+   - **Non-Goal Violation**: Falls into Non-Goals? → **stop and ask the user**. May need `pivot`.
+   - **Decision Consistency**: Contradicts a Decision Log entry? → **stop and warn**. Recommend `pivot`.
+   If the request represents a clear direction change → **stop and require `pivot`** before planning. Do not proceed even if the user insists.
 3. Read `docs/features.md` to understand what already exists
 4. Read `docs/dependency-map.md` to understand current architecture
 5. Read `docs/project-state.md` for current Sprint context
@@ -153,7 +147,7 @@ Apply these insights when creating the implementation plan. If the memory file i
 13. **After user approves** → Update `docs/project-state.md` with the new Story
 14. **After user approves** → Update `docs/features.md` with the new feature entry
 
-> **State File Write Deferral**: Steps 13-14 execute ONLY after user confirms the plan. If the user rejects or requests changes, no state files are modified — the plan is revised and re-presented. This prevents state file pollution from rejected plans.
+State file writes (Steps 13-14) execute ONLY after user approval. Rejected plans never touch state.
 
 ### For Architecture Query
 
@@ -187,8 +181,6 @@ After producing ANY plan (New Feature, Refactor, or Crew-Driven), **do NOT proce
 4. **Only after approval** → execute **MANDATORY State File Write** (below), then output 🧭 Next Step pointing to `lead`
 5. If the user requests changes → revise the plan and re-confirm. **No state files are written until approval.**
 
-> **Why**: The pm is planning a route, not driving. The user must confirm the route before the engine starts. This prevents irreversible code changes based on a misunderstood plan.
-
 ### ⚠️ MANDATORY: Post-Approval State File Write
 
 **This section executes IMMEDIATELY after user approval. Do NOT skip. Do NOT output the 🧭 Next Step block until ALL writes below are complete.**
@@ -226,6 +218,14 @@ After user approves the plan, perform these writes in order:
 
 If any write fails, report the failure and retry. Do NOT proceed to 🧭 with incomplete state files.
 
+### ✅ MANDATORY: Self-Verify with state-check (Iron Law #10)
+
+After the Post-Approval state writes complete, run the `state-check` skill:
+1. Invoke `state-check` skill — deterministic verification of state file consistency
+2. If state-check returns **PASS** → proceed to output 🧭 Next Step
+3. If state-check returns **WARN** → include the warnings in the plan output, then proceed
+4. If state-check returns **FAIL** → do NOT output STATUS: DONE. Fix the listed drift, then re-run state-check.
+
 ## Output Format
 
 ### New Feature Plan
@@ -281,9 +281,8 @@ Use this format when Crew Artifact Index exists in project-brief.md. If no Artif
 
 ## Sprint Completion Checkpoint
 
-**Trigger**: 현재 Sprint의 모든 Story가 ✅ 완료되었을 때 (reviewer pass → pm checkpoint)
-
-이 절차는 Sprint 종료 시 자동으로 실행된다. "계속할까요?"가 아니라 **구체적 선택을 강제**한다.
+**Trigger**: 현재 Sprint의 모든 Story가 ✅ 완료되었을 때 (reviewer pass → pm checkpoint).
+Sprint 종료 시 자동 실행 — **구체적 선택을 강제**한다 ("계속할까요?" 가 아님).
 
 ### 절차
 
@@ -314,7 +313,7 @@ Use this format when Crew Artifact Index exists in project-brief.md. If no Artif
 
    🏁 마무리: 현재 상태로 프로젝트를 완료하고 wrap-up 진행
    ```
-   > **"계속"은 선택지에 없다.** 사용자는 구체적 기능을 골라야 하거나, 명시적으로 "마무리"를 선택해야 한다.
+   **"계속"은 선택지에 없다** — 사용자는 구체적 기능 또는 "마무리"를 명시적으로 선택해야 한다.
 
 4. **사용자 선택에 따라 분기**:
    - **기능 선택** → 선택된 기능으로 Sprint 계획 (위의 "For New Feature" 절차 진행)

package/harness/agents/reviewer.md

@@ -65,6 +65,30 @@ Changed file list (user-provided or from `git diff --name-only`)
 - [ ] Constructor parameters match actual source (FP-002)
 - [ ] **Common First (Iron Law #9)**: No crew-specific logic outside crew marker blocks. All features must work without crew artifacts.
 
+<!-- CREW_MODE_START -->
+**Step 2.5: CI Standards Compliance (🟣 Pipeline only)**
+
+**Trigger**: Changed files include any build/CI artifacts:
+- `Dockerfile`, `.dockerignore`
+- `.github/workflows/*.yml`, `.gitlab-ci.yml`, `Jenkinsfile`
+- `pom.xml`, `build.gradle`, `gradle.properties`
+- `package.json` (scripts changes), `yarn.lock`, `package-lock.json`
+- `pyproject.toml`, `requirements.txt`, `Pipfile`, `poetry.lock`
+- `go.mod`, `go.sum`
+
+**Procedure**:
+1. Check if `docs/project-brief.md` has a `## CI Artifact Index` section (or `.harness/ci-index.md` exists). If neither → skip this step.
+2. Read the project's primary language/build tool from `docs/project-brief.md` Key Technical Decisions.
+3. Match the language/build tool to a row in the CI Artifact Index → get the reference URL and Key Constraints.
+4. Surface the reference in review output under a `### CI Standards Compliance` section:
+   - Reference URL (the indexed guide)
+   - Key Constraints listed in the index (echoed back so the user does not need to re-read the guide)
+   - `[CI-STANDARD]` flag if any obvious mismatch is detected against a listed constraint (best-effort LLM judgment based only on the changed files)
+5. **Warning only — do NOT block commit**. The user (or a human reviewer) decides whether the changes meet company standards. The reviewer agent never asserts compliance; it only points to the authoritative guide.
+
+If neither `## CI Artifact Index` nor `.harness/ci-index.md` is present → skip this step entirely (also true for 🟢/🔵/🔴 pipelines).
+<!-- CREW_MODE_END -->
+
 **Step 3: Test Integrity (sync-tests skill)**
 - [ ] Interface changes have synchronized mocks (FP-001)
 - [ ] New features have tests
@@ -125,7 +149,11 @@ If no Crew Artifact Index → skip this step entirely.
 
 **Step 8: State File Audit**
 
-Verify that state file updates actually happened. Check each:
+Verify that state file updates actually happened. **Run the `state-check` skill first** (Iron Law #10) for deterministic cross-checks, then perform the human-judgment items below that state-check cannot mechanically verify.
+
+> `state-check` covers: file existence, Story↔Feature consistency, dependency-map↔src/ drift, and agent-memory legacy names. The items below complement it with semantic checks the skill cannot perform.
+
+After running state-check, also verify:
 - [ ] **docs/project-state.md**: If stories were worked on, is Quick Summary current? Are story statuses updated?
 - [ ] **docs/features.md**: If new features were added, are they registered? If features were completed, is status updated?
 - [ ] **Cross-check features ↔ stories**: If a feature status is `✅ done` in features.md, verify all related stories in project-state.md are also `done`. If stories are `done` but their feature is still `🔄 in-progress`, flag as `[STATE-AUDIT]`.
@@ -180,23 +208,16 @@ If review is BLOCKED → do NOT suggest commit. Fix first.
 - Test integrity: ✅ / ⚠️ (detail)
 - Security check: ✅ / ❌ (detail)
 - Failure pattern check: ✅ / ⚠️ (FP-NNN)
+<!-- CREW_MODE_START -->
+- CI standards (🟣): ✅ / ⚠️ [CI-STANDARD] (detail) — included only when CI Artifact Index exists
+<!-- CREW_MODE_END -->
 
 STATUS: DONE / DONE_WITH_CONCERNS / BLOCKED
 ```
 
 ## Embedded Rules
 
-These rules are enforced during every review:
-
-### Iron Laws
-1. **Mock Sync**: Interface change → mock updated in same commit (FP-001)
-2. **Type Check**: Verify constructor/factory parameters from source, not memory (FP-002)
-3. **Scope Compliance**: Changes must be within current Story scope (docs/project-state.md)
-4. **Security**: No credentials, passwords, or API keys in code or commits
-5. **3-Failure Stop**: Same approach failed 3 times → stop and report
-6. **Dependency Map**: New/modified module → docs/dependency-map.md updated
-7. **Feature Registry**: New feature → docs/features.md updated
-8. **Session Handoff**: Session end → docs/project-state.md Quick Summary updated
+These rules are enforced during every review. The full Iron Laws (10) are defined in `harness/core-rules.md` — reviewer enforces all of them. Below are review-specific rules that supplement the Iron Laws.
 
 ### Testing Rules
 - New feature = New test. No feature code without tests.

package/harness/core-rules.md

@@ -1,6 +1,6 @@
-# Musher
+# kode:harness
 
-This project uses Musher for structured AI-assisted development.
+This project uses kode:harness for structured AI-assisted development.
 Skills and agents work together through shared state files.
 **Every response must end with a 🧭 Next Step block** — guide the user to the next action.
 
@@ -54,6 +54,7 @@ When external planning artifacts exist (requirements, analysis, design documents
 
 > Crew artifacts are detected by: `docs/crew/` directory, `docs/PM/`+`docs/Analyst/`+`docs/ARB/` directories, or user explicitly provides requirements/design documents (e.g., mentions "PRD", "산출물", "설계서", or provides file paths to planning artifacts).
 > **Reference, don't summarize**: setup creates a Crew Artifact Index (path table) in project-brief.md — each skill reads the original artifact directly via the indexed path.
+> Crew mode also enables the **CI Artifact Index** reference layer: if `docs/project-brief.md` contains `## CI Artifact Index`, reviewer Step 2.5 and release Step 3.5 surface the indexed company CI/CD guide when build/CI files change. The guide content stays external; only the path and key constraints are indexed.
 > This pipeline produces the same state files as 🟢 — the difference is the INPUT source and the addition of Validation Tracker for traceability.
 <!-- CREW_MODE_END -->
 
@@ -134,3 +135,16 @@ These laws are enforced across all skills and agents. Violations should be flagg
 7. **Feature Registry**: When adding a feature, register it in features.md in the same commit.
 8. **Session Handoff**: At session end, update project-state.md Quick Summary so the next session has context.
 9. **Common First**: All features must work at Common level (🟢🔵🔴) without crew dependency. Crew-specific logic must be inside crew marker blocks only. Never add crew-only code to Common paths.
+10. **Self-Verify**: Every agent MUST run the `state-check` skill before reporting STATUS: DONE. If state-check returns FAIL, the agent must NOT report DONE — fix the listed drift first. WARN may proceed but warnings must be included in the agent's output.
+
+## Confirmation Gate Defaults
+
+When the user does not respond to a confirmation prompt within the conversation, agents must apply the SAFE default — never assume implicit approval. The SAFE default for each gate:
+
+| Gate | Owner | SAFE default (no response) | Rationale |
+|------|-------|---------------------------|-----------|
+| Plan Confirmation | `pm` | Do NOT write `features.md` / `project-state.md` / `dependency-map.md`. Hold the plan and re-prompt. | Prevents state file pollution from rejected plans. |
+| Scope Check | `lead` | NO — block edits outside the current Story scope. | Iron Law #3 (Scope Compliance) cannot be silently bypassed. |
+| Commit Approval | `reviewer` | Hold the commit. Output the proposed commit command but do NOT execute it. | Code commits are hard to reverse without `git reset` — user must explicitly approve. |
+
+Any agent that wants to proceed past one of these gates without explicit approval is in violation of Iron Law #10 and must STOP.

package/harness/project-brief.md

@@ -1,6 +1,6 @@
 # Project Brief
 
-> **Fill this out immediately after running `musher init`.** The Planner agent uses this file for Direction Guard — without it, scope drift cannot be prevented.
+> **Fill this out immediately after running `@kodevibe/harness init`.** The Planner agent uses this file for Direction Guard — without it, scope drift cannot be prevented.
 
 ## Vision
 
@@ -106,6 +106,28 @@
    Status legend: ⬜ Not started, 🟡 In progress, ✅ Done
    Update flow: setup creates → pm fills Story column → wrap-up updates Status
 -->
+
+## CI Artifact Index
+
+<!-- 🟣 Pipeline only — references to company CI/CD standard guides.
+   reviewer Step 2.5 and release Step 3.5 read this index to surface the relevant guide
+   when build/CI files change or before deploy.
+
+   Reference Layer pattern: the original guide lives outside this repo (Confluence,
+   internal wiki, etc.). This index stores ONLY the path/URL and the key constraints
+   so that AI agents do not need to re-read the guide every time. The actual guide
+   content is never copied into this repository.
+
+   | Language | Build Tool | Reference URL | Key Constraints |
+   |----------|-----------|---------------|-----------------|
+   | _(예: Java)_ | _(예: Maven)_ | _(URL placeholder — fill with the company guide URL)_ | _(예: 표준 base image 사용, ACR 캐시 사용, 보안 스캔 단계 포함)_ |
+
+   Tips for filling this table:
+   - 1행만 채워도 충분 — 프로젝트의 주 언어/빌드도구만 기재
+   - 다중 서비스 (모놀리식 X, 멀티 모듈 O)인 경우 서비스/모듈별로 한 행씩
+   - Key Constraints는 LLM이 변경된 파일 대비 자동 점검할 수 있도록 짧고 검증 가능한 형태로 작성 (e.g., "base image: company-base:latest", "cache: 회사 ACR 미러 사용")
+   - Reference URL은 회사 내부 가이드 위치 (Confluence, wiki 등). OSS 코드베이스에는 절대 회사 URL을 커밋하지 않음 — 이 파일은 사용자 로컬 또는 사내 저장소에서만 채움.
+-->
 <!-- CREW_MODE_END -->
 
 ## Key Technical Decisions

package/harness/skills/release.md

@@ -44,6 +44,24 @@ Verify all state files are up to date:
 - [ ] **Validation Tracker FR Coverage**: All Functional Requirements (FR) have at least one mapped Story (`docs/project-brief.md` → Validation Tracker)
 - [ ] **Validation Tracker ARB Fail Resolution**: All ARB Fail items resolved (✅) or explicitly deferred with rationale
 - [ ] **KPI Coverage**: All KPIs addressed or deferred with documented reason
+- [ ] **CI Standards (🟣)**: If `docs/project-brief.md` has `## CI Artifact Index`, deploy artifacts (Dockerfile, CI workflow, build config) match the indexed guide's Key Constraints (see Step 3.5)
+<!-- CREW_MODE_END -->
+
+<!-- CREW_MODE_START -->
+### Step 3.5: CI Standards Compliance (🟣 Pipeline only)
+
+If `docs/project-brief.md` has a `## CI Artifact Index` section:
+
+1. Read the indexed reference URL and Key Constraints for the project's primary language/build tool.
+2. Verify the deployed configuration matches each Key Constraint listed in the index:
+   - Base image (e.g., must use the standard company base image)
+   - Build cache strategy (e.g., must use the company-approved cache mirror)
+   - Required CI stages (e.g., security scan, signing)
+   - Any other constraint listed in the index row
+3. If **any** constraint is unmet → mark **NOT_READY** and list the unmet constraints in the verdict.
+4. If `## CI Artifact Index` does not exist (or is empty) → skip this step entirely.
+
+This step references the indexed company guide; it does not embed the guide content itself. The reviewer agent (Step 2.5) catches CI standard issues earlier in the cycle; this step is the final gate before deploy.
 <!-- CREW_MODE_END -->
 
 ### Step 4: Security Scan
@@ -65,6 +83,25 @@ Verify all state files are up to date:
 2. If yes → verify they include entries for all changes since last release
 3. If no → generate a summary from `git log --oneline <last-tag>..HEAD`
 
+### Step 6.5: IDE Adapter 공식 문서 정합성 (IDE-targeting 프로젝트만)
+
+If the project ships IDE-specific adapters or generators (e.g., `src/init.js` with multiple `generate<IDE>` functions, OR distributes templates installed under IDE-specific directories like `.cursor/`, `.codex/`, `.windsurf/`, `.agents/`):
+
+1. **List all IDEs supported** by the project (read source — do not guess).
+2. For **each IDE**, fetch the **official current documentation** for that IDE's agent/rules/skills layout. Do not rely on training data.
+3. **Diff** the project's generated paths/file formats against the official docs:
+   - File extensions (e.g., Codex requires `.toml`, not `.md`)
+   - Directory locations (e.g., Antigravity uses `.agents/`, not `.gemini/`)
+   - Frontmatter schema (required fields per IDE)
+   - Cross-tool standards (e.g., `AGENTS.md`, `.agents/skills/`)
+4. If **any drift** is detected → mark **NOT_READY**. Block the release until adapters match official docs.
+5. Verify regression tests assert the **absence** of stale paths (e.g., `assert(!exists('.gemini/'))` if the IDE moved off Gemini).
+6. Cite the official doc URL inline in the generator code as a comment (source-of-truth pointer).
+
+**Rationale**: IDE vendors change their layouts (e.g., Cursor's skills location, Antigravity's `.gemini/` → `.agents/` migration). Without this gate, every IDE update silently breaks `harness init` for that IDE's users.
+
+If the project does not ship IDE adapters → skip this step entirely.
+
 ## Output Format
 
 ```
@@ -77,6 +114,9 @@ Verify all state files are up to date:
 - [x/✗] Security scan clean
 - [x/✗] Git status clean
 - [x/✗] Release notes prepared
+<!-- CREW_MODE_START -->
+- [x/✗/–] CI standards (🟣): [verdict] — `–` if no CI Artifact Index
+<!-- CREW_MODE_END -->
 
 ### Verdict: READY / NOT_READY
 [blockers if not ready]

package/harness/skills/setup.md

@@ -2,13 +2,13 @@
 
 ## Purpose
 
-Onboard a new or existing project into Musher by filling **state files AND rules files** automatically.
+Onboard a new or existing project into kode:harness by filling **state files AND rules files** automatically.
 Solves the cold-start problem: users don't know which `.md` files to fill or how.
 One command does everything — no manual editing required.
 
 ## When to Apply
 
-- Right after running `musher init` on a new project
+- Right after running `@kodevibe/harness init` on a new project
 - When joining an existing project that has empty state files
 - When state files are outdated and need a refresh
 - When any agent reports "state files are empty"
@@ -49,6 +49,16 @@ One command does everything — no manual editing required.
 
 4. **Scan for existing tests**: Find test files and map them to source modules
 5. **Scan imports/dependencies**: Trace module relationships from import statements
+6. **Detect legacy agent-memory files** (v0.9 migration):
+   - Look in `docs/agent-memory/` and `.harness/agent-memory/` for these legacy names from earlier framework versions:
+     - `planner.md` → should be renamed to `pm.md`
+     - `sprint-manager.md` → should be renamed to `lead.md`
+     - `navigator.md` → should be renamed to `lead.md`
+     - `builder.md` → should be renamed to `pm.md`
+   - For each legacy file found:
+     - If the new name does NOT exist → offer to rename: `mv {legacy}.md {new}.md` (preserves history)
+     - If BOTH exist → ask the user which to keep, or merge contents into the new name and delete the legacy
+   - Confirm with the user before renaming. Record the migration in `docs/project-state.md` Recent Changes.
 
 **Do NOT modify any code files in this phase.**
 
@@ -137,6 +147,7 @@ Using data from Phase 1 + Phase 2, fill the following files:
 <!-- CREW_MODE_START -->
 - Crew Artifact Index → from Phase 1.5 (🟣 pipeline only — leave as template comment for 🟢 pipeline)
 - Validation Tracker → from Phase 1.5 (🟣 pipeline only — leave as template comment for 🟢 pipeline)
+- CI Artifact Index → 🟣 pipeline only. After filling crew fields, ask the user: "회사 CI/CD 표준 가이드(Dockerfile/CI 파이프라인 규약)가 있다면 한 줄로 인덱싱하시겠습니까? (URL과 Key Constraints만 기록 — 가이드 본문은 외부에 둠)". If yes, fill one row in the CI Artifact Index table with their primary language/build tool, the guide URL, and 2-3 short Key Constraints. If no or skip → leave template comment as-is. Never commit company-specific URLs to the OSS template — this row is meant to be filled in the user's local/private project-brief.md only.
 <!-- CREW_MODE_END -->
 - Key Technical Decisions → from Phase 1 scan + user answer #4, #5
 
@@ -267,28 +278,6 @@ For projects with fewer than 3 modules (e.g., single-file scripts, small CLI too
 - `breakdown` Waves may collapse into a single Wave — skip Wave-level pacing
 - Consider a simplified workflow: `setup → pm → [code] → reviewer → wrap-up` (skip lead for single-story projects)
 
-## Embedded Knowledge
-
-### Session Bootstrap Protocol
-When starting a NEW session (not during setup), read these files in order:
-1. `docs/project-state.md` — Quick Summary tells you where we left off
-2. `docs/features.md` — What features exist
-3. `docs/failure-patterns.md` — What mistakes to avoid
-4. `docs/project-brief.md` — Project vision and non-goals
-
-### Workflow Pipeline
-- New feature: `pm → [code] → reviewer → lead → wrap-up`
-- Bug fix: `debug → [fix] → sync-tests → reviewer → wrap-up`
-- Session lifecycle: `lead ("where are we?") → [work] → wrap-up`
-
-### State File Size Limits
-- docs/project-brief.md: Max 200 lines
-- docs/project-state.md: Max 300 lines
-- docs/failure-patterns.md: Max 50 patterns
-- docs/dependency-map.md: Max 100 modules
-- docs/features.md: Max 50 features
-- docs/agent-memory/*.md: Max 100 lines each
-
 ## Anti-patterns
 
 | Anti-pattern | Correct Approach |
@@ -307,14 +296,14 @@ When starting a NEW session (not during setup), read these files in order:
 When running setup in Team mode:
 
 ### New Project (first developer)
-1. Run `musher init --team` to create shared + personal state files
+1. Run `@kodevibe/harness init --team` to create shared + personal state files
 2. Fill all state files via normal setup procedure
 3. Commit shared files (docs/) to git
 4. Push to remote — teammates will clone this
 
 ### Joining Developer (existing project)
 1. Clone the repository (shared docs/ already exist)
-2. Run `musher init --team` — only personal files (.harness/) are created; shared files are skipped
+2. Run `@kodevibe/harness init --team` — only personal files (.harness/) are created; shared files are skipped
 3. **DO NOT re-run setup interviews** — shared state is already filled by the first developer
 4. Review docs/project-brief.md to understand project goals
 5. Create your personal .harness/project-state.md with your current Story assignment

package/harness/skills/state-check.md

@@ -0,0 +1,189 @@
+# State Check
+
+## Purpose
+
+Deterministic verification that state files are internally consistent and not silently drifting.
+This skill exists because LLM self-checks miss state drift — every Iron Law #10 self-verify pass should run this skill before reporting STATUS: DONE.
+
+## Invoked By
+
+- **pm** agent — Post-Approval step (after writing features.md / project-state.md / dependency-map.md)
+- **reviewer** agent — Step 8 (State File Audit) — supplements existing STATE-AUDIT logic
+- **wrap-up** skill — Step 5.5 (after dependency-map verify)
+- **User** (direct) — "state 파일 일관성 점검해줘"
+
+## When to Apply
+
+- After ANY agent writes to state files (mandatory before STATUS: DONE)
+- Before committing changes that touch `docs/` or `.harness/`
+- When the user reports state files "feel out of sync"
+- Periodically — even when nothing recently changed (drift accumulates silently)
+
+## Procedure
+
+> **Philosophy**: Use deterministic cross-checks, not LLM intuition. Each check has a single PASS/WARN/FAIL outcome that does not depend on judgment. The LLM performs the file reads and comparisons listed below — no shell scripts, no external dependencies.
+
+### Check 1: Required State Files Exist with Non-Placeholder Content
+
+For each required state file, verify it exists and is not just a template stub:
+
+| File | Placeholder Sentinel (FAIL if present) |
+|------|----------------------------------------|
+| `docs/project-state.md` (or `.harness/`) | `S1-1 \| Project scaffolding` |
+| `docs/project-brief.md` | `This is the north star for all decisions` |
+| `docs/dependency-map.md` | `Add new modules above this line` |
+| `docs/features.md` | `Add new features above this line` |
+
+For each file:
+- **Missing** → FAIL: `[FAIL] {file} not found`
+- **Sentinel present** → WARN: `[WARN] {file} contains template placeholder — run setup`
+- **Real content** → PASS
+
+> `failure-patterns.md` is excluded — FP-001~004 templates with Frequency: 0 are normal initial state.
+
+### Check 2: features.md ↔ project-state.md Story Consistency
+
+1. Read all `✅ done` Stories from `docs/project-state.md` (or `.harness/project-state.md` in Team mode) Story Status table
+2. Read `docs/features.md` Feature Registry
+3. For each `✅ done` Story:
+   - If Story has `[FR-NNN]` prefix → must map to a feature row with that FR reference
+   - Otherwise → must map to at least one feature row whose Key Files overlap with the Story's Scope
+4. Outcomes:
+   - Story ✅ done but no matching feature row → FAIL: `[FAIL] Story {S-N-M} done but no feature registered`
+   - Story ✅ done but feature still `⬜ planned` → FAIL: `[FAIL] Feature status drift — {feature} is planned but Story {S-N-M} is done`
+   - All consistent → PASS
+
+### Check 3: dependency-map.md vs Actual src/ Directory Count
+
+> **Goal**: detect orphan modules (in src/ but not registered) and stale entries (registered but deleted).
+
+1. Read `docs/dependency-map.md` and count rows in the Module table (excluding header / comment lines like `Add new modules above this line`)
+2. Inspect the source root (priority order — first existing path wins):
+   - `src/`
+   - `lib/`
+   - `app/`
+   - Project root (if no src-like directory)
+3. Count direct child directories of the source root that look like modules (skip `__pycache__/`, `node_modules/`, `dist/`, `build/`, `.next/`, hidden dirs)
+4. Compare:
+   - `|map_count - dir_count| / max(map_count, dir_count) <= 0.20` → PASS
+   - Difference > 20% → WARN: `[WARN] dependency-map has {map_count} modules but src/ has {dir_count} directories — likely drift`
+   - One side is 0 and the other > 0 → FAIL: `[FAIL] dependency-map empty but {dir_count} src directories exist (or vice versa)`
+
+> For tiny projects (<3 modules), this check always passes — see setup.md "Small Project Guidance".
+
+### Check 4: agent-memory Legacy Names
+
+Verify no legacy agent-memory file names remain after the v0.9 rename (planner→pm, sprint-manager→lead, navigator→lead, builder→pm):
+
+1. Scan `docs/agent-memory/` (and `.harness/agent-memory/` in Team mode)
+2. If any of these legacy names exist → WARN with rename suggestion:
+   - `planner.md` → rename to `pm.md`
+   - `sprint-manager.md` → rename to `lead.md`
+   - `navigator.md` → rename to `lead.md`
+   - `builder.md` → rename to `pm.md`
+3. If both legacy and new names exist for the same role → FAIL: `[FAIL] Both {legacy} and {new} exist — merge then delete legacy`
+
+### Check 5: Iron Law #10 Self-Verify Marker
+
+When invoked from another agent (pm, reviewer, wrap-up), confirm the calling agent declared its self-verify intent:
+- The calling agent should have written nothing else after invoking state-check
+- If the agent already produced STATUS: DONE before calling state-check → WARN: `[WARN] Iron Law #10 violation — STATUS: DONE issued before state-check`
+
+This check is informational — humans calling the skill directly can ignore it.
+
+<!-- CREW_MODE_START -->
+### Check 6 (🟣 Pipeline only): Validation Tracker Coverage
+
+If `docs/project-brief.md` contains a `## Validation Tracker` section:
+
+1. Read FR Coverage table — for each FR with at least one Story, that Story must exist in project-state.md Story Status
+2. Read ARB Fail Resolution table — for each Fail item with a Story link, the Story must exist
+3. Outcomes:
+   - Tracker references missing Story → FAIL: `[FAIL] Validation Tracker references {S-N-M} but Story not found in project-state.md`
+   - Story marked ✅ done in project-state but Tracker still shows ⬜ → WARN: `[WARN] Validation Tracker out of sync — {Story} done but {KPI/FR/ARB} status unchanged`
+
+If no Validation Tracker → skip.
+<!-- CREW_MODE_END -->
+
+## Output Format
+
+```
+## State Check Result
+
+### Check 1: Required Files
+- [x] docs/project-state.md — has content
+- [x] docs/project-brief.md — has content
+- [x] docs/dependency-map.md — has content
+- [x] docs/features.md — has content
+
+### Check 2: Story ↔ Feature Consistency
+- {N} ✅ done Stories cross-checked
+- {M} matched / {K} drifted
+
+### Check 3: dependency-map ↔ src/ Coverage
+- map: {N} modules, src/: {M} directories — {diff}% drift
+
+### Check 4: Agent Memory Legacy Names
+- No legacy names found (or list of legacy files to rename)
+
+<!-- CREW_MODE_START -->
+### Check 6: Validation Tracker (🟣)
+- {N} FR references checked / {M} drifted
+<!-- CREW_MODE_END -->
+
+### Findings
+- [PASS] {N} checks passed
+- [WARN] {N} warnings: {list}
+- [FAIL] {N} failures: {list}
+
+STATUS: PASS | WARN | FAIL
+```
+
+### Result Interpretation
+
+- **PASS** — all checks passed; calling agent may proceed with STATUS: DONE
+- **WARN** — non-blocking issues; calling agent should include warnings in its output but may proceed
+- **FAIL** — blocking; calling agent must NOT report STATUS: DONE until failures are resolved
+
+### 🧭 Navigation — After State Check
+
+When invoked directly (not by another agent), append:
+
+```
+---
+🧭 Next Step
+→ Result: {PASS | WARN | FAIL}
+→ Next: {fix the listed issues, then re-run state-check} or {return to caller}
+→ Why: state-check is the deterministic gate before STATUS: DONE
+→ Pipeline: utility skill (no pipeline step)
+---
+```
+
+When invoked by another agent (pm/reviewer/wrap-up), control returns to the caller — no separate 🧭 block.
+
+## Rules
+
+- Do NOT invent data. Read the files and report exactly what you find.
+- Do NOT modify state files in this skill — diagnosis only. Caller decides remediation.
+- Do NOT run shell scripts. All checks are markdown-described file reads + comparisons.
+- If a check cannot be performed (e.g., `docs/` missing entirely), report it as FAIL and stop — further checks are meaningless.
+
+## Anti-patterns
+
+| Anti-pattern | Correct Approach |
+|---|---|
+| Skip state-check because "I just wrote those files" | Run it anyway — Iron Law #10 mandates self-verify |
+| Report PASS when one check could not be performed | Report FAIL with reason; PASS requires all applicable checks ran |
+| Auto-fix drift inside this skill | This skill is read-only diagnosis — caller fixes drift |
+
+<!-- TEAM_MODE_START -->
+## Team Mode: State Check
+
+In Team mode:
+- Personal state files live in `.harness/` (project-state.md, failure-patterns.md, agent-memory/)
+- Shared files live in `docs/` (project-brief.md, features.md, dependency-map.md)
+- Check 1 looks in BOTH directories — file exists if either path has it
+- Check 2 (Story ↔ Feature) reads `.harness/project-state.md` (personal) against `docs/features.md` (shared) — drift is per-developer
+- Check 4 (legacy agent-memory) scans `.harness/agent-memory/` only
+- If `git pull` was skipped before this run, shared-file checks may report stale data — note this in WARN output
+<!-- TEAM_MODE_END -->

package/harness/skills/wrap-up.md

@@ -4,7 +4,7 @@
 
 Capture lessons from the current session before ending.
 Updates docs/failure-patterns.md with new patterns and refreshes docs/project-state.md Quick Summary.
-This is Musher's memory mechanism — without it, the same mistakes repeat across sessions.
+This is kode:harness's memory mechanism — without it, the same mistakes repeat across sessions.
 
 ## Invoked By
 
@@ -131,8 +131,12 @@ For each issue/error that occurred in this session:
    - New module without dependency-map entry → **add it now**
    - Interface change without Interface Change Log entry → **add it now**
 4. Cross-reference `docs/features.md` Key Files against `docs/dependency-map.md` modules — flag orphaned modules
+5. **Run `state-check` skill** (Iron Law #10 — mandatory before STATUS: DONE):
+   - PASS → proceed to Step 5.6
+   - WARN → include warnings in the final wrap-up report, then proceed
+   - FAIL → fix the listed drift (update affected state files), then re-run state-check until PASS or WARN
 
-> **Self-check**: `docs/dependency-map.md`에 이 세션에서 새로 추가한 모듈이 모두 등록되었는지 확인. 누락 시 즉시 추가.
+> **Self-check**: `docs/dependency-map.md`에 이 세션에서 새로 추가한 모듈이 모두 등록되었는지 확인. 누락 시 즉시 추가. state-check가 PASS 또는 WARN을 반환해야 다음 단계로 진행합니다.
 
 ### Step 5.6: Resolve STATE-AUDIT Flags (if applicable)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kodevibe/harness",
-  "version": "0.9.1",
+  "version": "0.9.5",
   "description": "kode:harness — harness engineering for keeping every developer's AI aligned on one project direction.",
   "keywords": [
     "llm",

package/src/init.js

@@ -38,6 +38,7 @@ const SKILLS = [
   { id: 'pivot', desc: 'Propagate direction changes across all state files. Use when project goals, technology, scope, or architecture changes.' },
   { id: 'pr-review', desc: 'Review external Pull Requests for quality, security, and direction alignment. Use when reviewing incoming PRs.' },
   { id: 'release', desc: 'Pre-deployment validation checklist. Use before deploying, publishing, or creating release tags.' },
+  { id: 'state-check', desc: 'Deterministic verification of state file consistency. Use before STATUS: DONE (Iron Law #10) and when state drift is suspected.' },
 ];
 
 const AGENTS = [
@@ -77,13 +78,16 @@ function hasFrameworkMarker(content) {
 }
 
 function hasIdeLayout(targetDir, ide) {
+  // IDE-unique layout markers — used to disambiguate when multiple IDEs share
+  // common files (e.g., AGENTS.md, .agents/skills/). Each marker MUST be unique
+  // to its IDE and aligned with the IDE's official docs.
   const requiredByIde = {
-    vscode: '.github/skills/setup/SKILL.md',
-    claude: '.claude/skills/setup/SKILL.md',
-    cursor: '.cursor/skills/setup/SKILL.md',
-    codex: '.agents/skills/setup/SKILL.md',
-    windsurf: '.windsurf/skills/setup/SKILL.md',
-    antigravity: '.gemini/skills/setup/SKILL.md',
+    vscode: '.github/skills/setup/SKILL.md',          // VS Code: .github/skills/ (official)
+    claude: '.claude/skills/setup/SKILL.md',          // Claude Code: .claude/skills/ (official)
+    cursor: '.cursor/rules/core.mdc',                 // Cursor: .cursor/rules/*.mdc (official)
+    codex: '.codex/agents/reviewer.toml',             // Codex CLI: .codex/agents/*.toml (official)
+    windsurf: '.windsurf/skills/setup/SKILL.md',      // Windsurf: .windsurf/skills/ (official)
+    antigravity: '.agents/rules/core.md',             // Antigravity: .agents/rules/ (official)
   };
 
   const requiredPath = requiredByIde[ide];
@@ -250,8 +254,14 @@ function generateVscode(targetDir, overwrite, mode = 'solo', crew = false) {
 }
 
 function generateClaude(targetDir, overwrite, mode = 'solo', crew = false) {
-  // .claude/rules/core.md — dispatcher only (no paths = always loaded)
-  writeFile(targetDir, '.claude/rules/core.md', resolveContent(readTemplate('core-rules.md'), mode, crew), true);
+  const coreRules = resolveContent(readTemplate('core-rules.md'), mode, crew);
+
+  // CLAUDE.md — Claude Code's canonical project memory file (auto-loaded at session start)
+  writeFile(targetDir, 'CLAUDE.md', coreRules, true);
+
+  // .claude/rules/core.md — secondary dispatcher (also auto-loaded by Claude Code's
+  // InstructionsLoaded mechanism; kept for redundancy and rule-discovery tooling)
+  writeFile(targetDir, '.claude/rules/core.md', coreRules, true);
 
   // Skills (SKILL.md with frontmatter)
   writeSkills(targetDir, '.claude/skills', true, mode, crew);
@@ -264,31 +274,54 @@ function generateClaude(targetDir, overwrite, mode = 'solo', crew = false) {
 }
 
 function generateCursor(targetDir, overwrite, mode = 'solo', crew = false) {
-  // .cursor/rules/core.mdc — dispatcher only (always active)
+  // Cursor official docs: https://cursor.com/docs/context/rules
+  // Officially supported surfaces ONLY:
+  //   - .cursor/rules/*.mdc (with frontmatter: alwaysApply, description, globs)
+  //   - AGENTS.md at project root (and nested directories)
+  // Cursor does NOT publicly document custom skills/agents directories, so we
+  // emit Skills via the open Agent Skills standard path .agents/skills/
+  // (also recognized by VS Code, Codex, Antigravity), and skip a Cursor-specific
+  // agents directory entirely.
   const coreRules = resolveContent(readTemplate('core-rules.md'), mode, crew);
   const coreMdc =
     '---\ndescription: kode:harness dispatcher — workflow guidance and state file references\nalwaysApply: true\n---\n\n' +
     coreRules;
   writeFile(targetDir, '.cursor/rules/core.mdc', coreMdc, true);
 
-  // Skills (.cursor/skills — invokable by mentioning skill name)
-  writeSkills(targetDir, '.cursor/skills', true, mode, crew);
+  // AGENTS.md — Cursor reads project-root AGENTS.md as agent instructions
+  writeFile(targetDir, 'AGENTS.md', coreRules, true);
+
+  // Skills (.agents/skills — open Agent Skills standard, cross-tool)
+  writeSkills(targetDir, '.agents/skills', true, mode, crew);
 
-  // Agents (.cursor/agents/ — Cursor subagent definition files)
-  writeAgentsAsMd(targetDir, '.cursor/agents', true, mode, crew);
+  // Agents as additional rules (.cursor/rules/) so they auto-load with Cursor
+  // and are user-invocable via @rule-name. We use .md plain (no frontmatter
+  // beyond alwaysApply omitted → default "manual" activation).
+  for (const agent of AGENTS) {
+    const content = resolveContent(readTemplate(agent.file), mode, crew);
+    const ruleMd =
+      `---\ndescription: ${agent.desc}\nalwaysApply: false\n---\n\n` +
+      content;
+    writeFile(targetDir, `.cursor/rules/${agent.id}.mdc`, ruleMd, true);
+  }
 
   // State files (respect user's --overwrite for data files)
   writeStateFiles(targetDir, overwrite, mode, crew);
 }
 
 function generateCodex(targetDir, overwrite, mode = 'solo', crew = false) {
-  // AGENTS.md — dispatcher only
+  // Codex CLI official docs:
+  //   - AGENTS.md: https://developers.openai.com/codex/guides/agents-md
+  //   - Skills: https://developers.openai.com/codex/skills (.agents/skills/SKILL.md)
+  //   - Subagents: https://developers.openai.com/codex/subagents (.codex/agents/*.toml)
+  // AGENTS.md — Codex CLI's canonical project instructions file (auto-loaded).
   writeFile(targetDir, 'AGENTS.md', resolveContent(readTemplate('core-rules.md'), mode, crew), true);
 
-  // Skills (SKILL.md with frontmatter — invokable via $skill-name)
+  // Skills (.agents/skills/<name>/SKILL.md — official cross-tool standard)
   writeSkills(targetDir, '.agents/skills', true, mode, crew);
 
-  // Agents (.codex/agents/ — Codex TOML agent definition files)
+  // Subagents (.codex/agents/*.toml — Codex CLI's official format with
+  // name, description, developer_instructions fields)
   writeAgentsAsToml(targetDir, '.codex/agents', true, mode, crew);
 
   // State files (respect user's --overwrite for data files)
@@ -314,14 +347,31 @@ function generateWindsurf(targetDir, overwrite, mode = 'solo', crew = false) {
 }
 
 function generateAntigravity(targetDir, overwrite, mode = 'solo', crew = false) {
-  // GEMINI.md — project context (always loaded by Gemini CLI)
-  writeFile(targetDir, 'GEMINI.md', resolveContent(readTemplate('core-rules.md'), mode, crew), true);
+  // Antigravity official docs:
+  //   - Skills: https://antigravity.google/docs/skills (.agents/skills/<name>/SKILL.md)
+  //   - Rules: https://antigravity.google/docs/rules-workflows (.agents/rules/*.md)
+  // Note: Antigravity does NOT recognize a project-root GEMINI.md — the global
+  // GEMINI.md lives only at ~/.gemini/GEMINI.md. We emit AGENTS.md for cross-tool
+  // compat (harmless to Antigravity, useful when Codex/Cursor share the repo).
+  const coreRules = resolveContent(readTemplate('core-rules.md'), mode, crew);
+
+  // AGENTS.md — cross-tool agent instructions (recognized by Codex/Cursor;
+  // ignored by Antigravity but provides compatibility for mixed teams)
+  writeFile(targetDir, 'AGENTS.md', coreRules, true);
 
-  // Skills (.gemini/skills/ — SKILL.md format)
-  writeSkills(targetDir, '.gemini/skills', true, mode, crew);
+  // .agents/rules/core.md — workspace rules (Antigravity's official location)
+  writeFile(targetDir, '.agents/rules/core.md', coreRules, true);
 
-  // Agents (.gemini/agents/ — Gemini CLI subagent definition files)
-  writeAgentsAsMd(targetDir, '.gemini/agents', true, mode, crew);
+  // Skills (.agents/skills/<name>/SKILL.md — Antigravity's official location)
+  writeSkills(targetDir, '.agents/skills', true, mode, crew);
+
+  // Agents → Rules (Antigravity has no separate agents directory; agents
+  // are persistent rule prompts. We emit one rule file per agent under
+  // .agents/rules/, with alwaysApply implied — manual @-mention also works.)
+  for (const agent of AGENTS) {
+    const content = resolveContent(readTemplate(agent.file), mode, crew);
+    writeFile(targetDir, `.agents/rules/${agent.id}.md`, content, true);
+  }
 
   // State files (respect user's --overwrite for data files)
   writeStateFiles(targetDir, overwrite, mode, crew);
@@ -412,7 +462,7 @@ function detectExistingInstall(targetDir) {
     ['.claude/rules/core.md', 'claude'],
     ['.cursor/rules/core.mdc', 'cursor'],
     ['.windsurf/rules/core.md', 'windsurf'],
-    ['GEMINI.md', 'antigravity'],
+    ['.agents/rules/core.md', 'antigravity'],
   ];
   // Only count as existing if the file contains a framework marker (not from other frameworks)
   const existingIde = ideMarkers.filter(([f, ide]) => {
@@ -520,14 +570,17 @@ function runDoctor(targetDir) {
     }
   }
 
-  // Check for IDE-specific files (detect which IDE was used)
+  // Check for IDE-specific files (detect which IDE was used).
+  // Order matters: IDE-unique markers MUST be checked before AGENTS.md,
+  // because Cursor and Antigravity now also emit AGENTS.md for compat.
   const ideChecks = [
     ['.github/copilot-instructions.md', 'vscode'],
     ['.claude/rules/core.md', 'claude'],
     ['.cursor/rules/core.mdc', 'cursor'],
-    ['AGENTS.md', 'codex'],
     ['.windsurf/rules/core.md', 'windsurf'],
-    ['GEMINI.md', 'antigravity'],
+    ['.agents/rules/core.md', 'antigravity'],
+    ['.codex/agents/reviewer.toml', 'codex'],
+    ['AGENTS.md', 'codex'],
   ];
 
   let detectedIde = null;