From 23a1ae3f37bb983dc5dfd064919ff6cd323fb2c1 Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Mon, 5 Oct 2026 15:49:58 -0700
Subject: [PATCH] test(plugins): mark the imported admission_env fixture as an
 allowed F811

The rebased file trips the pre-push code-health F811 rule: pytest injects the
fixture imported from tests.pm by parameter name, which ruff reads as a
redefinition. Reviewed allowance on the line, same remedy the rule documents.
---
 tests/hermes_cli/test_plugin_dependency_consent.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/hermes_cli/test_plugin_dependency_consent.py b/tests/hermes_cli/test_plugin_dependency_consent.py
index 7d6db00901..7f62e9f393 100644
--- a/tests/hermes_cli/test_plugin_dependency_consent.py
+++ b/tests/hermes_cli/test_plugin_dependency_consent.py
@@ -96,7 +96,7 @@ def test_yes_deps_carries_consent_through_non_interactive_install(admission_env,
     assert 'dependency install skipped (non-interactive)' not in output
 
 
-def test_dashboard_install_publishes_a_plugin_the_config_already_selects(admission_env, monkeypatch):
+def test_dashboard_install_publishes_a_plugin_the_config_already_selects(admission_env, monkeypatch):  # health: allow F811 -- pytest injects the imported admission_env fixture by parameter name
     """The Desktop/dashboard Install click on a plugin memory.provider already names (a provider that
     left core, a synced config, a re-install after remove) publishes like any fresh install instead of
     the non-interactive 'Install declined' that a retry can never get past. A forced replacement of an