@cjhyy/code-shell-core 0.7.1 → 0.8.0

package/dist/arena/strategies/review.js

@@ -1,168 +0,0 @@
-/**
- * Review strategy — structured code review with findings.
- *
- * V2: produces ArenaFinding[] (strength/improvement/risk/question)
- * instead of free-text opinions.
- */
-import { formatBaseContext, formatReports, formatFindingReviews, formatClaimsForReview, formatDebateHistory, formatClaimSummaryForConsensus, formatDigestForPrompt, parseReport, parseReviews, parseConsensus, parseChallenges, parseDebateTurn, parseAdjudication, } from "./utils.js";
-export class ReviewStrategy {
-    // ─── Research Phase ──────────────────────────────────────────
-    researchSystemPrompt(name) {
-        return (`You are ${name}, a reviewer in a multi-model review arena.\n\n` +
-            `You may have access to read-only tools to fetch additional context. ` +
-            `The base context is intentionally lean — use tools to inspect details as needed.\n\n` +
-            `IMPORTANT RULES:\n` +
-            `- Limit yourself to AT MOST 3 tool rounds. Do NOT exhaustively read every file.\n` +
-            `- Focus on the HIGHEST-IMPACT findings. Quality over quantity.\n` +
-            `- Output as many findings as the topic warrants — typically 5-15 for a non-trivial subject. ` +
-            `Each <summary> should be 80+ words with concrete evidence and rationale, not a one-liner. ` +
-            `Rank by confidence.\n` +
-            `- Prioritize: risks > improvements > questions. Strengths are optional.\n\n` +
-            `When ready, respond ONLY with the following XML structure (no markdown fences, no commentary outside the root element):\n\n` +
-            `<report>\n` +
-            `  <contextSummary>brief summary of what you investigated</contextSummary>\n` +
-            `  <findings>\n` +
-            `    <finding id="unique-id" kind="risk|improvement|question|strength" severity="high|medium|low" confidence="0.0-1.0">\n` +
-            `      <title>short title</title>\n` +
-            `      <summary>detailed explanation, 80+ words, citing specific files/lines</summary>\n` +
-            `      <evidence type="file|diff|grep|git|doc" ref="path">what it shows</evidence>\n` +
-            `      <evidence type="file" ref="another/path">…</evidence>\n` +
-            `      <affectedFiles>\n` +
-            `        <file>src/foo.ts</file>\n` +
-            `        <file>src/bar.ts</file>\n` +
-            `      </affectedFiles>\n` +
-            `      <suggestedChange>optional concrete fix</suggestedChange>\n` +
-            `    </finding>\n` +
-            `    <!-- repeat <finding> blocks as needed -->\n` +
-            `  </findings>\n` +
-            `</report>\n\n` +
-            `XML is preferred over JSON because thinking-mode models produce more reliable output here. Do not wrap the XML in code fences. Do not include text outside <report>…</report>.`);
-    }
-    researchUserPrompt(topic, baseContext) {
-        return (`## Review Topic\n${topic}\n\n` +
-            `${formatBaseContext(baseContext)}\n\n` +
-            `Use tools to read specific files from the diff. Then output 3-6 highest-confidence findings as a single <report> XML element.`);
-    }
-    parseResearchResponse(participant, text) {
-        return parseReport(participant, text);
-    }
-    // ─── Cross Review Phase ──────────────────────────────────────
-    crossReviewSystemPrompt(reviewerName) {
-        return (`You are ${reviewerName}, reviewing other participants' review findings.\n\n` +
-            `For each finding, provide a verdict:\n` +
-            `- "agree": you confirm this finding\n` +
-            `- "refine": mostly agree but with refinements\n` +
-            `- "disagree": you believe this finding is incorrect\n` +
-            `- "needs_evidence": the finding lacks sufficient evidence\n\n` +
-            `Focus on HIGH VALUE findings: high severity, high risk, or conflicting conclusions.\n` +
-            `You don't need to review every single finding — prioritize the important ones.\n\n` +
-            `Respond ONLY with a JSON array (no markdown fences):\n` +
-            `[{"findingId": "...", "verdict": "agree|refine|disagree|needs_evidence", "reason": "...", "extraEvidence": ["optional"]}]`);
-    }
-    crossReviewUserPrompt(topic, myReport, otherReports) {
-        return (`## Topic: ${topic}\n\n` +
-            `## Your Findings\n${formatReports([myReport])}\n\n` +
-            `## Other Reviewers' Findings\n${formatReports(otherReports)}\n\n` +
-            `Review the other participants' findings. Focus on high-priority items.`);
-    }
-    parseCrossReviewResponse(reviewer, text) {
-        return parseReviews(reviewer, text);
-    }
-    // ─── Consensus Phase ─────────────────────────────────────────
-    consensusSystemPrompt() {
-        return (`You are a neutral moderator synthesizing a multi-model review into a structured consensus.\n\n` +
-            `You MUST faithfully reflect the aggregated findings and peer reviews. ` +
-            `Do NOT add new conclusions that have no source in the findings.\n\n` +
-            `IMPORTANT: Start with a "subjectSummary" — a factual overview of WHAT is being reviewed ` +
-            `(scope, key areas, high-level description). This comes BEFORE any judgment.\n\n` +
-            `Respond ONLY with JSON (no markdown fences):\n` +
-            `{\n` +
-            `  "summary": "one-paragraph overall assessment",\n` +
-            `  "subjectSummary": "factual overview of what is being reviewed — scope, key areas, subject description",\n` +
-            `  "strengths": [{"title": "...", "summary": "...", "support": ["participant names"], "challenge": [], "confidence": 0.0-1.0, "evidenceRefs": ["finding IDs"]}],\n` +
-            `  "improvements": [same structure],\n` +
-            `  "risks": [same structure],\n` +
-            `  "openQuestions": [same structure],\n` +
-            `  "nextActions": [{"title": "...", "priority": "high|medium|low", "rationale": "...", "relatedFindings": ["finding IDs"]}]\n` +
-            `}`);
-    }
-    consensusUserPrompt(topic, reports, reviews) {
-        return (`## Topic\n${topic}\n\n` +
-            `## Participant Reports\n${formatReports(reports)}\n\n` +
-            `## Peer Reviews\n${formatFindingReviews(reviews)}\n\n` +
-            `Synthesize a structured consensus. Group findings by category, note agreement/disagreement, and propose next actions.`);
-    }
-    parseConsensusResponse(text) {
-        return parseConsensus(text);
-    }
-    preferredFindingKinds() {
-        return ["strength", "improvement", "risk", "question"];
-    }
-    // ─── V2: Verification Review ────────────────────────────────────
-    verificationReviewUserPrompt(topic, myReport, claimsToReview, digest) {
-        return (`## Topic: ${topic}\n\n` +
-            `## Your Findings\n${formatReports([myReport])}\n\n` +
-            `## Claims to Verify\n${formatClaimsForReview(claimsToReview)}\n\n` +
-            `## Evidence Digest\n${formatDigestForPrompt(digest)}\n\n` +
-            `Verify each claim against the evidence. For claims lacking evidence, you may request specific checks.\n` +
-            `Respond ONLY with a JSON array:\n` +
-            `[{"claimId": "...", "verdict": "agree|refine|disagree|needs_evidence", "reason": "...", ` +
-            `"supportingEvidenceRefs": ["optional"], "requestedChecks": [{"description": "what to check", "priority": "high|medium|low"}]}]`);
-    }
-    parseVerificationReviewResponse(reviewer, text) {
-        return parseChallenges(reviewer, text);
-    }
-    // ─── V2: Debate ─────────────────────────────────────────────────
-    debateTurnUserPrompt(topic, claim, priorTurns, digest) {
-        return (`## Topic: ${topic}\n\n` +
-            `## Contested Claim\n` +
-            `[${claim.claimId}] ${claim.finding.title}\n${claim.finding.summary}\n` +
-            `Evidence: ${claim.evidenceRefs.join(", ") || "none"}\n\n` +
-            `## Prior Debate\n${formatDebateHistory(priorTurns)}\n\n` +
-            `## Evidence Digest\n${formatDigestForPrompt(digest)}\n\n` +
-            `State your position on this claim. Build on prior turns: cite specific evidence, ` +
-            `acknowledge counter-arguments, and explain your reasoning in 150-300 words. ` +
-            `Brevity here means missed nuance — depth wins.\n` +
-            `Respond ONLY with JSON:\n` +
-            `{"stance": "support|oppose|narrow|uncertain", "summary": "your argument", "newEvidenceRefs": ["optional"]}`);
-    }
-    parseDebateTurnResponse(participant, text) {
-        return parseDebateTurn(participant, text);
-    }
-    // ─── V2: Adjudication ──────────────────────────────────────────
-    adjudicationUserPrompt(topic, claim, debateRounds, digest) {
-        const debateSummary = debateRounds.length > 0
-            ? debateRounds.map((r) => `Round ${r.round}:\n${formatDebateHistory(r.participants)}\n${r.resolved ? "→ Resolved" : "→ Unresolved"}`).join("\n\n")
-            : "No debate rounds occurred.";
-        return (`## Topic: ${topic}\n\n` +
-            `## Claim Under Adjudication\n` +
-            `[${claim.claimId}] ${claim.finding.title}\n${claim.finding.summary}\n` +
-            `Owner: ${claim.owner} | Status: ${claim.status}\n` +
-            `Evidence: ${claim.evidenceRefs.join(", ") || "none"}\n\n` +
-            `## Challenges\n` +
-            claim.challenges.map((c) => `[${c.reviewer}] ${c.verdict}: ${c.reason}`).join("\n") + "\n\n" +
-            `## Debate\n${debateSummary}\n\n` +
-            `## Evidence Digest\n${formatDigestForPrompt(digest)}\n\n` +
-            `As moderator, you MUST issue a verdict — "unresolved" is reserved ONLY for the rare case where the debate produced genuinely irreconcilable interpretations of the same evidence. Default to deciding.\n\n` +
-            `Decision rule:\n` +
-            `- "accepted": claim is correct as stated AND has direct evidence (file/line refs).\n` +
-            `- "accepted_with_revision": core insight is correct but the challenge surfaced a real refinement (scope/severity/wording). Issue a corrected finalSummary.\n` +
-            `- "rejected": the challenger demonstrated the claim is factually wrong or already addressed in the code under review.\n` +
-            `- "unresolved": ONLY when no amount of further evidence could break the tie — e.g., taste-level disagreement on design philosophy. Using this on a verifiable code claim is a failure of adjudication.\n\n` +
-            `Respond ONLY with JSON:\n` +
-            `{"outcome": "accepted|accepted_with_revision|rejected|unresolved", "rationale": "...", ` +
-            `"finalSummary": "revised claim summary if needed", "supportingEvidenceRefs": ["..."]}`);
-    }
-    parseAdjudicationResponse(text) {
-        return parseAdjudication("", text);
-    }
-    // ─── V2: Claim-Aware Consensus ─────────────────────────────────
-    claimAwareConsensusUserPrompt(topic, reports, reviews, claimSummary) {
-        return (`## Topic\n${topic}\n\n` +
-            `## Claim Verification Status\n${formatClaimSummaryForConsensus(claimSummary)}\n\n` +
-            `## Participant Reports\n${formatReports(reports)}\n\n` +
-            `## Peer Reviews\n${formatFindingReviews(reviews)}\n\n` +
-            `Synthesize a structured consensus. Verified claims should appear as high-confidence items. ` +
-            `Unresolved claims should appear as open questions. Rejected claims should be excluded or noted as dismissed.`);
-    }
-}

