fix: migrate to WYRE-AI org (npm scope, ghcr namespace, registry)

[asachs01]

Migrates off the old @wyre-technology org identity per the fleet-wave checklist (pilot: timezest-mcp v2.0.1):

• package.json name -> @wyre-ai/syncro-mcp; repo/bugs/homepage URLs -> WYRE-AI; lockfile regenerated
• release.yml: uses -> WYRE-AI/.github@07bc1921cbd01ad8a079fe8a3dd28180080870d5; image-name -> ghcr.io/wyre-ai/syncro-mcp; deploy job commented out (legacy-tenant infra gap)
• server.json + Dockerfile labels -> io.github.WYRE-AI/syncro-mcp (case-exact) + ghcr.io/wyre-ai/syncro-mcp
• README/CONTRIBUTING/CODE_OF_CONDUCT/manifest/CODEOWNERS/dependabot org refs -> WYRE-AI
• .npmrc: added @WYRE-AI scope (env-substituted token, no literals)

Deliberately NOT flipped (checklist item 5 — flip AFTER the SDK republishes; the reusable workflow's @wyre-technology read-compat covers reads meanwhile):

• dependency + imports of @wyre-technology/node-syncro — @wyre-ai/node-syncro is not yet published (404 on npm.pkg.github.com; absent from WYRE-AI org packages)
• mcp-assert.yml / add-to-project.yml uses: stay pinned to wyre-technology/.github (public) — WYRE-AI/.github does not host those reusables
• ISSUE_TEMPLATE links to the wyre-technology org project / msp-claude-plugins, which stayed in the old org

https://claude.ai/code/session_01CNe2zVAcVSnxKi7eo6sUR5

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[asachs01]

CI is blocked by an SDK-phase gap, not by this diff: npm ci 403s fetching @wyre-technology/node-syncro@1.0.5 (E403 permission_denied: read_package). Root cause: the old-org npm package is visibility=internal and lost its linked repo when node-syncro transferred, so a WYRE-AI GITHUB_TOKEN cannot read it — the reusable workflow's legacy-scope compat only covers PUBLIC old-org packages. @wyre-ai/node-syncro is not yet published (404). Any commit to this repo would hit the same failure (latent since transfer; no Release/assert run has executed on main post-transfer).

Unblock options (either works):

1. Publish @wyre-ai/node-syncro from WYRE-AI/node-syncro (SDK phase), then flip the dep/imports here to @wyre-ai/node-syncro and regenerate the lockfile, or
2. Flip wyre-technology/node-syncro package visibility internal -> public (UI-only; no API).

Leaving this PR open — do not merge until CI is green.

[asachs01]

Org-migration takeover status: the failing checks are NOT caused by this diff. Root cause: this repo's SDK dep @wyre-technology/node-syncro is an ORPHANED old-org package with INTERNAL visibility, so WYRE-AI CI's GITHUB_TOKEN 403s on npm ci (dependabot PRs on main fail identically — pre-existing). The @wyre-ai/node-syncro twin is published PRIVATE and same-org cross-repo GITHUB_TOKEN reads also 403 (proven on huntress-mcp). GitHub has no API to change package visibility (UI-only).

Unblock (one UI click, either works):

1. https://github.com/orgs/WYRE-AI/packages/npm/node-syncro/settings -> Change visibility -> Public, then flip this PR's dep to @wyre-ai/node-syncro; or
2. old org package settings for @wyre-technology/node-syncro -> internal -> public, and this PR merges as-is.

https://claude.ai/code/session_01CNe2zVAcVSnxKi7eo6sUR5

[github-actions]

🎉 This PR is included in version 1.4.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