Qualify native rollout and preserve operator state during upgrades

[LeiterConsulting]

An upgrade rewrote operator-owned files, and a fresh browser received an older frontend after an earlier candidate identity check had passed. Add delivery guidance for protected state restoration and fresh-client asset identity, and update the existing controlled trial with completed post-merge native acceptance.

The follow-up deployed the reviewed correction to both supported lab versions, restored operator file bytes/permissions, resolved stale served assets with the project's supported cache refresh and verified preserved settings/startup state. Raw authentication, connections, backups, receipts and screenshots remain private. The public record contains reusable observations and aggregate results only.

Validation:

• Native qualification: 36 actual service/browser workflow checks passed; 12 additional briefing cases passed with browser-only synthetic responses and no server fixture writes. Eighteen scoped state/identity checks passed.
• Fresh merged application source: 11 model tests, all 15 backend/package tests on Linux and four local browser workflows passed. Windows has one explicit symlink skip. Both dependency audits reported zero advisories; rebuilt installer matches deployed artifact bytes.
• Old raw source manifest was rejected after Git line-ending normalization. Fresh current manifest and actual deployment/live evidence now validate the bounded record as complete, ready to close, with no unresolved gates. Historical results remain separate.
• Framework validation: preview 5, ten modules, 310 local links. Local suite: 114 discovered, 112 passed, two explicit Windows symlink skips. git diff --check passed.
• Hosted checks on this head passed all 114 tests without skips in each Windows/Linux Python 3.10/3.13 job, for both PR and push runs.

No entry, adapter, helper, catalog or version change. No cloud certification, native reader-role, real model inference, customer acceptance or independent cross-IDE claim.