0.3.0-alpha.1 Runtime Adapter Migration

Affected scope

• Critical runtime dependencies now use one exact version family.
• Session internals use the versioned repository layout while retaining the stable public session.dir/<id>.jsonl path returned by CLI and SDK callers.
• The static Provider catalog contains new entries, but those entries remain unverified.
• coremind doctor adds a Runtime compatibility check.

Application users

No coremind.yaml change is required. After upgrade, run coremind doctor and coremind check --profile strict. Existing Session files are not deleted. A legacy-only file stops with an explicit migration error instead of being overwritten. Backup-backed, idempotent migration belongs to the durable Session batch.

SDK users

Use inspectRuntimeCompatibility() and CoreMind public types instead of depending directly on low-level model, message, or tool types. Existing Config, RunOutcome, permission, and Checkpoint semantics remain unchanged.

Rollback

Restore the pre-upgrade source and lockfile, then reinstall dependencies. Roll back the complete critical family, never a mixed subset. Keep legacy Session files until migration has completed successfully.