@dzhechkov/harness-cli 0.3.221 → 0.3.223

package/README.md

@@ -431,7 +431,7 @@ Get the whole set with `dz init --target claude-code --preset meta`, or pick one
 
 > **A skill and its npx toolkit are not duplicates — they're a graduation.** Several skills (e.g. `feature-adr`, `design-thinking`) exist BOTH as a skill inside a `dz` preset AND as a standalone `npx` package. The preset's SKILL.md is **fully functional on its own** (the whole methodology — modules + references — travels with it, and it auto-activates by description), and it's the only way to compile that capability to the **non-Claude platforms** (Codex/OpenCode/Hermes/OpenClaude) via `dz`. The npx package adds **project-level runtime governance** around the same skill: a slash command, governance rules, a context shard, and (for feature-adr) reward-learning + `/harvest`. So: pick the **skill/preset** for a working capability across platforms; pick the **npx toolkit** when you want it as a governed, command-driven fixture of one project.
 
-## All Commands (47)
+## All Commands (49)
 
 ```
 dz setup             --target <name> [--preset <name>] [--select id,id,...] [--skills-dir <dir>] [--memory agentdb] [--no-memory] [--no-hooks] [--install-driver] [--force]
@@ -481,6 +481,8 @@ dz architecture      [--json] [--revise] [--check --slug <s> --desc "<text>" [--
 dz project-skills    [--json] [--stages-json]   # polymorphic feature-adr: resolve architecture/project-skills.json (fixed roles product-vision/critic/brand/impl-bar + open extra[]) into per-stage guidance; absent = generic run (byte-identical); feature-adr Step 0 reads it
 dz mr-rakes          [--json] [--candidate N --confirmed N] [--teach] [--gen-critic <path> [--apply]]   # mine review artifacts (features' QE reports + REVIEW files) for RECURRING mistakes; anti-noise (≥2/≥3 distinct sources); close into dz teach + a project-critic skill (R2 critic role)
 dz retro             [transcript] [--json] [--threshold N] [--no-teach] [--install-hook]   # per-session retro: mine the current session for recurring PROCESS rakes (claimed-done-without-verify, committed-without-verify, n-fix-cycles, ignored-correction), drill the user (socratic + checklist) AND teach the agent — co-learning via the dz teach store
+dz feature-adr-setup [--plan] [--from-spec <f>] [--apply]   # guided project onboarding engine (behind the `configure-feature-adr` skill): --plan shows which docs exist/missing; --from-spec scaffolds vision/map/testing/project-skills (propose; --apply writes; augment-never-clobber)
+dz challenge --plan <plan.md> [--json] [--context-only] [--author <model>]   # adversarial plan-gate (behind the `challenge-panel` skill): assemble a WIDE context pack (plan + vision + testing + map + degradations) + the fixed C1-C8 "break it" brief for a FRESH adversary (≠ plan author); advisory, never blocks
 dz publish           [--filter <name>] [--bump-only] [--claim-check <off|warn|error>]   (dry-run by default; pass --yes/--confirm to go live; claim-check gate defaults to warn — surfaces README claim findings, never blocks)
 dz auto-canonicalize --source <github-url> --pack <skills-pack>
 dz sync-upstream     [--package <dir>] [--list] [--all]
@@ -1343,6 +1345,30 @@ claude mcp add agentdb --env AGENTDB_PATH="$PWD/.dz/agentdb.db" -- npx agentdb@l
 Four commands that make the harness *self-aware*: it maps your product, keeps new features aligned to it, and
 learns from your reviews and sessions. Each shows **when to reach for it**, the exact command, and what it prints.
 
+### 🚀 Start here: the guided setup (no schema knowledge needed)
+
+Don't want to hand-author any config? Just tell Claude Code:
+
+> **"настрой feature-adr под мой продукт"** / **"configure feature-adr for my product"**
+
+The `configure-feature-adr` skill runs a short interview and scaffolds everything for you. Under the hood it
+uses the engine directly if you prefer the terminal:
+```bash
+dz feature-adr-setup --plan                 # which docs exist / are discoverable / are missing (read-only)
+dz feature-adr-setup --from-spec spec.json  # preview the scaffold (create / augment / unchanged)
+dz feature-adr-setup --from-spec spec.json --apply   # write — existing files are AUGMENTED, never clobbered
+```
+```
+feature-adr project setup — current state:
+  vision.md: ✓   manifest: ✓   testing.md: ✗ missing   project-skills.json: ✓
+  discovered 47 workspace package(s) → a map can be auto-scaffolded
+  next steps:
+    • author architecture/testing.md from a short interview (test commands, definition of done, gates)
+```
+It writes `architecture/vision.md`, `subsystems.manifest.json`, `testing.md` (the new `testing` role → Step-8
+QE), and wires `project-skills.json`. Re-run any time the product grows — it only augments, never overwrites.
+The four commands below are what it configures; you can also drive them directly.
+
 ### `dz architecture` — when you've lost the big picture, or before adding a feature
 
 ```bash
