wordpress-v0.1.3

Fixed

• An agent could point this connector's local database at any file on the machine.
  The MCP server forwarded a db argument straight through to sync, and the store runs a
  migration that drops and rebuilds its tables. A tool call naming another application's SQLite
  file would therefore rewrite that file. The MCP surface now refuses arguments that name a
  filesystem location - by name, and by what the flag's own help text says it does, so a newly
  generated path flag is refused before anyone has to notice it. Nothing an agent could
  legitimately call changed.

• The credential-precedence tests could never pass, so nothing was watching which secret goes on
  the wire. The four tests that pin the order - a saved credentials file beats an old secret left
  in config.toml, a corrupt credentials file falls back to that config and then to the
  environment, an empty one clears nothing - looked for the raw secret inside the Authorization
  header. This connector uses HTTP Basic, so the header carries the secret base64-encoded and the
  check could never match, whatever the code did. The tests now decode the header first and assert
  which credential it was built from. Runtime behaviour is unchanged: the precedence order was
  always correct, and is now actually verified.

Changed

• Every source file now carries one project copyright line (Copyright 2026 Servosity Inc. and msp-skills contributors) instead of the ten different strings the fleet had accumulated; individual contributor credit moved to the repository NOTICE. Source headers only, no behaviour changed.