InkkOops

Artifacts reference

This page is a file-by-file reference for the output bundles produced by InkkOops runs, replays, and recordings.

Run bundle files

result.json: overall run result
commands.log: text timeline of executed commands
*.png: captured frames
*.txt: telemetry dumps

result.json

Fields you should expect:

status
scriptName
artifactDirectory
commandCount
failedCommandIndex
failedCommandDescription
failureCategory
failureMessage
durationMilliseconds

commands.log

This file is optimized for timeline reconstruction. Each line contains a UTC timestamp and the command index that was logged. Read this when you want a quick operational view of the run.

Telemetry dump

The telemetry file is a text representation of runtime state. It typically includes:

timestamp
hovered and focused element
dirty-region summary
synchronized dirty roots summary
retained-render statistics
window and viewport dimensions
visual tree snapshot produced by the diagnostics contributor pipeline

Recording bundle files

recording.json: structured source of truth for replay

How to inspect a failed run

Open result.json to identify the failing command index.
Check the failureCategory and failedCommandDescription fields in result.json.
Use commands.log to understand the lead-up to the failure.
Check the final frame capture and telemetry dump to compare visible and structural state.