dsh-date-wrapper

DSH's built-in @deepseek-ai/dsh-time-context injects roughly 280 characters of time metadata on every request, consuming tokens and writing per-turn events into the session log. dsh-date-wrapper replaces that with a single 46-character date line (~12 tokens) and lands it in DSH's existing runtime-context snapshot via systemPrompt.context. Because the platform deduplicates snapshots by text, no extra event is written while the date stays the same; the append-only surfaceOp keeps the prefix cache intact. In a measured 10-turn / 231-step session the legacy approach produced ~3.4 KB of events, while this plugin folds ~46 B into an already-present snapshot.

Activation of the plugin row is the on/off switch: when inactive, apply() never runs and no characters are injected. Configuration is limited to an IANA time-zone value; an invalid zone throws at startup rather than silently falling back to UTC. The plugin registers no settings namespace, reads no session data, makes no RPC call, imports nothing from @deepseek-ai/* packages, and has no browser-side component, staying within the systemPrompt.context contract stable from DSH 0.1.0-rc.7 through 0.1.3-alpha.2.

It suits DSH 0.1.x users in agent workflows who care about token cost and request size, need only the current date, and want the lightest possible replacement for the default time context. Do not enable it alongside @deepseek-ai/dsh-time-context, as the two overlap.