docs(readme): ecosystem links, n8n package pointer, roadmap freshness

[johnxie]

What

README-only changes, two files:

• Root README.md
  • New Packages section pointing to the in-repo n8n community node at packages/n8n-nodes-taskade (relative link).
  • Roadmap freshness: the codegen bullet previously presented the n8n node as a future deliverable, but the package already lives in this repo — reworded so codegen now reads as letting the existing n8n node and future platform targets (Activepieces, Make, Pipedream) render from one manifest.
  • New Related repos footer: Taskade Docs (source for docs.taskade.com), Taskade MCP (official MCP server, @taskade/mcp-server on npm), and Taskade (platform home — Genesis AI app builder).
• packages/n8n-nodes-taskade/README.md
  • The install section tells users to install n8n-nodes-taskade from npm, but the package is not yet published (verified npm E404). Added the note: (npm publish pending — follow this repo for the release) so nobody hits a dead install.

Why

Taskade's public repos currently don't cross-link, so the org's link graph has dead ends: developers arriving here from the MCP registry, npm (@taskade/mcp-server), docs.taskade.com, or the awesome-list submissions can't discover the rest of the platform — and vice versa, nothing routes from this repo back to docs, MCP, or the platform home. This PR closes that loop from the integrations side and fixes the one stale roadmap claim plus the one misleading install instruction found while auditing.

For context on the platform these integrations plug into: Taskade Genesis is the AI app builder — one prompt generates a working app backed by your workspace, where projects become the database, AI agents the team, and automations the execution layer, with 100+ integrations and MCP support. Docs: https://docs.taskade.com

Zero-regression verification

Checks actually run before pushing:

• curl -sL -o /dev/null -w "%{http_code}" on every new/changed URL: https://github.com/taskade/docs → 200, https://docs.taskade.com → 200, https://github.com/taskade/mcp → 200, https://github.com/taskade/taskade → 200, existing https://help.taskade.com/en/articles/8958540-zapier-integration → 200
• https://www.npmjs.com/package/@taskade/mcp-server → 403 to curl (npmjs.com Cloudflare bot blocking, including with a browser UA); package existence verified via registry API https://registry.npmjs.org/@taskade/mcp-server → 200 — the page link works in browsers
• Relative link target exists: packages/n8n-nodes-taskade/ present in repo; https://github.com/taskade/integrations/tree/master/packages/n8n-nodes-taskade → 200
• n8n-nodes-taskade confirmed unpublished: https://registry.npmjs.org/n8n-nodes-taskade → 404 (backs the "publish pending" note)
• Markdown tables untouched and pipe counts consistent per row (root capabilities table: 4 pipes × 14 rows; n8n operations table: 3 pipes × 5 rows)
• git diff reviewed — only the intended lines changed (12 insertions, 2 deletions across the two READMEs); no other sections touched

cc @deanzaka @lxcid

[johnxie]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance — relative package links resolve on master, roadmap rewording is consistent with the PR #14→#16 commit sequence, the npm-publish-pending note is accurate (registry 404 verified), and no prior-PR comment guidance applies. Note: the BLOCKED merge state is the pre-existing CI failure present on every run since PR #14 including master pushes — unrelated to this README-only diff.

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}