@dzhechkov/harness-cli 0.6.0 → 0.7.0

package/src/core-compat.ts

@@ -44,7 +44,10 @@ import { fileURLToPath } from 'node:url';
  * standing test (`test/core-import-floor.test.ts`, F1) fails if the two drift apart,
  * because a guard that says 0.4.7 while npm may install 0.4.2 is worse than no guard.
  */
-export const MIN_CORE = '0.6.0';
+// 0.7.0: this CLI reads `HybridRecall.semanticRanked` and `VectorTierStatus.mirroredOther` /
+// `orphaned` / `unmirrored`, none of which exist in 0.6.1 — a lower core would not merely behave
+// differently, it would be missing the fields every recall claim is now derived from.
+export const MIN_CORE = '0.7.0';
 
 /** The npm name of the guarded package — one literal, used by every leg below. */
 export const CORE_PACKAGE_NAME = '@dzhechkov/harness-core';

package/src/index.ts

@@ -15,4 +15,7 @@ export type { CliIo, ReleaseExecRunner } from './cli.js';
 // The Codex hook DELIVERY seam (crossrt-2 fix round, findings 1+2): the argv→operation mapping and
 // the one place a success word may be printed, exported so both can be pinned without a live codex.
 export { codexHooksSummary, codexHooksSyncOptions, deliverCodexHooks } from './cli.js';
+// Exported for its own test: the guard that keeps `--json` stdout parseable when a dependency greets
+// stdout. Tested directly because the end-to-end path cannot reach it without a populated vector tier.
+export { withForeignStdoutOnStderr } from './cli.js';
 export type { CodexHooksSummary, CodexHooksSyncInput } from './cli.js';