Record the Python project config VS Code wrote for MECHSPECSHEET

Side-effect of configuring a Python environment while building the mech spec
tooling. Harmless to keep: the scripts are standard-library only and need no
venv, so this just stops VS Code re-prompting.

Worth knowing that this same file sets files.eol to CRLF workspace-wide, which
is right for the game content but also applies to newly created files -- it is
why the MECHSPECSHEET scripts were born with CRLF shebangs and had to be
normalised to LF before they would execute directly.

Co-authored-by: Claude Opus 5 (Anthropic) <noreply@anthropic.com>
Co-authored-by: GitHub Copilot <copilot@github.com>

.vscode/settings.json

@@ -9,5 +9,12 @@
 
     // Preserve the original Windows CRLF line endings (Git's * -text in
     // .gitattributes also prevents conversion, but this keeps VS Code consistent).
-    "files.eol": "\r\n"
+    "files.eol": "\r\n",
+    "python-envs.pythonProjects": [
+        {
+            "path": ".",
+            "envManager": "ms-python.python:venv",
+            "packageManager": "ms-python.python:pip"
+        }
+    ]
 }