Verification and Limits

Verification and limits

A visible screen, fixture response, native run and installed upgrade answer different questions.

Evidence	Supports	Does not establish
Source/unit/integration tests	Tested contracts/state/boundaries	Every provider/editor/version
Scripted tutorial	Observed UI/service workflow	Model reasoning or autonomous production
Live engine/provider	Named operation/version/Project/host	All targets or authoring operations
Rendered desktop smoke	Observed controls/errors	Complete physical input/accessibility
Package/upgrade receipt	Recorded artifact/lifecycle step	Signing/uninstall/rollback unless tested

Public testing context

The 0.21.0 prerelease records hosted quality/package results, scoped editor operations, desktop checks and one local Windows 0.20.0-to-0.21.0 upgrade with retention. Executable/metadata are unsigned; testing versions are manual downloads outside stable automatic updates.

Full uninstall/rollback, broader provider/engine matrices and human acceptance remain separate. Configuring an account, installing a skill or detecting an editor is not execution evidence.

Choose the relevant record

Guides contain historical and cumulative evidence. Prefer the newest version-specific receipt for that version. Older passages can describe limits later addressed; do not generalize newer checks to all hosts or retrospectively certify old packages.

Start with status, adversarial review, editor acceptance and release notes. The development plan owns work-package status; design documents include intended work. This wiki changes no confirmed requirement or work-package decision.