Release Notes: Chrome Extension 0.1.117

Version 0.1.117 closes the 0.1.109–0.1.117 development series: the workflow engine slice (settle_after, strict validation), agent batch tooling (overlay menu control, the session task queue), a UI restructure, and a set of reliability fixes driven by live incident work.

What Changed

Workflow engine

  • settle_after on workflow steps: wait for a locator state or a delay after a primitive before advancing (fixes SPA post-navigation races).
  • Strict validation: unknown workflow fields, unknown step fields, and (when the runtime supplies its primitive dictionary) unknown primitive names are rejected at validation time with errors naming the step and the field.

Agent tooling

  • Overlay menu control primitives: overlay.menu.collapse, expand, move, hide, show. Hide-operate-unhide makes page clicks reliable when the overlay covers a target.
  • Session task queue: task.add, task.next, task.complete, task.list, task.clear. Externalizes multi-step plans; the empty-queue task.next returns a grounded summary of every task’s outcome.
  • actions.site call-argument recovery: the model-habitual name parameter and nested arguments.action shapes are normalized to the canonical action; error messages teach the correct call shape.
  • Every target_not_found error now reports when the actions.json overlay is visible and suggests overlay.menu.hide — the overlay is the first suspect for dead clicks and missing elements.

UI

  • The page overlay is a single agent pane (no Settings tab). All settings live in the extension popup as collapsible sections, with Take control / Open agent overlay buttons and a Session card.
  • Transcript noise removed: successful tool calls show only a transient launcher state; failures append a single line; the live label is “Session live”; mute icons carry a full diagonal slash.
  • The popup explains and disables take-control on Chrome internal pages, and announces an unset bridge URL instead of silently authorizing 127.0.0.1.

Reliability and observability

  • Local execution exceptions are recorded before any bridge fallback and carry through to the final error — a bridge-side 404 can no longer mask a local crash.
  • Bridge storage hydration is observable end-to-end: every send/skip/failure is recorded and the runtime’s import result is exposed as storage_hydration in the actions-json://bridge/runtimes resource.
  • Hosted screenshots keep compact defaults (JPEG q60, 960x960, 180 KB cap).

What To Test

  • A multi-card batch (for example a board-wide reschedule) driven through the task queue: seed with task.add, drain with task.next/task.complete, and confirm the final report matches the queue’s grounded summary.
  • A click-heavy stored action on a page region covered by the overlay, with the overlay visible before and after.
  • A workflow authored with a typo’d step field or primitive name: validation should reject it by name instead of silently ignoring it.
  • Fresh-install flow: load the extension, open the popup on a normal website tab, follow the bridge-URL guidance, take control, and confirm credential and storage hydration land without manual sync.