Store Protected Zones in Devtools [AARD-2064]

[rutmanz]

Task

AARD-2064

Symptom

Currently protected zones, which are a field specific property, aren't stored in the mirabuf file via developer tools and have to be configured by each user

Solution

Added protected zones to the developer tools menu to allow them to be persisted into the mirabuf data

Verification

1. bun run assetpack
2. Open synthesis, clear your preferences, and import FRC Field 2023_v7.mira
3. Observe that scoring zones and protected zones are already configured
4. Drive around in match mode to confirm that they actually work properly

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.

[AlexD717]

lgtm

[azaleacolburn]

I'm a bit confused by some of the things you're doing, both with how they relate to this PR and why we would want to do them in general.

[rutmanz]

The answer to both of those comments is that they are to allow you to access helpful information from the browser devtools, which famously cannot import World or THREE.Vector3. The reason it's part of this PR is that it can be quite useful when trying to get positioning information when configuring predefined zones (I found myself wanting it when defining the 2023 field zones).

synthesis/fission/src/systems/World.ts

Lines 90 to 92 in d9474b2

	if (import.meta.env.DEV) {
	window.World = World
	}

[BrandonPacewic]

This pull request is 3rd in que.