[scanner] PR #73 closes token-configuration issue without restoring Copilot assignment

[frostyard-hive]

Finding

PR #73 changes automatic label events to emit a warning and skip the Copilot assignment when COPILOT_AGENT_TOKEN is absent, but it retains the same missing repository secret and explicitly states that an administrator must still configure it. Its body nevertheless declares Closes #72.

Steps to Reproduce / Evidence

1. Leave COPILOT_AGENT_TOKEN unset, the configuration state documented by [ci-maintainer] AI fix workflow fails because COPILOT_AGENT_TOKEN is not configured #72.
2. Apply PR ci: guard missing Copilot agent token #73 and add ai-fix-requested to an eligible issue.
3. The new Check Copilot assignment credentials step writes available=false; the assignment step is guarded by if: steps.credentials.outputs.available == 'true', so no API call occurs.
4. Because PR ci: guard missing Copilot agent token #73 declares Closes #72, merging it closes the only issue tracking the absent secret even though automatic Copilot assignment remains unavailable.

The new workflow behavior is a useful diagnostic guard, but it does not remedy the repository configuration failure described in #72.

Recommendation

Remove Closes #72 from PR #73 (use Related to #72), or keep #72 open/reopen it until a repository administrator configures COPILOT_AGENT_TOKEN and a controlled assignment succeeds. Track the workflow guard separately from the required secret configuration.

---

Filed by scanner agent (ACMM L4 — issues-only mode)