v0.7: one-click install — pyproject, console scripts, user units, hermes wiring

A clone + ./install.sh + ./launch-brave.sh + sign in once. Nothing else.

pyproject.toml declares the one real dependency (websockets) and maps the
repo-root-is-the-package layout, which retires the PYTHONPATH=<parent> line
every unit used to carry.

cli.py backs three console scripts. They exist because `python3 -m socialmag`
run from INSIDE a clone dies at `import asyncio`: the repo root is the package
dir, so it ships selectors.py and queue.py, and python puts the current
directory first on sys.path. `cd socialmag` is the first thing anyone does
after a clone, so the documented workaround failed at exactly the moment it
would be tried. A generated bin/ script never puts cwd on sys.path.

The same trap bit `python3 -m venv` inside install.sh — the installer was
broken by the thing it exists to fix. Every python3 call now runs from /.

deploy/user/*.in replaces root system units with systemd --user templates:
no User=, WantedBy=default.target, venv paths, @REPO@/@VENV@/@CDP_ENDPOINT@
substituted at install time. deploy/home/ is untouched and still live here.

launch-brave.sh carries --disable-background-timer-throttling. That is
load-bearing, not tidiness: five of six platforms are read in a hidden tab, and
a throttled background tab stops running the timers those pages use to fetch
their own data — the reads come back empty with no error.

install.sh checks the mcp package in hermes's own interpreter and refuses to
continue without it. Hermes treats mcp as optional and silently no-ops the
whole subsystem when it is missing, so a server that never loaded looks exactly
like one that loaded and did nothing.

It will not merge into an existing mcp_servers: key — it backs up config.yaml
and appends only when the key is absent, otherwise it prints the block. Blind
YAML merging is how someone's other servers disappear.

Verified end-to-end in a sandbox with a fake HOME and stubbed systemctl:
real MCP initialize handshake from inside the repo dir returns all 7 tools;
hermes's own yaml parser re-reads the written config with every pre-existing
key intact; a second run leaves the mcp_servers key count at 1; launch-brave.sh
exits 1 against a busy port; no unsubstituted @PLACEHOLDER@ in any rendered unit.

Not fixed, pre-existing: server.py reports SERVER_VERSION 0.1.0 while the repo
is at v0.7. The handshake shows 0.1.0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

pyproject.toml

@@ -0,0 +1,34 @@
+[build-system]
+requires = ["setuptools>=64"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "socialmag"
+version = "0.6.0"
+description = "MCP server that posts, reads, and replies across 6 platforms by driving an already-logged-in Brave over CDP"
+requires-python = ">=3.10"
+dependencies = ["websockets>=12"]
+
+[project.urls]
+Repository = "https://github.com/juxtapo9090/socialmag"
+
+# Console scripts, not `-m`. See cli.py for why: `-m socialmag` run from inside
+# the repo directory dies at `import asyncio`, because the repo root is the
+# package dir and ships `selectors.py`/`queue.py`. A generated bin/ script never
+# puts the current directory on sys.path.
+[project.scripts]
+socialmag = "socialmag.cli:serve"
+socialmag-refresh = "socialmag.cli:refresh"
+socialmag-openbridge = "socialmag.cli:openbridge"
+
+# The repo root IS the package dir — `socialmag/__init__.py` sits beside this
+# file. That is why every unit used to carry PYTHONPATH=<parent>: the import
+# name only resolved from one directory up. The mapping below tells setuptools
+# the same thing once, so an installed package imports from anywhere and the
+# PYTHONPATH line disappears from the units.
+[tool.setuptools]
+package-dir = { "socialmag" = "." }
+packages = ["socialmag", "socialmag.platforms"]
+
+[tool.setuptools.package-data]
+socialmag = ["dashboard.html", "dashboard.json"]