cyclr-migration

# Cyclr Migration Knowledge for analyzing Cyclr cycle JSON exports and converting them to the standard integration schema for Prismatic CNI migration. ## Cyclr Export Format Cyclr exports are single JSON files per cycle. Each file contains the complete cycle definition including steps, edges, variables, and connector metadata. **Top-level keys in export:** - `VersionedCycle` - Version metadata and publication status (Tags, Published) - `Steps[]` - Array of step definitions with connector info, field mappings, and parameters - `Edges[]` - Directed edges defining execution order (TailStep_Id → HeadStep_Id) - `Variables[]` - Cycle-level variables - `ExportedConnectors[]` - Encrypted connector data (not parseable — auth details come from Steps instead) - `Name` - Cycle display name - `Status` - Cycle status code - `CustomMethodReleases[]` - Custom API method definitions if any - `ShareFields[]` - Fields exposed to customer configuration - `CycleStepErrorAction` - Error handling strategy - `MaxRetriesOnError` - Retry configuration **Note:** `ExportedConnectors` contains encrypted data and cannot be used for migration. All connector and authentication details are extracted from the `AccountConnector` blocks within each step. ## Parser Use `prismatic-tools parse-export` to deterministically extract structured data from Cyclr JSON exports. The parser handles all JSON parsing, reference resolution, and topological sorting, then outputs JSON. See `references/cyclr-export-parsing...