Release SAGE wrapper 2.6.0

[PsYcGoD]

What changed

• fixes Windows argument preservation and adds explicit Electron/desktop workspace support through --cwd and SAGE_WORKSPACE_CWD
• removes foreground proof-network calls from the coding path
• makes npm enforce a compatible PyPI core and publishes only the thin launcher/bridge artifact
• synchronizes all public version metadata at 2.6.0
• publishes PyPI first and npm second from the existing trusted-publisher workflow
• refreshes live proof metrics and the dashboard screenshot

Root causes

The npm and PyPI registries had drifted (2.5.9 vs 2.5.8), the npm launcher accepted any importable Python core, Windows commands were reparsed through cmd.exe, and desktop hosts had no explicit way to pass their project directory.

Validation

• clean committed worktree: 238 Python tests passed
• npm launcher: 4 tests passed; npm audit found 0 vulnerabilities
• npm dry-run: 16 wrapper/bridge files, about 5.9 KB
• Python wheel/sdist: twine check passed; wheel contains no GUI, TUI, dashboard, or Electron paths
• fresh virtual environment: PyPI wheel and npm-to-Python version handoff both reported sage 2.6.0
• Windows Electron-style cwd and quoted metacharacter regression tests passed

Release behavior

After merge, publish GitHub release v2.6.0. The release workflow uploads the Python core to PyPI, waits until 2.6.0 is visible, then publishes the npm launcher through OIDC.