@nijaru/pi-peak-hours 0.0.7 → 0.0.9

package/README.md

@@ -8,7 +8,7 @@ The default covers DeepSeek direct only: pi records it at the published **peak**
 
 With a compatible [pi-provider-compaction](https://github.com/nijaru/pi-provider-compaction) companion loaded, this extension scales existing `usage.cost` before request completion reaches stream consumers or cache observers. It covers observed foreground requests, compaction, branch summaries, and cache warming for scheduled providers. Without the companion, it still corrects finalized foreground assistant messages through `message_end`; auxiliary usage stays unchanged. Both paths preserve token counts and existing cost corrections such as `/fast`.
 
-The status line quotes the selected model's scheduled catalog estimate — `· est. $0.30/$1.20/M` during a peak window, `· est. ▼ off-peak $0.15/$0.60/M` off it. `▲ peak` or `▼ off-peak` marks a rate above or below pi's recorded rate. With stock peak-base prices, peak has no indicator and off-peak is marked as a discount. `/peak-hours status` names the schedule.
+The status line quotes the selected model's scheduled catalog estimate — `· $0.30/$1.20/M` during a peak window, `· ▼ off-peak $0.15/$0.60/M` off it. `▲ peak` or `▼ off-peak` marks a rate above or below pi's recorded rate. With stock peak-base prices, peak has no indicator and off-peak is marked as a discount. `/peak-hours status` names the schedule.
 
 The footer describes the current hour, not a particular request: a request invoked before a boundary uses its invocation timestamp even after the footer moves to the new hour. Request-specific corrections can also differ from the quoted catalog rate. Stale base prices remain stale; this extension applies a multiplier, not a price lookup. All costs are estimates, not invoices: server arrival times and Chinese public holidays are not modeled.
 
@@ -102,16 +102,16 @@ Note that a coding plan is billed in credits against a subscription, so pi's cos
 
 OpenRouter publishes the same windows machine-readably for models it hosts (`pricing.overrides` with `utc_days` / `utc_start` / `utc_end` on `https://openrouter.ai/api/v1/models`), but this extension reads its schedule from config rather than the network: the correction is a rate difference, not a price lookup, and a fetch would add a failure mode to a handler that must never throw.
 
-A malformed field falls back to its default rather than disabling the extension; a malformed file warns and resolves to defaults.
+A malformed field falls back to its default rather than disabling the extension; a malformed file warns and resolves to defaults. `/peak-hours on|off` refuses to rewrite a malformed, unreadable, or non-object config and reports that the save failed, leaving the existing file untouched.
 
 ## Design notes
 
-- **Only the selected model drives the indicator.** Schedules are provider- and model-scoped, so the footer shows no rate for uncovered models. A rate above the recorded one reads `peak`, below it `off-peak`. The `est.` label applies even with request-wide coverage.
+- **Only the selected model drives the indicator.** Schedules are provider- and model-scoped, so the footer shows no rate for uncovered models. A rate above the recorded one reads `peak`, below it `off-peak`.
 - **The footer follows the window it quotes.** pi has no render tick and fires no event while a session is idle, and a rate that changes at 04:00 would otherwise stay on screen until the next turn. The extension arms a single timer for the next instant the quoted rate changes and re-arms it after each fire, from the same clock reading as the status it is keeping fresh. It arms nothing when there is no status on screen, and the timer is unreferenced and cleared on session shutdown, so it neither holds pi open nor outlives its session.
 - **Rate by provider invocation.** Pi providers timestamp each assistant message before preparing and sending its HTTP request. That timestamp selects the multiplier, not completion time or the shared payload hook. With the companion, active state and schedules are captured at request dispatch; without it, foreground fallback uses the configuration at `message_end`.
 - **Scaled once.** Global weak identity guards protect usage and foreground message objects across loaded copies, retries, and returned replacements. Usage observed at dispatch remains handled even when its decision is unchanged (×1 or inactive), so fallback cannot overwrite it after a config change.
 - **Shared ownership.** The client requests usage-only leases for covered available models and the current model, deduplicated by provider. The companion scopes callbacks to the owning session. Retired leases are reacquired on reconciliation; shutdown and SDK disposal remove only this client's leases. Neither catalogs nor unrelated provider slots are replaced.
-- **Only cost moves.** The four cost fields are scaled and `total` is recomputed from them, matching pi's own invariant. Token counts are untouched, so rate-from-cost derivations stay self-consistent — including pi's cache-miss accounting, which derives its paid and read rates from the same message and scales with it.
+- **Only cost moves.** The four catalog cost fields are scaled and estimated totals are recomputed from them. Provider-reported billed totals are preserved, including zero. Token counts are untouched, so rate-from-cost derivations stay self-consistent — including pi's cache-miss accounting, which derives its paid and read rates from the same message and scales with it.
 - **Coverage.** Only requests observed by the companion's safe dispatcher receive request-wide correction. Unavailable models, unsupported provider registrations, and usage reported independently by tools can remain uncorrected. Without the companion, coverage is foreground assistant messages only. The default weekday schedule does not encode Chinese public holidays, which DeepSeek treats as off-peak; holiday costs can therefore be overstated.
 
 ## Stack

package/extensions/index.ts

@@ -4,7 +4,7 @@
  * DeepSeek is the clearest example: a 2x multiplier applies during peak windows
  * (01:00-04:00 and 06:00-10:00 UTC, Monday-Friday, as of September 2026) and the
  * off-peak rate is half of it. pi has no notion of time-of-day pricing —
- * `usage.cost` is computed once from the model's flat rates when usage is
+ * `usage.cost` component estimates use the model's flat rates when usage is
  * finalized — so a session is over- or understated by up to 2x, in whichever
  * direction the recorded rate sits from the billed one.
  *
@@ -15,8 +15,8 @@
  *
  * The footer indicator is scoped to the selected model and quotes the rate that
  * applies to it right now, in dollars per million tokens: with the default
- * schedule, `· est. $0.30/$1.20/M` at peak and
- * `· est. ▼ off-peak $0.15/$0.60/M` off it. This is a scheduled catalog estimate;
+ * schedule, `· $0.30/$1.20/M` at peak and
+ * `· ▼ off-peak $0.15/$0.60/M` off it. This is a scheduled catalog estimate;
  * request-specific corrections such as /fast can change the actual usage cost.
  * Uncovered models show no rate; switching models re-evaluates it.
  *
@@ -46,15 +46,15 @@
  *   instead of correcting it.
  * - A message is never scaled twice. Retries and overflow recovery can deliver
  *   the same message object again, so adjustments are guarded by identity.
- * - Only the four cost fields are touched, and `total` is recomputed from
- *   them, preserving pi's own invariant. Token counts are real and never
+ * - Scale catalog cost fields and recompute estimated totals; preserve
+ *   provider-reported billed totals, including zero. Token counts are never
  *   modified, so any rate derived from cost/tokens stays self-consistent
  *   (cache-miss accounting derives paid and read rates from the same message
  *   and scales with it).
  * - Unknown or malformed configuration falls back to the defaults with a
  *   warning; no path throws from a message handler.
  *
- * All costs remain estimates, not invoices: server arrival, Chinese public
+ * Scheduled rates remain estimates, not invoices: server arrival, Chinese public
  * holidays, and usage outside observed provider requests are not modeled.
  */
 
@@ -415,11 +415,11 @@ export function statusIndicator(
 
 	switch (rateStateAt(now, schedule)) {
 		case "peak":
-			return `· est. ${STATUS_PEAK} ${rate}`;
+			return `· ${STATUS_PEAK} ${rate}`;
 		case "off-peak":
-			return `· est. ${STATUS_OFF_PEAK} ${rate}`;
+			return `· ${STATUS_OFF_PEAK} ${rate}`;
 		default:
-			return `· est. ${rate}`;
+			return `· ${rate}`;
 	}
 }
 
@@ -444,14 +444,16 @@ export function readConfig(path: string): ConfigFile {
 	}
 }
 
