Do not block lint / format on metaschema failures

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR removes the “metaschema failure blocks everything” behavior so that linting and format checking still run even when metaschema validation reports errors.

Changes:

• Removed the blockedByMetaschema flag from the extension↔webview protocol (PanelState).
• Updated the VS Code extension to stop short-circuiting on metaschema errors and instead run metaschema, lint, and format-check together.
• Removed UI logic that forced the Metaschema tab / disabled Lint & Format when metaschema failed.
• Simplified LintTab and FormatTab props by dropping the “blocked” state handling.
• Adjusted HealthBar behavior to no longer treat metaschema errors as a hard “N/A” health state.
• Added a VS Code integration test asserting lint diagnostics are still produced even when metaschema validation fails.

Technical Notes: Extension diagnostics now update both lint and metaschema results from a single refresh cycle, allowing lint/format feedback to remain available while metaschema issues are present.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[jviotti]

@Karan-Palan Shot it myself now, as I need to release it before tomorrow!

[Karan-Palan]

Looks good @jviotti

However:

Screencast.from.2026-01-28.23-32-51.mp4

Do I replace it with something like this or the format command output?:

[jviotti]

Ahh good catch. And that's not even a metaschema error though, it is failing to even locate the metaschema. Can you first of all open an issue for this? I believe the metaschema command and others will return a different exit code in this case?