peaks-loop 4.0.0-beta.7 → 4.0.0-beta.8

package/dist/src/services/rd/reviewer-dispatch-policy.d.ts

@@ -1,122 +0,0 @@
-/**
- * Slice 2026-06-24-efficiency-4p-bundle / G4 (P1.3) — karpathy-skip policy
- * Slice v2.12.0 Group B (Tier 4) — collapse 5-way → 3-way fanout.
- *
- * Background — peaks-rd's "Parallel review fan-out" (SKILL.md §130) is
- * a fanout triggered at the end of implementation. The shape changed
- * across releases:
- *
- *   v2.11.x (legacy, 5-way):
- *     1. code-reviewer
- *     2. security-reviewer
- *     3. perf-baseline-reviewer
- *     4. qa-test-cases-writer
- *     5. karpathy-reviewer (the hard Karpathy-Gate)
- *
- *   v2.12.0 (canonical, 3-way):
- *     1. code-reviewer
- *     2. qa-test-cases-writer
- *     3. karpathy-reviewer (the hard Karpathy-Gate)
- *
- * The `security-reviewer` and `perf-baseline-reviewer` slots were
- * moved out of the RD fanout into two new independent skills:
- *   - `peaks-security-audit` (skill id: peaks-security-audit)
- *   - `peaks-perf-audit`     (skill id: peaks-perf-audit)
- * Both are dispatched as pre-RD audit runs that consume the public
- * PRD handoff + the project-scoped audit templates (slice v2.12.0
- * Tier 1+2+3 = Group A).
- *
- * The dispatch policy here is the **canonical decision table** consumed
- * by the LLM-side runner and pinned by tests:
- *   - `tests/unit/rd/karpathy-skip-on-config-docs-chore.test.ts`
- *     (5 → 3 element pinning)
- *   - `tests/unit/rd/deprecated-reviewer-back-compat.test.ts`
- *     (NEW in v2.12.0 — 8 cases; back-compat for the 2 removed slots)
- *
- * For `config | docs | chore` request types, the slice already skips
- * the entire fanout (SKILL.md line 132 says "Config / docs / chore: no
- * fan-out"). This helper makes the policy **explicit and testable**:
- *
- *   - `shouldDispatchKarpathy(type)` returns `false` for
- *     `config | docs | chore`, `true` for the other types.
- *   - `reviewerListFor(type)` returns the 3-sub-agent list when the
- *     type triggers the fanout, otherwise returns the empty list.
- *
- * The 2 removed reviewers (`security-reviewer`, `perf-baseline-reviewer`)
- * are exposed as `RD_DEPRECATED_REVIEWERS` for the 1-minor-release
- * back-compat window. The `isDeprecatedReviewer(name)` predicate lets
- * dispatchers (or legacy on-disk rd/{security-review,perf-baseline}.md
- * readers) detect a removed slot and route to the new audit skill
- * instead of failing the gate. See Tier 5 (`artifact-prerequisites.ts`)
- * for the matching prereq-side back-compat (`mustContainAny` form).
- */
-export declare const RD_REVIEW_REQUEST_TYPES: readonly ["feat", "bugfix", "refactor", "config", "docs", "chore"];
-export type RdReviewRequestType = (typeof RD_REVIEW_REQUEST_TYPES)[number];
-/**
- * The 3-sub-agent fanout triggered at the end of RD implementation
- * (v2.12.0). In v2.11.x this was a 5-element list; the
- * `security-reviewer` and `perf-baseline-reviewer` slots moved to
- * the standalone `peaks-security-audit` / `peaks-perf-audit` skills.
- */
-export declare const RD_FANOUT_REVIEWERS: readonly ["code-reviewer", "qa-test-cases-writer", "karpathy-reviewer"];
-export type RdFanoutReviewer = (typeof RD_FANOUT_REVIEWERS)[number];
-/**
- * Reviewer roles removed from the v2.11.x 5-way fanout. Exposed as a
- * separate constant so:
- *   (a) back-compat code paths can detect a legacy dispatch record
- *       (e.g. `.peaks/_sub_agents/<sid>/dispatch/security-reviewer.json`)
- *       and route to the new audit skill instead of failing,
- *   (b) the 1-minor-release window (v2.12.0) preserves read access to
- *       `rd/{security-review,perf-baseline}.md` on disk; v2.13.0
- *       hard-deletes them.
- *
- * Use `isDeprecatedReviewer(name)` (not direct array membership) so
- * future deprecations can use the same predicate without churn.
- */
-export declare const RD_DEPRECATED_REVIEWERS: readonly ["security-reviewer", "perf-baseline-reviewer"];
-export type RdDeprecatedReviewer = (typeof RD_DEPRECATED_REVIEWERS)[number];
-/** Subset of request types that fire the 3-way fanout. */
-export declare const RD_FANOUT_REQUEST_TYPES: readonly ["feat", "bugfix", "refactor"];
-export type RdFanoutRequestType = (typeof RD_FANOUT_REQUEST_TYPES)[number];
-/**
- * True iff the karpathy-reviewer sub-agent should be dispatched for
- * this request type. For `config | docs | chore` the entire 3-way
- * fanout is skipped; karpathy is a no-op there.
- */
-export declare function shouldDispatchKarpathy(type: RdReviewRequestType): boolean;
-/**
- * True iff the request type triggers the 3-way review fanout.
- */
-export declare function isFanoutTriggerType(type: RdReviewRequestType): type is RdFanoutRequestType;
-/**
- * Returns the ordered list of reviewer roles to dispatch for this
- * request type. Empty list when the type does not trigger the
- * fanout (config/docs/chore) — the karpathy-reviewer (and the rest
- * of the 3-way fanout) is skipped.
- *
- * For `feat`, `bugfix`, and `refactor`: the 3 reviewers
- *   (code-reviewer, qa-test-cases-writer, karpathy-reviewer).
- *
- * The `security-reviewer` and `perf-baseline-reviewer` slots that
- * used to live here (v2.11.x 5-way) are now independent audit
- * skills — see `peaks-security-audit` / `peaks-perf-audit`. Their
- * outputs land at `audit/security.md` / `audit/perf.md` (see
- * `artifact-prerequisites.ts` `AUDIT_SECURITY` / `AUDIT_PERF`).
- */
-export declare function reviewerListFor(type: RdReviewRequestType): readonly RdFanoutReviewer[];
-/**
- * Returns the karpathy-reviewer's slot index in the 3-way fanout
- * (or -1 if it should be skipped for this type). Used by the
- * dispatch record writer so the count of emitted dispatch records
- * matches the policy: 3 for feat/bugfix/refactor, 0 for
- * config/docs/chore.
- */
-export declare function karpathySlotIndex(type: RdReviewRequestType): number;
-/**
- * True iff `name` is one of the reviewer roles removed in v2.12.0.
- * Used by back-compat readers to detect legacy dispatch records or
- * on-disk artifacts and route to the new audit skill instead of
- * failing the gate. See `RD_DEPRECATED_REVIEWERS` for the canonical
- * list.
- */
-export declare function isDeprecatedReviewer(name: string): name is RdDeprecatedReviewer;

