[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"]