@adia-ai/web-modules 0.8.27 → 0.8.29

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog — @adia-ai/web-modules
 
+## [0.8.29] — 2026-08-06
+
+### Added
+- **chat-surfaces renders plan-envelope chrome** — `wireAgentEvents` gains a `step` case rendering the turn's surface manifest and "what changed" synthesis as feed chrome (workflow:'plan'), riding the existing AgentEvent `step` kind — no event-vocabulary change (gh#648, PR #654).
+
+### Maintenance
+- **`dist/` bundles rebuilt** in this cut's window (1 file(s)) — regenerated from the source changes described above, not independent edits.
+
+## [0.8.28] — 2026-08-05
+
+### Fixed
+- **Generated CSS barrel regenerated — the `agent-admin` family was missing since 0.8.26**: `admin-roster`, `admin-settings`, and `agent-admin` shipped unstyled on every page linking `index.css` (gh#632).
+- **`sideEffects` allowlist covered only 6 of 13 self-registering module families** — a consumer's bare side-effect import of `billing`, `dashboard`, `feedback`, `form`, `onboarding`, `settings`, or `simple` (e.g. `import '@adia-ai/web-modules/form/form-popover'`) was tree-shaken from production bundles: the `customElements.define` never shipped while the paired CSS survived, so the element rendered its raw light-DOM fallback in deployed builds only (gh#625, bit adiav2's admin dashboard — Linear ADIA2-7422). All 7 families added; a new repo gate (`check:sideeffects-coverage`) derives the required list from the registration idioms so the next family can't repeat this.
+
+### Maintenance
+- **`dist/` bundles rebuilt** in this cut's window (2 file(s)) — regenerated from the source changes described above, not independent edits.
+
 ## [0.8.27] — 2026-08-05
 
 ### Changed

package/chat/chat-surfaces/chat-surfaces.d.ts

@@ -39,6 +39,22 @@ export function createSurfaceRegistry(opts: {
 /** CHAT-HARNESS law 3 — code-owned progress labels, never model text. */
 export const PROGRESS_LABELS: Record<string, string>;
 
+/** Plan-envelope feed chrome (gh#648) — code-owned sentence around a
+ *  `PlanEnvelope`'s per-surface rationale. Ruling 3: feed chrome, never a canvas. */
+export function describePlanManifest(plan: {
+  turnId: string;
+  surfaces: { surfaceId: string; rationale: string }[];
+}): string;
+
+/** Plan-envelope feed chrome (gh#648) — code-owned sentence around a
+ *  `TurnSynthesis`'s new/updated/closed surface lists. */
+export function describeTurnSynthesis(synthesis: {
+  turnId: string;
+  new: string[];
+  updated: string[];
+  closed: string[];
+}): string;
+
 export function wireAgentEvents(
   chatShell: Element & {
     appendChunk?(text: string): void;

package/chat/chat-surfaces/chat-surfaces.js

@@ -163,6 +163,38 @@ export const PROGRESS_LABELS = {
   done: 'Done',
 };
 
+/**
+ * Plan-envelope feed chrome (gh#648, docs/ORCHESTRATION.md §Plan envelope
+ * ruling 3 — "what changed" is feed chrome, never a canvas). These render
+ * from the `{ type: 'step', workflow: 'plan', step: 'manifest'|'synthesis' }`
+ * AgentEvent — the EXISTING `step` kind (`@adia-ai/agent`'s `AgentEvent`
+ * union already carries `workflow`/`step`/`data`), so no closed-vocabulary
+ * `type` amendment is needed to carry this: `workflow: 'plan'` is just a
+ * new value inside an already-open string field, the same way
+ * `packages/agent/src/workflow.ts`'s own step events use `workflow` for a
+ * different named workflow.
+ *
+ * Code-owned text (CHAT-HARNESS law 3's spirit, applied to `step` the way
+ * PROGRESS_LABELS applies it to `progress`): the rationale strings inside
+ * a PlanEnvelope ARE planner-authored copy (not raw model text — R-O10's
+ * `rationale` is a structured field, one line per surface), so they render
+ * verbatim; the surrounding sentence is code-owned.
+ */
+export function describePlanManifest(plan) {
+  const n = plan.surfaces.length;
+  const list = plan.surfaces.map((s) => `${s.surfaceId} — ${s.rationale}`).join('; ');
+  return `Planning ${n} surface${n === 1 ? '' : 's'}: ${list}`;
+}
+
+const SYNTHESIS_LABELS = { new: 'New', updated: 'Updated', closed: 'Closed' };
+
+export function describeTurnSynthesis(synthesis) {
+  const parts = ['new', 'updated', 'closed']
+    .filter((key) => synthesis[key].length > 0)
+    .map((key) => `${SYNTHESIS_LABELS[key]}: ${synthesis[key].join(', ')}`);
+  return parts.length ? `What changed — ${parts.join(' · ')}` : 'What changed — nothing this turn';
+}
+
 /**
  * Consumes ONE `AsyncIterable<AgentEvent>` for the turn already opened on
  * `chatShell` (the caller has already appended the user message and an
@@ -206,6 +238,21 @@ export async function wireAgentEvents(chatShell, registry, opts) {
         break;
       }
 
+      case 'step': {
+        // Plan-envelope chrome (gh#648, ruling 1 — harness-level progress,
+        // never wire; ruling 3 — feed chrome, never a canvas). Any other
+        // `workflow` value falls through unrendered — this switch only
+        // owns the 'plan' workflow's two steps.
+        if (event.workflow === 'plan' && event.step === 'manifest') {
+          chatShell.appendMessage?.({ role: 'assistant', content: describePlanManifest(event.data), render: true });
+          chatShell.appendMessage?.({ role: 'assistant', content: '' });
+        } else if (event.workflow === 'plan' && event.step === 'synthesis') {
+          chatShell.appendMessage?.({ role: 'assistant', content: describeTurnSynthesis(event.data), render: true });
+          chatShell.appendMessage?.({ role: 'assistant', content: '' });
+        }
+        break;
+      }
+
       case 'tool_use':
         chatShell.appendMessage?.({
           role: 'assistant',