Add Confirmation Before Dev Tool Removal and Modification [AARD-2033]

[ryanzhangofficial]

Task

Add a confirmation dialog when removing a Dev Tools–placed scoring zone, allowing the user to either remove it temporarily (current behavior) or permanently by also deleting it from the Dev Tools cache.

Jira Ticket

Symptom

Currently if you remove a protected zone or scoring zone from the configure field panel that is placed by the dev tool it will remove it until the next refresh. Only the dev tool is able to cache scoring zone placement.

Solution

Popup a confirmation window when we remove a scoring zone that was placed by dev tools, and give us the option of removing it from dev tools as well (saving to cache).

Verification

• Tested temporary removal + refresh
• Tested permanent removal + refresh

---

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.

[rutmanz]

I think it would be better to say that the zones were defined in the field file/asset file/mirabuf file and avoid all reference to the developer tools. I think that, in theory, the developer tools are used by us to add this information to the cached files that people download, and so we shouldn't expect that they've used them / know they're there.

Also, this doesn't handle modifying the zones

[rutmanz]

should probably be renamed if this is being generalized

[rutmanz]

otherwise lgtm

[AlexD717]

Why are we only adding this confirmation for scoring zones?

Also Biome test fail

[ryanzhangofficial]

Why are we only adding this confirmation for scoring zones?

Also Biome test fail

As noted in comments in code, protected zones are not supported yet.

[AlexD717]

Why are we only adding this confirmation for scoring zones?

As noted in comments in code, protected zones are not supported yet.

Yeah, I can see that, I am just wondering why we are only adding this for scoring zones. Are we planning to add this for protected zones later on? From a user perspective it feels weird if they are only getting the popup for scoring zones, and nothing else.

[ryanzhangofficial]

Why are we only adding this confirmation for scoring zones?

As noted in comments in code, protected zones are not supported yet.

Yeah, I can see that, I am just wondering why we are only adding this for scoring zones. Are we planning to add this for protected zones later on? From a user perspective it feels weird if they are only getting the popup for scoring zones, and nothing else.

Yes that's the plan.

I think the order of merging should be this PR -> Zach's protected zone pr -> protected zone removal and modification

[AlexD717]

Is it also intentional that you have to go into developer tools and press save to actually have scoring zones persist in cache? Currently spawning in a scoring zone and then refreshing doesn't have it persist. If this is the case, I am personally not a fan of this, and think that they should auto cache.

Screen.Recording.2025-08-19.at.9.29.14.AM.mov

[rutmanz]

I agree with @AlexD717, but this appears to be the current behavior on dev as well

[ryanzhangofficial]

I agree with @AlexD717, but this appears to be the current behavior on dev as well

Yes I agree too, currently fixing this issue. It isn't a problem on prod so must've been an issue that came up throughout the summer.

[ryanzhangofficial]

Would appreciate thoughts on this approach. I thought it would be appropriate because of the rewording of the modals, but at the same time it makes devtools seem less useful.