Clarify current waits and operator execution context

[rmcdaniel]

Implements #141. Prepares Waterline 2.2.0 after published prerelease acceptance.

Change

• Classification filters apply to dashboards and execution lists, with namespace, status and saved-view filters. Missing-summary runs remain visible. Views show scope and observation time.
• Wait summaries distinguish planned retries, eligible work, unknown timing and elapsed known deadlines, using each activity's own attempts and budgets.
• Application context uses explicitly configured scalar fields and encoded entity links.
• Initial canonical run details use bounded observations in both embedded and service modes. A shared presenter keeps waits, relationships, failures and history consistent.
• Default reads contain 200 history events, 50 related runs per direction and ten recent failure references. Children keep independent outcomes. Cursors authenticate the selected run and original sequence ceiling. Supporting failures have direct history links. Pruned or unavailable evidence stays explicit.
• The service initial read skips describe, all-run navigation, full diagnostics, activities and streams. External payload references stay encoded. Context is fetched only after the workflow type identifies the host's permitted profile, pinned to the observed run.
• Complete input/output, actions and deeper diagnostics require explicit inspection. Existing deep bookmarks remain usable. History pagination appends earlier pages and rejects stale selection responses.

Qualification

Exact published dependencies: Workflow 2.4.5, PHP SDK 2.2.3 and Server 2.5.5.
The backward-compatible stable release preparation is 6014bb0.
Final normal checks are running.

RC2 passes its
complete source matrix
and two-architecture image publication and smoke.
Fresh registry installation and the exact image each pass maintenance-heavy,
delayed retry, unknown wait, independent child outcomes and pruned history
fixtures on desktop and mobile, 20 browser cases total. These are synthetic
persisted operator fixtures using real published APIs and the actual UI.
Failure event 1002 is directly reachable beyond the first 200 events.
No browser errors, initial full reads or unpermitted context are observed.
RC2 removes a conflicting generic “ready to run” label from a planned retry.
Older unsupported observers offer explicit complete inspection.

The prior fresh registry acceptance suite passes 98 cases / 1464 assertions,
with one documented legacy timer-transport skip and one existing XML deprecation.
The focused published-dependency source selection passes 63 / 822 with zero skips.
All 52 frontend cases and production build pass.

Server 2.5.5 publication
and all 12 PHP/Python/Rust lifecycle cells
pass. A fresh PHP SDK consumer passes 38 actual HTTP checks, including a real
worker failure, bounded observation, direct failure cursor and namespace refusal.

Release follow-through: qualify merged source, publish stable2.2.0 and verify
its exact registry package/image, then update the website and Sample App.
Issue 141 stays open until that delivery completes. Python, Rust and CLI do not
need unchanged releases. Cloud qualification remains private and separate.