Repository navigation
vilsem-mcp 0.7.3 (evaluation patch)
Pre-releaseMCP 0.7.3 evaluation patch
Fixes editing and validation of existing Vilsem visuals saved by Desktop with a newer official 2.x container declaration. The entire payload must pass the bundled 2.7 field contract. The response explicitly warns that full validation against the declared schema was not performed. The original declaration, query, layout and manual formatting remain intact. Unknown fields, malformed payloads and non-Microsoft/other-major declarations are refused. No native objects are edited or reported. New commits still use the bundled schema.
- Full MCP suite: 311/311 passed against the actual public core 0.7.2 package.
- Core/renderer unchanged: core 0.7.2, renderer 4.42; private/public core suites each passed 1,357 tests and the complete app build passed.
- Evaluation prerelease; it does not replace stable 0.6 or certify native interactions, exports, accessibility or performance.
- Native gesture/export checks remain unverified because the supported automation helper cannot connect to its native pipe. The 5,000-point animated 60fps target remains failed; no points are removed and no animation is disabled to claim a pass.
- No new app installer is published in this patch. Existing tags/assets remain immutable.
Packaged candidate acceptance: both existing Desktop2.14-declared QA visuals passed real-data read/preview, reviewed dry-run, title edit and restore. Their query, layout, manual formatting and schema declaration were preserved. validate_visuals reports170/170 Vilsem visuals valid, including two explicit known-contract warnings; all15 native fixture files are unchanged and unreported. The21 model hashes remain unchanged. A legacy spec may gain its normal specVersion migration on save; this is not a container-schema retag.
SHA256 vilsem-mcp-0.7.3.tgz: 3bb36a77b9b3fd821bc16617c57eaa553157f888c0bb6cf2d121f68efbb360aa
Public distribution verification: normal installs from the actual v0.7.3 release URL and documented Git tag both pass with audit0,19tools/one prompt, viewport-spec validation/resources, genuine core0.7.2 and no app-path/development link/overrides. The public-URL installation connects to Desktop62071 and validates170/170 custom visuals with the two explicit compatibility warnings. Downloaded archive SHA256 matches the tested candidate. Final owned-report clean reload accepted renderer4.42;21model hashes remain unchanged. Native physical acceptance and the failed frame-rate target remain open.