@harness-engineering/cli 1.1.1 → 1.2.0

package/dist/agents/agents/skills/node_modules/zod/v4-mini/index.cjs

@@ -1,17 +0,0 @@
-"use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    var desc = Object.getOwnPropertyDescriptor(m, k);
-    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
-      desc = { enumerable: true, get: function() { return m[k]; } };
-    }
-    Object.defineProperty(o, k2, desc);
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __exportStar = (this && this.__exportStar) || function(m, exports) {
-    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-__exportStar(require("../v4/mini/index.cjs"), exports);

package/dist/agents/agents/skills/node_modules/zod/v4-mini/index.d.cts

@@ -1 +0,0 @@
-export * from "../v4/mini/index.cjs";

package/dist/agents/agents/skills/node_modules/zod/v4-mini/index.d.ts

@@ -1 +0,0 @@
-export * from "../v4/mini/index.js";

package/dist/agents/agents/skills/node_modules/zod/v4-mini/index.js

@@ -1 +0,0 @@
-export * from "../v4/mini/index.js";

package/dist/agents/agents/skills/package.json

@@ -1,17 +0,0 @@
-{
-  "name": "@harness-engineering/skills",
-  "version": "1.0.0",
-  "private": true,
-  "description": "Agent skills for harness engineering",
-  "type": "module",
-  "scripts": {
-    "test": "vitest",
-    "test:coverage": "vitest run --coverage"
-  },
-  "devDependencies": {
-    "glob": "^10.3.0",
-    "vitest": "^4.0.18",
-    "yaml": "^2.3.0",
-    "zod": "^3.22.0"
-  }
-}

package/dist/agents/agents/skills/tests/references.test.ts

@@ -1,85 +0,0 @@
-// agents/skills/tests/references.test.ts
-import { describe, it, expect } from 'vitest';
-import { glob } from 'glob';
-import { readFileSync } from 'fs';
-import { resolve, dirname } from 'path';
-import { fileURLToPath } from 'url';
-import { parse } from 'yaml';
-import { SkillMetadataSchema } from './schema';
-
-const __dirname = dirname(fileURLToPath(import.meta.url));
-const SKILLS_DIR = resolve(__dirname, '..');
-
-describe('skill.yaml schema validation', () => {
-  const skillFiles = glob.sync('**/skill.yaml', {
-    cwd: SKILLS_DIR,
-    ignore: ['**/node_modules/**', '**/tests/**'],
-  });
-
-  if (skillFiles.length === 0) {
-    it.skip('no skill files found yet', () => {});
-    return;
-  }
-
-  // Only validate skills that match the new schema (skip old-format during migration)
-  const validSkills = skillFiles.filter((file) => {
-    const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-    const parsed = parse(content);
-    return SkillMetadataSchema.safeParse(parsed).success;
-  });
-
-  if (validSkills.length === 0) {
-    it.skip('no skills matching new schema found yet', () => {});
-  } else {
-    it.each(validSkills)('%s conforms to schema', (file) => {
-      const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-      const parsed = parse(content);
-      const result = SkillMetadataSchema.safeParse(parsed);
-      expect(
-        result.success,
-        `Schema validation failed for ${file}: ${JSON.stringify(result)}`
-      ).toBe(true);
-    });
-  }
-});
-
-describe('depends_on references', () => {
-  const skillFiles = glob.sync('**/skill.yaml', {
-    cwd: SKILLS_DIR,
-    ignore: ['**/node_modules/**', '**/tests/**'],
-  });
-
-  if (skillFiles.length === 0) {
-    it.skip('no skill files found yet', () => {});
-    return;
-  }
-
-  // Only validate skills matching new schema; collect all names for reference checking
-  const allSkillNames = new Set<string>();
-  for (const file of skillFiles) {
-    const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-    const parsed = parse(content);
-    if (parsed?.name) allSkillNames.add(parsed.name);
-  }
-
-  const validSkills = skillFiles.filter((file) => {
-    const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-    const parsed = parse(content);
-    return SkillMetadataSchema.safeParse(parsed).success;
-  });
-
-  if (validSkills.length === 0) {
-    it.skip('no skills matching new schema found yet', () => {});
-  } else {
-    it.each(validSkills)('%s depends_on references existing skills', (file) => {
-      const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-      const parsed = parse(content);
-      const result = SkillMetadataSchema.safeParse(parsed);
-      if (!result.success) return;
-
-      for (const dep of result.data.depends_on) {
-        expect(allSkillNames.has(dep), `${file} references unknown skill: ${dep}`).toBe(true);
-      }
-    });
-  }
-});

package/dist/agents/agents/skills/tests/schema.test.ts

@@ -1,95 +0,0 @@
-// agents/skills/tests/schema.test.ts
-import { describe, it, expect } from 'vitest';
-import { SkillMetadataSchema } from './schema';
-
-describe('SkillMetadataSchema', () => {
-  const validSkill = {
-    name: 'harness-tdd',
-    version: '1.0.0',
-    description: 'Test-driven development integrated with harness validation',
-    triggers: ['manual', 'on_new_feature', 'on_bug_fix'],
-    platforms: ['claude-code', 'gemini-cli'],
-    tools: ['Bash', 'Read', 'Write', 'Edit'],
-    type: 'rigid',
-  };
-
-  it('validates a complete skill.yaml', () => {
-    const result = SkillMetadataSchema.safeParse(validSkill);
-    expect(result.success).toBe(true);
-  });
-
-  it('validates with all optional fields', () => {
-    const full = {
-      ...validSkill,
-      cli: {
-        command: 'harness skill run harness-tdd',
-        args: [{ name: 'path', description: 'Project root', required: false }],
-      },
-      mcp: { tool: 'run_skill', input: { skill: 'harness-tdd', path: 'string' } },
-      phases: [
-        { name: 'red', description: 'Write failing test' },
-        { name: 'green', description: 'Implement minimal code' },
-      ],
-      state: { persistent: true, files: ['.harness/state.json'] },
-      depends_on: ['harness-verification'],
-    };
-    const result = SkillMetadataSchema.safeParse(full);
-    expect(result.success).toBe(true);
-  });
-
-  it('applies defaults for optional fields', () => {
-    const result = SkillMetadataSchema.parse(validSkill);
-    expect(result.state).toEqual({ persistent: false, files: [] });
-    expect(result.depends_on).toEqual([]);
-  });
-
-  it('rejects invalid name format', () => {
-    const result = SkillMetadataSchema.safeParse({ ...validSkill, name: 'Invalid Name' });
-    expect(result.success).toBe(false);
-  });
-
-  it('rejects invalid platform', () => {
-    const result = SkillMetadataSchema.safeParse({ ...validSkill, platforms: ['invalid'] });
-    expect(result.success).toBe(false);
-  });
-
-  it('rejects invalid trigger', () => {
-    const result = SkillMetadataSchema.safeParse({ ...validSkill, triggers: ['on_deploy'] });
-    expect(result.success).toBe(false);
-  });
-
-  it('rejects invalid type', () => {
-    const result = SkillMetadataSchema.safeParse({ ...validSkill, type: 'optional' });
-    expect(result.success).toBe(false);
-  });
-
-  it('rejects invalid version format', () => {
-    const result = SkillMetadataSchema.safeParse({ ...validSkill, version: '1' });
-    expect(result.success).toBe(false);
-  });
-
-  it('validates phase with required field', () => {
-    const withPhases = {
-      ...validSkill,
-      phases: [
-        { name: 'red', description: 'Write failing test', required: true },
-        { name: 'refactor', description: 'Clean up', required: false },
-      ],
-    };
-    const result = SkillMetadataSchema.safeParse(withPhases);
-    expect(result.success).toBe(true);
-    if (result.success) {
-      expect(result.data.phases![0].required).toBe(true);
-      expect(result.data.phases![1].required).toBe(false);
-    }
-  });
-
-  it('defaults required to true for phases', () => {
-    const withPhases = {
-      ...validSkill,
-      phases: [{ name: 'red', description: 'Write failing test' }],
-    };
-    const result = SkillMetadataSchema.parse(withPhases);
-    expect(result.phases![0].required).toBe(true);
-  });
-});

package/dist/agents/agents/skills/tests/schema.ts

@@ -1,66 +0,0 @@
-// agents/skills/tests/schema.ts
-import { z } from 'zod';
-
-const SkillPhaseSchema = z.object({
-  name: z.string(),
-  description: z.string(),
-  required: z.boolean().default(true),
-});
-
-const SkillCliSchema = z.object({
-  command: z.string(),
-  args: z
-    .array(
-      z.object({
-        name: z.string(),
-        description: z.string(),
-        required: z.boolean().default(false),
-      })
-    )
-    .default([]),
-});
-
-const SkillMcpSchema = z.object({
-  tool: z.string(),
-  input: z.record(z.string()),
-});
-
-const SkillStateSchema = z.object({
-  persistent: z.boolean().default(false),
-  files: z.array(z.string()).default([]),
-});
-
-const ALLOWED_TRIGGERS = [
-  'manual',
-  'on_pr',
-  'on_commit',
-  'on_new_feature',
-  'on_bug_fix',
-  'on_refactor',
-  'on_project_init',
-  'on_review',
-] as const;
-
-const ALLOWED_PLATFORMS = ['claude-code', 'gemini-cli'] as const;
-
-export const SkillMetadataSchema = z.object({
-  name: z.string().regex(/^[a-z][a-z0-9-]*$/, 'Name must be lowercase with hyphens'),
-  version: z.string().regex(/^\d+\.\d+\.\d+$/, 'Version must be semver format'),
-  description: z.string(),
-  triggers: z.array(z.enum(ALLOWED_TRIGGERS)),
-  platforms: z.array(z.enum(ALLOWED_PLATFORMS)),
-  tools: z.array(z.string()),
-  cli: SkillCliSchema.optional(),
-  mcp: SkillMcpSchema.optional(),
-  type: z.enum(['rigid', 'flexible']),
-  phases: z.array(SkillPhaseSchema).optional(),
-  state: SkillStateSchema.default({}),
-  depends_on: z.array(z.string()).default([]),
-});
-
-export type SkillMetadata = z.infer<typeof SkillMetadataSchema>;
-export type SkillPhase = z.infer<typeof SkillPhaseSchema>;
-export type SkillCli = z.infer<typeof SkillCliSchema>;
-export type SkillState = z.infer<typeof SkillStateSchema>;
-
-export { ALLOWED_TRIGGERS, ALLOWED_PLATFORMS };

package/dist/agents/agents/skills/tests/structure.test.ts

@@ -1,82 +0,0 @@
-// agents/skills/tests/structure.test.ts
-import { describe, it, expect } from 'vitest';
-import { glob } from 'glob';
-import { readFileSync, existsSync } from 'fs';
-import { resolve, dirname } from 'path';
-import { fileURLToPath } from 'url';
-import { parse } from 'yaml';
-import { SkillMetadataSchema } from './schema';
-
-const __dirname = dirname(fileURLToPath(import.meta.url));
-const SKILLS_DIR = resolve(__dirname, '..');
-
-const REQUIRED_SECTIONS = [
-  '## When to Use',
-  '## Process',
-  '## Harness Integration',
-  '## Success Criteria',
-  '## Examples',
-];
-const RIGID_SECTIONS = ['## Gates', '## Escalation'];
-
-describe('SKILL.md structure', () => {
-  const skillMdFiles = glob.sync('**/SKILL.md', {
-    cwd: SKILLS_DIR,
-    ignore: ['**/node_modules/**', '**/tests/**'],
-  });
-
-  if (skillMdFiles.length === 0) {
-    it.skip('no SKILL.md files found yet', () => {});
-    return;
-  }
-
-  it.each(skillMdFiles)('%s has required sections', (file) => {
-    const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-    for (const section of REQUIRED_SECTIONS) {
-      expect(content, `Missing section: ${section} in ${file}`).toContain(section);
-    }
-  });
-
-  it.each(skillMdFiles)('%s starts with h1 heading', (file) => {
-    const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-    expect(content.trim()).toMatch(/^# /);
-  });
-
-  it.each(skillMdFiles)('%s has corresponding skill.yaml', (file) => {
-    const dir = resolve(SKILLS_DIR, file, '..');
-    expect(existsSync(resolve(dir, 'skill.yaml')), `Missing skill.yaml for ${file}`).toBe(true);
-  });
-});
-
-describe('rigid skills have Gates and Escalation sections', () => {
-  const skillYamlFiles = glob.sync('**/skill.yaml', {
-    cwd: SKILLS_DIR,
-    ignore: ['**/node_modules/**', '**/tests/**'],
-  });
-
-  if (skillYamlFiles.length === 0) {
-    it.skip('no skill.yaml files found yet', () => {});
-    return;
-  }
-
-  const rigidSkills = skillYamlFiles.filter((file) => {
-    const content = readFileSync(resolve(SKILLS_DIR, file), 'utf-8');
-    const parsed = parse(content);
-    return parsed?.type === 'rigid';
-  });
-
-  if (rigidSkills.length === 0) {
-    it.skip('no rigid skills found yet', () => {});
-    return;
-  }
-
-  it.each(rigidSkills)('%s (rigid) has Gates and Escalation sections', (file) => {
-    const dir = resolve(SKILLS_DIR, file, '..');
-    const skillMdPath = resolve(dir, 'SKILL.md');
-    if (!existsSync(skillMdPath)) return; // skip if SKILL.md doesn't exist yet
-    const content = readFileSync(skillMdPath, 'utf-8');
-    for (const section of RIGID_SECTIONS) {
-      expect(content, `Rigid skill missing section: ${section}`).toContain(section);
-    }
-  });
-});

package/dist/agents/agents/skills/tsconfig.json

@@ -1,12 +0,0 @@
-{
-  "extends": "../../tsconfig.base.json",
-  "compilerOptions": {
-    "outDir": "./dist",
-    "rootDir": ".",
-    "module": "NodeNext",
-    "moduleResolution": "NodeNext",
-    "types": ["node"]
-  },
-  "include": ["tests/**/*"],
-  "exclude": ["node_modules", "dist"]
-}

package/dist/agents/agents/skills/vitest.config.mts

@@ -1,9 +0,0 @@
-import { defineConfig } from 'vitest/config';
-
-export default defineConfig({
-  test: {
-    globals: true,
-    environment: 'node',
-    include: ['tests/**/*.test.ts'],
-  },
-});

package/dist/agents/skills/.turbo/turbo-test.log

@@ -1,16 +0,0 @@
-
-> @harness-engineering/skills@1.0.0 test /Users/cwarner/Projects/harness-engineering/agents/skills
-> vitest
-
-
- RUN  v4.0.18 /Users/cwarner/Projects/harness-engineering/agents/skills
-
- ✓ tests/schema.test.ts (10 tests) 5ms
- ✓ tests/structure.test.ts (91 tests) 10ms
- ✓ tests/references.test.ts (48 tests) 41ms
-
- Test Files  3 passed (3)
-      Tests  149 passed (149)
-   Start at  12:08:55
-   Duration  572ms (transform 58ms, setup 0ms, import 443ms, tests 56ms, environment 0ms)
-

package/dist/agents/skills/gemini-cli/add-harness-component/SKILL.md

@@ -1,182 +0,0 @@
-# Add Harness Component
-
-> Add layers, documentation, components, or skills to an existing harness project with proper integration. Validate against existing constraints, wire into architecture, and verify the result.
-
-## When to Use
-
-- Adding a new layer to the project's architecture
-- Adding a new documentation file that harness should track
-- Adding a new component (module, service, package) that must be wired into existing layer boundaries
-- Adding a new skill to the project's skill library
-- When a plan calls for introducing a new architectural boundary or module
-- NOT when initializing a project from scratch (use initialize-harness-project)
-- NOT when modifying an existing component (use standard editing workflows)
-- NOT when removing components (manual process — removing requires careful dependency analysis)
-
-## Process
-
-### Phase 1: DETERMINE — Identify What to Add
-
-1. **Clarify the component type.** Ask if not obvious from context:
-   - **Layer:** A new architectural boundary (e.g., adding an "infrastructure" layer to a project that only has "business" and "data")
-   - **Document:** A documentation file that harness should track for drift detection (e.g., API docs, architecture decision records)
-   - **Component:** A code module, service, or package that lives within an existing layer
-   - **Skill:** A new harness skill definition for the project's workflow
-
-2. **Gather requirements.** For each type:
-   - **Layer:** Name, which directories belong to it, which layers it can import from, which layers can import from it
-   - **Document:** Path, what it documents, which code files it relates to
-   - **Component:** Name, which layer it belongs to, what it depends on, what will depend on it
-   - **Skill:** Name, purpose, type (rigid or flexible), triggers
-
-3. **Check prerequisites.** The project must already be initialized with harness. If `harness.yaml` does not exist, stop and run initialize-harness-project first.
-
-### Phase 2: VALIDATE — Check Against Existing Constraints
-
-1. **Read the current configuration.** Load `harness.yaml` and `AGENTS.md` to understand existing layers, constraints, and architecture.
-
-2. **Verify the new component does not conflict:**
-   - Does the layer name already exist?
-   - Does the component directory already exist?
-   - Would the new dependency relationships create circular imports?
-   - Does the component violate any existing forbidden-import rules?
-
-3. **If conflicts are found,** report them clearly: "Adding layer X would conflict with existing layer Y because [reason]. Options: [A] rename, [B] merge into existing layer, [C] restructure. Which do you prefer?"
-
-4. **Run `harness check-deps`** on the current state to establish a clean baseline. If it already fails, fix existing violations before adding new components.
-
-### Phase 3: ADD — Create the Component
-
-1. **Run `harness add` with appropriate arguments:**
-   - Layer: `harness add layer <name> --dirs <dir1,dir2> --imports <allowed-layers>`
-   - Document: `harness add doc <path> --tracks <related-code-paths>`
-   - Component: `harness add component <name> --layer <layer-name>`
-   - Skill: `harness add skill <name> --type <rigid|flexible>`
-
-2. **Review generated files and configuration changes.** `harness add` modifies `harness.yaml` and may generate template files. Check that the changes look correct.
-
-3. **Create the actual code or content.** `harness add` creates the configuration entry but not necessarily the implementation. Create the directories, files, and initial code as needed.
-
-### Phase 4: WIRE — Integrate into Architecture
-
-1. **Update imports and exports.** If the new component needs to be imported by existing code, add the imports. If existing code needs to be aware of the new layer, update barrel files or index modules.
-
-2. **Update `AGENTS.md`.** Add the new component to the architecture section. Document its purpose, boundaries, and relationships to other components. This keeps agent instructions accurate.
-
-3. **Update layer configuration** if the new component changes dependency relationships. Ensure `harness.yaml` reflects the actual import graph.
-
-4. **For new skills:** Write the `skill.yaml` and `SKILL.md` files following the harness skill format. Use harness-skill-authoring for guidance on writing good skill content.
-
-### Phase 5: VERIFY — Confirm Integration
-
-1. **Run `harness validate`** to verify the full project configuration is still valid after the addition.
-
-2. **Run `harness check-deps`** to verify no dependency violations were introduced. The new component's imports must respect layer boundaries.
-
-3. **If validation fails,** fix the issues before committing. Common causes:
-   - New layer not properly registered in `harness.yaml`
-   - Component placed in wrong directory for its declared layer
-   - Imports from forbidden layers
-   - `AGENTS.md` references outdated architecture
-
-4. **Commit the addition.** All new and modified files in a single atomic commit.
-
-## Harness Integration
-
-- **`harness add layer <name>`** — Register a new architectural layer with directory mappings and import rules.
-- **`harness add doc <path>`** — Register a documentation file for drift tracking.
-- **`harness add component <name> --layer <layer>`** — Register a new code component within an existing layer.
-- **`harness add skill <name> --type <type>`** — Scaffold a new skill definition.
-- **`harness validate`** — Verify project configuration after the addition.
-- **`harness check-deps`** — Verify dependency constraints are respected after the addition.
-
-## Success Criteria
-
-- The new component is properly registered in `harness.yaml`
-- The component's files exist in the correct directories for its declared layer
-- `AGENTS.md` is updated to reflect the new component
-- `harness validate` passes after the addition
-- `harness check-deps` passes after the addition (no new violations)
-- No circular dependencies were introduced
-- The addition is committed as a single atomic commit
-
-## Examples
-
-### Example: Adding a New Layer
-
-```
-Human: "We need an infrastructure layer for external API clients."
-
-DETERMINE: Adding a layer. Name: infrastructure. Dirs: src/infrastructure/.
-  Imports from: (none — infrastructure is a leaf layer, no internal dependencies).
-  Imported by: business layer (services call external APIs through infrastructure).
-
-VALIDATE:
-  Read harness.yaml — existing layers: presentation, business, data.
-  No conflict with "infrastructure" name.
-  Run: harness check-deps — passes (clean baseline).
-
-ADD:
-  harness add layer infrastructure --dirs src/infrastructure --imports none
-  mkdir -p src/infrastructure
-
-WIRE:
-  Update harness.yaml: allow business → infrastructure imports.
-  Update AGENTS.md: document infrastructure layer purpose and boundaries.
-
-VERIFY:
-  harness validate    # Pass
-  harness check-deps  # Pass
-  git add harness.yaml AGENTS.md src/infrastructure/
-  git commit -m "feat: add infrastructure layer for external API clients"
-```
-
-### Example: Adding a Document for Drift Tracking
-
-```
-Human: "Track our API specification for documentation drift."
-
-DETERMINE: Adding a document. Path: docs/api-spec.md.
-  Tracks: src/routes/, src/models/response.ts.
-
-ADD:
-  harness add doc docs/api-spec.md --tracks src/routes,src/models/response.ts
-
-WIRE:
-  Update AGENTS.md: note that docs/api-spec.md is tracked for drift.
-
-VERIFY:
-  harness validate  # Pass
-  git add harness.yaml AGENTS.md
-  git commit -m "feat: track API spec for documentation drift detection"
-```
-
-### Example: Adding a Component to an Existing Layer
-
-```
-Human: "Add a notification service to the business layer."
-
-DETERMINE: Adding a component. Name: notification-service. Layer: business.
-  Depends on: data layer (notification repository). Depended on by: presentation layer (routes).
-
-VALIDATE:
-  Read harness.yaml — business layer exists, maps to src/services/.
-  No existing notification-service directory.
-  business → data is an allowed import. Presentation → business is allowed.
-  Run: harness check-deps — passes.
-
-ADD:
-  harness add component notification-service --layer business
-  Create src/services/notification-service.ts
-  Create src/services/notification-service.test.ts
-
-WIRE:
-  Add export to src/services/index.ts (if barrel file exists).
-  Update AGENTS.md: add notification service to business layer component list.
-
-VERIFY:
-  harness validate    # Pass
-  harness check-deps  # Pass
-  git add harness.yaml AGENTS.md src/services/notification-service.*
-  git commit -m "feat: add notification service to business layer"
-```

package/dist/agents/skills/gemini-cli/add-harness-component/skill.yaml

@@ -1,32 +0,0 @@
-name: add-harness-component
-version: "1.0.0"
-description: Add a component to an existing harness project
-cognitive_mode: constructive-architect
-triggers:
-  - manual
-platforms:
-  - claude-code
-  - gemini-cli
-tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
-  - Glob
-cli:
-  command: harness skill run add-harness-component
-  args:
-    - name: path
-      description: Project root path
-      required: false
-mcp:
-  tool: run_skill
-  input:
-    skill: add-harness-component
-    path: string
-type: flexible
-state:
-  persistent: false
-  files: []
-depends_on:
-  - initialize-harness-project