package/dist/src/services/rd/reviewer-dispatch-policy.js

@@ -1,148 +0,0 @@
-/**
- * Slice 2026-06-24-efficiency-4p-bundle / G4 (P1.3) — karpathy-skip policy
- * Slice v2.12.0 Group B (Tier 4) — collapse 5-way → 3-way fanout.
- *
- * Background — peaks-rd's "Parallel review fan-out" (SKILL.md §130) is
- * a fanout triggered at the end of implementation. The shape changed
- * across releases:
- *
- *   v2.11.x (legacy, 5-way):
- *     1. code-reviewer
- *     2. security-reviewer
- *     3. perf-baseline-reviewer
- *     4. qa-test-cases-writer
- *     5. karpathy-reviewer (the hard Karpathy-Gate)
- *
- *   v2.12.0 (canonical, 3-way):
- *     1. code-reviewer
- *     2. qa-test-cases-writer
- *     3. karpathy-reviewer (the hard Karpathy-Gate)
- *
- * The `security-reviewer` and `perf-baseline-reviewer` slots were
- * moved out of the RD fanout into two new independent skills:
- *   - `peaks-security-audit` (skill id: peaks-security-audit)
- *   - `peaks-perf-audit`     (skill id: peaks-perf-audit)
- * Both are dispatched as pre-RD audit runs that consume the public
- * PRD handoff + the project-scoped audit templates (slice v2.12.0
- * Tier 1+2+3 = Group A).
- *
- * The dispatch policy here is the **canonical decision table** consumed
- * by the LLM-side runner and pinned by tests:
- *   - `tests/unit/rd/karpathy-skip-on-config-docs-chore.test.ts`
- *     (5 → 3 element pinning)
- *   - `tests/unit/rd/deprecated-reviewer-back-compat.test.ts`
- *     (NEW in v2.12.0 — 8 cases; back-compat for the 2 removed slots)
- *
- * For `config | docs | chore` request types, the slice already skips
- * the entire fanout (SKILL.md line 132 says "Config / docs / chore: no
- * fan-out"). This helper makes the policy **explicit and testable**:
- *
- *   - `shouldDispatchKarpathy(type)` returns `false` for
- *     `config | docs | chore`, `true` for the other types.
- *   - `reviewerListFor(type)` returns the 3-sub-agent list when the
- *     type triggers the fanout, otherwise returns the empty list.
- *
- * The 2 removed reviewers (`security-reviewer`, `perf-baseline-reviewer`)
- * are exposed as `RD_DEPRECATED_REVIEWERS` for the 1-minor-release
- * back-compat window. The `isDeprecatedReviewer(name)` predicate lets
- * dispatchers (or legacy on-disk rd/{security-review,perf-baseline}.md
- * readers) detect a removed slot and route to the new audit skill
- * instead of failing the gate. See Tier 5 (`artifact-prerequisites.ts`)
- * for the matching prereq-side back-compat (`mustContainAny` form).
- */
-export const RD_REVIEW_REQUEST_TYPES = [
-    'feat',
-    'bugfix',
-    'refactor',
-    'config',
-    'docs',
-    'chore',
-];
-/**
- * The 3-sub-agent fanout triggered at the end of RD implementation
- * (v2.12.0). In v2.11.x this was a 5-element list; the
- * `security-reviewer` and `perf-baseline-reviewer` slots moved to
- * the standalone `peaks-security-audit` / `peaks-perf-audit` skills.
- */
-export const RD_FANOUT_REVIEWERS = [
-    'code-reviewer',
-    'qa-test-cases-writer',
-    'karpathy-reviewer',
-];
-/**
- * Reviewer roles removed from the v2.11.x 5-way fanout. Exposed as a
- * separate constant so:
- *   (a) back-compat code paths can detect a legacy dispatch record
- *       (e.g. `.peaks/_sub_agents/<sid>/dispatch/security-reviewer.json`)
- *       and route to the new audit skill instead of failing,
- *   (b) the 1-minor-release window (v2.12.0) preserves read access to
- *       `rd/{security-review,perf-baseline}.md` on disk; v2.13.0
- *       hard-deletes them.
- *
- * Use `isDeprecatedReviewer(name)` (not direct array membership) so
- * future deprecations can use the same predicate without churn.
- */
-export const RD_DEPRECATED_REVIEWERS = [
-    'security-reviewer',
-    'perf-baseline-reviewer',
-];
-/** Subset of request types that fire the 3-way fanout. */
-export const RD_FANOUT_REQUEST_TYPES = ['feat', 'bugfix', 'refactor'];
-/**
- * True iff the karpathy-reviewer sub-agent should be dispatched for
- * this request type. For `config | docs | chore` the entire 3-way
- * fanout is skipped; karpathy is a no-op there.
- */
-export function shouldDispatchKarpathy(type) {
-    return isFanoutTriggerType(type);
-}
-/**
- * True iff the request type triggers the 3-way review fanout.
- */
-export function isFanoutTriggerType(type) {
-    return (type === 'feat' || type === 'bugfix' || type === 'refactor');
-}
-/**
- * Returns the ordered list of reviewer roles to dispatch for this
- * request type. Empty list when the type does not trigger the
- * fanout (config/docs/chore) — the karpathy-reviewer (and the rest
- * of the 3-way fanout) is skipped.
- *
- * For `feat`, `bugfix`, and `refactor`: the 3 reviewers
- *   (code-reviewer, qa-test-cases-writer, karpathy-reviewer).
- *
- * The `security-reviewer` and `perf-baseline-reviewer` slots that
- * used to live here (v2.11.x 5-way) are now independent audit
- * skills — see `peaks-security-audit` / `peaks-perf-audit`. Their
- * outputs land at `audit/security.md` / `audit/perf.md` (see
- * `artifact-prerequisites.ts` `AUDIT_SECURITY` / `AUDIT_PERF`).
- */
-export function reviewerListFor(type) {
-    if (!isFanoutTriggerType(type)) {
-        return [];
-    }
-    return RD_FANOUT_REVIEWERS;
-}
-/**
- * Returns the karpathy-reviewer's slot index in the 3-way fanout
- * (or -1 if it should be skipped for this type). Used by the
- * dispatch record writer so the count of emitted dispatch records
- * matches the policy: 3 for feat/bugfix/refactor, 0 for
- * config/docs/chore.
- */
-export function karpathySlotIndex(type) {
-    if (!shouldDispatchKarpathy(type)) {
-        return -1;
-    }
-    return RD_FANOUT_REVIEWERS.indexOf('karpathy-reviewer');
-}
-/**
- * True iff `name` is one of the reviewer roles removed in v2.12.0.
- * Used by back-compat readers to detect legacy dispatch records or
- * on-disk artifacts and route to the new audit skill instead of
- * failing the gate. See `RD_DEPRECATED_REVIEWERS` for the canonical
- * list.
- */
-export function isDeprecatedReviewer(name) {
-    return RD_DEPRECATED_REVIEWERS.includes(name);
-}

package/dist/src/services/rd/standards-diagnostic.d.ts

@@ -1,76 +0,0 @@
-/** Stable exit code surfaced to the CLI when `--strict-standards` is set. */
-export declare const EPEAKS_NO_STANDARDS: "EPEAKS_NO_STANDARDS";
-/** Subdirectories of `<projectRoot>/.claude/rules/` that must be populated. */
-export type RdStandardsSubdir = 'common' | 'typescript';
-export declare const RD_STANDARDS_REQUIRED_SUBDIRS: ReadonlyArray<RdStandardsSubdir>;
-/** The three gates the RD bootstrap inspects. */
-export type RdStandardGateName = 'code-review' | 'security-review' | 'performance-review';
-export type RdStandardGateStatus = 'ready' | 'skipped';
-export type RdStandardGate = {
-    readonly name: RdStandardGateName;
-    readonly status: RdStandardGateStatus;
-    readonly reason: string | null;
-};
-export type DetectMissingProjectStandardsInput = {
-    readonly projectRoot: string;
-};
-export type DetectMissingProjectStandardsResult = {
-    readonly missing: boolean;
-    readonly path: string;
-    readonly missingSubdirs: ReadonlyArray<RdStandardsSubdir>;
-    readonly remediation: string;
-};
-export type RenderRdStandardsDiagnosticInput = {
-    readonly projectRoot: string;
-    readonly detection: DetectMissingProjectStandardsResult;
-};
-export type ResolveRdStartupStandardsCheckInput = {
-    readonly projectRoot: string;
-    readonly strict: boolean;
-};
-export type ResolveRdStartupStandardsCheckResult = {
-    readonly exitCode: 0 | 1;
-    readonly errorCode: typeof EPEAKS_NO_STANDARDS | null;
-    readonly diagnostic: string | null;
-    readonly gates: ReadonlyArray<RdStandardGate>;
-};
-/**
- * Pure detection: scan `<projectRoot>/.claude/rules/{common,typescript}/`
- * for at least one `.md` rule file per subdir. Empty subdirs and missing
- * subdirs both count as "missing".
- *
- * Defensive: never throws. Missing projectRoot, permission errors, or a
- * non-directory at the path all collapse to `{ missing: true }`. The caller
- * (CLI bootstrap) is expected to surface the remediation; this function
- * just reports the truth.
- */
-export declare function detectMissingProjectStandards(input: DetectMissingProjectStandardsInput): DetectMissingProjectStandardsResult;
-/**
- * Render the human-readable diagnostic line that goes to stderr.
- * The line is single-line + copy-pasteable so the model can echo it
- * into a Bash command verbatim.
- */
-export declare function renderRdStandardsDiagnostic(input: RenderRdStandardsDiagnosticInput): string;
-/**
- * Build the gate list for the JSON envelope returned by `peaks rd --json`.
- * Mirrors the PRD's AC2 contract: when missing, each gate is
- * `{ name, status: 'skipped', reason: 'no project-local standards' }`.
- */
-export declare function buildRdStandardsGateList(input: {
-    readonly missing: boolean;
-}): ReadonlyArray<RdStandardGate>;
-/**
- * Single entry point for the RD / QA / Code bootstrap. Returns the
- * exit code + error code + diagnostic + gate list. The CLI wrapper is
- * responsible for `process.stderr.write(diagnostic ?? '')` and
- * `process.exit(result.exitCode)`.
- *
- * - `strict=true`  + missing  → exitCode 1, errorCode EPEAKS_NO_STANDARDS,
- *                                diagnostic + skipped gates emitted.
- * - `strict=false` + missing  → exitCode 0, errorCode null,
- *                                diagnostic + skipped gates emitted
- *                                (warn-and-continue; PRD NG1).
- * - strict any     + present  → exitCode 0, errorCode null,
- *                                diagnostic null, gates ready.
- */
-export declare function resolveRdStartupStandardsCheck(input: ResolveRdStartupStandardsCheckInput): ResolveRdStartupStandardsCheckResult;

