k-harness 0.6.0 → 0.8.1

package/README.md

@@ -49,24 +49,22 @@ npx k-harness init --ide antigravity
 
 ## Supported IDEs
 
-| IDE | Global Rules | File-Scoped Rules | Skills | Agents |
-|-----|-------------|-------------------|--------|--------|
-| **VS Code Copilot** | `.github/copilot-instructions.md` | `.vscode/instructions/*.instructions.md` | `.github/skills/*/SKILL.md` | `.github/agents/*.agent.md` |
-| **Claude Code** | `CLAUDE.md` | (merged into CLAUDE.md) | `.claude/skills/*/SKILL.md` | (merged into CLAUDE.md) |
-| **Cursor** | `.cursor/rules/core.mdc` | `.cursor/rules/*.mdc` | (merged into rules) | (merged into rules) |
-| **Codex** | `AGENTS.md` | (merged into AGENTS.md) | `.agents/skills/*/SKILL.md` | (merged into AGENTS.md) |
-| **Windsurf** | `.windsurfrules` | (merged) | (merged) | (merged) |
-| **Augment Code** | `.augment/rules/core.md` | `.augment/rules/*.md` | `.augment/skills/*/SKILL.md` | `.augment/skills/*/SKILL.md` |
-| **Google Antigravity** | `.agent/rules/core.md` | `.agent/rules/*.md` | `.agent/skills/*/SKILL.md` | `.agent/skills/*/SKILL.md` |
+| 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/skills/*/SKILL.md` |
+| **Cursor** | `.cursor/rules/core.mdc` | `.cursor/rules/*.mdc` | `.cursor/rules/*.mdc` |
+| **Codex** | `AGENTS.md` | `.agents/skills/*/SKILL.md` | (merged into AGENTS.md) |
+| **Windsurf** | `.windsurfrules` | (merged) | (merged) |
+| **Augment Code** | `.augment/rules/core.md` | `.augment/skills/*/SKILL.md` | `.augment/skills/*/SKILL.md` |
+| **Google Antigravity** | `.agent/rules/core.md` | `.agent/skills/*/SKILL.md` | `.agent/skills/*/SKILL.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.
 
 ## What Gets Installed
 
-### Rules (always active)
-- **Core Rules** — Architecture enforcement, Iron Laws, completion protocol, concreteness rules
-- **Testing Rules** — Mock synchronization, forbidden patterns (applied to test files)
-- **Backend Rules** — Dependency inversion, type safety, explicit staging (applied to source files)
+### Dispatcher (always active)
+- **Core Rules** — 22-line dispatcher: session start guidance, workflow references, state file list. Detailed rules are embedded in each skill/agent that enforces them.
 
 ### Skills (on-demand procedures)
 - **bootstrap** — Onboard project into K-Harness: scans codebase + fills state files automatically

package/harness/agents/planner.md

