perps-core-sync

To sync a controller from mobile to a core monorepo, run an automated 13-step pipeline that handles change detection, file copying, install, lint, format, build, artifact verification, tests, changelog updates, and sync-state tracking.

Propagating perps controller changes after a PR merge is best handled by an automated pipeline that detects updates, validates builds, updates changelogs, and writes sync state to track progress across repositories.

Yes, the cross-repo sync pipeline enforces automated validation by running lint, format, build, artifact verification, and tests, while providing failure resolution and post-sync commit guidance to ensure repository stability.

You need to run a 13-step sync pipeline after perps controller changes land in the mobile repository or when related PRs merge to the core monorepo to propagate and validate those updates.

Yes, you can automate changelog updates and write sync-state tracking during cross-repo synchronization as part of a deterministic pipeline that propagates controller changes from mobile to core.

Pre-flight checks are required before syncing a perps controller to a core monorepo to detect changes and verify environment readiness, ensuring the source and target repositories are prepared for the automated validation pipeline.