internal/

Package artifacts holds filesystem helpers shared by every provider that writes per-step / per-action artifacts (mobile screenshots, browser DOM dumps, etc.).

Package browser is the Tales browser step provider.

Package chrome holds the production Chrome / Chromium binding used by the Tales browser provider.

Package driver defines the browser-driver abstraction used by the Tales browser provider.

Package exec implements the exec provider (step "exec"), which runs an external program directly (never through a shell) and exposes its exit code, stdout, stderr and duration for assertions and capture.

Package file implements the file provider (step "file"), which inspects a file produced earlier in a scenario — existence, size, hex digests, UTF-8 text and parsed JSON — and exposes them under the file.* namespace for assertions and capture.

Package load implements a Go-native HTTP load benchmark provider.

Package mail implements the "mail" provider: it injects an email message into an application under test over SMTP or LMTP.

Package mobile is the Tales mobile step provider.

Package apple groups the macOS/Xcode lifecycle helpers used by the mobile provider: simctl wrappers, xcodebuild driver launcher, and the high-level Lifecycle facade.

Package embeddeddriver orchestrates extraction, build, and caching of the embedded Apple XCUITest driver source so the Tales binary can run iOS tests without the repository being checked out next to it.

Package simctl wraps a small, curated subset of `xcrun simctl` commands behind a Runner-backed API so the rest of the mobile provider can drive iOS Simulator lifecycle (boot, install, launch, terminate, ...) without shelling out from multiple places.

Package xcodebuild starts and stops the XCUITest runner that ships the in-simulator HTTP driver.

Package driver exposes the transport-agnostic interface every mobile UI driver must implement.

Package tree models a normalized UI hierarchy returned by mobile drivers.

Package webhook implements the Tales `webhook` provider: a generic, in-memory HTTP receiver used to assert on inbound webhooks during e2e tests.

Package visual builds a renderable view-model of a SuiteResult tailored to the offline HTML visual report.