@@ -1404,6 +1430,36 @@ retro: 2 recurring rake(s) to drill (from 6800 events):
 First-seen rakes accrue silently; only **recurring** ones get a drill (no nagging on a one-off). The user gets the
 drill, the agent gets the taught rule — from the same mistake, out of one shared `dz teach` store.
 
+### `dz challenge` — when you have an implementation plan and want it broken BEFORE you code
+
+The cross-model QE at feature-adr Step 8 catches problems *after* the code is written. The most expensive plan
+mistakes — overengineering, silent decisions, cemented bad patterns, test-theater, unrealistic scope — cement at
+the plan stage, and the plan's author can't see their own gaps. `dz challenge` assembles the "round"; the
+`challenge-panel` skill fires it at a FRESH adversary that did **not** write the plan:
+```bash
+dz challenge --plan features/my-feature/06_implementation_plan.md              # print the WIDE brief + C1-C8 + verdict schema
+dz challenge --plan features/my-feature/06_implementation_plan.md --context-only  # just what the panel will read + the adversary to use
+dz challenge --plan features/my-feature/06_implementation_plan.md --author codex  # who wrote the plan → prints the CROSS-family adversary
+```
+```
+challenge context for features/my-feature/06_implementation_plan.md:
+  plan:        ✓ 23752 chars
+  vision:      ✓ 2443 chars
+  testing:     ✗ (less calibration)
+  map:         ✓ 4470 chars
+  degradations:✓ 719 chars
+  → adversary: codex — plan authored on claude (Claude) → Codex adversary (cross-family)
+```
+The panel asks a fixed owner-question set in "break it, don't confirm it" mode — **C1** arch-anti-cement (a
+deviation from a pattern in `architecture/degradations.md` is *not* flagged), **C2** prod-ready, **C3** test
+sufficiency + honesty (both under- and over-testing), **C4** overengineering, **C5** silent decisions, **C6**
+runtime consistency, **C7** scope, **C8** executability. Every P0/P1 finding is **cross-validated** by a second
+independent agent (theory is dropped), and the verdict is **advisory — it never auto-blocks**. Two invariants:
+the panel is never the plan's own author (cross-family adversary), and the context pack is WIDE (a narrow slice
+yields shallow findings). In the feature-adr pipeline this runs automatically at the L/XL plan checkpoint; ad-hoc,
+just say **"прогони challenge на этот план"** / **"challenge this plan"**. Scaffold the degradations registry with
+`dz feature-adr-setup --from-spec <spec with {"degradations":true}> --apply`.
+
 ## Recipes & FAQ
 
 Scenario → exact command → how to verify → gotcha. **Three gotchas worth calling out up front:**

package/dist/cli.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAgNH,2EAA2E;AAC3E,MAAM,WAAW,KAAK;IACpB,QAAQ,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC;;;;OAIG;IACH,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;CACzB;AA2xID,wBAAsB,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,EAAE,EAAE,GAAE,KAAU,GAAG,OAAO,CAAC,MAAM,CAAC,CA8H5E"}
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AA0NH,2EAA2E;AAC3E,MAAM,WAAW,KAAK;IACpB,QAAQ,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC;;;;OAIG;IACH,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;CACzB;AAy4ID,wBAAsB,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,EAAE,EAAE,GAAE,KAAU,GAAG,OAAO,CAAC,MAAM,CAAC,CAkI5E"}

package/dist/cli.js

@@ -9,7 +9,7 @@ import { fileURLToPath } from 'node:url';
 import { execSync } from 'node:child_process';
 import { homedir } from 'node:os';
 import { createRequire } from 'node:module';
