1847123733/dsh-prompt-optimize

## Core Features
- Prompt optimization reads the current draft, shows a loading state on the button, generates a rewrite with the default provider and model, previews the result in a bubble above the button, and writes to the input box only after Apply is selected.
- User question anchors collect user messages and accepted follow-up questions in conversation order, display an anchor panel on the right with a question count, reveal full text on hover or keyboard focus, and scroll smoothly to the selected user message.
- The floating DeepSeek API usage capsule appears in the lower-right corner, expands on hover or click, and shows the configured key name, masked identifier, spending for today, yesterday, and the last seven days, with account balance displayed separately.
- Usage data reuses the DEEPSEEK_API_KEY stored in DSH model settings, refreshes automatically every 60 seconds or manually, and keeps full API keys and platform tokens parsed only on the DSH host side rather than returning them to the browser.

## Use Cases
- Optimizing a prompt before sending it in a DSH web chat session.
- Navigating long conversations by locating prior user questions through the anchor panel.
- Monitoring DeepSeek API balance and key-level spending while using the web interface.

## Technical Details
- The plugin is installed into the DSH web profile with dsh plugin add from GitHub, a local path, or npm, and requires restarting the web profile after installation or removal.
- Runtime dependencies include the host llm and webServer services, the client slots input-area integration, and an available LLM configured in DSH settings.
- Prompt optimization behavior can be changed through cordis.patch.yml or profile patch settings for provider, model, maximum input characters, maximum output tokens, and temperature.
- Account balance is fetched from the public DeepSeek user balance endpoint, while per-key cost uses a platform usage endpoint matched by sensitive_id and tracking_id.

## Notes
- The per-key usage display depends on an internal DeepSeek platform interface that may stop working when login state expires, a WAF blocks access, or the interface changes.
- Environment variables or the DSH credential provider can override the bundled default DEEPSEEK_PLATFORM_TOKEN, and the token value may include or omit the Bearer prefix.
- Usage amounts are calculated by GMT+8 calendar days, and platform data may be delayed by about five minutes.