/**
 * 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).
 *
 * This module holds the machine-readable decision table for that collapse;
 * the prose the LLM runner actually reads is
 * `skills/bee/peaks-rd/references/parallel-review-fanout.md`. It used to
 * describe itself as "consumed by the LLM-side runner", which named no
 * mechanism — an LLM reads prose, not TypeScript exports — and that is the
 * reason every export below sat at zero importers until slice F2.
 *
 * Pinning is complete. The two test files this block used to cite were
 * both deleted in `f17aa377`. The **predicate half**
 * (`RD_DEPRECATED_REVIEWERS` + `isDeprecatedReviewer`) was re-pinned by
 * `tests/unit/rd/reviewer-dispatch-policy.test.ts` (`7191140f`, 6 cases).
 * The **decision-table half** — `RD_FANOUT_REVIEWERS`' 3-element
 * membership, `reviewerListFor`, `karpathySlotIndex`,
 * `shouldDispatchKarpathy` — is pinned by
 * `tests/unit/rd/reviewer-dispatch-policy-decision-table.test.ts`,
 * including the 5→3 relationship: the fanout request types are exactly
 * the review request types `isFanoutTriggerType` accepts, and no
 * deprecated reviewer appears in the returned list.
 *
 * `src/cli/commands/sub-agent-shared.ts` (`deprecatedReviewerWarnings`),
 * invoked from the dispatch chokepoint in
 * `src/cli/commands/dispatch-commands.ts` and pinned by
 * `tests/unit/cli/sub-agent-dispatch-deprecated-reviewer.test.ts`, is the
 * only runtime importer. The decision-table exports are pinned by tests
 * rather than imported, which is the point of the table. The three type
 * aliases derived from the tuple constants are module-internal: no
 * importer names them, so they are not exported.
 *
 * 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. Tier 5 (`artifact-prerequisites.ts`)
 * holds the matching prereq-side back-compat: `AUDIT_SECURITY` /
 * `AUDIT_PERF` accept the legacy `rd/security-review.md` /
 * `rd/perf-baseline.md` artifacts via `legacyRelativePaths`.
 *
 * Both halves are wired as of slice F2 and both ACCEPT the legacy slot.
 * The dispatch side emits the reroute notice as a warning
 * (`deprecatedReviewerWarnings`) rather than a refusal, precisely so it
 * does not disagree with the prereq side about the same deprecation.
 */
export declare const RD_REVIEW_REQUEST_TYPES: readonly ["feat", "bugfix", "refactor", "config", "docs", "chore"];
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"];
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"];
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;
export {};