Heimdallv1.0.0

Engineering teams author a Heimdall JSON plan with p0 read-only cases that load key routes and assert visible content plus noConsoleErrors. The plan runs on every pull request via cdp, and the non-zero exit on any failure blocks the merge. The honest blocked/skipped semantics prevent green builds from masking untested paths.

A platform team uses the container driver to run tests that create, delete, and reset production-like resources without touching shared environments. Docker isolation keeps Linux Chrome fidelity consistent across developer machines and CI. Risk-gated destructive cases ensure side effects are inspected before execution.

For an insurance portal, Heimdall plans use the extension driver to hand off to a human-controlled logged-in browser, reporting cases as blocked when the agent cannot self-drive. This produces a verifiable audit trail that separates executed assertions from handoffs. Compliance reviewers can distinguish blocked cases from passes.

Backend teams write Heimdall plans that exercise REST APIs through cdp, passing tokens via ${env.API_TOKEN} so credentials never appear in plans or reports. Cases assert status codes, response shapes, and absence of console errors for web-adjacent endpoints. The report.json and HAR files become release evidence.

An AI agent is pointed at a staging web app and asked to verify critical user journeys. The agent authors a Heimdall plan with explicit oracles, runs it with --concurrency 4 and --filter smoke, then reports blocked and skipped cases honestly to its operator. This avoids the common failure mode of treating unexecuted steps as success.

The core Heimdall CLI is free and installed from the public GitHub repo, maximizing adoption among developers and agents. A paid hosted service runs plans on managed Chrome/container fleets, stores reports and HARs, and provides dashboards and alerting. This mirrors the Playwright/Cypress open-core model.

Teams in regulated industries pay for features that make Heimdall reports audit-ready: immutable evidence storage, role-based access, signed run attestations, and retention policies. The honest blocked/skipped semantics become a compliance differentiator rather than a developer convenience.

A managed offering where Heimdall-powered agents continuously test a customer's live web app and API, delivering reviewed reports and blocked-case handoffs. Customers subscribe to ongoing verification instead of building an in-house QA automation stack. Pricing scales with plan volume and target environments.