Update repository references for rename to ably-pubsub-flutter

[umair-ably]

Do not merge until the repository is renamed ably-flutter → ably-pubsub-flutter, in the programme's rename freeze window. Merging early points docs.yml and features.yml at the ably-sdk-builds-ably-pubsub-flutter IAM role, whose OIDC trust is bound to the new repository name, so the credential step would fail. Conversely, once the rename happens the old role name stops matching, so this is a same-window change in both directions.

Sibling of ably-pubsub-ruby#457, ably-js#2298, ably-java#1237, ably-dotnet#1332, ably-python#682 and ably-php#222. It only updates strings inside the repo; it does not rename anything. The Flutter split is sequenced after the cocoa and java splits (PDR-091b2); the repo rename is independent of that, since the legacy ably_flutter package consumes the Ably pod and io.ably:ably-java by registry name, not repo URL.

What changed

• .github/workflows/docs.yml — role-to-assume → ably-sdk-builds-ably-pubsub-flutter. Provisioned by infrastructure#13005, with the ID-qualified OIDC subject added by infrastructure#13054 (both merged).
• .github/workflows/features.yml — repository-name: ably-pubsub-flutter.
• pubspec.yaml — repository URL (shown on pub.dev). Package name ably_flutter untouched.
• README.md — licence badge and GitHub Issues link.
• CONTRIBUTING.md — the two raw-image links and the release-workflow / releases links.
• API_REF_INTRO_BLURB.md — source-code link on the dartdoc front page.
• .claude/skills/release/SKILL.md — CHANGELOG link templates.

Deliberately left as-is

• ably_flutter package name — pub.dev identity, not the repo. The new ably_pubsub_device package arrives with the split.
• ably-flutter/<version> agent identifier — a registered identifier; the family rename belongs to the split, gated on ably-common#361.
• CHANGELOG.md and issue/PR links in comments — history; GitHub's redirect covers them.

⚠️ pub.dev automated publishing

release.yaml publishes via dart-lang/setup-dart's reusable workflow using pub.dev's GitHub Actions publishing, which is bound to the exact repository ably/ably-flutter (plus the pub.dev environment and the tag pattern). Re-point it on the ably_flutter package's Admin → Automated publishing page to ably/ably-pubsub-flutter in the same window, or the next tag push fails to publish. Registry work, not repo work.

Post-rename verification

• git ls-remote from an existing checkout and web redirects for repo / a PR / a file permalink.
• check.yaml, iOS unit tests and integration workflows green.
• docs.yml and features.yml runs: AWS credential step succeeds and the upload lands at sdk.ably.com/builds/ably/ably-pubsub-flutter/main/… (the upload failure mode is silent).
• pub.dev automated publishing shows the new repository; confirm on the next release.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ttypic]

LGTM