s3k-zone-bring-up

Zone bring-up is managed by orchestrating disassembly analysis, feature dispatch, conflict-safe merging, build verification, and visual validation. You provide a zone abbreviation like HCZ or CNZ, and the workflow sequences the entire implementation process end to end.

Coordinating parallel work on shared engine files requires conflict-safe integration that resolves additive merge conflicts in a predictable order. This ensures features like parallax and animated tiles are dispatched and merged without overwriting shared engine modifications.

Palette cycling validation works by applying feature scope decisions that determine whether visual elements should be implemented, validated, or skipped. The process includes review gates and visual comparison checks to verify the animated palette matches the target zone's expected behavior.

You can skip review gates or request validate-only modes by passing specific flags when starting the zone bring-up. These options manage the workflow sequence by bypassing intermediate approvals or restricting the process to visual and build verification checks.

You need a structured analysis spec and a target zone abbreviation such as LBZ or CNZ. The workflow uses this specification to manage feature applicability, parallel dispatch, and merging across the selected zone.

Parallel changes cause conflicts when multiple features modify the same shared engine files simultaneously. Conflict-safe integration resolves these additive merge conflicts by enforcing a predictable merge order during the zone bring-up orchestration.