refactor(mcp): promote mcp from optional extra to core dependency (#53)

Aligns attune-gui with the sibling-package pattern: attune-help and
attune-author both treat `mcp>=0.9.0` as a core dep, not an optional
extra. With Phase 1 just landed (#50) the asymmetry would have created
ongoing friction — every "did you install [mcp]?" doc note, every CI
config carrying a magic `[dev,mcp]` install line, every user surprised
by ModuleNotFoundError on `attune-gui-mcp`.

Changes:
  - pyproject.toml — move `mcp>=0.9.0` from
    [project.optional-dependencies].mcp into the main `dependencies`
    list. Drop the now-empty `mcp` extra. The `mcp` SDK is a small
    pure-Python package; adding it to the base install isn't a meaningful
    weight increase.
  - .github/workflows/tests.yml — install line shrinks from `[dev,mcp]`
    back to `[dev]`. No more leaky abstraction as future extras land.
  - sidecar/attune_gui/mcp/__init__.py — docstring updated; no more
    "install via the mcp extra" language.
  - CHANGELOG.md — Phase 1 Unreleased entry rewritten to drop the
    optional-extra prose.

Compatibility note: PR #50 introduced the `[mcp]` extra hours ago.
0.7.1 (the latest PyPI release) doesn't have MCP at all, so no released
user is currently relying on `pip install 'attune-gui[mcp]'`. Anyone
who scripted that incantation in the meantime should drop the suffix.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: silversurfer562

.github/workflows/tests.yml

@@ -27,10 +27,10 @@ jobs:
           python-version: ${{ matrix.python-version }}
           cache: pip
 
-      - name: Install with dev + mcp extras
+      - name: Install with dev extras
         run: |
           python -m pip install --upgrade pip
-          python -m pip install -e ".[dev,mcp]"
+          python -m pip install -e ".[dev]"
 
       - name: Run ruff
         run: python -m ruff check sidecar/

CHANGELOG.md

@@ -25,11 +25,10 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   happy path plus validation errors.
 - **MCP server — Phase 1 scaffold.** New `attune-gui-mcp` console
   script boots a stdio MCP server (named `attune-gui`) with an
-  empty tool registry. SDK lives behind a new `mcp` optional
-  dependency (`pip install 'attune-gui[mcp]'`); importing
-  `attune_gui` without the extra still works. Mirrors the
-  `attune-help` / `attune-author` stdio pattern so one Claude
-  Code config block covers the family. See
+  empty tool registry. `mcp>=0.9.0` is a core dependency — matches
+  the `attune-help` / `attune-author` packaging so one Claude Code
+  config block covers the family with one consistent install
+  command. See
   [docs/specs/mcp-server-scope/](docs/specs/mcp-server-scope/).
 
 ## [0.7.1] — 2026-05-22

pyproject.toml

@@ -35,6 +35,7 @@ dependencies = [
     "jinja2>=3.1,<4.0",
     "python-frontmatter>=1.1,<2.0",
     "markdown>=3.5,<4.0",
+    "mcp>=0.9.0",
 ]
 
 [project.optional-dependencies]
@@ -47,7 +48,6 @@ dev = [
     "build>=1.0,<2.0",
     "twine>=5.0,<7.0",
 ]
-mcp = ["mcp>=0.9.0"]
 
 [project.scripts]
 attune-gui = "attune_gui.main:main"

sidecar/attune_gui/mcp/__init__.py

@@ -4,7 +4,7 @@
 living-docs) to MCP clients like Claude Code. See
 ``docs/specs/mcp-server-scope/`` for the scope decisions.
 
-The ``mcp`` SDK is an *optional* dependency — install via the
-``mcp`` extra (``pip install 'attune-gui[mcp]'``). Importing this
-package without the SDK is fine; importing :mod:`.server` is not.
+The ``mcp`` SDK is a core dependency — installing ``attune-gui`` is
+enough to get the ``attune-gui-mcp`` console script, matching the
+``attune-help`` and ``attune-author`` packaging pattern.
 """