-/** Persist `active` while preserving keys this version does not model. */
-export function writeActive(path: string, active: boolean): void {
+/** Refuse to replace unreadable/malformed config; preserve unknown valid keys. */
+export function writeActive(path: string, active: boolean): boolean {
 	try {
+		const config: unknown = existsSync(path) ? JSON.parse(readFileSync(path, "utf8")) : {};
+		if (!isRecord(config)) return false;
 		mkdirSync(dirname(path), { recursive: true });
-		writeFileSync(path, `${JSON.stringify({ ...readConfig(path), active }, null, 2)}\n`, "utf8");
-	} catch (error) {
-		const message = error instanceof Error ? error.message : String(error);
-		console.warn(`[${STATUS_KEY}] Failed to write ${path}: ${message}`);
+		writeFileSync(path, `${JSON.stringify({ ...config, active }, null, 2)}\n`, "utf8");
+		return true;
+	} catch {
+		return false;
 	}
 }
 
@@ -686,7 +688,10 @@ export default function peakHours(pi: ExtensionAPI, options: PeakHoursOptions =
 				ctx.ui.notify("Usage: /peak-hours [on|off|status]", "error");
 				return;
 			}
-			writeActive(configPath, arg === "on");
+			if (!writeActive(configPath, arg === "on")) {
+				ctx.ui.notify(`Peak hours: failed to save configuration at ${configPath}; keeping the previous setting.`, "error");
+				return;
+			}
 			refresh();
 			await pricing.reconcile(ctx);
 			if (!pricing.isCurrent(ctx)) return;

package/extensions/request-pricing.ts

@@ -36,7 +36,7 @@ export function applyMultiplier(cost: Usage["cost"], multiplier: number): Usage[
 		cacheRead: cost.cacheRead * multiplier,
 		cacheWrite: cost.cacheWrite * multiplier,
 	};
-	scaled.total = scaled.input + scaled.output + scaled.cacheRead + scaled.cacheWrite;
+	if (cost.totalFromProvider !== true) scaled.total = scaled.input + scaled.output + scaled.cacheRead + scaled.cacheWrite;
 	return scaled;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nijaru/pi-peak-hours",
-  "version": "0.0.7",
+  "version": "0.0.9",
   "type": "module",
   "description": "Correct pi's recorded cost for providers that bill by time of day, with a peak multiplier in the footer status.",
   "keywords": [
@@ -34,8 +34,8 @@
     "check": "bun test && oxlint extensions/ tests/ && tsc --noEmit"
   },
   "devDependencies": {
-    "@earendil-works/pi-ai": "1.4.0",
-    "@earendil-works/pi-coding-agent": "1.4.0",
+    "@earendil-works/pi-ai": "1.5.0",
+    "@earendil-works/pi-coding-agent": "1.5.0",
     "@types/bun": "latest",
     "oxlint": "latest",
     "typescript": "^6.0.3"