v0.2.2

[0.2.2] - 2026-07-28

Added

• get_steps MCP tool and aframes steps CLI: expand one activity frame
  into its ordered click-by-click script (clicks with element name / role /
  AXIdentifier / URL, typed runs, pastes, focus changes) - the replay view of
  a demonstrated run. aframes steps --find "task query" resolves a
  natural-language task to the demonstrated frame without a frame id.
• Entity parsers for Atlassian (Jira/Confluence).
• --debug CLI flag: include sessionization debug info (why segments split
  or merge).
• End-to-end MCP agent integration example under examples/ (#19).
• Date-range header on aframes patterns output, and an explicit message
  when no patterns are detected (#29).

Changed

• Engine downloads fail closed: sha256 verification now covers every
  published nocta-recorder build, and aframes record refuses to install a
  build it has no pinned hash for.
• The package version is single-sourced from activity_frames.__version__
  (hatchling dynamic version).
• The default capture database is resolved by newest mtime instead of
  candidate order.

Fixed

• O(n²) page scan in _pages_for_segment(): large sessions compile
  measurably faster, byte-identical output (#26).
• Product Hunt profile URLs (producthunt.com/@user) now parse to a
  profile page reference.

Docs

• aframes comms documented in the README CLI block.
• SPEC dwell and flicker-merge formulas aligned with the reference
  implementation (the final frame of a session contributes 0 dwell; a
  flicker's recorded seconds is its measured active time and may exceed
  the 20s span threshold).

v0.2.0 — communications view

Added

Communications view — the first drill-down tool over compiled activity: ActivityLog.communications() / comm_surfaces(), the get_communications MCP tool (4 → 5), and aframes comms. Email/messaging/notification surfaces with the window titles measured on each (timing, counts, frame-id evidence). Titles only, measured tier: message bodies are never read; a client that doesn't title its windows with the conversation leaves only its presence to report.

Deterministic (double-run byte-identical), zero new dependencies, suite passes under UTC/Tokyo/Auckland. See #1.