package/dist/src/services/rd/standards-diagnostic.js

@@ -1,166 +0,0 @@
-/**
- * Slice 2026-06-16-peaks-rd-no-gates — missing-project-standards diagnostic
- * + JSON gate list shape for the RD bootstrap path.
- *
- * Background: when `peaks-rd` (or `peaks-qa` / `peaks-code`) starts in a
- * project whose `.claude/rules/{common,typescript}/` is missing or empty,
- * the existing code-review / security / performance gates were silently
- * dropped. This module makes the missing-standards condition observable:
- *
- *   G1  `detectMissingProjectStandards` + `renderRdStandardsDiagnostic`
- *       produce a clear stderr/JSON diagnostic with a copy-pasteable
- *       `peaks standards init --project <X> --apply` remediation hint.
- *   G2  `resolveRdStartupStandardsCheck({ strict: true })` returns an
- *       exitCode of 1 with errorCode `EPEAKS_NO_STANDARDS` when standards
- *       are missing. Default (`strict: false`) keeps the warn-and-continue
- *       behavior so existing users with empty rules don't break.
- *   G3  `buildRdStandardsGateList` returns the three gates each marked
- *       `{ status: 'skipped', reason: 'no project-local standards' }` when
- *       standards are missing. When present, gates are `{ status: 'ready' }`.
- *   G4  The remediation string is the exact copy-pasteable CLI invocation.
- *
- * This module is a pure-function helper. The `peaks rd` / `peaks qa` /
- * `peaks code` runtime hooks call `resolveRdStartupStandardsCheck` at
- * bootstrap and decide whether to write `process.stderr` + JSON envelope
- * + exit. The bootstrap is intentionally side-effect-free here so unit
- * tests can run it without spawning child processes.
- *
- * Cross-platform: `path` field is rendered verbatim from the caller's
- * projectRoot string (we never normalize or rewrite the user's path —
- * Windows users see their `C:\Users\foo` form; macOS / Linux users see
- * their `/Users/foo` form). The remediation command always uses POSIX
- * forward slashes since the CLI is invoked through a shell that
- * double-normalizes on Windows (`peaks standards init --project C:/Users/...`).
- *
- * Out of scope (downstream slices):
- *   - audit-log emission for gate-skip events (see memory
- *     `peaks-ide-skill-ac-10-audit-log-writer-is-a-thin-helper-not-a-separate-cli-primitive`
- *     — the helper is intentionally not surfaced here).
- *   - one-time suppression marker (`peaks standards suppress --project <X>`
- *     or `.peaks/.no-standards`); tracked in PRD#004 R3 as a future slice.
- */
-import { existsSync, readdirSync } from 'node:fs';
-import { join } from 'node:path';
-/** Stable exit code surfaced to the CLI when `--strict-standards` is set. */
-export const EPEAKS_NO_STANDARDS = 'EPEAKS_NO_STANDARDS';
-export const RD_STANDARDS_REQUIRED_SUBDIRS = ['common', 'typescript'];
-/**
- * Pure detection: scan `<projectRoot>/.claude/rules/{common,typescript}/`
- * for at least one `.md` rule file per subdir. Empty subdirs and missing
- * subdirs both count as "missing".
- *
- * Defensive: never throws. Missing projectRoot, permission errors, or a
- * non-directory at the path all collapse to `{ missing: true }`. The caller
- * (CLI bootstrap) is expected to surface the remediation; this function
- * just reports the truth.
- */
-export function detectMissingProjectStandards(input) {
-    const projectRoot = input.projectRoot;
-    const rulesPath = join(projectRoot, '.claude', 'rules');
-    const missingSubdirs = [];
-    if (!existsSync(rulesPath)) {
-        return {
-            missing: true,
-            path: rulesPath,
-            missingSubdirs: [...RD_STANDARDS_REQUIRED_SUBDIRS],
-            remediation: buildRemediationCommand(projectRoot)
-        };
-    }
-    for (const subdir of RD_STANDARDS_REQUIRED_SUBDIRS) {
-        if (!hasMdRules(join(rulesPath, subdir))) {
-            missingSubdirs.push(subdir);
-        }
-    }
-    return {
-        missing: missingSubdirs.length > 0,
-        path: rulesPath,
-        missingSubdirs,
-        remediation: buildRemediationCommand(projectRoot)
-    };
-}
-/**
- * Render the human-readable diagnostic line that goes to stderr.
- * The line is single-line + copy-pasteable so the model can echo it
- * into a Bash command verbatim.
- */
-export function renderRdStandardsDiagnostic(input) {
-    const { projectRoot: _projectRoot, detection } = input;
-    const missingList = detection.missingSubdirs.length > 0 ? ` (missing: ${detection.missingSubdirs.join(', ')})` : '';
-    return [
-        `⚠ no project-local standards found at ${detection.path}${missingList}`,
-        `— run ${detection.remediation} to scaffold.`,
-        `Gates (code-review, security-review, performance-review) will be skipped.`
-    ].join(' ');
-}
-/**
- * Build the gate list for the JSON envelope returned by `peaks rd --json`.
- * Mirrors the PRD's AC2 contract: when missing, each gate is
- * `{ name, status: 'skipped', reason: 'no project-local standards' }`.
- */
-export function buildRdStandardsGateList(input) {
-    if (input.missing) {
-        return [
-            { name: 'code-review', status: 'skipped', reason: 'no project-local standards' },
-            { name: 'security-review', status: 'skipped', reason: 'no project-local standards' },
-            { name: 'performance-review', status: 'skipped', reason: 'no project-local standards' }
-        ];
-    }
-    return [
-        { name: 'code-review', status: 'ready', reason: null },
-        { name: 'security-review', status: 'ready', reason: null },
-        { name: 'performance-review', status: 'ready', reason: null }
-    ];
-}
-/**
- * Single entry point for the RD / QA / Code bootstrap. Returns the
- * exit code + error code + diagnostic + gate list. The CLI wrapper is
- * responsible for `process.stderr.write(diagnostic ?? '')` and
- * `process.exit(result.exitCode)`.
- *
- * - `strict=true`  + missing  → exitCode 1, errorCode EPEAKS_NO_STANDARDS,
- *                                diagnostic + skipped gates emitted.
- * - `strict=false` + missing  → exitCode 0, errorCode null,
- *                                diagnostic + skipped gates emitted
- *                                (warn-and-continue; PRD NG1).
- * - strict any     + present  → exitCode 0, errorCode null,
- *                                diagnostic null, gates ready.
- */
-export function resolveRdStartupStandardsCheck(input) {
-    const detection = detectMissingProjectStandards({ projectRoot: input.projectRoot });
-    if (!detection.missing) {
-        return {
-            exitCode: 0,
-            errorCode: null,
-            diagnostic: null,
-            gates: buildRdStandardsGateList({ missing: false })
-        };
-    }
-    const diagnostic = renderRdStandardsDiagnostic({ projectRoot: input.projectRoot, detection });
-    const exitCode = input.strict ? 1 : 0;
-    return {
-        exitCode,
-        errorCode: input.strict ? EPEAKS_NO_STANDARDS : null,
-        diagnostic,
-        gates: buildRdStandardsGateList({ missing: true })
-    };
-}
-// --- internal helpers -------------------------------------------------------
-function buildRemediationCommand(projectRoot) {
-    // The remediation command is always rendered with POSIX forward slashes
-    // because the CLI shell normalizes path separators on Windows anyway,
-    // and users on macOS / Linux will copy this verbatim.
-    const posix = projectRoot.split('\\').join('/');
-    return `peaks standards init --project ${posix} --apply`;
-}
-function hasMdRules(dirPath) {
-    try {
-        if (!existsSync(dirPath)) {
-            return false;
-        }
-        const entries = readdirSync(dirPath);
-        return entries.some((entry) => entry.toLowerCase().endsWith('.md'));
-    }
-    catch {
-        return false;
-    }
-}

