dsh-jev-advisor

LIMITATIONS

Known limitations

- **Requires a DSH whose settings service projects `Config` forms (0.1.7-rc.1 or newer).** DSH removed the `settings.register` / settings-namespace API this plugin was originally written against, and with it the `settingsScope` client service. On 0.1.5-rc.2 and earlier the host half would call a method that no longer exists and the browser half would never resolve `configForms`, so the plugin does not load at all. There is no dual-API fallback — DSH is a fast-moving developer preview. - The card floats at the top right and can overlap a wide right sidebar; dismiss it with `✕`. - With more than one session holding a pending question at once, the card follows the current session and falls back to the first pending interaction. - Plan-review questions are advised like any other option-bearing question; the card never replaces the approve/refuse buttons. - The API key round-trips to the host process, which is what performs the HTTPS call. It is never returned to the browser, but it is stored in plain text in your profile's Cordis patch — protect that file as you would any credential. - Jev is charged per input token. The transcript tail is capped at ~24k characters per request. - No retry beyond the two documented overload codes (`429`, `529`).