chartremotely 0.3.1__tar.gz → 0.3.2__tar.gz

{chartremotely-0.3.1 → chartremotely-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: chartremotely
-Version: 0.3.1
+Version: 0.3.2
 Summary: Remote control of desktop charting applications on macOS
 Author: Lonnie VanZandt
 License: 
@@ -305,6 +305,7 @@ chartremotely serve                         run the local listener
 chartremotely pair                          adopt this display to an operator
 chartremotely relay                         hold a connection open for the operator
 chartremotely doctor                        check everything the agent needs
+chartremotely token                         print the local listener's access token
 ```
 
 `serve` and `relay` are two different transports and most setups want both.
@@ -421,19 +422,23 @@ curl -fsSL https://chartremotely.tollbooth-dpyc.com/install.sh | sh
 
 That installs [uv](https://docs.astral.sh/uv/) if it is missing, installs this
 agent from PyPI (`uv tool install --python 3.12 'chartremotely[macos,setup]'`),
-and runs `chartremotely setup`, which:
-
-1. proves who owns the display — your existing npub by answering a Nostr DM,
-   a key already saved on this Mac, or a new key it makes and saves for you
-   in the Keychain and, through Safari, in iCloud Passwords;
-2. pairs this Mac with that identity, with no code to copy;
-3. gives the Mac its tailnet address with `tailscale serve`;
-4. installs the listener and the relay as launchd agents;
-5. asks macOS for Accessibility and Screen Recording for the Python that runs them;
-6. fetches the Whisper speech model (about 1.6 GB, once) and your display names;
-7. makes this Mac's Shortcut, "ChartRemotely" (talk, or type when it asks),
-   opens it for import, and removes a "ChartRemotely Ask" an older setup left
-   in your library.
+and runs `chartremotely setup`. Setup first says what is installing — version,
+where it came from, the Python it runs on — lists its six steps, and asks
+before changing anything:
+
+1. **Identity** — proves who owns the display (your existing npub by answering
+   a Nostr DM, a key already saved on this Mac, or a new key it makes and saves
+   for you in the Keychain and, through Safari, in iCloud Passwords), then
+   pairs this Mac with that identity, with no code to copy;
+2. **Tailscale** — gives the Mac its tailnet address with `tailscale serve`;
+3. **Services** — installs the listener and the relay as launchd agents;
+4. **Permissions** — asks macOS for Accessibility and Screen Recording for the
+   Python that runs them;
+5. **Hearing** — fetches the Whisper speech model (about 1.6 GB, once) and
+   your display names;
+6. **Shortcut** — makes this Mac's Shortcut, "ChartRemotely" (talk, or type
+   when it asks), opens it for import, and removes a "ChartRemotely Ask" an
+   older setup left in your library.
 
 Run it again at any time: finished steps are skipped. `chartremotely doctor`
 reports anything still missing.
@@ -473,7 +478,11 @@ switch to a grid - discovery follows, and takes about a second.
 
 ## Status
 
-Early. The thinkorswim adapter works; the interfaces are still moving.
+In service. Releases are published to PyPI and installed with the one-line
+installer above; a paired Mac takes commands by voice, from the web app at
+<https://chartremotely.tollbooth-dpyc.com>, and from any MCP client through the
+operator ([ChartRemotely-mcp](https://github.com/lonniev/ChartRemotely-mcp)).
+thinkorswim is the one charting application it drives today.
 
 ## License
 

{chartremotely-0.3.1 → chartremotely-0.3.2}/README.md

@@ -78,6 +78,7 @@ chartremotely serve                         run the local listener
 chartremotely pair                          adopt this display to an operator
 chartremotely relay                         hold a connection open for the operator
 chartremotely doctor                        check everything the agent needs
+chartremotely token                         print the local listener's access token
 ```
 
 `serve` and `relay` are two different transports and most setups want both.
@@ -194,19 +195,23 @@ curl -fsSL https://chartremotely.tollbooth-dpyc.com/install.sh | sh
 
 That installs [uv](https://docs.astral.sh/uv/) if it is missing, installs this
 agent from PyPI (`uv tool install --python 3.12 'chartremotely[macos,setup]'`),
-and runs `chartremotely setup`, which:
-
-1. proves who owns the display — your existing npub by answering a Nostr DM,
-   a key already saved on this Mac, or a new key it makes and saves for you
-   in the Keychain and, through Safari, in iCloud Passwords;
-2. pairs this Mac with that identity, with no code to copy;
-3. gives the Mac its tailnet address with `tailscale serve`;
-4. installs the listener and the relay as launchd agents;
-5. asks macOS for Accessibility and Screen Recording for the Python that runs them;
-6. fetches the Whisper speech model (about 1.6 GB, once) and your display names;
-7. makes this Mac's Shortcut, "ChartRemotely" (talk, or type when it asks),
-   opens it for import, and removes a "ChartRemotely Ask" an older setup left
-   in your library.
+and runs `chartremotely setup`. Setup first says what is installing — version,
+where it came from, the Python it runs on — lists its six steps, and asks
+before changing anything:
+
+1. **Identity** — proves who owns the display (your existing npub by answering
+   a Nostr DM, a key already saved on this Mac, or a new key it makes and saves
+   for you in the Keychain and, through Safari, in iCloud Passwords), then
+   pairs this Mac with that identity, with no code to copy;
+2. **Tailscale** — gives the Mac its tailnet address with `tailscale serve`;
+3. **Services** — installs the listener and the relay as launchd agents;
+4. **Permissions** — asks macOS for Accessibility and Screen Recording for the
+   Python that runs them;
+5. **Hearing** — fetches the Whisper speech model (about 1.6 GB, once) and
+   your display names;
+6. **Shortcut** — makes this Mac's Shortcut, "ChartRemotely" (talk, or type
+   when it asks), opens it for import, and removes a "ChartRemotely Ask" an
+   older setup left in your library.
 
 Run it again at any time: finished steps are skipped. `chartremotely doctor`
 reports anything still missing.
@@ -246,7 +251,11 @@ switch to a grid - discovery follows, and takes about a second.
 
 ## Status
 
-Early. The thinkorswim adapter works; the interfaces are still moving.
+In service. Releases are published to PyPI and installed with the one-line
+installer above; a paired Mac takes commands by voice, from the web app at
+<https://chartremotely.tollbooth-dpyc.com>, and from any MCP client through the
+operator ([ChartRemotely-mcp](https://github.com/lonniev/ChartRemotely-mcp)).
+thinkorswim is the one charting application it drives today.
 
 ## License
 

{chartremotely-0.3.1 → chartremotely-0.3.2}/chartremotely/mcpclient.py

@@ -60,8 +60,11 @@ class Client:
         self._ids = itertools.count(1)
 
     def _send(self, message: dict) -> dict:
+        # The operator refuses a request with no bearer. The agent proves
+        # itself in its arguments, so at the connection it is anonymous.
         headers = {"Content-Type": "application/json",
-                   "Accept": "application/json, text/event-stream"}
+                   "Accept": "application/json, text/event-stream",
+                   "Authorization": "Bearer anonymous"}
         if self.session:
             headers["mcp-session-id"] = self.session
         request = urllib.request.Request(

{chartremotely-0.3.1 → chartremotely-0.3.2}/chartremotely.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: chartremotely
-Version: 0.3.1
+Version: 0.3.2
 Summary: Remote control of desktop charting applications on macOS
 Author: Lonnie VanZandt
 License: 
@@ -305,6 +305,7 @@ chartremotely serve                         run the local listener
 chartremotely pair                          adopt this display to an operator
 chartremotely relay                         hold a connection open for the operator
 chartremotely doctor                        check everything the agent needs
+chartremotely token                         print the local listener's access token
 ```
 
 `serve` and `relay` are two different transports and most setups want both.
@@ -421,19 +422,23 @@ curl -fsSL https://chartremotely.tollbooth-dpyc.com/install.sh | sh
 
 That installs [uv](https://docs.astral.sh/uv/) if it is missing, installs this
 agent from PyPI (`uv tool install --python 3.12 'chartremotely[macos,setup]'`),
-and runs `chartremotely setup`, which:
-
-1. proves who owns the display — your existing npub by answering a Nostr DM,
-   a key already saved on this Mac, or a new key it makes and saves for you
-   in the Keychain and, through Safari, in iCloud Passwords;
-2. pairs this Mac with that identity, with no code to copy;
-3. gives the Mac its tailnet address with `tailscale serve`;
-4. installs the listener and the relay as launchd agents;
-5. asks macOS for Accessibility and Screen Recording for the Python that runs them;
-6. fetches the Whisper speech model (about 1.6 GB, once) and your display names;
-7. makes this Mac's Shortcut, "ChartRemotely" (talk, or type when it asks),
-   opens it for import, and removes a "ChartRemotely Ask" an older setup left
-   in your library.
+and runs `chartremotely setup`. Setup first says what is installing — version,
+where it came from, the Python it runs on — lists its six steps, and asks
+before changing anything:
+
+1. **Identity** — proves who owns the display (your existing npub by answering
+   a Nostr DM, a key already saved on this Mac, or a new key it makes and saves
+   for you in the Keychain and, through Safari, in iCloud Passwords), then
+   pairs this Mac with that identity, with no code to copy;
+2. **Tailscale** — gives the Mac its tailnet address with `tailscale serve`;
+3. **Services** — installs the listener and the relay as launchd agents;
+4. **Permissions** — asks macOS for Accessibility and Screen Recording for the
+   Python that runs them;
+5. **Hearing** — fetches the Whisper speech model (about 1.6 GB, once) and
+   your display names;
+6. **Shortcut** — makes this Mac's Shortcut, "ChartRemotely" (talk, or type
+   when it asks), opens it for import, and removes a "ChartRemotely Ask" an
+   older setup left in your library.
 
 Run it again at any time: finished steps are skipped. `chartremotely doctor`
 reports anything still missing.
@@ -473,7 +478,11 @@ switch to a grid - discovery follows, and takes about a second.
 
 ## Status
 
-Early. The thinkorswim adapter works; the interfaces are still moving.
+In service. Releases are published to PyPI and installed with the one-line
+installer above; a paired Mac takes commands by voice, from the web app at
+<https://chartremotely.tollbooth-dpyc.com>, and from any MCP client through the
+operator ([ChartRemotely-mcp](https://github.com/lonniev/ChartRemotely-mcp)).
+thinkorswim is the one charting application it drives today.
 
 ## License
 

{chartremotely-0.3.1 → chartremotely-0.3.2}/chartremotely.egg-info/SOURCES.txt

@@ -44,6 +44,7 @@ chartremotely.egg-info/entry_points.txt
 chartremotely.egg-info/requires.txt
 chartremotely.egg-info/top_level.txt
 chartremotely/assets/shortcut.plist
+tests/test_changelog.py
 tests/test_hearing.py
 tests/test_patron.py
 tests/test_popups.py

{chartremotely-0.3.1 → chartremotely-0.3.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "chartremotely"
-version = "0.3.1"
+version = "0.3.2"
 description = "Remote control of desktop charting applications on macOS"
 readme = "README.md"
 requires-python = ">=3.12"

chartremotely-0.3.2/tests/test_changelog.py

@@ -0,0 +1,85 @@
+"""The changelog must not be the reason two independent changes conflict.
+
+`CHANGELOG.md` was the single most conflict-prone file in the fleet, and not
+through carelessness: every pull request appended to the same
+`### Added` / `### Fixed` anchors of the same `## [Unreleased]` section, so any
+two concurrent PRs collided there even when their code touched nothing in
+common. Six did in `beesknees-mcp` in one day.
+
+If A and B are independent, it must not matter whether they land A-then-B or
+B-then-A. These tests hold that as a property rather than as an intention.
+"""
+
+from __future__ import annotations
+
+import importlib.util
+import pathlib
+import re
+
+import pytest
+
+ROOT = pathlib.Path(__file__).resolve().parents[1]
+
+
+def _module():
+    spec = importlib.util.spec_from_file_location("changelog", ROOT / "scripts" / "changelog.py")
+    assert spec and spec.loader
+    mod = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(mod)
+    return mod
+
+
+cl = _module()
+
+
+def _write(d: pathlib.Path, name: str, body: str) -> None:
+    (d / name).write_text(body)
+
+
+def test_the_order_two_changes_land_in_does_not_reach_the_output(tmp_path) -> None:
+    """The property the whole change exists for.
+
+    Two independent entries, folded in both possible orders, must produce the
+    same section — otherwise the changelog still carries a fact about merge
+    order that nobody needs and everybody has to resolve.
+    """
+    first, second = tmp_path / "a", tmp_path / "b"
+    for d in (first, second):
+        d.mkdir()
+    _write(first, "fixed-alpha.md", "- Alpha was broken and is not.\n")
+    _write(first, "fixed-beta.md", "- Beta was broken and is not.\n")
+    # The same two, created in the opposite order.
+    _write(second, "fixed-beta.md", "- Beta was broken and is not.\n")
+    _write(second, "fixed-alpha.md", "- Alpha was broken and is not.\n")
+
+    a = cl.section("1.0.0", cl.read_fragments(first), "2026-01-01")
+    b = cl.section("1.0.0", cl.read_fragments(second), "2026-01-01")
+    assert a == b
+
+
+def test_kinds_are_grouped_in_keep_a_changelog_order(tmp_path) -> None:
+    _write(tmp_path, "fixed-one.md", "- A fix.\n")
+    _write(tmp_path, "added-two.md", "- An addition.\n")
+    _write(tmp_path, "notes-three.md", "- Some reasoning.\n")
+
+    out = cl.section("2.1.0", cl.read_fragments(tmp_path), "2026-01-01")
+    assert out.startswith("## [2.1.0] — 2026-01-01")
+    order = [m.group(1) for m in re.finditer(r"^### (\w+)", out, re.MULTILINE)]
+    assert order == ["Added", "Fixed", "Notes"], order
+    # Nothing empty is left standing.
+    assert "### Changed" not in out
+
+
+def test_a_misnamed_fragment_is_refused_rather_than_dropped(tmp_path) -> None:
+    """A changelog that quietly loses an entry is worse than one that refuses
+    to build — the entry is somebody's account of what they did to the money."""
+    _write(tmp_path, "fxied-typo.md", "- Something real.\n")
+    with pytest.raises(SystemExit, match="unknown kind"):
+        cl.read_fragments(tmp_path)
+
+
+def test_the_new_section_goes_above_the_ones_already_there(tmp_path) -> None:
+    existing = "# Changelog\n\nPreamble.\n\n## [0.9.0] — 2025-01-01\n\n### Fixed\n\n- Older.\n"
+    out = cl.fold(existing, "## [1.0.0] — 2026-01-01\n\n### Added\n\n- Newer.\n")
+    assert out.index("## [1.0.0]") < out.index("## [0.9.0]")
+    assert "Preamble." in out and "- Older." in out