@@ -92,6 +92,9 @@ Architecture & design intent: `docs/getting-started/architecture/` (overview, wr
 
 - Use type hints on all Python function signatures
 - Follow existing patterns in the module you are modifying
+- Do not put `pip install` commands in docstrings or code comments. Security scanners flag them as runtime
+  package installs, which fail in air-gapped or mirror-only environments. Name the extra instead
+  (e.g. "Requires the ``glide`` extra (``feast[glide]``).") and keep install commands in `docs/`.
 - PR titles must follow conventional commit conventions with a lowercase type and a capitalized subject after the colon: `feat: Add ...`, `fix: Correct ...`, `ci: Update ...`, `chore: Refresh ...`, `docs: Add ...`
 - Sign off commits with `git commit -s` (DCO requirement)
 - Uses `ruff` for Python linting and formatting; Go uses standard `gofmt`
 
@@ -89,7 +89,7 @@ class RedisOnlineStoreConfig(FeastConfigBaseModel):
 
     With ``glide``, the synchronous read paths (``online_read`` and the batched read
     behind ``get_online_features``) issue their HMGET commands as one non-atomic GLIDE
-    batch, so the fetch runs off the GIL. Requires ``pip install 'feast[glide]'``.
+    batch, so the fetch runs off the GIL. Requires the ``glide`` extra (``feast[glide]``).
     Writes and async reads always use redis-py. GLIDE has no Sentinel support, so
     ``client: glide`` cannot be combined with ``redis_type: redis_sentinel``."""
 
 
@@ -70,6 +70,9 @@ uv run bash -c "cd sdk/python && mypy feast/path/to/file.py"
 - Use type hints on all function signatures
 - Use `from __future__ import annotations` at the top of new files
 - Follow existing patterns in the module you are modifying
+- Do not put `pip install` commands in docstrings or code comments. Security scanners flag them as runtime
+  package installs, which fail in air-gapped or mirror-only environments. Name the extra instead
+  (e.g. "Requires the ``glide`` extra (``feast[glide]``).") and keep install commands in `docs/`.
 - PR titles must follow semantic conventions: `feat:`, `fix:`, `ci:`, `chore:`, `docs:`
 - Add a GitHub label to PRs (e.g. `kind/bug`, `kind/feature`, `kind/housekeeping`)
 - Sign off commits with `git commit -s` (DCO requirement)