@fyeeme/pi-statusline 1.2.1 → 1.2.3

package/CHANGELOG.md

@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.2.3] - 2026-09-09
+
+### Added
+
+- Footer subscribes to `ui_prompt_start`/`ui_prompt_end`: the elapsed timer freezes while a blocking dialog (ask_user, permission gates, ...) is open and the footer shows "waiting for user" instead of running time.
+
+### Changed
+
+- Peer/dev dependencies bumped to pi 0.84.4 (the `ui_prompt` events require >= 0.84.4).
+
+## [1.2.2] - 2026-08-23
+
+### Changed
+
+- Follow DeepSeek's weekend flat-rate adjustment (effective 2026-08-23 00:00 Beijing time): weekends (Saturday/Sunday) no longer distinguish peak/off-peak periods and are billed at the off-peak price all day. `isDeepSeekPeakTime()` now returns false for any Beijing-time Saturday/Sunday from the effective date onward; messages before that instant keep the old per-hour rule, so long sessions spanning 2026-08-23 are still priced correctly per message. Footer indicator and registry patch follow automatically.
+
 ## [1.2.1] - 2026-08-21
 
 ### Fixed

package/README.md

@@ -8,7 +8,7 @@ A rich custom status bar for [pi](https://pi.dev) that replaces the default foot
 ## Features
 
 - **Provider-aware usage** — special support for DeepSeek and GLM/ZAI (see [Provider Support](#provider-support))
-- **DeepSeek peak/off-peak pricing** — session cost follows DeepSeek's 2026-08-17 peak/off-peak billing (peak 9:00-12:00 / 14:00-18:00 Beijing time, off-peak half price), priced per-message by timestamp, with a live `peak`/`off-peak` indicator in the footer (see [DeepSeek](#deepseek))
+- **DeepSeek peak/off-peak pricing** — session cost follows DeepSeek's 2026-08-17 peak/off-peak billing (peak 9:00-12:00 / 14:00-18:00 Beijing time on weekdays; weekends are off-peak all day since 2026-08-23), priced per-message by timestamp, with a live `peak`/`off-peak` indicator in the footer (see [DeepSeek](#deepseek))
 - **Token usage**: input, output, cache read/write, total per session, with cache hit rate
 - **Cost**: cumulative session cost with currency auto-detection (¥ for DeepSeek/CNY, $ otherwise)
 - **Context window**: usage percentage and size
@@ -25,7 +25,7 @@ Shows live **account balance**, **weekly token usage**, and **peak/off-peak awar
 
 #### Peak / Off-peak pricing (since 2026-08-17)
 
-DeepSeek now bills in two periods — **peak hours are 9:00-12:00 and 14:00-18:00 Beijing time** (UTC+8), all other hours are off-peak, and **off-peak is half the peak price**. Official CNY prices per million tokens:
+DeepSeek now bills in two periods — **peak hours are 9:00-12:00 and 14:00-18:00 Beijing time** (UTC+8) on weekdays, all other hours are off-peak, and **off-peak is half the peak price**. Since **2026-08-23 00:00 Beijing time**, weekends (Saturday/Sunday) no longer distinguish periods and bill at the off-peak price all day. Official CNY prices per million tokens:
 
 | Model | Period | Cache-hit input | Cache-miss input | Output |
 |---|---|---|---|---|
@@ -33,7 +33,7 @@ DeepSeek now bills in two periods — **peak hours are 9:00-12:00 and 14:00-18:0
 | deepseek-v4-pro | off-peak / peak | ¥0.15 / ¥0.30 | ¥4.5 / ¥9.0 | ¥13.5 / ¥27.0 |
 
 - **Per-message pricing by timestamp** — each message is priced at the rate of its own time (`AssistantMessage.timestamp`), so a long session spanning a period boundary (9:00/12:00/14:00/18:00) accounts every message correctly instead of using a single fixed rate.
-- **Peak/off-peak indicator** — the footer appends the current period so you always know which rate is in effect: `peak` during 9:00-12:00 / 14:00-18:00 Beijing time, `off-peak` otherwise:
+- **Peak/off-peak indicator** — the footer appends the current period so you always know which rate is in effect: `peak` during weekday 9:00-12:00 / 14:00-18:00 Beijing time, `off-peak` otherwise (including all day on weekends since 2026-08-23):
 
   ```
   ¥0.12/50.00 · 7d:1.2M · off-peak

package/index.ts

@@ -46,6 +46,11 @@ let lastModel: ExtensionContext["model"] = undefined;
 let agentRunning = false;
 let lastElapsedSec = 0;
 let lastTps = 0;
+/** True while a blocking ctx.ui dialog (select/confirm/input/editor/custom)
+ *  span is open (ui_prompt_start → ui_prompt_end). Elapsed time freezes and
+ *  the footer says "waiting for user" instead of showing a running timer —
+ *  the doc-intended status-integration use of the ui_prompt events. */
+let waitingForUser = false;
 
 const tokenCalculator = new SessionTokenUsageCalculator(() => deepSeekPricing.getCurrencyOverride());
 
@@ -90,6 +95,25 @@ export default function (pi: ExtensionAPI) {
 		}
 	});
 
+	// ---- Blocking-dialog spans: freeze the elapsed timer + surface the wait ----
+	pi.on("ui_prompt_start", () => {
+		// Nested/overlapping prompts coalesce into one span (doc), so these are
+		// balanced set/reset pairs. Freeze first so user think-time never counts
+		// as agent work; resume on the matching end.
+		if (agentRunning && agentStartMs !== null) {
+			lastElapsedSec += (Date.now() - agentStartMs) / 1000;
+			agentStartMs = null;
+		}
+		waitingForUser = true;
+	});
+
+	pi.on("ui_prompt_end", () => {
+		if (agentRunning && agentStartMs === null) {
+			agentStartMs = Date.now();
+		}
+		waitingForUser = false;
+	});
+
 	// ---- /status-debug ----
 	pi.registerCommand("status-debug", {
 		description: "Dump session stats to /tmp/pi-status-debug.log + console.error",
@@ -237,8 +261,10 @@ export default function (pi: ExtensionAPI) {
 					}
 
 					// Line 1: tokens + cost + provider usage + context + elapsed + tps + mcp
+					let statLine = dim(buildStatLine(stats, cu, providerResult, providers, getElapsedSec, lastTps));
+					if (waitingForUser) statLine += theme.fg("warning", " · waiting for user");
 					lines.push(truncateToWidth(
-						dim(buildStatLine(stats, cu, providerResult, providers, getElapsedSec, lastTps)),
+						statLine,
 						width,
 						dim("..."),
 					));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fyeeme/pi-statusline",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "description": "Rich custom status bar for pi with token usage, cost, DeepSeek balance, context window, and timing.",
   "type": "module",
   "license": "MIT",
@@ -48,14 +48,14 @@
     "typecheck": "tsc"
   },
   "peerDependencies": {
-    "@earendil-works/pi-coding-agent": ">=0.84.1",
-    "@earendil-works/pi-ai": ">=0.84.1",
-    "@earendil-works/pi-tui": ">=0.84.1"
+    "@earendil-works/pi-coding-agent": ">=0.84.4",
+    "@earendil-works/pi-ai": ">=0.84.4",
+    "@earendil-works/pi-tui": ">=0.84.4"
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "0.84.1",
-    "@earendil-works/pi-ai": "0.84.1",
-    "@earendil-works/pi-tui": "0.84.1",
+    "@earendil-works/pi-coding-agent": "0.84.4",
+    "@earendil-works/pi-ai": "0.84.4",
+    "@earendil-works/pi-tui": "0.84.4",
     "@types/node": "22.19.19",
     "typescript": "5.9.3"
   }

package/pricing/deepseek.ts

@@ -10,7 +10,8 @@
  * 因此所有「修正」都必须跟随结算币种与峰谷时段：
  *   1. `billedInCny()`：判定是否按 CNY 计价 —— 用户显式 `/currency` 优先；否则按 balance API
  *      探测到的账户币种（探测失败/未知时按 CNY，保持原有「deepseek → ¥」默认行为）。
- *   2. `isDeepSeekPeakTime()`：按北京时间（UTC+8，无夏令时）判定指定时刻是否高峰时段。
+ *   2. `isDeepSeekPeakTime()`：按北京时间（UTC+8，无夏令时）判定指定时刻是否高峰时段
+ *      （2026-08-23 00:00 起周末周六、周日全天不再区分峰谷，统一按低谷价）。
  *   3. `messageCost()`：按消息时刻对应的峰谷单价重算单条消息成本（仅 CNY 计价时接管；USD 计价
  *      返回 null 回退 pi 记录的 cost —— 会话文件里已记录的 cost 无法追溯修正）。
  *   4. `applyPricingPatch()`：运行时把注册表中 deepseek 模型定价覆盖为当前时段的官方 CNY 价
@@ -51,12 +52,26 @@ export const DEEPSEEK_CNY_PRICES: Record<string, DeepSeekCnyPrice> = {
 
 const PER_MILLION = 1_000_000;
 
+const BJ_OFFSET_MS = 8 * 60 * 60 * 1000;
+
+/** 周末全天低谷价生效起点：2026-08-23 00:00 北京时间 = 2026-08-22T16:00Z。 */
+const WEEKEND_OFFPEAK_SINCE_MS = Date.parse("2026-08-22T16:00:00Z");
+
 /**
  * DeepSeek 高峰时段判定：北京时间（UTC+8，无夏令时）9:00-12:00、14:00-18:00 为高峰，
  * 其余为空闲时段（官方定价页备注）。`at` 可指定时刻，默认当前时间。
+ *
+ * 2026-08-23（周日）00:00 北京时间起，官方调整：周末（周六、周日）全天不再区分峰谷，
+ * 统一按低谷价收取 —— 即生效后的周六/周日任何时刻均判为空闲时段。生效前（如 2026-08-22
+ * 周六）的历史消息仍按旧规则计价，保证跨生效日的长会话逐条重算正确。
  */
 export function isDeepSeekPeakTime(at: Date = new Date()): boolean {
-	const beijingHour = (at.getUTCHours() + 8) % 24;
+	const beijing = new Date(at.getTime() + BJ_OFFSET_MS);
+	if (at.getTime() >= WEEKEND_OFFPEAK_SINCE_MS) {
+		const bjDay = beijing.getUTCDay(); // 0=周日 6=周六（按北京日期，非 UTC 日期）
+		if (bjDay === 0 || bjDay === 6) return false;
+	}
+	const beijingHour = beijing.getUTCHours();
 	return (beijingHour >= 9 && beijingHour < 12) || (beijingHour >= 14 && beijingHour < 18);
 }