@@ -105,6 +105,16 @@ If `docs/project-brief.md` alone is empty → Warn the user but proceed (the pla
 - Last changed: [Sprint/Story reference]
 ```
 
+## Enforced Rules
+
+- **Direction Guard**: Before planning, read `docs/project-brief.md` and check:
+  - If it conflicts with **Non-Goals** → stop and ask the user
+  - If it contradicts a **Decision Log** entry → warn and recommend `pivot` skill
+  - If it represents a direction change → recommend `pivot` skill
+- **Dependency Map**: When the plan adds or modifies modules, include docs/dependency-map.md updates in the plan.
+- **Feature Registry**: When the plan adds a new feature, include docs/features.md registration in the plan.
+- **Type Check**: Before referencing constructors or factories, verify parameters from source files. Do not rely on memory (FP-002).
+
 ## Constraints
 
 - Never skip reading docs/dependency-map.md — the plan is only as good as the map

package/harness/agents/reviewer.md

@@ -99,6 +99,40 @@ For each missing update: flag as `[STATE-AUDIT]` in the output and provide the e
 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
+
+### Testing Rules
+- New feature = New test. No feature code without tests.
+- Mocks must implement ALL interface methods with sensible defaults.
+- No `any` type casting on mocks. Use the actual interface type.
+- No `skip`, `only`, or debug statements (`console.log`, `print`) in committed test files.
+- Async tests must use `await`. No floating promises.
+
+### Backend Rules
+- Follow project architecture pattern strictly (e.g., Domain must not import Infrastructure)
+- No hardcoded environment variables or secrets — use centralized config
+- Use explicit file staging (`git add <file>`), never `git add .` or `git add -A`
+
+### Completion Protocol
+Report using: **DONE** | **DONE_WITH_CONCERNS** | **BLOCKED** | **NEEDS_CONTEXT**
+
+### Concreteness
+- Specify exact file paths and line numbers
+- Quote test names and error messages on failure
+- Specify expected vs actual types on type errors
+
 ## Constraints
 
 - Do not refactor beyond the review scope

package/harness/agents/sprint-manager.md

@@ -98,6 +98,11 @@ Progress: {done}/{total} Stories
 STATUS: DONE
 ```
 
+## Enforced Rules
+
+- **Scope Compliance**: Do not modify files outside the current Story scope. If user requests an out-of-scope change, warn first and proceed only after confirmation.
+- **Completion Protocol**: Report using: **DONE** | **DONE_WITH_CONCERNS** | **BLOCKED** | **NEEDS_CONTEXT**
+
 ## Constraints
 
 - Do not modify code directly — manage state only

package/harness/core-rules.md

@@ -1,126 +1,24 @@
-# Project Instructions
+# K-Harness
 
-## Architecture
+This project uses K-Harness for structured AI-assisted development.
+Skills and agents work together through shared state files — invoke them as needed.
 
-<!-- TODO: Describe your project's architecture here.
-   Example:
-   TypeScript / Express / PostgreSQL
-   Hexagonal Architecture (Port + Adapter)
--->
+## Session Start
 
-## Directory Structure
+Read `docs/project-state.md` first. If all state files are empty, run `bootstrap` skill.
 
-<!-- TODO: Map your directory structure.
-   Example:
-   src/
-   ├── domain/           # Entities, Repository interfaces
-   ├── application/      # Use Cases
-   ├── infrastructure/   # DB, HTTP adapters
-   ├── presentation/     # Controllers, DTOs
-   └── shared/           # Utils, types, errors
--->
+## Workflow
 
-## Core Type Rules
+- New feature → run `planner` before coding
+- Before commit → run `reviewer`
+- Bug or issue → run `investigate`
+- Session end → run `learn`
+- Direction change → run `pivot`
 
-<!-- TODO: Document type decisions that LLMs frequently get wrong.
-   Example:
-   - `ServerType` is a union type ("stdio" | "sse"), NOT an enum.
-   - `UserRole` is a union type ("admin" | "user"), NOT an enum.
--->
+## State Files
 
-## Iron Laws
-
-1. **Mock Sync**: When you modify a repository/service interface, update corresponding mocks in the same commit.
-2. **Type Check**: Before calling a constructor or factory, read the actual source file to verify parameters. Do not rely on memory.
-3. **Scope Compliance**: Do not modify files outside the current Story scope (see docs/project-state.md) without reporting first.
-4. **Security**: Never include credentials, passwords, or API keys in code or commits.
-5. **3-Failure Stop**: If the same approach fails 3 times, stop and report to the user.
-6. **Dependency Map**: When adding or modifying a module, update docs/dependency-map.md in the same commit. Register new modules, update relationship columns.
-7. **Feature Registry**: When adding a new feature, register it in docs/features.md in the same commit. Include key files and test files.
-8. **Session Handoff**: Before ending a chat session, update docs/project-state.md Quick Summary. Never leave the project in an undocumented state.
-
-## Test Rules
-
-- New feature = New test. Do not commit feature code without tests.
-- Test command: <!-- TODO: e.g. npm test, pytest, go test ./..., mvn test -->
-- Mock location: <!-- TODO: e.g. tests/__mocks__/, test/fixtures/ -->
-
-## Completion Status Protocol
-
-Report completion using one of:
-- **DONE**: All steps completed. Present evidence (test results, file list, etc).
-- **DONE_WITH_CONCERNS**: Completed but with concerns. List each concern.
-- **BLOCKED**: Cannot proceed. Describe the cause and what was tried.
-- **NEEDS_CONTEXT**: Need more information. Describe exactly what is needed.
-
-## Concreteness Rules
-
-- When modifying files, specify exact paths and line numbers.
-- When tests fail, quote the test name and error message.
-- When type errors occur, specify expected type and actual type.
-
-## Direction Guard (Every Request)
-
-Before starting ANY coding task, do this:
-
-1. Read `docs/project-brief.md` — check Vision, Goals, Non-Goals, and Decision Log
-2. If `docs/project-brief.md` is empty → run the `bootstrap` skill first, then return to the request
-3. If the request conflicts with **Non-Goals** → stop and warn: "This falls under Non-Goals. Do you want to proceed? If yes, run `pivot` skill first."
-4. If the request contradicts a **Decision Log** entry → warn: "This conflicts with a previous decision: [entry]. Run `pivot` skill to update direction."
-5. If aligned → proceed
-
-This applies to EVERY request, not just new sessions. Skip only for trivial questions ("what does this function do?").
-
-## New Session Bootstrap
-
-When starting a NEW chat session, read these files in order before doing any work:
-1. `docs/project-state.md` — Quick Summary tells you where we left off
-2. `docs/features.md` — What features exist in this project
-3. `docs/failure-patterns.md` — What mistakes to avoid
-4. `docs/project-brief.md` — Project vision, goals, and non-goals
-
-If ALL state files are empty (only TODOs/placeholders), run the `bootstrap` skill before doing anything else.
-
-## Workflow Pipeline
-
-Follow this order for different workflows. Each step's output feeds the next.
-
-### New Feature
-```
-bootstrap (if state files empty) → planner → [code] → reviewer → sprint-manager → learn
-```
-
-### Bug Fix
-```
-investigate → [fix] → test-integrity → reviewer → learn
-```
-
-### Session Lifecycle
-```
-[session start] → sprint-manager ("where are we?") → [work] → learn → [session end]
-```
-
-### Key Rules
-- **planner before code**: Never start coding a feature without running planner first.
-- **reviewer before commit**: Never commit without running reviewer.
-- **learn before closing**: Run learn as the last skill of every session.
-- **bootstrap once**: Run bootstrap once when state files are empty. Not needed after that.
-
-## References
-
-- docs/project-brief.md — Project vision, goals, non-goals (the "why")
-- docs/features.md — Feature registry (the "what")
-- docs/project-state.md — Sprint/Story tracking, module registry (the "where")
-- docs/dependency-map.md — Module dependency graph (the "how")
-- docs/failure-patterns.md — Log of known failure patterns (the "watch out")
-- docs/agent-memory/ — Per-agent persistent memory (the "learned")
-
-## State File Size Limits
-
-State files must stay compact to fit in LLM context windows. Enforce these limits:
-- **docs/project-brief.md**: Max 200 lines. Keep Vision/Goals/Non-Goals concise.
-- **docs/project-state.md**: Max 300 lines. Archive completed sprints when exceeding limit.
-- **docs/failure-patterns.md**: Max 50 patterns. Periodically remove `Status: Resolved` entries.
-- **docs/dependency-map.md**: Max 100 modules. Merge trivial internal modules.
-- **docs/features.md**: Max 50 features. Archive shipped features when exceeding limit.
-- **docs/agent-memory/*.md**: Max 100 lines each. Keep only actionable learnings.
+- docs/project-state.md — current sprint/story and quick summary
+- docs/failure-patterns.md — known pitfalls (FP-NNN)
+- docs/dependency-map.md — module dependency graph
+- docs/features.md — feature registry
+- docs/project-brief.md — project vision, goals, and non-goals

package/harness/skills/bootstrap.md

@@ -2,8 +2,9 @@
 
 ## Purpose
 
-Onboard a new or existing project into K-Harness by filling state files automatically.
+Onboard a new or existing project into K-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
 
@@ -74,6 +75,23 @@ Using data from Phase 1 + Phase 2, fill the following files:
 - Keep FP-001 through FP-004 as templates (Frequency: 0)
 - No changes unless user reports known issues
 
+### Phase 3.5: Project Brief Auto-Configuration
+
+Using language/framework detected in Phase 1 + user answers from Phase 2, enrich `docs/project-brief.md`:
+
+1. **Fill Key Technical Decisions** with detected tech stack:
+   - Language, framework, database (from Phase 1)
+   - Architecture pattern (from user answer #4)
+   - Type conventions (from user answer #5)
+   - Test command and mock location (from user answer #6)
+
+2. **Add language-specific defaults** to Key Technical Decisions if not already present:
+   - Python: `Use Pydantic models for API schemas, not plain dicts.`
+   - TypeScript: `Prefer union types ("a" | "b") over enums.`
+   - Go: `Use interfaces for dependency injection.`
+   - Java: `Use records for DTOs.`
+   - Rust: `Use enum variants, not string constants.`
+
 ### Phase 4: Verify
 
 1. Present a summary of all filled state files to the user
@@ -88,6 +106,7 @@ Using data from Phase 1 + Phase 2, fill the following files:
 
 ### Project: [name]
 ### Tech Stack: [detected stack]
+### Language: [detected language]
 ### Modules Found: [count]
 ### Features Mapped: [count]
 ### Dependency Links: [count]
@@ -104,12 +123,35 @@ STATUS: DONE
 
 ## Rules
 
-- Never modify source code — this skill only writes to state files
+- Never modify source code — this skill only writes to state files and rules files
 - Always show the user what was discovered BEFORE writing files
 - If the project has 0 source files, skip Phase 1 scan and go straight to Phase 2
 - If a state file already has content, ask before overwriting
+- Rules file TODO sections can be overwritten without asking (they are placeholders)
 - Run this skill only once per project (or when explicitly requested for refresh)
 
+## Embedded Knowledge
+
+### Session Bootstrap Protocol
+When starting a NEW session (not during bootstrap), 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: `planner → [code] → reviewer → sprint-manager → learn`
+- Bug fix: `investigate → [fix] → test-integrity → reviewer → learn`
+- Session lifecycle: `sprint-manager ("where are we?") → [work] → learn`
+
+### 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 |
@@ -118,3 +160,6 @@ STATUS: DONE
 | Skip user interview | Phase 1 scan alone is insufficient — always confirm with user |
 | Overwrite existing state files silently | Ask before overwriting non-empty files |
 | Create perfect dependency map on first try | Start with what's detectable, refine over time |
+| Leave rules file TODOs unfilled | Phase 3.5 fills ALL TODO sections — no manual editing needed |
+| Use TypeScript globs for non-TS projects | Detect language in Phase 1 and set correct globs |
+| Only fill state files, skip rules | Bootstrap fills BOTH — state files AND rules files |

package/harness/skills/investigate.md

@@ -74,6 +74,12 @@ After the fix is verified (Phase 4):
 - [ ] **docs/failure-patterns.md**: If the root cause is a repeatable pattern, add a new FP-NNN entry or increment the Frequency of an existing one. This is NOT optional.
 - [ ] **docs/project-state.md**: Add the fix to Recent Changes with the root cause hypothesis.
 
+## Enforced Rules
+
+- **3-Failure Stop**: If the same fix approach fails 3 times, stop and report to the user. Do not keep trying.
+- **Concreteness**: Specify exact file paths and line numbers. Quote error messages. Specify expected vs actual types.
+- **Scope Lock**: Do not modify files outside the identified problem scope (Phase 2).
+
 ## Related Failure Patterns
 
 - FP-002: Type confusion → Phase 1 requires verifying actual types

package/harness/skills/learn.md

@@ -108,6 +108,17 @@ STATUS: DONE
 - Do not modify source code — this skill only updates state files
 - Quick Summary must be exactly 3 lines — concise enough for the next session to scan instantly
 
+## Enforced Rules
+
+- **Session Handoff**: Before ending a session, docs/project-state.md Quick Summary MUST be updated. Never leave the project in an undocumented state.
+- **State File Size Limits**: Keep state files compact for LLM context windows:
+  - docs/project-brief.md: Max 200 lines
+  - docs/project-state.md: Max 300 lines (archive completed sprints)
+  - docs/failure-patterns.md: Max 50 patterns (remove resolved entries)
+  - 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 |

package/harness/skills/test-integrity.md

@@ -48,6 +48,15 @@ After synchronizing mocks:
 - [ ] **docs/failure-patterns.md**: If mock sync was missed and caused a test failure, increment FP-001 Frequency.
 - [ ] **docs/dependency-map.md**: If the interface change altered module relationships, update the relevant row.
 
+## Testing Rules (enforced during this skill)
+
+- Mocks must implement ALL interface methods. Missing method = build failure.
+- No `any` type casting on mocks. Create mocks using the actual interface type.
+- New methods must have default mock return values (e.g., `mockResolvedValue`, stub returns).
+- No `skip`, `only`, or debug statements in committed test files.
+- Async tests must use `await`. No floating promises.
+- Each test must be independent. No shared state between tests.
+
 ## Related Failure Patterns
 
 - FP-001: Interface changed, mock not updated → Checklist item 1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "k-harness",
-  "version": "0.6.0",
+  "version": "0.8.1",
   "description": "LLM Development Harness — IDE-agnostic rules, skills, and agents that prevent common AI coding failures",
   "keywords": [
     "llm",

package/src/init.js

@@ -59,6 +59,25 @@ const AGENT_MEMORY_FILES = [
 
 const STATE_DEST_DIR = 'docs';
 
+// ─── Language detection ──────────────────────────────────────
+function detectLanguage(targetDir) {
+  const markers = [
+    ['python', ['requirements.txt', 'pyproject.toml', 'setup.py', 'Pipfile', 'setup.cfg']],
+    ['go', ['go.mod']],
+    ['java', ['pom.xml', 'build.gradle', 'build.gradle.kts']],
+    ['rust', ['Cargo.toml']],
+    ['ruby', ['Gemfile']],
+  ];
+  for (const [lang, files] of markers) {
+    for (const f of files) {
+      if (fs.existsSync(path.join(targetDir, f))) return lang;
+    }
+  }
+  return 'typescript';
+}
+
+
+
 // ─── Shared writers ──────────────────────────────────────────
 
 function writeStateFiles(targetDir, overwrite) {
@@ -94,23 +113,10 @@ function writeAgentsAsSkills(targetDir, skillsDir, overwrite) {
 
 function generateVscode(targetDir, overwrite) {
   const coreRules = readTemplate('core-rules.md');
-  const testingRules = readTemplate('testing-rules.md');
-  const backendRules = readTemplate('backend-rules.md');
 
-  // Global instructions
+  // Global instructions (dispatcher only — rules are embedded in skills)
   writeFile(targetDir, '.github/copilot-instructions.md', coreRules, overwrite);
 
-  // File-scoped instructions (add VS Code applyTo frontmatter)
-  const testingWithFrontmatter =
-    '---\napplyTo: "**/*.test.ts,**/*.test.js,**/*.spec.ts,**/*.spec.js,**/__mocks__/**,**/__tests__/**"\n---\n\n' +
-    testingRules;
-  writeFile(targetDir, '.vscode/instructions/testing.instructions.md', testingWithFrontmatter, overwrite);
-
-  const backendWithFrontmatter =
-    '---\napplyTo: "src/**/*.ts,src/**/*.js"\n---\n\n' +
-    backendRules;
-  writeFile(targetDir, '.vscode/instructions/backend.instructions.md', backendWithFrontmatter, overwrite);
-
   // Skills (.github/skills — VS Code default search path, SKILL.md with frontmatter)
   writeSkills(targetDir, '.github/skills', overwrite);
 
@@ -128,43 +134,27 @@ function generateVscode(targetDir, overwrite) {
 }
 
 function generateClaude(targetDir, overwrite) {
-  // CLAUDE.md — merge core + testing + backend rules
-  const merged = [
-    readTemplate('core-rules.md'),
-    '\n---\n\n',
-    readTemplate('testing-rules.md'),
-    '\n---\n\n',
-    readTemplate('backend-rules.md'),
-  ].join('');
-  writeFile(targetDir, 'CLAUDE.md', merged, overwrite);
+  // .claude/rules/core.md — dispatcher only (no paths = always loaded)
+  writeFile(targetDir, '.claude/rules/core.md', readTemplate('core-rules.md'), overwrite);
 
-  // Skills (SKILL.md with frontmatter for slash commands)
+  // Skills (SKILL.md with frontmatter)
   writeSkills(targetDir, '.claude/skills', overwrite);
 
+  // Agents as skills (Claude Code skills pattern)
+  writeAgentsAsSkills(targetDir, '.claude/skills', overwrite);
+
   // State files
   writeStateFiles(targetDir, overwrite);
 }
 
 function generateCursor(targetDir, overwrite) {
-  // .cursor/rules/*.mdc — each needs frontmatter
+  // .cursor/rules/core.mdc — dispatcher only
   const coreRules = readTemplate('core-rules.md');
   const coreMdc =
-    '---\ndescription: Core project rules — Iron Laws, completion protocol, concreteness\nalwaysApply: true\n---\n\n' +
+    '---\ndescription: K-Harness dispatcher — workflow guidance and state file references\nalwaysApply: true\n---\n\n' +
     coreRules;
   writeFile(targetDir, '.cursor/rules/core.mdc', coreMdc, overwrite);
 
-  const testingRules = readTemplate('testing-rules.md');
-  const testingMdc =
-    '---\ndescription: Testing rules — mock sync, forbidden patterns\nglobs: "**/*.test.*,**/*.spec.*,**/__mocks__/**,**/__tests__/**"\nalwaysApply: false\n---\n\n' +
-    testingRules;
-  writeFile(targetDir, '.cursor/rules/testing.mdc', testingMdc, overwrite);
-
-  const backendRules = readTemplate('backend-rules.md');
-  const backendMdc =
-    '---\ndescription: Backend code rules — architecture enforcement, type safety\nglobs: "src/**/*.ts,src/**/*.js"\nalwaysApply: false\n---\n\n' +
-    backendRules;
-  writeFile(targetDir, '.cursor/rules/backend.mdc', backendMdc, overwrite);
-
   // Skills as rules
   for (const skill of SKILLS) {
     const content = readTemplate(`skills/${skill.id}.md`);
@@ -188,15 +178,8 @@ function generateCursor(targetDir, overwrite) {
 }
 
 function generateCodex(targetDir, overwrite) {
-  // AGENTS.md — merge core + testing + backend rules
-  const merged = [
-    readTemplate('core-rules.md'),
-    '\n---\n\n',
-    readTemplate('testing-rules.md'),
-    '\n---\n\n',
-    readTemplate('backend-rules.md'),
-  ].join('');
-  writeFile(targetDir, 'AGENTS.md', merged, overwrite);
+  // AGENTS.md — dispatcher only
+  writeFile(targetDir, 'AGENTS.md', readTemplate('core-rules.md'), overwrite);
 
   // Skills (SKILL.md with frontmatter for slash commands)
   writeSkills(targetDir, '.agents/skills', overwrite);
@@ -206,46 +189,21 @@ function generateCodex(targetDir, overwrite) {
 }
 
 function generateWindsurf(targetDir, overwrite) {
-  // .windsurfrules — everything in one file
-  const sections = [
-    readTemplate('core-rules.md'),
-    readTemplate('testing-rules.md'),
-    readTemplate('backend-rules.md'),
-    '---\n\n# Skills\n\n',
-  ];
-  for (const skill of SKILLS) {
-    sections.push(readTemplate(`skills/${skill.id}.md`));
-  }
-  sections.push('---\n\n# Agents\n\n');
-  for (const agent of AGENTS) {
-    sections.push(readTemplate(agent.file));
-  }
-  writeFile(targetDir, '.windsurfrules', sections.join('\n\n---\n\n'), overwrite);
+  // .windsurfrules — dispatcher only (rules are embedded in skills)
+  writeFile(targetDir, '.windsurfrules', readTemplate('core-rules.md'), overwrite);
 
   // State files
   writeStateFiles(targetDir, overwrite);
 }
 
 function generateAugment(targetDir, overwrite) {
-  // .augment/rules/ — Always-type rules for core, testing, backend
+  // .augment/rules/core.md — dispatcher only
   const coreRules = readTemplate('core-rules.md');
   const coreRule =
-    '---\ndescription: Core project rules — Iron Laws, completion protocol, concreteness\ntype: always\n---\n\n' +
+    '---\ndescription: K-Harness dispatcher — workflow guidance and state file references\ntype: always\n---\n\n' +
     coreRules;
   writeFile(targetDir, '.augment/rules/core.md', coreRule, overwrite);
 
-  const testingRules = readTemplate('testing-rules.md');
-  const testingRule =
-    '---\ndescription: Testing rules — mock sync, forbidden patterns\ntype: auto\nglobs: "**/*.test.*,**/*.spec.*,**/__mocks__/**,**/__tests__/**"\n---\n\n' +
-    testingRules;
-  writeFile(targetDir, '.augment/rules/testing.md', testingRule, overwrite);
-
-  const backendRules = readTemplate('backend-rules.md');
-  const backendRule =
-    '---\ndescription: Backend code rules — architecture enforcement, type safety\ntype: auto\nglobs: "src/**/*.ts,src/**/*.js"\n---\n\n' +
-    backendRules;
-  writeFile(targetDir, '.augment/rules/backend.md', backendRule, overwrite);
-
   // .augment/skills/ — SKILL.md format (enables / slash commands)
   writeSkills(targetDir, '.augment/skills', overwrite);
   writeAgentsAsSkills(targetDir, '.augment/skills', overwrite);
@@ -255,25 +213,13 @@ function generateAugment(targetDir, overwrite) {
 }
 
 function generateAntigravity(targetDir, overwrite) {
-  // .agent/rules/ — Always-type rules (same as Augment format, read by Antigravity)
+  // .agent/rules/core.md — dispatcher only
   const coreRules = readTemplate('core-rules.md');
   const coreRule =
-    '---\ndescription: Core project rules — Iron Laws, completion protocol, concreteness\ntype: always\n---\n\n' +
+    '---\ndescription: K-Harness dispatcher — workflow guidance and state file references\ntype: always\n---\n\n' +
     coreRules;
   writeFile(targetDir, '.agent/rules/core.md', coreRule, overwrite);
 
-  const testingRules = readTemplate('testing-rules.md');
-  const testingRule =
-    '---\ndescription: Testing rules — mock sync, forbidden patterns\ntype: auto\nglobs: "**/*.test.*,**/*.spec.*,**/__mocks__/**,**/__tests__/**"\n---\n\n' +
-    testingRules;
-  writeFile(targetDir, '.agent/rules/testing.md', testingRule, overwrite);
-
-  const backendRules = readTemplate('backend-rules.md');
-  const backendRule =
-    '---\ndescription: Backend code rules — architecture enforcement, type safety\ntype: auto\nglobs: "src/**/*.ts,src/**/*.js"\n---\n\n' +
-    backendRules;
-  writeFile(targetDir, '.agent/rules/backend.md', backendRule, overwrite);
-
   // .agent/skills/ — SKILL.md format (enables / slash commands)
   writeSkills(targetDir, '.agent/skills', overwrite);
   writeAgentsAsSkills(targetDir, '.agent/skills', overwrite);
@@ -378,10 +324,11 @@ async function run(argv) {
     }
 
     const gen = GENERATORS[ide];
-    console.log(`\n  Installing for ${gen.name}...\n`);
+    const lang = detectLanguage(args.dir);
+    console.log(`\n  Installing for ${gen.name}... (detected language: ${lang})\n`);
     gen.fn(args.dir, args.overwrite);
-    console.log(`\n  Done! Edit docs/project-state.md to set up your first sprint.\n`);
+    console.log(`\n  Done! Run "bootstrap" in your AI chat to auto-fill state files and rules.\n`);
   }
 }
 
-module.exports = { run };
+module.exports = { run, detectLanguage };

package/harness/backend-rules.md

@@ -1,24 +0,0 @@
-# Backend Code Rules
-
-## Required
-
-- Follow the project's architecture patterns strictly.
-  <!-- TODO: Define your architecture layers. Examples:
-  - Domain layer must not import from infrastructure.
-  - Application layer accesses data only through domain interfaces.
-  - Infrastructure implements domain interfaces.
-  - Controllers/routes handle request/response only. No business logic.
-  -->
-- Before calling any constructor or factory, read the actual source file to verify parameters. Do not trust memory. (FP-002)
-
-## Forbidden
-
-- Violating the project's dependency direction (e.g. importing infrastructure from domain).
-- Suppressing type safety without an explicit reason comment.
-- Hardcoding environment variables or secrets in code. Use centralized config.
-- `git add .` or `git add -A` — use explicit per-file staging.
-
-## References
-
-- docs/failure-patterns.md FP-002: Type confusion
-- docs/failure-patterns.md FP-004: Unnecessary files committed

package/harness/testing-rules.md

@@ -1,21 +0,0 @@
-# Testing Rules
-
-## Required
-
-- When interface changes, update corresponding mocks in the same commit (FP-001).
-- Mocks must implement ALL interface methods. Missing method = build failure.
-- Do not use real credentials in test data. Use fixtures or fakers.
-- Async tests must use `await`. No floating promises.
-- Each test must be independent. No shared state between tests.
-
-## Forbidden
-
-- Casting mocks with `any` type. Create mocks using the actual interface type.
-- Creating mocks with no default return values. Always set sensible defaults (e.g. `mockResolvedValue`, stub returns).
-- Committing with `skip` or `only` left in test files.
-- Committing with debugging statements (e.g. `console.log`, `print`, `println`).
-
-## References
-
-- test-integrity skill
-- docs/failure-patterns.md FP-001: Mock not updated