BotV8 validation focuses on profile-backed Web API behavior and local evidence quality.
Public validation material stays at a product level. It describes coverage areas, report shape, and release review expectations without publishing private profiles, customer traffic, raw service responses, reusable test internals, or provider-specific workflows.
| Area | Public validation signal |
|---|---|
| Runtime state | environment creates, runs, reports, and closes cleanly |
| Profile loading | approved profile material is accepted by the matching runtime package |
| Web API behavior | browser-visible API families stay aligned with the selected profile family |
| Locale and timezone | runtime-visible values stay coherent with the selected context |
| Storage and cookies | environment-owned state stays scoped to the workflow |
| Network execution | approved requests run through BotV8-owned network and cookie state |
| Report quality | summaries use sanitized metadata and redact sensitive material |
| SDK compatibility | Python and Node examples use the supported SDK surface |
The public report shape is intentionally compact:
- runtime state summary
- cookie counts and lengths
- network entries with URL classes
- event timing summaries
- success and failure counts
See examples/audit-report/sample-report.json for a sanitized example.
A release package is ready for customer-side validation when:
- runtime package, SDK files, and approved profile material come from the same supported release line
- Python and Node examples parse cleanly in the target package
- a profile-backed environment can create, run one approved workflow, emit a sanitized report, and close cleanly
- the report includes runtime state, cookie summary, network summary, and event summary categories
- local evidence excludes profile paths, proxy credentials, cookies, raw service responses, customer traffic, and private package material
Reports used for QA or support should stay local unless they have been sanitized.
Public evidence should use aggregate or sample material only:
- sanitized report shape
- supported runtime area list
- SDK example command shape
- release package layout
- access and support route
Live customer evidence, private profiles, and provider-specific workflows stay outside this repository.