# Humanish 0.86.0: know which assignment and action you are reviewing

The Observer now shows each participant's assigned mission and lane focus.
Expand **Assigned task** in the player or participant details to read the
instructions. Computer-use runs also include their participant-facing task
goals. Hidden success checks and runtime access details stay outside this
assignment. Older recordings explicitly say when an assignment was not recorded.

Selecting an activity entry now selects that entry's identity, timestamp and
coordinate pin. Two clicks between the same screenshots can be inspected
separately. The image remains the recorded capture; its label explains whether
its timestamp is before, after or equal to the selected entry's timestamp.
Missing timestamps stay explicit. **Show capture interval** returns to the
complete interval, and **Next action** visits actions within the same interval.

Copied links and local saved moments retain the selected action. Saved entries
include subsecond timestamps and their recorded order, so repeated clicks or
keypresses remain distinguishable. A missing saved entry reports its absence.
On phones, the player keeps the selected participant's name above the evidence.

This release also supports the current `@e2b/desktop` 2.4.0 startup cleanup path.
If startup fails after an instance is acquired, the SDK's internal kill and
Humanish's fallback share one cleanup result bounded by the lower of the
caller's request timeout and ten seconds. Unconfirmed cleanup prevents another
allocation. Successful creation restores normal teardown behavior. Older
supported SDKs retain their cleanup protection.

Install with `npm install -g humanish@0.86.0`. Reopen an existing run with
`humanish observe --run RUN`, or regenerate its HTML export, to update its viewer.
Updating the viewer cannot reconstruct assignments absent from the original run.

## Verification and limits

The [retained study receipt](https://github.com/danielgwilson/humanish/blob/main/docs/goals/observer-qol/receipts/2026-09-09-participant-context.md)
records the two-participant app study, actual-recording browser review and two
hosted SDK startup-fault probes, including their incomplete outcomes and limits.

Assignment tests cover computer-use, shared-world and terminal producers,
including redaction, old bundles and hidden-field exclusion. Shared-world and
terminal routes retain their mission and role instructions; they do not expose
unexecuted manifest tasks as participant assignments. Browser checks cover
action selection, refresh, save/recall and phone context in the production
artifact. SDK conformance uses the actual installed create/start implementation
with controlled method faults on the current, older and minimum supported peers.

Screenshot replay remains sparse. This change does not add continuous video,
infer participant thoughts, or certify physical mobile input. A cleanup deadline
does not establish ownership before the SDK returns a handle or prove provider
reclamation after an unconfirmed response. Saved moments remain local to the
browser.