package/dist/arena/strategies/utils.d.ts

@@ -1,36 +0,0 @@
-/** Shared utilities for arena strategy implementations. */
-import type { ArenaBaseContext, FindingReview, ParticipantReport, ArenaConsensus, ArenaRoadmapPhaseDetail, ClaimRecord, ClaimChallenge, ClaimAdjudication, ClaimStatusSummary, DebateTurn, RoundResearchDigest } from "../types.js";
-export { extractJSON, extractJSONArray } from "../../utils/json.js";
-/** Format base context into a readable text block for LLM prompts */
-export declare function formatBaseContext(ctx: ArenaBaseContext): string;
-/** Format participant reports for cross-review or consensus prompts */
-export declare function formatReports(reports: ParticipantReport[]): string;
-/** Format finding reviews for consensus prompts */
-export declare function formatFindingReviews(reviews: FindingReview[]): string;
-/**
- * Parse a ParticipantReport. The research prompt now asks for an
- * XML <report> element because thinking-mode models (DeepSeek V4)
- * produced malformed JSON often enough to derail the loop. We try
- * XML first, then JSON, then a free-text salvage.
- */
-export declare function parseReport(participant: string, text: string): ParticipantReport;
-/** Parse FindingReview[] from LLM JSON output */
-export declare function parseReviews(reviewer: string, text: string): FindingReview[];
-/** Parse ArenaConsensus from LLM JSON output */
-export declare function parseConsensus(text: string): ArenaConsensus;
-/** Format claims for verification-review prompts */
-export declare function formatClaimsForReview(claims: ClaimRecord[]): string;
-/** Format debate history for debate turn prompts */
-export declare function formatDebateHistory(turns: DebateTurn[]): string;
-/** Format claim status summary for consensus prompts */
-export declare function formatClaimSummaryForConsensus(summary: ClaimStatusSummary): string;
-/** Format a digest text block for inclusion in prompts */
-export declare function formatDigestForPrompt(digest: RoundResearchDigest): string;
-/** Parse ClaimChallenge[] from LLM JSON output */
-export declare function parseChallenges(reviewer: string, text: string): ClaimChallenge[];
-/** Parse a DebateTurn from LLM JSON output */
-export declare function parseDebateTurn(participant: string, text: string): DebateTurn;
-/** Parse a ClaimAdjudication from LLM JSON output */
-export declare function parseAdjudication(claimId: string, text: string): ClaimAdjudication;
-/** Parse an ArenaRoadmapPhaseDetail from LLM JSON output */
-export declare function parseDetailExpansion(text: string): ArenaRoadmapPhaseDetail;