@adia-ai/a2ui-compose 0.2.1 → 0.2.3

package/CHANGELOG.md

@@ -14,6 +14,48 @@ _Nothing yet._
 
 ---
 
+## [0.2.3] - 2026-05-04
+
+**Lockstep cut.** All 8 published `@adia-ai/*` packages bump
+0.2.2 → 0.2.3 per
+[`docs/specs/package-architecture.md` § 15](../../../../docs/specs/package-architecture.md#15-versioning-policy).
+Patch cut — no breaking changes.
+
+### Changed
+
+- `version`: `0.2.2` → `0.2.3`.
+- `dependencies["@adia-ai/a2ui-corpus"]`: `^0.2.0` (covers `0.2.3`).
+- `dependencies["@adia-ai/a2ui-retrieval"]`: `^0.2.0` (covers `0.2.3`).
+- `dependencies["@adia-ai/a2ui-validator"]`: `^0.2.0` (covers `0.2.3`).
+
+### No source changes
+
+`@adia-ai/a2ui-compose` source is byte-identical to `0.2.2`. The cut bumps version + the internal dep range entries only.
+
+## [0.2.2] - 2026-05-02
+
+**Lockstep cut + reasoning-panel emission fixes.** All 8 published `@adia-ai/*` packages bump 0.2.1 → 0.2.2 per [`docs/specs/package-architecture.md` § 15](../../../docs/specs/package-architecture.md#15-versioning-policy). Patch cut — no breaking changes.
+
+### Changed
+
+- `version`: `0.2.1` → `0.2.2`.
+- `dependencies["@adia-ai/a2ui-corpus"]`: `^0.2.0` (covers `0.2.2`).
+- `dependencies["@adia-ai/a2ui-utils"]`: `^0.2.0` (covers `0.2.2`).
+- `dependencies["@adia-ai/a2ui-validator"]`: `^0.2.0` (covers `0.2.2`).
+- `dependencies["@adia-ai/a2ui-retrieval"]`: `^0.2.0` (covers `0.2.2`).
+- `core/generator.js` and `strategies/` are the surfaces that gained the new behavior below; no other compose directories touched.
+
+### Fixed — Reasoning-panel emissions surface confidence + retrieval candidates (2026-05-02)
+
+`generator.js` was emitting `status` events whose labels looked truthful but hid the data needed to judge their reliability. Two fixes that surface the missing data as `outcomes`:
+
+- **Interpret stage** now includes the domain confidence percentage and the matched signals. Previously `Domain: data` read identical at 3% confidence vs 95% — same label. Now: `Domain: data (3% confidence)` plus `Matched signals: pricing` as outcomes. Per memory `feedback_panel_label_reliability.md`.
+- **Analyze stage** runs a fast keyword `searchBlocks(intent)` and emits the top-5 candidates with scores + domains. Previously the stage reported `context.patterns.length` from `getContext(intent, 2)` — but the context-assembler only populates `result.patterns` at tier ≥ 3, so the count was structurally guaranteed to be 0. The label read "nothing relevant" when it actually meant "we didn't even look here." The fix runs a real retrieval at the analyze stage instead of relying on the wrong-tier context.
+
+Companion fix in `@adia-ai/a2ui-retrieval` Unreleased (web-research.js EXPLICIT/IMPLICIT pattern split). Both surfaces feed the same reasoning-panel deception class — five distinct bugs caught + fixed in commit `9986c71e`.
+
+---
+
 ## [0.2.1] - 2026-05-02
 
 **Lockstep cut + scope-drift gate at composer time + skeleton harvest + Tier-1 block filter + high-resolution session ticket trace.** All 8 published `@adia-ai/*` packages bump 0.2.0 → 0.2.1 per [`docs/specs/package-architecture.md` § 15](../../../docs/specs/package-architecture.md#15-versioning-policy). Patch cut — no breaking changes.

package/core/generator.js

@@ -244,9 +244,23 @@ export async function* generateUIStream({ intent, executionId, llmAdapter, model
   executionId = engine.start({ intent, mode: 'stream', previousExecId });
 
   // ── Stage 1: Interpret ──
+  // Include confidence + matched signals in the status message so a reader can
+  // distinguish a strong domain match from a 3% tie-breaker. The bare label
+  // "Domain: data" is indistinguishable between "build a data dashboard" (high
+  // confidence, many signals) and "tier pricing page" (0.03 confidence, one
+  // weak signal) — same text, very different reliability.
   const domain = lookupDomain(intent);
   engine.submitStage(executionId, 'interpret', { domain, intent, confidence: domain.confidence });
-  yield { type: 'status', stage: 'interpret', message: `Domain: ${domain.domain}` };
+  const conf = domain.confidence != null ? Math.round(domain.confidence * 100) : null;
+  const signals = Array.isArray(domain.matchedSignals) && domain.matchedSignals.length
+    ? domain.matchedSignals.slice(0, 4)
+    : null;
+  yield {
+    type: 'status',
+    stage: 'interpret',
+    message: `Domain: ${domain.domain}${conf != null ? ` (${conf}% confidence)` : ''}`,
+    outcomes: signals ? [`Matched signals: ${signals.join(', ')}`] : [],
+  };
 
   // ── Clarity gate: yield clarify event if intent is vague ──
   // Only for fresh intents (not multi-turn iterations which have prior context)
@@ -267,12 +281,34 @@ export async function* generateUIStream({ intent, executionId, llmAdapter, model
   }
 
   // ── Stage 2: Analyze ──
+  // Surface the actual top-N retrieval candidates with scores. Two reasons the
+  // previous `${...patterns.length} patterns` line was misleading:
+  //   (a) `getContext(intent, 2)` runs at tier=2, but the context-assembler
+  //       only populates `result.patterns` at tier≥3 — so `context.patterns`
+  //       was STRUCTURALLY empty. "0 patterns" wasn't a retrieval result; it
+  //       was a tier mismatch. Fixed by running a fast keyword search here.
+  //   (b) The synthesizer composes from below-threshold patterns too; "0
+  //       patterns" reading as "nothing relevant" actively misleads the user.
   const context = await getContext(intent, 2);
+  const topPatternsRaw = searchBlocks(intent).slice(0, 5);
+  const candidateLines = topPatternsRaw.length
+    ? topPatternsRaw.map(p => {
+        const score = p.score != null ? ` · ${Number(p.score).toFixed(2)}` : '';
+        const domainTag = p.domain ? ` (${p.domain})` : '';
+        return `  • ${p.name}${domainTag}${score}`;
+      })
+    : ['  (no keyword match — synthesizer will compose from components)'];
   engine.submitStage(executionId, 'analyze', {
-    context, componentCount: context.components.length, patternCount: context.patterns.length,
+    context, componentCount: context.components.length, patternCount: topPatternsRaw.length,
+    topPatterns: topPatternsRaw.map(p => ({ name: p.name, score: p.score, domain: p.domain })),
     confidence: context.components.length > 0 ? 0.85 : 0.5,
   });
-  yield { type: 'status', stage: 'analyze', message: `${context.components.length} components, ${context.patterns.length} patterns` };
+  yield {
+    type: 'status',
+    stage: 'analyze',
+    message: `${context.components.length} components inspected · ${topPatternsRaw.length} pattern candidate${topPatternsRaw.length === 1 ? '' : 's'}`,
+    outcomes: ['Top retrievals:', ...candidateLines],
+  };
 
   // ── Research: web search enrichment (optional) ──
   let researchContext = '';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/a2ui-compose",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "AdiaUI A2UI compose engine — framework-agnostic. Takes natural-language intents + a catalog and produces A2UI protocol messages. Pairs with `@adia-ai/a2ui-retrieval` (intent classification, catalog lookup) and `@adia-ai/a2ui-validator` (schema + semantic checks).",
   "type": "module",
   "exports": {