Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web → app handoff·12 in this wave

Approve: Web → app handoffTo do · blocker Register the deep-link scheme on iOSTo do Set up iOS Universal Links for the handoff pathsTo do Set up Android App Links for the handoff pathsTo do Build the deep-link routing layerTo do Design the handoff experienceTo do Build the desktop handoffTo do Build the mobile-web handoffTo do Handle the not-installed case gracefullyTo do Build the return path after programmingTo do Make the capability boundary honest in the web UITo do Verify the handoff end to endTo do

Wave

Web → app handoff

Web can't write NFC tags, so programming a physical tag has to hand off cleanly to the native app. Deep-link infrastructure may not exist at all — verify before building on it.

TacTile › Launch TacTile › Web › Web → app handoff

0/12 done12 open1 open blocker

Selected taskclear

Set up Android App Links for the handoff paths

To doOwner · Vivt_ff4ae1e2

Viv — Extend the existing autoVerify App Links setup to cover the handoff route, not just auth. Done when: a new autoVerify intent-filter (or extended data path) covers the handoff route on tactile.to and `adb shell pm get-app-links com.tactile.app` shows it verified. File: apps/android/app/src/main/AndroidManifest.xml, apps/web/public/.well-known/assetlinks.json.

Unlocks 2Build the deep-link routing layer Approve: Web → app handoff

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Set up Android App Links for the handoff paths** · to do

Viv — Extend the existing autoVerify App Links setup to cover the handoff route, not just auth. Done when: a new autoVerify intent-filter (or extended data path) covers the handoff route on tactile.to and `adb shell pm get-app-links com.tactile.app` shows it verified. File: apps/android/app/src/main/AndroidManifest.xml, apps/web/public/.well-known/assetlinks.json.

Where it sits: TacTile › Launch TacTile › Web › Web → app handoff

## Unlocks 2

- Build the deep-link routing layer
- Approve: Web → app handoff

## The brief on file

Audit finding: apps/web/public/.well-known/assetlinks.json already exists and is correctly configured — package_name com.tactile.app matches applicationId in apps/android/app/build.gradle.kts, with a real SHA-256 cert fingerprint. AndroidManifest.xml (apps/android/app/src/main/AndroidManifest.xml) already has two android:autoVerify="true" intent-filters on MainActivity, but both are scoped ONLY to /auth/callback (one for host tactile.to, one for tactile-connect.com) — the Supabase OAuth redirect. There is no general-purpose App Link path and no DeepLink routing layer referenced anywhere in the Android source (only AuthDeepLinkHandler.kt exists, auth-scoped). Add a new autoVerify intent-filter (or broaden the existing one's android:path/pathPrefix) covering the web→app handoff route decided in the handoff-experience design task, on the tactile.to host. Verify with `adb shell pm get-app-links com.tactile.app` showing the domain verified, and by tapping a real https://tactile.to/<handoff-path> link on a signed build.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Web → app handoff

Set up Android App Links for the handoff paths