-import { createSkill, getSkillInfo, getWorkflow, isTargetName, listSkills, runDoctor, runInit, benchmarkSkill, benchmarkSkills, scanMcp, reconcileCapabilities, RECONCILE_BANNER, buildRegistry, discoverSkillPackDirs, checkUpstream, compareSkills, checkAllUpstream, sweepSkillDrift, syncCanonicalSkill, checkUpgrades, discoverPackages, discoverSourcePackages, fetchAllDownloads, filterByCategory, pretrain, recommend, generatePlugin, publishPackages, runSetup, runMigrate, searchRegistry, runSync, runVerify, runInitAgentsMd, runInitGeminiMd, TARGET_NAMES, WORKFLOW_NAMES, importEcc, recordPattern, resolveLearningBackend, storeStats, consolidateSessions, pruneNoisePatterns, lessonDeltaReport, removePatternsByIds, snapshotStore, recallHybrid, teachGuard, mirrorPatternsToVector, vectorMirrorEnabled, vectorTierStatus, resolveVectorEngine, reindexVectorStore, harmonizeVectorStore, importRvfCheckpoint, statuslineData, writeFeatureAdrState, computeUsage, deriveUsageCalibration, normalizeClaudeUsageModelKey, readUsageLimits, claimCheck, summarize, queryBookKnowledge, loadStorePatternsSync, patternRecordId, loadStoreRecords, recordToPattern, bundleSkills, brainHome, listBrain, promoteProjectToBrain, updateBrainSource, queryBrain, groundPrompt, expandKu, reindexBrainVectors, buildPrimer, exportBrainSlice, importBrainSlice, registerKusToBrain, RECALL_USAGE_LOG_RELATIVE, RECALL_USAGE_LOG_MAX_BYTES, parseRecallUsageLog, buildRecallUsageReport, buildManifest, buildSbom, resolveTrustRoot, decideVerifyPolicy, decideProvenance, isInsideTree, signManifest, verifyManifest, assertKeyOutsideTree, decidePublishGate, MANIFEST_NAME, SBOM_NAME, buildArchitectureMap, renderMapHuman, findArchitectureDrift, renderDriftReport, scanWorkspacePackages, loadSubsystemManifest, loadProductVision, checkFeatureAgainstArchitecture, renderArchCheck, planProjectSkills, guidanceForStage, renderInjectionReport, analyzeCorpus, renderRakeReport, renderCriticSection, rakeAsLesson, rakeReward, DEFAULT_RAKE_THRESHOLDS, streamSessionEvents, findLatestTranscript, detectProcessRakes, buildRetro, renderRetro, retroLessonText, PROCESS_SIGNATURES, RETRO_DOMAIN, } from '@dzhechkov/harness-core';
+import { createSkill, getSkillInfo, getWorkflow, isTargetName, listSkills, runDoctor, runInit, benchmarkSkill, benchmarkSkills, scanMcp, reconcileCapabilities, RECONCILE_BANNER, buildRegistry, discoverSkillPackDirs, checkUpstream, compareSkills, checkAllUpstream, sweepSkillDrift, syncCanonicalSkill, checkUpgrades, discoverPackages, discoverSourcePackages, fetchAllDownloads, filterByCategory, pretrain, recommend, generatePlugin, publishPackages, runSetup, runMigrate, searchRegistry, runSync, runVerify, runInitAgentsMd, runInitGeminiMd, TARGET_NAMES, WORKFLOW_NAMES, importEcc, recordPattern, resolveLearningBackend, storeStats, consolidateSessions, pruneNoisePatterns, lessonDeltaReport, removePatternsByIds, snapshotStore, recallHybrid, teachGuard, mirrorPatternsToVector, vectorMirrorEnabled, vectorTierStatus, resolveVectorEngine, reindexVectorStore, harmonizeVectorStore, importRvfCheckpoint, statuslineData, writeFeatureAdrState, computeUsage, deriveUsageCalibration, normalizeClaudeUsageModelKey, readUsageLimits, claimCheck, summarize, queryBookKnowledge, loadStorePatternsSync, patternRecordId, loadStoreRecords, recordToPattern, bundleSkills, brainHome, listBrain, promoteProjectToBrain, updateBrainSource, queryBrain, groundPrompt, expandKu, reindexBrainVectors, buildPrimer, exportBrainSlice, importBrainSlice, registerKusToBrain, RECALL_USAGE_LOG_RELATIVE, RECALL_USAGE_LOG_MAX_BYTES, parseRecallUsageLog, buildRecallUsageReport, buildManifest, buildSbom, resolveTrustRoot, decideVerifyPolicy, decideProvenance, isInsideTree, signManifest, verifyManifest, assertKeyOutsideTree, decidePublishGate, MANIFEST_NAME, SBOM_NAME, buildArchitectureMap, renderMapHuman, findArchitectureDrift, renderDriftReport, scanWorkspacePackages, loadSubsystemManifest, loadProductVision, checkFeatureAgainstArchitecture, renderArchCheck, planProjectSkills, guidanceForStage, renderInjectionReport, analyzeCorpus, renderRakeReport, renderCriticSection, rakeAsLesson, rakeReward, DEFAULT_RAKE_THRESHOLDS, streamSessionEvents, findLatestTranscript, detectProcessRakes, buildRetro, renderRetro, retroLessonText, PROCESS_SIGNATURES, RETRO_DOMAIN, scanForSetup, buildSetupPlan, scaffoldFromSpec, renderScaffoldPreview, readExistingForScaffold, assembleChallengeContext, buildChallengeBrief, pickAdversaryModel, CHALLENGE_QUESTIONS, } from '@dzhechkov/harness-core';
 import { getPreset, PRESET_NAMES } from '@dzhechkov/harness-presets';
 import { scanGitHub, analyzeRepo, generateReport, deepAnalyze, scanAllSources, ScoutMemory } from '@dzhechkov/scout';
 const USAGE = `dz - DZ cross-platform harness CLI
@@ -4121,6 +4121,134 @@ async function cmdRetro(options, flags, cwd, write) {
     }
     return 0;
 }
+/**
+ * `dz feature-adr-setup` — the deterministic engine behind the `configure-feature-adr` SKILL (R5). Scaffolds
+ * the project-awareness files (vision / map / testing / project-skills) so a user configures feature-adr
+ * without knowing any schema.
+ *   --plan [--json]            read-only: what exists / discoverable / missing (the "which docs, where?" answer)
+ *   --from-spec <spec.json>    preview the scaffold (create / augment per file); the SKILL fills the spec
+ *   --apply                    with --from-spec: WRITE (create missing, AUGMENT existing — never clobber)
+ */
+function cmdFeatureAdrSetup(options, flags, cwd, write) {
+    let repoRoot = cwd;
+    try {
+        repoRoot = execSync('git rev-parse --show-toplevel', { cwd, encoding: 'utf-8' }).trim() || cwd;
+    }
+    catch { /* not git */ }
+    const specPath = options.get('from-spec');
+    if (specPath === undefined) {
+        // default + --plan: the read-only "which documents, and where?" answer.
+        const plan = buildSetupPlan(scanForSetup(repoRoot));
+        if (flags.has('json')) {
+            write(JSON.stringify(plan, null, 2));
+            return 0;
+        }
+        write('feature-adr project setup — current state:');
+        write(`  vision.md: ${plan.exists.vision ? '✓' : '✗ missing'}   manifest: ${plan.exists.manifest ? '✓' : '✗ missing'}   testing.md: ${plan.exists.testing ? '✓' : '✗ missing'}   project-skills.json: ${plan.exists.projectSkills ? '✓' : '✗ missing'}`);
+        if (plan.discoveredPackages.length > 0)
+            write(`  discovered ${plan.discoveredPackages.length} workspace package(s) → a map can be auto-scaffolded`);
+        if (plan.suggestions.length > 0) {
+            write('  next steps:');
+            for (const s of plan.suggestions)
+                write(`    • ${s}`);
+        }
+        if (plan.missing.length === 0)
+            write('  all set — feature-adr is project-aware here.');
+        else
+            write('  → the `configure-feature-adr` skill walks you through the missing docs; or pass a filled spec with --from-spec.');
+        return 0;
+    }
+    // --from-spec: scaffold (preview, or --apply to write).
+    let spec;
+    try {
+        spec = JSON.parse(readFileSync(resolve(cwd, specPath), 'utf-8'));
+    }
+    catch (e) {
+        write(`dz feature-adr-setup: cannot read spec ${specPath}: ${e instanceof Error ? e.message : String(e)}`);
+        return 1;
+    }
+    const result = scaffoldFromSpec(spec, readExistingForScaffold(repoRoot));
+    if (flags.has('json') && !flags.has('apply')) {
+        write(JSON.stringify(result, null, 2));
+        return 0;
+    }
+    write(renderScaffoldPreview(result));
+    if (!flags.has('apply')) {
+        write('\n(preview only — pass --apply to write)');
+        return 0;
+    }
+    let wrote = 0;
+    for (const f of result.files) {
+        if (f.action === 'unchanged')
+            continue; // never clobber
+        const abs = resolve(repoRoot, f.path);
+        // Write-boundary augment-never-clobber guard (defense in depth): a 'create' must NEVER overwrite an
+        // existing file, even if the plan (built from a caller-supplied `existing`) said create. 'augment' has
+        // already union-merged the prior content, so overwriting there is the merged result, not a clobber.
+        if (f.action === 'create' && existsSync(abs)) {
+            write(`  · skipped ${f.path} — already exists (not overwritten)`);
+            continue;
+        }
+        try {
+            mkdirSync(dirname(abs), { recursive: true });
+            writeFileSync(abs, f.content);
+            write(`  ✓ ${f.action === 'create' ? 'created' : 'augmented'} ${f.path}`);
+            wrote++;
+        }
+        catch (e) {
+            write(`  ✗ ${f.path}: ${e instanceof Error ? e.message : String(e)}`);
+        }
+    }
+    write(`\n↳ wrote ${wrote} file(s). Verify: dz project-skills   +   dz architecture --revise`);
+    return 0;
+}
+/**
+ * `dz challenge` — the deterministic "cartridge" behind the `challenge-panel` adversarial plan-gate (R6).
+ * Assembles a WIDE context pack (plan + vision + testing + map + degradations) and prints the fixed C1-C8
+ * "break it, don't confirm it" brief + the verdict schema. It runs NO LLM and writes nothing — the
+ * `challenge-panel` SKILL fires the brief at a FRESH adversary (a model ≠ the plan author) + a mandatory
+ * cross-validator. ADVISE, never block.
+ *   --plan <plan.md>      the plan under review (required)
+ *   --json                emit the assembled context + brief as JSON
+ *   --context-only        just the assembled context summary (what the panel will read)
+ *   --author <model>      the plan-author model → prints the cross-family adversary to dispatch (FR-4)
+ */
+function cmdChallenge(options, flags, cwd, write) {
+    let repoRoot = cwd;
+    try {
+        repoRoot = execSync('git rev-parse --show-toplevel', { cwd, encoding: 'utf-8' }).trim() || cwd;
+    }
+    catch { /* not git */ }
+    const planPath = options.get('plan');
+    if (planPath === undefined) {
+        write('dz challenge: pass --plan <plan.md> (the implementation plan to challenge).');
+        return 1;
+    }
+    const ctx = assembleChallengeContext(repoRoot, planPath);
+    if (ctx.plan === '') {
+        write(`dz challenge: plan not found or empty: ${planPath}`);
+        return 1;
+    }
+    const adversary = pickAdversaryModel(options.get('author') ?? 'claude');
+    if (flags.has('json')) {
+        write(JSON.stringify({ context: ctx, brief: buildChallengeBrief(ctx), adversary, questions: CHALLENGE_QUESTIONS }, null, 2));
+        return 0;
+    }
+    if (flags.has('context-only')) {
+        const has = (v) => (v === undefined ? '✗ (less calibration)' : `✓ ${v.length} chars`);
+        write(`challenge context for ${planPath}:`);
+        write(`  plan:        ✓ ${ctx.plan.length} chars`);
+        write(`  vision:      ${has(ctx.vision)}`);
+        write(`  testing:     ${has(ctx.testing)}`);
+        write(`  map:         ${has(ctx.map)}`);
+        write(`  degradations:${has(ctx.degradations)}`);
+        write(`  → adversary: ${adversary.model} — ${adversary.note}`);
+        return 0;
+    }
+    write(buildChallengeBrief(ctx));
+    write(`\n── dispatch (panel ≠ plan author) ──\n${adversary.model}: ${adversary.note}`);
+    return 0;
+}
 function cmdStats(cwd, write) {
     const baseDir = join(cwd, 'packages', '@dzhechkov');
     if (!existsSync(baseDir)) {
@@ -4376,6 +4504,10 @@ export async function runCli(argv, io = {}) {
                 return await cmdMrRakes(options, flags, cwd, write);
             case 'retro':
                 return await cmdRetro(options, flags, cwd, write);
+            case 'feature-adr-setup':
+                return cmdFeatureAdrSetup(options, flags, cwd, write);
+            case 'challenge':
+                return cmdChallenge(options, flags, cwd, write);
             case 'dashboard':
                 return cmdDashboard(cwd, write);
             case 'roam':