opencode-matrixx 2.6.10 → 2.6.12

package/dist/tools/index.d.ts

@@ -4,11 +4,13 @@ export { createBddCreateContractTool } from "./bdd-create-contract";
 export { createBddParseGherkinTool } from "./bdd-parse-gherkin";
 export { createBddPipelineTool } from "./bdd-pipeline";
 export { createBddValidateContractTool } from "./bdd-validate-contract";
+export { createEvolutionTool } from "./evolution";
 export { createGithubSearchTools } from "./github-search";
 export { createGlobTools } from "./glob";
 export { createGrepTools } from "./grep";
 export { createHandoffTools } from "./handoff";
 export { interactive_bash, startBackgroundCheck as startTmuxCheck } from "./interactive-bash";
+export { createKnowledgeHubConfirmTool } from "./knowledge-hub-confirm";
 export { createPdfExtractFiguresTool } from "./pdf-extract-figures";
 export { createPlanCreateTool } from "./plan/plan-create";
 export { createPlanDeleteTool } from "./plan/plan-delete";
@@ -25,7 +27,6 @@ import type { PluginInput, ToolDefinition } from "@opencode-ai/plugin";
 import type { BackgroundManager } from "../features/background-agent";
 type OpencodeClient = PluginInput["client"];
 export { createAssemblyTool } from "./assembly";
-export { createDcpSwitchProfileTool } from "./dcp-switch-profile";
 export { createDelegateTask } from "./delegate-task";
 export { createHashlineEditTool } from "./hashline-edit";
 export { createLookAt } from "./look-at";

package/dist/tools/knowledge-hub-confirm/index.d.ts

@@ -0,0 +1 @@
+export { createKnowledgeHubConfirmTool } from "./tools";

package/dist/tools/knowledge-hub-confirm/tools.d.ts

@@ -0,0 +1,12 @@
+import type { PluginInput } from "@opencode-ai/plugin";
+import { type ToolDefinition } from "@opencode-ai/plugin/tool";
+/**
+ * `knowledge_hub_confirm` tool — records a user-confirmed override for the
+ * knowledge-hub read-only guard.
+ *
+ * Call this ONLY after the user explicitly approved the write via the
+ * question tool. It records a session-scoped approval (default TTL 10 min)
+ * for the resolved absolute path, then the agent retries the blocked write
+ * and the guard lets it through.
+ */
+export declare function createKnowledgeHubConfirmTool(ctx: PluginInput): ToolDefinition;

package/dist/tools/knowledge-hub-confirm/tools.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/tools/plan/constants.d.ts

@@ -4,6 +4,7 @@
  */
 export declare const PLANS_DIR = ".matrixx/plans";
 export declare const MAX_PLAN_FILE_BYTES = 102400;
+export declare const MAX_PLAN_READ_RENDERED_BYTES = 40000;
 export declare const PLAN_FILENAME_KEBAB_REGEX: RegExp;
 export declare const PLAN_BASENAME_KEBAB_REGEX: RegExp;
 export declare const META_TAG_PREFIX = "<!-- plan-persister:";

package/dist/tools/plan/index.d.ts

@@ -3,4 +3,5 @@ export { createPlanCreateTool } from "./plan-create";
 export { createPlanDeleteTool } from "./plan-delete";
 export { createPlanListTool } from "./plan-list";
 export { createPlanReadTool } from "./plan-read";
+export { createPlanTasksTool } from "./plan-tasks";
 export { createPlanUpdateTool } from "./plan-update";

package/dist/tools/plan/plan-tasks.d.ts

@@ -0,0 +1,3 @@
+import { type ToolDefinition } from "@opencode-ai/plugin/tool";
+import type { PluginContext } from "../../plugin/types";
+export declare function createPlanTasksTool(ctx?: PluginContext): ToolDefinition;

package/dist/tools/plan/types.d.ts

@@ -9,8 +9,18 @@ export interface PlanCreateArgs {
     filePath: string;
     content: string;
 }
