@davesheffer/hunch 1.31.1 → 1.32.1

package/README.md

@@ -59,7 +59,7 @@ hunch integrations check --harness claude --probe --require mcp
 hunch integrations check --harness codex --require context,edit-blocking
 ```
 
-Capabilities are reported as **verified**, **advisory-only**, **unsupported** or **untested**. `--require` fails unless every named capability is verified.
+Capabilities are reported as **verified**, **advisory-only**, **unsupported** or **untested**. `--require` fails unless every named capability is verified. `mcp` is verified by a fresh-server probe; hook capabilities become verified only from lifecycle events actually delivered to Hunch's hook on the expected version within the last 30 days (machine-local evidence, the same trust level as the served ledger), so a repository whose agent has actually run shows it, and one that only has configuration does not.
 
 The Codex integration currently supplies MCP and instructions, with no native lifecycle adapter. The opt-in `--probe` verifies a fresh MCP process, not whether an existing host session or model actually followed the memory.
 
@@ -133,6 +133,7 @@ Read the [Project DNA contract](docs/project-dna.md) and broader [Project DNA vi
 | `hunch compare branch-a branch-b` | Rank candidate changes by invariant/decision conflicts |
 | `hunch prove origin/main --public-only` | Produce a publication-safe `hunch.change-proof/1` artifact for an exact committed change |
 | `hunch landscape review` | Inspect a hash-bound repository landscape without writing authority |
+| `hunch task start "<title>"` · `hunch report <id> --html` | See what Hunch contributed to a task: the lesson recalled, the agent's stated application, whether the lesson's own rule held on the changed files, and the command Hunch observed — separate evidence grades, in a local evidence view |
 | `hunch now` | See recent memory and live decision-backed roadmap |
 | `hunch escalations` | See questions that genuinely require a human answer |
 | `hunch doctor` | Diagnose setup, provider, index or overlay problems |

package/dist/cli/automaticReviewMemory.d.ts

@@ -0,0 +1,13 @@
+import type { Command } from "commander";
+import type { Constraint } from "../core/types.js";
+export interface ReviewMemoryContext {
+    root: string;
+    existing: Constraint[];
+}
+/** Only bounded tracked files inside this checkout may enter model context. */
+export declare function readReviewCode(root: string, file: string): string;
+export declare function registerAutomaticReviewMemory(command: Command, context: (repository: string, privateOnly?: boolean) => ReviewMemoryContext, capture: (records: Constraint[], repository: string, privateOnly: boolean) => void, chooseProvider?: (root: string, configFile?: string, initiator?: string) => Promise<{
+    name: string;
+    draftProse(prompt: string): Promise<string>;
+    providersUsed?: () => string[];
+}>): void;

package/dist/cli/dna.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};

package/dist/cli/index.d.ts

@@ -0,0 +1,16 @@
+#!/usr/bin/env node
+/**
+ * `hunch` CLI (DESIGN.md §6). Subcommands:
+ *   init      scaffold .hunch/, install hook, write .mcp.json + CLAUDE.md + slash cmds
+ *   index     parse repo -> symbol/dependency graph + components (no LLM)
+ *   backfill  replay git history -> seed decisions (cold-start fix)
+ *   sync      commit diff -> Claude/heuristic -> decision write-back (post-commit hook)
+ *   query     FTS + graph query over Hunch
+ *   why       decisions/bugs/constraints explaining a file/symbol
+ *   fragile   ranked fragility report with evidence
+ *   record-bug  capture a Bug from a (failing) test
+ *   test      run the suite, auto-capture failures as Bugs, resolve fixed ones
+ *   mcp       start the MCP server (Claude Code connects here)
+ *   doctor    environment diagnostics
+ */
+import "./preflight.js";