[LeiterConsulting]

An existing deployment can pass verification while a repaired local candidate still lacks native acceptance. Add observed trial evidence and refine the field-trial guidance to keep those versions distinct, inspect verifier side effects, preserve private evidence and report platform/scanner limits.

The controlled application trial reproduced and repaired unknown-health briefings and a Windows symlink fixture assumption. Only reusable observations, aggregate results and public correction provenance appear here. Connection details, authentication, screenshots and raw receipts remain private. This does not establish independent cross-IDE adoption or candidate deployment acceptance.

Validation:

• Framework validation passed: preview 5, 10 modules and 309 local links.
• Framework suite: 114 discovered, 112 passed and two explicit Windows symlink skips. git diff --check passed.
• Hosted push and PR CI passed on this head: all 114 tests passed without skips in each Windows/Linux Python 3.10/3.13 job. Runs: PR and push.
• Application: 11 model tests, 15 backend/package tests on Linux and four repaired-build browser workflows passed. Windows has one explicit application symlink skip; both dependency audits report zero advisories.
• Existing deployments passed 36 baseline service/browser checks. Four deliberately invalid closure claims were rejected by the offline helper; the fresh candidate record remains valid/pending on native acceptance.

Two documentation files only; no entry, adapter, helper, catalog or framework-version change.