EleSync v1.7.1

Fixed

• MCP Registry publishing restored. The registry validates ownership by
  requiring mcp-name: io.github.darknodebros/elesync inside the PyPI README
  of the exact version being published. That marker was dropped in the
  README rewrite (d440aa8), so every registry publish since silently failed
  server-side validation and the registry entry froze at 1.3.0. The marker is
  back (as an HTML comment, invisible on PyPI/GitHub), and
  tests/test_packaging.py now fails the build if it is ever removed again,
  alongside checks that pyproject, __init__, and server.json versions agree.
• Windows ConnectionAbortedError [WinError 10053] on rejected writes.
  The web dashboard's 401/403 auth gates responded before reading the request
  body; closing the connection with unread data triggers a TCP reset, which
  Windows clients surface as a connection abort instead of the status code.
  The gates now drain the unread body (capped at 1 MiB) before rejecting.
• Base CI job green again. The web-auth test suites hash passwords, but
  the extras-free CI job has no bcrypt - 22 tests errored on every run since
  the web-auth PRs landed. They now skip cleanly without bcrypt, following the
  same convention as the fastembed and mcp-SDK guards. The one test that
  specifically exercises the missing-bcrypt error message stays unguarded.

Added

• CI fails on version drift between pyproject.toml, server.json, and
  __init__.__version__ - the manifest shipped stale in two consecutive
  releases; now it cannot.