Ontology as code workflows generate validate migrate

[anand-testcompare]

Why This Exists

Users need reliable Ontology-as-Code workflows in the plugin: generate, validate, and migrate.

Desired Outcome

A practical OAC toolset that helps users move faster while reducing upload-time failures.

Scope

In scope:

• OAC generation/edit support.
• OAC validation beyond TypeScript type checks (relationship/reference sanity).
• Migration from exported ontology JSON to OAC TypeScript with clear fallback notes for unsupported fields.
• Offline-first validation with optional online checks when configured.

Out of scope:

• Guaranteeing parity with every stack-specific server-side validation path in v1.

Success Criteria

• Users can generate or update OAC artifacts through plugin workflows.
• Validation catches common structural issues before upload.
• Migration handles common exported JSON shapes and flags non-representable fields clearly.
• Optional online checks are additive and do not block offline workflows.

High-Level Plan

1. Define user-facing commands/tools for generate, validate, migrate.
2. Implement offline validation path as baseline.
3. Add optional online checks behind explicit config/env.
4. Add migration path with clear TODO fallbacks for edge cases.