[lucas-koontz]

User story

As an engineer, I want removing a Deploys: mindshub_stafftools#... line to turn the staff console off in my PR env, so that the console runs only while a PR selects it.

Why this matters

argocd app set only adds parameters. Removing the line left the console running until someone unset its parameters by hand.

What should happen

When the deploy sets no stafftools revision, the deploy step unsets tags.mindshub_stafftools and revisions.mindshub_stafftools on the parent. A mindshub_stafftools anchor or a Deploys: mindshub_stafftools#... line sets that revision, so the step reads the links the deploy already resolved rather than parsing the body a second time. It keeps every other parameter, and it does nothing when neither is set.

Test plan

• Removing the line turns the console off: the action's shell, from the anchor's parameters through the Deploys: link loop with GitHub stubbed, run against a fake argocd, unsets exactly those two parameters. Passed under bash 5.2, as on the runner.
• A selected console stays on: a stafftools anchor and each Deploys: form (#N, #staging, #main, with or without the org), resolved by the action's own link loop, skip the unset. Other repos' links and look-alike names don't select it. Passed.
• Other parameters stay: a parent with other parameters loses only the two staff console ones, and a parent with neither sees no unset call. Passed.
• The unset runs after the parent is read and before app set, and not before the parent exists. Passed.