opencode-harness-kit 0.6.3 → 0.7.0

package/dist/config.d.ts

@@ -27,6 +27,35 @@ export declare const GLOBAL_INSTRUCTIONS = "~/.config/opencode/GLOBAL.md";
  * @returns {string}
  */
 export declare function kitVersion(): string;
+/** Where opencode's user config lives when nothing overrides it. */
+export declare const DEFAULT_CONFIG_DIR: string;
+/** Where this kit itself lives - the parent of the bundle (or src) directory. */
+export declare function kitRoot(): string;
+/**
+ * The skills.paths entries of a base config, with the dead ones dropped.
+ *
+ * A `paths` entry that never resolves is not a configuration - it is noise
+ * the file carries for every reader to puzzle over, and a reader who DOES
+ * puzzle over it gets a wrong model of the world: this kit's config shipped
+ * `["../skills"]` which had dl resolved to `~/.config/skills` - a directory
+ * that has never existed on this machine - for release after release.
+ *
+ * A relative entry resolves against the opencode config directory; an
+ * absolute one stands as written; a relative one is also checked against the
+ * kit root, because an entry pointing INTO the kit was always a plausible
+ * intent and the kit knows where its own skills are. Nothing that resolves
+ * is kept; word everything else is dropped and named in the header, the same
+ * way dropped bash rules and removed lanes are.
+ *
+ * @param {any} skills
+ * @param {string} configDir
+ * @param {string} [kitRoot] where the kit itself lives, when overridable
+ * @returns {{ skills: any, dropped: string[] }}
+ */
+export declare function cleanSkillPaths(skills: any, configDir: string, kitRoot?: string): {
+    skills: any;
+    dropped: string[];
+};
 /**
  * The memory plugin this kit can turn on.
  *
@@ -122,11 +151,15 @@ export declare const BASH_ALLOWLIST: string[];
 export { BASH_DENYLIST } from "./denylist.js";
 /**
  * @param {Profile} p
- * @param {{ base?: Record<string, any>, comments?: boolean, unhealthy?: Set<string> }} [opts]
+ * @param {{ base?: Record<string, any>, comments?: boolean, unhealthy?: Set<string>,
+ *          configDir?: string, kitRoot?: string, skills?: boolean }} [opts]
  * @returns {string}
  */
 export declare function generateConfig(p: Profile, opts?: {
     base?: Record<string, any>;
     comments?: boolean;
     unhealthy?: Set<string>;
+    configDir?: string;
+    kitRoot?: string;
+    skills?: boolean;
 }): string;

package/dist/effort.d.ts

@@ -35,12 +35,23 @@ export type EffortResult = {
  */
 export declare const MANAGED_ROLES: string[];
 /**
+ * The spent routes the effort plan honours.
+ *
+ * `opts.unhealthy` is a bare-model set a caller computed already - the one
+ * contract the tests and the CLI use. `opts.dir` is the project root, and it
+ * asks the plan to read the health file itself under the profile's OWN
+ * provider: a health file keyed `openrouter/<x>` must not read as a spent
+ * `opencode/<x>`, and a bare set has already lost the provider it came from,
+ * so the caller cannot narrow it after the fact. Passing both is the
+ * caller's narrowed set, and it wins.
+ *
  * @param {string} profileId
- * @param {{ unhealthy?: Set<string> }} [opts]
+ * @param {{ unhealthy?: Set<string>, dir?: string }} [opts]
  * @returns {EffortResult}
  */
 export declare function planEffort(profileId: string, opts?: {
     unhealthy?: Set<string>;
+    dir?: string;
 }): EffortResult;
 /**
  * Mutate the resolved OpenCode config so each managed agent declares its own

package/dist/guard.d.ts

@@ -8,6 +8,11 @@ export declare const MARKER = "[opencode-harness-kit] blocked";
  * markers, and a plain unified diff with `--- a/path` and `+++ b/path`
  * headers.
  *
+ * An update may also carry `*** Move to: path`, which is the path the file
+ * is written TO. Reading only the `*** Update File:` line checked the file
+ * the patch read from and left the destination unchecked, so a patch could
+ * move a file out of the project while every path it named was inside it.
+ *
  * A unified diff names the file TWICE: `--- a/path` is where the change
  * comes FROM, `+++ b/path` is where it goes TO. A deletion is `--- a/path`
  * and `+++ /dev/null`, so the path that has to be scope-checked is the one

package/dist/health.d.ts

@@ -110,11 +110,22 @@ export declare function unhealthyRoutes(dir: string): Record<string, SpentEntry>
  * lane chains list bare model ids, so the prefix is dropped here. Comparing
  * the two directly would never match, and a spent route would look healthy.
  *
+ * The drop collides when two providers host the same model id: a recorded
+ * `openrouter/<x>` then reads as a spent `opencode/<x>`, and every lane whose
+ * chain names the opencode one is pushed off a route that is fine. `provider`
+ * narrows the answer to the routes a session of THAT provider can actually
+ * hit - a provider-qualified key for another provider is dropped, and a key
+ * with no provider at all is kept, because a bare key is a standing statement
+ * about the model id and it is not readable as any narrower one. Callers
+ * including the router, whose lane set may not share one provider, keep the
+ * unfiltered call and its old behaviour.
+ *
  * A route whose window has passed is not spent any more, and is not returned
  * here: the provider's quota comes back at 00:00 UTC, and a lane that stays
  * on its fallback forever is a lane that never comes back either.
  *
  * @param {string} dir the project root
+ * @param {string} [provider] only count routes served by this provider
  * @returns {Set<string>}
  */
-export declare function unhealthyModels(dir: string): Set<string>;
+export declare function unhealthyModels(dir: string, provider?: string): Set<string>;