package/dist/src/services/rd/strategic-stage.d.ts

@@ -1,4 +0,0 @@
-import { type WriteStrategyInput } from './strategy.js';
-import type { StrategyOutput } from './types.js';
-export type RunStrategicInput = WriteStrategyInput;
-export declare function runStrategicStage(input: RunStrategicInput): Promise<StrategyOutput>;

package/dist/src/services/rd/strategic-stage.js

@@ -1,15 +0,0 @@
-/**
- * Per spec §4.2 战略审计 — orchestrator.
- * Pure pass-through to writeStrategy; this exists so the public rd-service
- * entry point is a single function (consistent with tactical-stage).
- */
-import { dirname } from 'node:path';
-import { writeStrategy } from './strategy.js';
-// H8 chain enforcement (R1-W2): register STRAT.sig by project dir so
-// the tactical stage can verify its inputSig chains to a real STRAT upstream.
-import { registerStratSig } from './tactical-stage.js';
-export async function runStrategicStage(input) {
-    const result = await writeStrategy(input);
-    registerStratSig(dirname(input.out), result.sha256);
-    return result;
-}

package/dist/src/services/rd/strategy.d.ts

@@ -1,13 +0,0 @@
-import { type StrategyOutput } from './types.js';
-export interface WriteStrategyInput {
-    readonly out: string;
-    readonly goal: string;
-    readonly rootCauseAnalysis: string;
-    readonly impactSurface: string[];
-    readonly designRationale: string;
-    readonly askUserQuestion?: {
-        readonly question: string;
-        readonly options: string[];
-    };
-}
-export declare function writeStrategy(input: WriteStrategyInput): Promise<StrategyOutput>;

