Skip to content

CHANGELOG.md

Latest commit

 

History

History
57 lines (37 loc) · 4.07 KB

CHANGELOG.md

File metadata and controls

57 lines (37 loc) · 4.07 KB
Raw

Changelog

All notable changes to ai-consensus-core will be documented here. Format: Keep a Changelog, SemVer.

[0.11.1] — 2026-05-25

Fixed — judge-confidence parser contract

buildJudgeSystemPrompt now idempotently appends the JUDGE_CONFIDENCE: [number 0-100] directive, mirroring the CONFIDENCE: [number 0-100] handshake that buildParticipantSystemPrompt has always emitted. Previously, any caller that supplied a custom ConsensusOptions.judge.systemPrompt (instead of relying on JUDGE_PERSONA.systemPrompt, which has the directive inline) silently broke the parser contract: extractJudgeConfidence would not find the marker, fall through to its 50 default, and return a measurement-shaped value that polluted downstream statistics.

Discovered by a 12-run benchmark in ai-consensus-mcp where judge confidence was reported as exactly μ=50.0, σ=0.0 across every run — the unmistakable fingerprint of the silent default. Every panel in that repo overrode judgeSystemPrompt and none re-emitted the marker.

  • buildJudgeSystemPrompt auto-appends the directive when it is not already present in the supplied prompt
  • Idempotency check is case-insensitive substring on JUDGE_CONFIDENCE, so JUDGE_PERSONA's inline directive (and any diligent custom caller) is not duplicated
  • New contract tests in prompts.test.ts mirror the existing participant-side test and fail loudly if a future edit breaks the handshake

Backward compatibility

No public API change. The only observable difference is that buildJudgeSystemPrompt's output string is longer when the input prompt lacks the marker. Callers that snapshot-test that output will need to regenerate snapshots. Callers that relied on the previous silent-50 behaviour will now see the real model-emitted value (which is the documented intent).

[0.11.0] — 2026-04-30

Added — tool calling

The engine can now drive a per-participant tool-call loop. Hosts plug in a toolExecutor; participants declare a tools list; the engine dispatches each ToolCall from the model, feeds the results back, and re-invokes the caller until the model returns final content or maxToolIterations is hit.

  • Participant.tools?: ToolDefinition[] — per-participant tool inventory
  • ConsensusOptions.toolExecutor?: ToolExecutor — host-supplied dispatcher
  • ConsensusOptions.maxToolIterations?: number — loop cap (default 8, clamped to [1, 32])
  • ModelCallRequest.tools?: ToolDefinition[] — forwarded verbatim to the caller
  • ModelCallRequest.toolCallTurns?: ToolCallTurn[] — accumulated history on follow-up calls
  • ModelCallResponse.toolCalls?: ToolCall[] — caller may return tool-call requests
  • New types: ToolDefinition, ToolCall, ToolCallTurn, ToolCallContext, ToolExecutionResult, ToolExecutor
  • New events: toolCallStart, toolCallComplete, toolError
  • Schema export: ToolDefinitionSchema
  • Constant export: MAX_TOOL_ITERATIONS_CAP (= 32)

See README "Tool calling" section for the full contract and integration recipe.

Backward compatibility

100% backward compatible with 0.10.x. Every new field is optional; absence of toolExecutor ⇒ engine behaviour is byte-identical to 0.10. Existing tests pass without modification (130/130) plus 12 new tool-calling tests (142 total).

Internal

  • New private engine helper: #runParticipantTurn (drives the tool loop)
  • New private engine helper: #dispatchToolCalls (per-iteration dispatch + events)
  • Token usage is summed across loop iterations; the final response's content is the participant turn's output

[0.10.0] — 2026-04-24

  • Removed the seven Roundtable personas from the library; they live in docs/personas.md for callers to copy. Only JUDGE_PERSONA remains in code.
  • Added ConsensusOptions.judge.systemPrompt to override the synthesis prompt (with documented contract on the ## Majority Position / ## Synthesis Confidence markers).
  • Replaced ReDoS-prone regex parsers with linear string scans.

(Earlier history is in git; this CHANGELOG starts at 0.10.0.)