maintain-cross-platform

Cross-platform release validation is performed by running local checks that align version fields across plugin manifests, CI validators, and pre-push hooks for the 3-platform architecture. This ensures configuration consistency and release readiness before deployment.

Cross-platform configuration alignment synchronizes version fields and platform-specific rules across Claude Code, OpenCode, and Codex. It centralizes validation and pre-push enforcement to prevent configuration drift during AgentSys release preparation.

To synchronize version fields, run local validation checks that verify version alignment across plugin manifests, CI validators, and pre-push hooks. The process documents platform-specific rules in SKILL.md to maintain consistency across the 3-platform architecture.

Yes, pre-push hooks enforce cross-platform release consistency by validating configuration alignment across Claude Code, OpenCode, and Codex before code is pushed. This local mechanism prevents version mismatches in plugin manifests and CI validators.

Cross-platform release validation fails when version fields in plugin manifests, CI validators, or pre-push hooks are not aligned across Claude Code, OpenCode, and Codex. Running centralized local checks identifies and resolves these configuration mismatches.

The best way to maintain consistent tooling configurations is using a centralized local framework that validates and aligns configurations across Claude Code, OpenCode, and Codex. It enforces consistency through pre-push hooks and documents platform-specific rules in SKILL.md.