# Humanish 0.89.0: evidence-linked study findings

Completed studies can now produce ranked findings with links to the participant
events and captures that support them. Observer keeps Participants and Findings
inside the same study shell, with the recording grid, original participant
feedback and playback controls available throughout the review.

## Analyze a completed study

```bash
npm install humanish@0.89.0
npx humanish analyze --run latest --max-cost 3 --dry-run --json
npx humanish analyze --run latest --max-cost 3 --json
npx humanish observe --run latest
```

Select a verified, completed live run. The first analysis command checks admission
without credentials or a provider request; the second requires `OPENAI_API_KEY`
and sends selected text and captures to OpenAI. The required cost ceiling bounds
a conservative estimate, not the provider's invoice. Opening Observer never
starts analysis.

The standard analysis covers session summary, apparent intent, observed outcome,
friction, dead ends and recovery. Findings explain task impact, affected and
exposed participants, evidence and limitations. Participant reports, recorded
completion conditions and independent analysis remain separate. Missing evidence
can leave an outcome unknown even when the participant reported success.

Identical source input, configuration and prompt version reuse a saved analysis.
`--rerun` requests a new immutable version; `--question` adds a reviewer question.
The default is `gpt-6-astra` with high reasoning, a five-minute timeout and 16,384
output tokens including reasoning. Each attempt makes one stateless request,
without tools or automatic retries, and retains known usage or explicit
uncertainty.

## Review findings against the recording

Participants and Findings share the study library, header and available width.
Ranked findings expand in place and open their exact source event. A screenshot
shown only as context is labeled accordingly; nonvisual evidence opens its
original event without inventing a frame. Playback links, return navigation and
phone controls retain their source context. The scrubber thumb and track now
share the same centerline, with component geometry checks at multiple sizes.

Use `analyze list` and `analyze show` to inspect history. `analyze correct` appends
a confirmed, dismissed or amended review against the exact analysis and finding
hashes. Original claims and evidence remain intact. Full correction history
refuses another write before existing records become unreadable; analysis and
correction writers share the run lock.

Feedback drafting and export validate the included analysis snapshot and retain
the existing sharing gates. Redacted bundle derivatives omit analyses tied to
the original source bytes. A local-only HTML export remains portable and clearly
labeled. Feedback commands print drafts; they do not post to GitHub.

## Compatibility and verification

The Observer data v1 contract is unchanged. Older recordings remain readable,
and absent, failed, stale or invalid analysis does not erase participant evidence.
The CLI also explains empty participant-feedback candidates and the available
run-summary drafting path.

[The feature implementation and verification](https://github.com/danielgwilson/humanish/pull/773)
cover analysis validation and storage, sharing boundaries, the existing Observer
flows, mobile layout, component geometry and fresh-package review/export paths.
Final source-first model review covered five exposed regression cases and two
untouched controlled task families, with a separate hostile-evidence challenge.
That is bounded validation, not a general accuracy benchmark. One conservative
outcome required an explicit task-scope reconciliation; one accurate positive
recovery item did not motivate a product change.

Evidence selection follows source order and has size/count limits; upstream
truncation also constrains what can be established. Schema and reference checks
do not certify interpretation or exhaustive issue discovery. Review the cited
evidence before acting. Browser proof uses Chromium desktop and phone emulation;
physical-device and cross-browser behavior remain separate verification work.

See the [study-analysis contract](../contracts/study-analysis.md) for limits,
artifact layout, cancellation, corrections and sharing behavior.