Add Index trigger gesture to webhook headers

[sarfata]

Summary

• include the Index recording gesture in webhook requests as X-Index-Trigger
• send stable values single-click-hold and double-click-hold
• prevent user-configured headers from overriding the actual trigger
• document the header and receiving example

Why

Webhook receivers currently get the recording and transcription but cannot tell which configured Index action triggered the request. Exposing the gesture lets integrations route single-click-and-hold and double-click-and-hold recordings to different workflows.

The app already computes this distinction in RecordingOperationFactory; this change carries it through the upload operation to the HTTP request.

Testing

• added a common test that locks the two public header values
• checked every IndexWebhookApi.uploadIfEnabled implementation and call site
• git diff --check passes
• local Gradle execution could not configure the project because this machine has no Android SDK; upstream CI should exercise the full multiplatform build

[CLAassistant]

All committers have signed the CLA.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3af4716741

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[derek-knox]

@sarfata I noticed this PR after PRing a related one here.

I think adding a X-Index-Trigger header makes sense, but I was wondering how were you making requests with two different gestures to begin with? Maybe you are using a fork? Or am I missing a means to wire two Webhooks with each gesture in the existing Pebble app?

[sarfata]

@derek-knox I am selecting the option to send Both trigger to the webhook.

[derek-knox]

@derek-knox I am selecting the option to send Both trigger to the webhook.

Ah, makes sense. I removed that part in my PR. Your header vs. my different endpoints to get to the similar reliable routing—difference is single vs. multiple endpoints.

[ericmigi]

@crc-32 good one to merge

[crc-32]

looks good! thanks for the contribution!