chore(140): repoint github URLs at pipefy/ai-toolkit

[gbrlcustodio]

Summary

Repoint every github.com / raw.githubusercontent.com owner-path reference from gbrlcustodio/pipefy-mcp-server to pipefy/ai-toolkit, ahead of the repo rename and org transfer tracked in #140. Also drops the "community-maintained / not an official Pipefy product" disclaimer from the README, since the repo moves under the Pipefy org.

Do not merge before the transfer. Every pipefy/ai-toolkit URL is dead until the org and repo exist. Merging early breaks install.sh, the README CI badge, and the bootstrap curl. Sequence: approve now, transfer + re-add secrets / branch protection / webhooks, then merge in the same window.

Scope

URL paths only. Files touched: install.sh (the REPO= constant), README.md (badge, release link, install examples, issues link, disclaimer removal), packages/mcp/README.md, packages/cli/README.md, commands/install.md (bootstrap curl), docs/MIGRATION.md, skills/README.md, RELEASE.md, packages/mcp/src/pipefy_mcp/_docs.py, .claude-plugin/plugin.json (homepage/repository), .mcp.json.

Deliberately left alone

• Distribution names (pipefy-mcp-server, pipefy-cli, pipefy-sdk, pipefy-auth, pipefy-infra). These are consumer-facing PyPI/install identifiers; renaming them breaks every install script. Tracked as an open question on Rename to ai-toolkit and transfer to the Pipefy GitHub org #140, out of scope here.
• CHANGELOG.md (2 entries). Historical release records; not rewritten.
• README # pipefy-labs umbrella heading. Rename to ai-toolkit and transfer to the Pipefy GitHub org #140 lists this as an undecided naming question (keep / rename / drop), so it stays until that's settled.

Interaction with #260

#260 (wheel-URL install) is unmerged. It rewrites .mcp.json to release-wheel URLs and adds a release.yml step that regenerates those URLs from GITHUB_REPOSITORY on every release. If #260 lands first, .mcp.json self-heals on the next release and this PR's .mcp.json hunk becomes a moot conflict to drop at rebase. This PR is correct against current main, where .mcp.json is still the @latest git form and does not self-heal.

Not covered (needs a runbook, not a PR)

The operational transfer mechanics: re-add Actions secrets (release signing / future PyPI OIDC), re-apply branch protection, re-verify webhooks. See #140's "Transfer mechanics" checklist.

Verification

• grep -rn "gbrlcustodio/pipefy-mcp-server" returns only the two intentional CHANGELOG.md entries.
• No pyproject.toml [project].name changed.
• .mcp.json and .claude-plugin/plugin.json parse as JSON; pipefy_mcp._docs imports.
• Post-transfer: curl -fsSL https://raw.githubusercontent.com/pipefy/ai-toolkit/main/install.sh | sh -s -- --yes --no-skills --client none --dry-run should print Resolved tag: vX.Y.Z.

[adriannoes]

Summary

Reviewed statically on head 2024a70 (URL/docs chore only; no runtime logic). The diff consistently repoints install and docs surfaces from gbrlcustodio/pipefy-mcp-server to pipefy/ai-toolkit, updates DOCS_SETUP_REF, and leaves distribution names and CHANGELOG history alone as scoped. git grep 'gbrlcustodio/pipefy-mcp-server' on the PR branch leaves only the two intentional CHANGELOG.md lines; CI (lint, test, skill frontmatter) is green.

Approve the change set. Merge only in the #140 transfer window — every pipefy/ai-toolkit URL is dead until the org/repo exists, as you already documented.

Also noted

• #260: If release-wheel .mcp.json lands first, dropping this PR’s .mcp.json hunk on rebase is fine.
• .claude-plugin/marketplace.json: Still lists owner profile https://github.com/gbrlcustodio (not in this PR’s file list). Optional follow-up to https://github.com/pipefy when you refresh marketplace metadata after transfer.