@harness-engineering/cli 1.26.1 → 1.27.0

package/dist/templates/orchestrator/harness.orchestrator.md

@@ -64,14 +64,24 @@ Your goal is to implement the following issue using the standard Harness Enginee
 
 ## Standard Workflow
 
-Follow these steps exactly, using the corresponding slash commands to ensure high-quality, architecturally sound delivery:
+Follow these steps exactly, using the corresponding slash commands to ensure
+high-quality, architecturally sound delivery:
 
-1. **Brainstorming:** Use `/harness:brainstorming` to explore the problem space and draft a technical proposal in `docs/changes/`.
-2. **Planning:** Use `/harness:planning` to create a detailed implementation plan and task breakdown.
-3. **Execution:** Use `/harness:execution` to implement the changes task-by-task, following TDD principles.
-4. **Verification:** Use `/harness:verification` to ensure the implementation is complete, wired correctly, and meets all requirements.
-5. **Code Review:** Use `/harness:code-review` and `/harness:pre-commit-review` to perform a final quality check before completing the task.
-6. **Ship:** When the review is clean, you are pre-authorized to ship without asking:
+1. **Brainstorming:** Use `/harness:brainstorming` to explore the problem space
+   and draft a technical proposal in `docs/changes/`. The spec MUST include an
+   Integration Points section defining how the feature connects to the system.
+2. **Planning:** Use `/harness:planning` to create a detailed implementation plan.
+   The plan MUST include integration tasks derived from the spec's Integration Points.
+3. **Execution:** Use `/harness:execution` to implement the changes task-by-task,
+   including integration tasks (registrations, ADRs, doc updates).
+4. **Verification:** Use `/harness:verification` to ensure the implementation is
+   complete, wired correctly, and meets all requirements.
+5. **Integration:** Use `/harness:integration` to verify that system wiring,
+   knowledge materialization, and documentation updates are complete per the
+   integration tier.
+6. **Code Review:** Use `/harness:code-review` and `/harness:pre-commit-review`
+   to perform a final quality check before completing the task.
+7. **Ship:** When the review is clean, you are pre-authorized to ship without asking:
    - Create a topic branch if you are still on `main`/`master` (e.g. `feat/{{ issue.identifier }}`).
    - Stage your changes and create a descriptive commit (Conventional Commits style).
    - Push the branch with `git push -u origin HEAD`.
@@ -91,6 +101,6 @@ Follow these steps exactly, using the corresponding slash commands to ensure hig
 - Always verify your changes with `harness validate`.
 - Adhere to the architectural constraints defined in `harness.config.json`.
 - Document your progress and any learnings in `.harness/learnings.md`.
-- Step 6 (Ship) is part of the standard workflow. Do not pause to ask for commit authorization — completing the issue means the PR has been opened.
+- Step 7 (Ship) is part of the standard workflow. Do not pause to ask for commit authorization — completing the issue means the PR has been opened.
 
 Attempt Number: {{ attempt }}

package/dist/{validate-CWGXR7QM.js → validate-EAVGKZQB.js}

@@ -1,12 +1,12 @@
 import {
   handleValidateProject,
   validateToolDefinition
-} from "./chunk-NY7DTZ6K.js";
-import "./chunk-TSVYBDDE.js";
+} from "./chunk-Q5DKIL46.js";
+import "./chunk-YZH4I4JO.js";
 import "./chunk-W6Y7ZW3Y.js";
-import "./chunk-YC4EYIER.js";
+import "./chunk-IBTHD2UA.js";
 import "./chunk-RL4VMEXL.js";
-import "./chunk-2FPUPRCY.js";
+import "./chunk-GAIOIINV.js";
 import "./chunk-KFQGP6VL.js";
 export {
   handleValidateProject,

package/dist/{validate-cross-check-BKCNLZYG.js → validate-cross-check-SPL3H4O5.js}

@@ -1,9 +1,9 @@
 import {
   runCrossCheck
-} from "./chunk-7GY6WNEI.js";
-import "./chunk-YC4EYIER.js";
+} from "./chunk-SDPHFDQS.js";
+import "./chunk-IBTHD2UA.js";
 import "./chunk-RL4VMEXL.js";
