[APP] Lara

**Name of app / service**
Lara

**Link to developer documentation**
https://developers.laratranslate.com

**Is lack of support preventing you from moving forward, or do you have a workaround?**
We're contributing the components ourselves (app file + actions) via PR. Blocker is the app registration + custom connected-account auth, which only the Pipedream team can configure server-side. Once the Lara app slug + auth fields are registered, this.$auth populates and our PR unblocks.

Auth is HMAC — two custom fields, not a single API key:
- access_key_id — "Access Key ID" (text)
- access_key_secret — "Access Key Secret" (password, masked)

The `@translated/lara` SDK does the HMAC signing. Question: can the connected-account test request run custom code to HMAC-sign, or is it a static HTTP template? If static, we can't verify the key on Save.
Proposed fallback: map the first 401 on an action run to Authentication failed — update your Lara connection.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**
Actions we're contributing: Translate text, Start document translation, Check document status, Download translated document.

Start with the Lara developer documentation and the contributed app file and actions for Translate text, Start document translation, Check document status, and Download translated document. Verify the app slug, the two connected-account fields, and the HMAC authentication behavior; done means server-side registration populates this.$auth and the actions can authenticate, with a clear failure path for invalid credentials.

Written by the indexing model from the issue text.