+export type PlanReadFormat = "hashline" | "content";
+export interface PlanOutlineEntry {
+    level: 2 | 3;
+    text: string;
+    line: number;
+    anchor: string;
+}
 export interface PlanReadArgs {
     filePath: string;
+    format?: PlanReadFormat;
+    offset?: number;
+    limit?: number;
 }
 export interface PlanUpdateArgs {
     filePath: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-matrixx",
-  "version": "2.6.10",
+  "version": "2.6.12",
   "description": "The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/dist/config/schema/failure-counter.d.ts

@@ -1,7 +0,0 @@
-import { z } from "zod";
-export declare const FailureCounterConfigSchema: z.ZodObject<{
-    enabled: z.ZodDefault<z.ZodBoolean>;
-    threshold: z.ZodDefault<z.ZodNumber>;
-    resetOnSuccess: z.ZodDefault<z.ZodBoolean>;
-}, z.core.$strip>;
-export type FailureCounterConfig = z.infer<typeof FailureCounterConfigSchema>;

package/dist/features/builtin-commands/templates/bdd-backend.d.ts

@@ -1 +0,0 @@
-export declare const BDD_BACKEND_TEMPLATE = "# /bdd-backend\n\nGenerate typed API services from one or more BDD Contract JSON files.\n\n## Usage\n\nSingle file:\n```\n/bdd-backend <contract.json> --out <out-dir>\n```\n\nBatch (directory or glob):\n```\n/bdd-backend <dir> --out <out-dir>\n/bdd-backend \"<dir>/**/*.contract.json\" --out <out-dir>\n```\n\n## Workflow\n\nSingle file:\n1. Read the Contract JSON\n2. Extract @api:endpoint and @api:response annotations\n3. Generate typed service files with Zod request/response schemas\n4. One service function per endpoint\n5. Report generated file paths\n\nBatch input (directory or glob):\n1. Expand the input into a list of .contract.json files\n2. For each contract, run the single-file workflow above\n3. Use background subagents (`task(run_in_background=true)`) to run each in parallel (up to 5 concurrent)\n4. Wait for all to finish, then collect results and report a summary\n\n## Output\n\nSingle file: TypeScript service files (.ts) with Zod validation schemas for each API endpoint.\n\nBatch: per-feature service subdirectory tree under `<out-dir>/<feature>/backend/`.\n\n## Git Actions (HARD RULE)\nNEVER run `git commit`, `git add`, `git push`, `git rebase`, `git reset`, `git tag`, or any other git command in this command context. The pipeline runner is responsible for version control. You may only create/edit the generated files in the target output directory.\n";

package/dist/features/builtin-commands/templates/bdd-contract.d.ts

@@ -1 +0,0 @@
-export declare const BDD_CONTRACT_TEMPLATE = "# /bdd-contract\n\nGenerate BDD Contract JSON from one or more Gherkin .feature files. The .feature file must be 100% pure Gherkin (no '# @annotation' comments). The bdd-contract agent infers all annotations (api/ui/state/assumptions) via LLM reasoning from feature content.\n\n## Usage\n\nSingle file:\n```\n/bdd-contract <feature-path> [--force]\n```\n\nBatch (directory or glob):\n```\n/bdd-contract <dir> [--force]\n/bdd-contract \"<dir>/**/*.feature\" [--force]\n```\n\n## Workflow\n\nSingle file:\n1. Parse the .feature file using bdd_parse_gherkin tool (deterministic AST)\n2. Create initial Contract JSON using bdd_create_contract tool (deterministic, empty annotations)\n3. ENRICH the Contract: the bdd-contract agent infers annotations (api/ui/state/assumptions) via LLM reasoning from feature content and edits the Contract JSON file in place\n4. **VALIDATE**: call bdd_validate_contract on the file -- if it returns errors, fix the contract and re-validate. The contract must conform to the strict ContractSchema (all annotation field names must match the required naming conventions: kebab-case for routes/testIds, camelCase for state variables, dotted kebab-case for string keys).\n5. Report the Contract file path, key features identified, and annotations inferred\n\nBatch input (directory or glob):\n1. Expand the input into a list of .feature files\n2. For each .feature file, run the single-file workflow above\n3. Report a summary of all generated contracts (count, paths, any failures)\n\n## Output\n\nSingle file: a `<file>.contract.json` alongside the source .feature file, conforming to ContractSchema v1 with schemaVersion: 1, scenarios, and LLM-inferred annotations.\n\nBatch: one contract file per source .feature, written next to each source file.\n\n## Git Actions (HARD RULE)\nNEVER run `git commit`, `git add`, `git push`, `git rebase`, `git reset`, `git tag`, or any other git command in this command context. The pipeline runner is responsible for version control. You may only create/edit the generated contract JSON.\n";

package/dist/features/builtin-commands/templates/bdd-frontend.d.ts

@@ -1 +0,0 @@
-export declare const BDD_FRONTEND_TEMPLATE = "# /bdd-frontend\n\nGenerate React components and a dev preview server from one or more BDD Contract JSON files.\n\n## Usage\n\nSingle file:\n```\n/bdd-frontend <contract.json>\n```\n\nBatch (directory or glob):\n```\n/bdd-frontend <dir> --out <out-dir>\n/bdd-frontend \"<dir>/**/*.contract.json\" --out <out-dir>\n```\n\n## Workflow\n\nSingle file:\n1. Read the Contract JSON\n2. Extract @ui:* annotations (routes, testIds, strings)\n3. Generate React components for each route/feature\n4. Implement form fields from state variables\n5. Apply test IDs and accessibility attributes\n6. Generate a preview-server.ts for visual review\n\nBatch input (directory or glob):\n1. Expand the input into a list of .contract.json files\n2. For each contract, run the single-file workflow above\n3. Use background subagents (`task(run_in_background=true)`) to run each in parallel (up to 5 concurrent)\n4. Wait for all to finish, then collect results and report a summary\n\n## Output\n\nSingle file: React component files (.tsx) with TypeScript props, design tokens, data-testid attributes, and a preview-server.ts for visual review.\n\nBatch: per-feature component subdirectory tree under `<out-dir>/<feature>/components/`, with one preview-server.ts per feature.\n\n## Git Actions (HARD RULE)\nNEVER run `git commit`, `git add`, `git push`, `git rebase`, `git reset`, `git tag`, or any other git command in this command context. The pipeline runner is responsible for version control. You may only create/edit the generated files in the target output directory.\n";

package/dist/features/builtin-commands/templates/bdd-tests.d.ts

@@ -1 +0,0 @@
-export declare const BDD_TESTS_TEMPLATE = "# /bdd-tests\n\nGenerate Cucumber step definitions and page objects from one or more BDD Contract JSON files.\n\n## Usage\n\nSingle file:\n```\n/bdd-tests <contract.json> --out <out-dir>\n```\n\nBatch (directory or glob):\n```\n/bdd-tests <dir> --out <out-dir>\n/bdd-tests \"<dir>/**/*.contract.json\" --out <out-dir>\n```\n\n## Workflow\n\nSingle file:\n1. Read the Contract JSON file\n2. Extract feature scenarios and their steps\n3. Generate Cucumber step definition files (Given/When/Then/And/But)\n4. Generate page object classes for UI interactions\n5. Generate `cucumber.cjs` (CommonJS, NOT `cucumber.js`) + a per-feature `Dockerfile` + `run-tests.sh` so the tests are runnable in CI and locally\n6. Verify with `npx cucumber-js` via bash (use the generated `run-tests.sh` if it exists, else invoke cucumber directly)\n\nBatch input (directory or glob):\n1. Expand the input into a list of .contract.json files\n2. For each contract, run the single-file workflow above (including the per-feature Dockerfile + run-tests.sh generation)\n3. Use background subagents (`task(run_in_background=true)`) to run each in parallel (up to 5 concurrent)\n4. Wait for all to finish and collect results\n5. AFTER all per-feature runs finish, generate TWO parent-shared files at the input directory root:\n   - `<input-dir>/Dockerfile` -- same base image as the per-feature one, CMD points to the parent run-tests.sh\n   - `<input-dir>/run-tests.sh` -- iterates every feature subdir that has a run-tests.sh and invokes it in sequence (with BDD_FEATURE filter support)\n6. Report a summary that lists the per-feature outputs AND the parent batch runner\n\n## Output\n\nSingle file: `<out-dir>/<feature>/` containing `cucumber.cjs`, `Dockerfile`, `run-tests.sh`, plus `tests/` (step definitions, page objects, world, hooks).\n\nBatch: per-feature subdirectory tree under `<input-dir>/<feature>/` with the same layout for each feature, PLUS parent-shared `<input-dir>/Dockerfile` and `<input-dir>/run-tests.sh` for running every feature in one go.\n\n## Git Actions (HARD RULE)\nNEVER run `git commit`, `git add`, `git push`, `git rebase`, `git reset`, `git tag`, or any other git command in this command context. The pipeline runner is responsible for version control. You may only create/edit the generated files in the target output directory.\n";

package/dist/features/builtin-commands/templates/dcp-profile.d.ts

@@ -1 +0,0 @@
-export declare const DCP_PROFILE_TEMPLATE = "You are switching the active DCP (Dynamic Context Pruning) profile tier.\n\nThis command is provided by the Matrixx plugin. It uses the built-in `dcp_switch_profile` tool to apply DCP profile configurations \u2014 no external scripts needed.\n\n## Step 1: Verify DCP is installed\n\nCheck whether the DCP plugin is installed at the standard OpenCode plugin location:\n\n```bash\nif [ ! -d \"$HOME/.config/opencode/node_modules/@tarquinen/opencode-dcp\" ]; then\n  echo \"DCP is not installed at the standard OpenCode plugin location.\" >&2\n  echo \"Install it with: npm install --prefix ~/.config/opencode @tarquinen/opencode-dcp\" >&2\n  exit 1\nfi\n```\n\nIf the directory does not exist, stop immediately and report the error to the user. Do not proceed.\n\n## Step 2: Determine the target profile\n\nParse the arguments passed to this command. The user invoked `/dcp-profile <arguments>` where `<arguments>` is the first positional argument.\n\n- If the argument is a known profile name (one of: economy, balanced, performance, ultimate), use it directly.\n- If the argument is empty or missing, read `dcp.default_profile` from the user's `matrixx.jsonc` config; if absent, default to `balanced`.\n- If the argument is not a recognized profile name, list the available profiles and stop. Do NOT guess or pass invalid names.\n\n## Step 3: Call the built-in `dcp_switch_profile` tool\n\nUse the `dcp_switch_profile` tool with the resolved profile name. This tool reads profile parameters from the Matrixx plugin configuration and writes the full inline DCP config to `~/.config/opencode/dcp.jsonc`.\n\nThe tool will handle all file operations \u2014 you do NOT need to run any external scripts or edit DCP config files directly.\n\n## Step 4: Confirm and instruct\n\nAfter a successful switch:\n\n1. Report the tool's output to the user.\n2. Tell the user that the new DCP configuration will take effect after they restart their OpenCode session (the active session has already loaded the previous config into memory).\n3. Do not attempt to reload DCP in-place; a session restart is required.\n\n## Important constraints\n\n- Use the built-in `dcp_switch_profile` tool. Do NOT bypass it by editing DCP config files directly.\n- Do not install, upgrade, or modify the DCP plugin from this command. If the user needs to install or upgrade DCP, instruct them to run `opencode plugin @tarquinen/opencode-dcp@<version>` (or use `npm install --prefix ~/.config/opencode` for cached installs).\n";

package/dist/hooks/failure-counter/counter.d.ts

@@ -1,7 +0,0 @@
-import { clearFailureCounter, getFailureCount, resetFailureCounter } from "../../features/session-state/state";
-export declare const CONTINUATION_COOLDOWN_MS = 30000;
-export interface HandleToolAfterOptions {
-    parentSessionID?: string;
-}
-export declare function handleToolAfter(sessionID: string, output: string, isSuccess: boolean, options?: HandleToolAfterOptions): void;
-export { clearFailureCounter, getFailureCount, resetFailureCounter };

package/dist/hooks/failure-counter/hook.d.ts

@@ -1,18 +0,0 @@
-import type { PluginInput } from "@opencode-ai/plugin";
-export declare function createFailureCounterHook(_ctx: PluginInput): {
-    "tool.execute.after": (input: {
-        tool: string;
-        sessionID: string;
-        callID: string;
-    }, output: {
-        title: string;
-        output: string;
-        metadata: unknown;
-    }) => Promise<void>;
-    event: (input: {
-        event: {
-            type: string;
-            properties: Record<string, unknown>;
-        };
-    }) => Promise<void>;
-};

package/dist/hooks/failure-counter/index.d.ts

@@ -1,3 +0,0 @@
-export * from "./counter";
-export { createFailureCounterHook } from "./hook";
-export * from "./patterns";

package/dist/hooks/failure-counter/patterns.d.ts

@@ -1,6 +0,0 @@
-export interface FailureSignature {
-    pattern: string | RegExp;
-    kind: "task_error" | "timeout" | "abort_excluded";
-}
-export declare const FAILURE_COUNTER_PATTERNS: FailureSignature[];
-export declare function isCountableFailure(output: string): boolean;

package/dist/hooks/hashline-edit-diff-enhancer/hook.d.ts

@@ -1,28 +0,0 @@
-interface HashlineEditDiffEnhancerConfig {
-    hashline_edit?: {
-        enabled: boolean;
-    };
-}
-type BeforeInput = {
-    tool: string;
-    sessionID: string;
-    callID: string;
-};
-type BeforeOutput = {
-    args: Record<string, unknown>;
-};
-type AfterInput = {
-    tool: string;
-    sessionID: string;
-    callID: string;
-};
-type AfterOutput = {
-    title: string;
-    output: string;
-    metadata: Record<string, unknown>;
-};
-export declare function createHashlineEditDiffEnhancerHook(config: HashlineEditDiffEnhancerConfig): {
-    "tool.execute.before": (input: BeforeInput, output: BeforeOutput) => Promise<void>;
-    "tool.execute.after": (input: AfterInput, output: AfterOutput) => Promise<void>;
-};
-export {};

package/dist/hooks/hashline-edit-diff-enhancer/index.d.ts

@@ -1 +0,0 @@
-export { createHashlineEditDiffEnhancerHook } from "./hook";

package/dist/tools/dcp-switch-profile/index.d.ts

@@ -1 +0,0 @@
-export { createDcpSwitchProfileTool } from "./tools";