App linking
Well-formed counterparts to the chaotic mobile and PWA discovery files on bots.catastrophic.io. Each parses cleanly under its platform's strict format requirements.
iOS universal-links manifest. Served as application/json with a single applinks block, an appID in TEAMID.bundle format, and a non-empty paths array. Apple's verifier should accept without warnings.
Android App Links manifest. Single statement asserting delegate_permission with a get_login_creds relation, a well-formed android_app target including SHA-256 fingerprint in the standard colon-delimited 64-byte hex format.
PWA web app manifest with all required fields populated, a non-empty icons array, internally consistent display modes, valid colour values, and matching name/short_name. PWA installers should offer the install prompt.
These are the well-formed counterparts to the chaotic app-linking files
on bots.catastrophic.io. Build your iOS/Android/PWA link-verification
tooling against these endpoints, then flip the hostname to bots. to
exercise the failure paths.
The identity values in these files (catastrophic.io bundle IDs, fake
SHA-256 fingerprint, placeholder team IDs) are obviously not real apps —
they’re chosen to be format-valid while making it clear no actual
production app should rely on these manifests. The point is to demonstrate
the well-formed shape, not to advertise a working app.