> ## Documentation Index
> Fetch the complete documentation index at: https://momentic.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The canonical docs host is https://momentic.ai/docs. Append .md to any page URL for clean Markdown. Fetch https://momentic.ai/docs/llms.txt for the page index and https://momentic.ai/docs/llms-full.txt for every page in one file.
> For an unattended setup, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools skills` (use `--platform ios` or `--platform android` for mobile). Never run an interactive command in a non-TTY shell.
> You cannot complete the browser sign-in yourself. Read the API key from the MOMENTIC_API_KEY environment variable, or ask the user to create one at https://app.momentic.ai/settings/api-keys and paste it back.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Install the skills with `npx skills@latest add momentic-ai/skills`.
> Tests are YAML files in the user's repository. Use only the step names listed at https://momentic.ai/docs/reference/commands.md and the file structure at https://momentic.ai/docs/core-concepts/file-format.md. Do not invent step names, config keys, or CLI flags.
> Web tests run on Chromium, iOS tests on simulators, and Android tests on emulators. Physical devices are not supported.

# Session reports

> What a Mo session records: test cases, a verdict per case, and bugs with reproduction steps and a recording.

Every Mo session keeps one report. The session agent owns it, merges
complementary entries, and removes duplicates as the sub-agents submit their
work.

## Test cases

A test case is the coverage Mo decided on, written so a person or a Momentic
test can follow it:

| Field                | Content                                                 |
| -------------------- | ------------------------------------------------------- |
| `name`               | Short name for the behavior under test.                 |
| `summary`            | What the case checks.                                   |
| `preconditions`      | The state and the account needed before the first step. |
| `outline`            | The steps through the flow.                             |
| `acceptanceCriteria` | What must be true for the case to pass.                 |

Two cases are duplicates when they check the same behavior under the same
meaningful conditions, so Mo keeps distinct roles, permissions, and outcomes as
separate cases.

## Verdicts

A bug bash agent submits one verdict per case:

* **Verified**: the case behaved as its acceptance criteria require.
* **Issues found**: the agent saw behavior that does not match the criteria.
* **Blocked**: the case could not be checked. Access, missing data, or a sandbox
  limit stopped it.

Each verdict carries a summary, the parts the agent verified, and the gaps it
could not close. Alongside the verdict, the agent records the individual
controls it exercised, each marked checked, failed, partial, or out of scope.

## Bugs

Only a reproduced bug reaches the report. Each one holds:

| Field        | Content                                                      |
| ------------ | ------------------------------------------------------------ |
| `name`       | Short name for the defect.                                   |
| `summary`    | The defect in one paragraph.                                 |
| `expected`   | The behavior the product should have.                        |
| `actual`     | The behavior the agent observed.                             |
| `reproSteps` | The steps from the start of the flow to the broken behavior. |
| `recording`  | The video of the reproduction, with the start and end times. |

The report records which agent reproduced the bug, so you can open that
conversation and read the run that confirmed it. From a bug you make a
[triage decision](/docs/mo/triage).

## Review the coverage

Read the case list before you rely on a pass. A flow that is missing from it was
not tested. Message Mo to widen or narrow the scope, or tell it which behavior
is expected: that reason goes to the knowledge base as a
[triage decision](/docs/mo/triage).