feat: rebrand to FlashCat for v1 (iOS + Android)

[Fiona2016]

Summary

Rebrands this fork (DataDog/dd-sdk-flutter) to the FlashCat platform for a v1 release, keeping the change minimal (in the spirit of the iOS/Android forks). Scope: iOS + Android, supporting RUM, Crash Reporting, and WebView tracking (native path). The Flutter Web target is dropped for v1.

Baseline: v3.0.1 (deliberate)

Based on tag datadog_flutter_plugin/v3.0.1, not develop (upstream v3.4.0). develop calls native APIs (Datadog.flush(), iOS 3.8+/Android 3.8+) that the FlashCat native forks (iOS 3.6 / Android 3.5) don't expose, so it would not compile against our SDKs. v3.0.1's native requirements are a subset of what the forks provide. This is why main for this fork tracks the v3.0.1 baseline.

What changed (and what deliberately did NOT)

Published package name only — datadog_flutter_plugin → flashcat_flutter_plugin, datadog_webview_tracking → flashcat_webview_tracking, version 0.1.0.

Note on the Flutter platform: unlike iOS (pod name vs module_name) and Android (maven group vs package), a Dart package's name = import path = pub.dev id — they cannot be separated. Publishing publicly (as the iOS/Android SDKs do to CocoaPods trunk / Maven Central) requires a unique name, and datadog_flutter_plugin is owned by Datadog on pub.dev. So the name must change, and the package: imports change with it. That import churn (~one line per file) is the unavoidable minimum for a public package rename.

Kept datadog internally (minimal):

• Package directories stay packages/datadog_flutter_plugin/ etc. (directory name doesn't affect consumers — pub caches by package name).
• Kotlin package com.datadoghq.flutter, Swift/internal type and file names, the C bridge module, and method-channel names all stay datadog*.

Native dependencies point at the FlashCat forks: iOS pods Flashcat* ~> 0.5 / SPM fc-sdk-ios 0.5.0; Android cloud.flashcat:*:0.4.1.

Site model DatadogSite → FlashcatSite { cn, staging } (default cn → browser.flashcat.cloud). This is functional, not cosmetic — the native forks removed DatadogSite and the endpoints differ; the Dart enum must bridge to the native FlashcatSite.

Logs = no-op for v1 (FlashCat ingest doesn't accept Logs yet): the iOS podspec links FlashcatLogs-NoOp; the API compiles but sends nothing. No feature/public-API removal.

iOS integration files are renamed to the plugin name (podspec + Swift package dir/name/product/target) — Flutter resolves iOS plugins by name, so this is required, not branding. (This accounts for the 15 renames in the diff.)

Fixes found during on-device verification

• Android init crash (fixed here): cloud.flashcat:dd-sdk-android-core:0.4.1's Gradle module metadata misfiles okhttp under the test-fixtures variant → ClassNotFoundException: okhttp3.Authenticator at init. Worked around by declaring okhttp:4.9.0 in the plugin. Proper fix is upstream in fc-sdk-android (publish okhttp as an api dep of the core runtime variant), after which the workaround can be removed.

Verification

flutter pub publish --dry-run → 0 warnings on both packages. End-to-end against the staging intake: Android (emulator) RUM batch sent successfully; iOS (simulator, pure SPM) RUM batch HTTP 202 accepted.

Follow-ups (not blocking)

1. fc-sdk-android: fix okhttp module-metadata scope, then drop the plugin-side workaround.
2. fc-sdk-ios: FlashcatLogs / FlashcatLogs-NoOp missing from CocoaPods trunk (needed for the CocoaPods integration path).
3. Cosmetic: iOS podspec metadata (homepage/author) still say Datadog.
4. Publishing to pub.dev is gated on publisher access for the flashcat_* names.

🤖 Generated with Claude Code