## Exploratory Verification

For any task involving interactive IBM i display file screens, you must perform some ad-hoc exploratory verifications before the task can be considered complete. This applies both to coding and non-coding tasks that involve interactive screens.

The goal is to produce a coherent summary of your explorations, including screen renderings.

**Important: You MUST properly sign off any IBM i sessions you create during your task.**

1. Come up with a list of ad-hoc tests that verify your task is complete and working. The list should cover all affected screens. Keep a "mental note" (and/or temp file) of this list.
2. For coding tasks, finish the coding work and verify all changes build successfully.
3. Use your `ibmi-interactive-session` skill to start a new session.
4. For each test case:

- Use the `ibmi-interactive-session` skill to operate the application. Interpret the screen buffer and fields information to understand what is on screen and navigate to the screen you want to test and perform any required operations.
- Keep "mental notes" (and/or temp files) of what you are doing and make sure that specific screen history file names can be correlated to each step.
- In your notes, create a text summary that explains how your exploration passed or failed the test. Use the `ibmi-interactive-session` skill to produce an HTML rendering and correlate the generated `<iframe>` tag text with your summary. Do not use basic renderings unless HTML rendering fails, or unless you are specifically asked to.

5. Review the results of your test cases.

- If all pass, proceed to step 6.
- If there are failures:
    - If you think you can solve them, sign off and end your IBM i session. Restart at step 2.
    - If the problems don't seem solvable, you can proceed to step 6.

6. Sign off and end your session.
7. Using your notes, prepare a final summary of all explorations, including corresponding renderings, as a temporary Markdown file. This content will be embedded directly in your final summary file. Use this format:

## Exploratory Verification Results

### Test Case 1: Title
Summary text to describe the exploration and results

<screen rendering>

### Test Case 2: Title
Summary text to describe the exploration and results

<screen rendering>

**Important** Make sure that screen rendering content is placed at the root of the Markdown document (i.e. not in lists, etc.) as shown above.