package/dist/src/services/rd/strategy.js

@@ -1,60 +0,0 @@
-/**
- * Per spec §4.2 战略审计 — strategy.md writer + STRAT.sig computation.
- *
- * Hard constraints:
- *   H8 (audit trail hashable): sig field embedded in strategy.md is the
- *       sha256 of all OTHER content (chicken-and-egg avoided).
- */
-import { createHash } from 'node:crypto';
-import { writeFile, rename, unlink } from 'node:fs/promises';
-import { StrategyOutputSchema } from './types.js';
-function sha256Of(content) {
-    const { sha256: _omit, ...rest } = content;
-    void _omit;
-    const canonical = JSON.stringify(rest, Object.keys(rest).sort());
-    return createHash('sha256').update(canonical).digest('hex');
-}
-export async function writeStrategy(input) {
-    const partial = {
-        version: '1.0',
-        sha256: '',
-        generatedAt: new Date().toISOString(),
-        goal: input.goal,
-        rootCauseAnalysis: input.rootCauseAnalysis,
-        impactSurface: input.impactSurface,
-        designRationale: input.designRationale,
-        ...(input.askUserQuestion ? { askUserQuestion: input.askUserQuestion } : {}),
-    };
-    const sha256 = sha256Of(partial);
-    const final = { ...partial, sha256 };
-    StrategyOutputSchema.parse(final);
-    const body = [
-        `# Strategy`,
-        ``,
-        `## Goal`,
-        input.goal,
-        ``,
-        `## Root Cause Analysis`,
-        input.rootCauseAnalysis,
-        ``,
-        `## Impact Surface`,
-        input.impactSurface.map((s) => `- ${s}`).join('\n'),
-        ``,
-        `## Design Rationale`,
-        input.designRationale,
-        ...(input.askUserQuestion ? [``, `## Decision Needed`, `**${input.askUserQuestion.question}**`, ...input.askUserQuestion.options.map((o) => `- ${o}`)] : []),
-        ``,
-        `---`,
-        `STRAT.sig: ${sha256}`,
-    ].join('\n');
-    const tmp = `${input.out}.tmp`;
-    try {
-        await writeFile(tmp, body, 'utf8');
-        await rename(tmp, input.out);
-    }
-    catch (err) {
-        await unlink(tmp).catch(() => undefined);
-        throw err;
-    }
-    return final;
-}

