docs(readme): direct docs links + ecosystem footer

[johnxie]

What

README-only change, two things:

1. Direct docs links — both developers.taskade.com references (Links section + Roadmap/TaskOS bullet) now point to https://docs.taskade.com directly. developers.taskade.com 301-redirects there anyway, so this just skips the redirect hop.
2. New "More from Taskade" section (placed before License) cross-linking the rest of the org:
   • Taskade Docs (source) — developer documentation and API reference
   • Integration Kit — open-source Zapier/n8n actions & triggers
   • Taskade — platform home, including Genesis, the AI app builder

Nothing else in the README is touched.

Why

Taskade's public repos currently don't cross-link. Developers arrive at this repo from the MCP registries, npm (@taskade/mcp-server), docs.taskade.com, and awesome-MCP lists — and hit a dead end with no path to the docs source, the integration kit, or the platform repo. This closes the org link graph so the MCP server is a doorway into the rest of the platform, and removes a redirect hop on the docs links while at it.

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

Zero-regression verification

• Every new/changed URL returns HTTP 200 via curl -sL -o /dev/null -w "%{http_code}":
  • https://docs.taskade.com → 200
  • https://github.com/taskade/docs → 200
  • https://github.com/taskade/integrations → 200
  • https://github.com/taskade/taskade → 200
• git diff shows only the intended lines: 2 link substitutions + the new 8-line section (10 insertions, 2 deletions, README.md only)
• No markdown tables modified (no tables in the touched sections; pipe structure unaffected)
• No other sections, files, or formatting touched

cc @deanzaka @lxcid

[changeset-bot]

⚠️ No Changeset found

Latest commit: 20eeca1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR