feat(scripts): devc_remote_uri.py — Cursor URI construction for remote devcontainers (#153)

[gerchowl]

Description

Adds scripts/devc_remote_uri.py — a standalone Python module/CLI that builds the Cursor/VS Code nested authority URI for remote devcontainers. Part of #70. Opening Cursor/VS Code into a remote devcontainer requires constructing a vscode-remote:// URI with hex-encoded JSON specs; Python handles this cleanly with stdlib only.

Type of Change

• feat -- New feature
• fix -- Bug fix
• docs -- Documentation only
• chore -- Maintenance task (deps, config, etc.)
• refactor -- Code restructuring (no behavior change)
• test -- Adding or updating tests
• ci -- CI/CD pipeline changes
• build -- Build system or dependency changes
• revert -- Reverts a previous commit
• style -- Code style (formatting, whitespace)

Modifiers

• Breaking change (!) -- This change breaks backward compatibility

Changes Made

• scripts/devc_remote_uri.py (new): hex_encode(), build_uri(), CLI with argparse
• tests/test_devc_remote_uri.py (new): 11 pytest unit tests (hex_encode, build_uri, CLI, edge cases)
• CHANGELOG.md: Added entry under ## Unreleased

Changelog Entry

Added

• devc_remote_uri.py — Cursor URI construction for remote devcontainers (#153)
  • Standalone Python module with hex_encode() and build_uri() for vscode-remote URIs
  • CLI: devc_remote_uri.py <workspace_path> <ssh_host> <container_workspace> prints URI to stdout
  • Stdlib only (json, argparse); called by devc-remote.sh (sibling sub-issue)

Testing

• Tests pass locally (just test)
• Manual testing performed (describe below)

Manual Testing Details

N/A — uv run pytest tests/test_devc_remote_uri.py -v passes (11 tests). just lint passes.

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly (edit docs/templates/, then run just docs)
• I have updated CHANGELOG.md in the [Unreleased] section (and pasted the entry above)
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Additional Notes

Design and implementation plan posted on issue #153. Sub-issue of #70 (remote devcontainer orchestration).

Refs: #153