package/dist/src/services/rd/tactical-stage.d.ts

@@ -1,33 +0,0 @@
-import { type AstGateContext } from './ast-gate.js';
-import type { ImplOutput } from './types.js';
-export declare const STRAT_SIG_REGISTRY: Map<string, string>;
-export declare function registerStratSig(projectDir: string, sig: string): void;
-export declare const STRAT_SIG_CHAIN_INVARIANT = "STRAT.sig chain broken";
-export interface RunTacticalInput {
-    readonly project: string;
-    readonly changedFiles: ReadonlyArray<string>;
-    readonly inputSig: string;
-    readonly context: AstGateContext;
-    readonly out: string;
-}
-/**
- * Run the tactical stage: AST gate → STRAT.sig chain check → TACT.sig write.
- *
- * @remarks
- * **Call-order contract (H8 / load-bearing):** the caller MUST invoke
- * `registerStratSig(projectDir, inputSig)` BEFORE calling `runTacticalStage`.
- * The chain check runs AFTER the AST gate (intentionally — see inline comment
- * below) and keys `STRAT_SIG_REGISTRY` by `dirname(input.out)`. If no STRAT.sig
- * is registered for that key, this function throws
- * `${STRAT_SIG_CHAIN_INVARIANT}: stratSig=<unregistered>`. The common
- * production path is `runStrategicStage(...)` → `runTacticalStage(...)`;
- * `runStrategicStage` calls `registerStratSig` internally.
- *
- * @param input - project, changed files, inputSig (must match registered
- *                STRAT.sig for `dirname(input.out)`), AST-gate context, output path.
- * @returns `ImplOutput` written atomically to `input.out`.
- * @throws When the AST gate fails (re-thrown from `runAstGate`).
- * @throws When `inputSig` does not match the registered STRAT.sig for the
- *         project dir, or when no STRAT.sig is registered.
- */
-export declare function runTacticalStage(input: RunTacticalInput): Promise<ImplOutput>;