[argszero]

Summary

Implements peak-hour pricing for DeepSeek (rant timestamp 2026-08-20T11:58:40). DeepSeek's official pricing doubles during Beijing peak hours (9:00-12:00 / 14:00-18:00); previously billing always used the off-peak price, undercharging by half during peak hours.

Changes

• config.rs: [[models]] gains 3 optional fields — peak_input_per_m / peak_output_per_m / peak_cache_hit_input_per_m (default 0 = peak billing disabled, off-peak price applies)
• db.rs: schema migration v9 adds the three peak_* columns to models (idempotent ensure_column); seed_models upserts them from config
• billing.rs: is_peak_hour() — fixed Asia/Shanghai (UTC+8, no DST), peak = 09:00-12:00 / 14:00-18:00 Beijing time, Mon-Sun; effective_prices() — peak-hour price selection with 0-default fallback to off-peak
• gateway.rs: settle_usage bills at peak prices when the current Beijing time falls in a peak window
• dao.rs / admin_models.rs: GET /api/models, admin model list, and admin create/patch endpoints carry the peak fields (validated ≥ 0)
• UI: market table shows a "peak ×N" badge + expanded detail shows peak-hour prices; admin model form gains three peak-price inputs; guest mock market entry updated; zh/en i18n keys
• config.example.toml: DeepSeek official peak prices (flash 3.0/0.10/9.0, pro 9.0/0.30/27.0 CNY/M); README + docs/architecture.md updated

Acceptance checklist (from rant)

• Models without peak config keep unchanged billing (compat: default 0 → off-peak price)
• Beijing 09:00-12:00 / 14:00-18:00 calls to deepseek models bill at peak price
• Boundary tests: 8:59/9:00, 11:59/12:00, 13:59/14:00, 17:59/18:00 (Beijing) switch correctly

Tests

• cargo test: 128 passed (125 existing + 3 new: is_peak_hour_beijing_boundaries, effective_prices_selects_peak_or_falls_back, calc_points_uses_peak_price_in_peak_hour; db seed test extended)
• cargo clippy: 0 warnings; cargo fmt --check: clean
• JS syntax check (node --check) on app.js / i18n.js / data.js: OK