Integration Request: OptionsAhoy (equity-comp tax/trade optimizer, 7 functions)

### Required Pre-requisites

- [x] I have read the Documentation
- [x] I have searched the Issue Tracker
- [x] I have searched the apps directory (no `optionsahoy` app exists)

### App Name

OptionsAhoy

### Functions

`amt_iso_optimize`, `nso_calculate`, `rsu_sell_vs_hold`, `concentration_analyze`, `protective_put_price`, `qsbs_check`, `equity_funding_plan`

### API Docs Link

https://optionsahoy.com/openapi.json (also https://optionsahoy.com/for-agents)

### Additional Context

OptionsAhoy is an equity-compensation tax/trade optimizer covering ISO/AMT exercise scheduling, NSO exercise, RSU sell-vs-hold, Section 1202 QSBS qualification, single-stock concentration, protective-put/collar hedging, and multi-year equity-funding plans, computed against the full federal tax code plus all 50 states and DC. All 7 endpoints are public REST, `no_auth`.

I have already prepared `app.json` + `functions.json` in ACI's format (`rest` protocol against `https://optionsahoy.com/api/v1/*`) and validated them locally against your `AppUpsert` / `FunctionUpsert` pydantic models, the REST-protocol parameter validator, and the Draft-7 meta-schema (with `MAX_STRING_LENGTH = 255`). Every endpoint was also exercised live and returns a real `200`.

The two files are ready on a fork branch:
https://github.com/AlvisoOculus/aci/tree/app/optionsahoy/backend/apps/optionsahoy

I tried to open a pull request but the repository limits PR creation to collaborators, so I'm filing this request instead. Happy to (a) open the PR directly if granted access, (b) have a maintainer copy the two files from the branch above, or (c) follow whatever intake you prefer. CLA: will sign. Logo: hosted SVG at https://optionsahoy.com/favicon.svg. Category: `Financial Services`.

Review backend/apps/optionsahoy/app.json and functions.json on the linked fork branch, then compare them with ACI's AppUpsert and FunctionUpsert models and REST parameter validator. Verify the seven listed endpoints against the provided OpenAPI document; the work is done when the files pass the repository schemas and the OptionsAhoy integration is accepted.

Written by the indexing model from the issue text.