-import "./chunk-2FPUPRCY.js";
+import "./chunk-GAIOIINV.js";
 import "./chunk-KFQGP6VL.js";
 export {
   runCrossCheck

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@harness-engineering/cli",
-  "version": "1.26.1",
+  "version": "1.27.0",
   "description": "CLI for Harness Engineering toolkit",
   "type": "module",
   "bin": {
@@ -37,13 +37,21 @@
     "web-tree-sitter": "^0.24.7",
     "yaml": "^2.8.3",
     "zod": "^3.25.76",
-    "@harness-engineering/core": "0.23.2",
-    "@harness-engineering/dashboard": "0.2.1",
-    "@harness-engineering/graph": "0.5.0",
+    "@harness-engineering/core": "0.23.3",
+    "@harness-engineering/dashboard": "0.2.2",
+    "@harness-engineering/graph": "0.6.0",
     "@harness-engineering/linter-gen": "0.1.7",
-    "@harness-engineering/orchestrator": "0.2.14",
+    "@harness-engineering/orchestrator": "0.2.15",
     "@harness-engineering/types": "0.10.1"
   },
+  "peerDependencies": {
+    "@harness-engineering/intelligence": "0.1.3"
+  },
+  "peerDependenciesMeta": {
+    "@harness-engineering/intelligence": {
+      "optional": true
+    }
+  },
   "devDependencies": {
     "@types/node": "^22.19.15",
     "@types/semver": "^7.7.1",

package/dist/hooks/profiles.ts

@@ -1,48 +0,0 @@
-/**
- * Hook profile definitions.
- *
- * Profiles are additive: each higher tier includes all hooks from lower tiers.
- * - minimal: safety floor (block-no-verify only)
- * - standard: + protect-config, quality-gate, pre-compact-state (default)
- * - strict: + cost-tracker, sentinel-pre, sentinel-post
- */
-
-export type HookProfile = 'minimal' | 'standard' | 'strict';
-
-export interface HookScript {
-  /** Script filename without .js extension */
-  name: string;
-  /** Claude Code hook event */
-  event: 'PreToolUse' | 'PostToolUse' | 'PreCompact' | 'Stop';
-  /** Tool matcher pattern */
-  matcher: string;
-  /** Minimum profile tier that includes this hook */
-  minProfile: HookProfile;
-}
-
-export const HOOK_SCRIPTS: HookScript[] = [
-  { name: 'block-no-verify', event: 'PreToolUse', matcher: 'Bash', minProfile: 'minimal' },
-  { name: 'protect-config', event: 'PreToolUse', matcher: 'Write|Edit', minProfile: 'standard' },
-  { name: 'quality-gate', event: 'PostToolUse', matcher: 'Edit|Write', minProfile: 'standard' },
-  { name: 'pre-compact-state', event: 'PreCompact', matcher: '*', minProfile: 'standard' },
-  { name: 'adoption-tracker', event: 'Stop', matcher: '*', minProfile: 'standard' },
-  { name: 'telemetry-reporter', event: 'Stop', matcher: '*', minProfile: 'standard' },
-  { name: 'cost-tracker', event: 'Stop', matcher: '*', minProfile: 'strict' },
-  { name: 'sentinel-pre', event: 'PreToolUse', matcher: '*', minProfile: 'strict' },
-  { name: 'sentinel-post', event: 'PostToolUse', matcher: '*', minProfile: 'strict' },
-];
-
-const PROFILE_ORDER: HookProfile[] = ['minimal', 'standard', 'strict'];
-
-function hooksForProfile(profile: HookProfile): string[] {
-  const profileIndex = PROFILE_ORDER.indexOf(profile);
-  return HOOK_SCRIPTS.filter((h) => PROFILE_ORDER.indexOf(h.minProfile) <= profileIndex).map(
-    (h) => h.name
-  );
-}
-
-export const PROFILES: Record<HookProfile, string[]> = {
-  minimal: hooksForProfile('minimal'),
-  standard: hooksForProfile('standard'),
-  strict: hooksForProfile('strict'),
-};