v1.1.21

Remove the MiMo mode Credits comparison card from the detail page. It compared average daily Credits before and after enabling MiMo mode, but the figures are estimates that depend on task difficulty and cache hit rate, and the comparison was not wanted. The four related locale strings and the now-unused state were removed as well; the host still computes the underlying stats but nothing renders them.

v1.1.20

Fix usage persistence still failing after restart with "Cannot convert undefined or null to object". The storage domain spec must declare tables explicitly even when none are used, because the official validator iterates over spec.tables first; leaving it out made open() throw and the error was swallowed into save-failed. The offline fake backend now replicates that required-field check so this class of mistake cannot pass locally again.

v1.1.19

Local usage statistics no longer reset on restart and no longer miss finished sessions. The plugin now subscribes to the session/event stream (the official production path, replacing deprecated snapshot reads) and persists aggregates through the official storageDomain facade, with a hydration barrier so data collected during recovery is not overwritten by the older snapshot, a dirty-flag with backoff retry on write failure, and the storage unit name kept hyphen-free as the official validator requires.

v1.1.18

The expired-sign-in banner button now opens the plugin settings page. It used to look up the cookie input by id from the detail view, but that input moved to the plugin page, so the lookup always returned null and clicking did nothing. It now reuses the same entry point as the header plugin-settings button, and the banner wording points at Settings - Plugins - dsh-mimo-extension.

v1.1.17

Align token accounting with the official dsh-token-meter. Usage was under-counted by roughly 3-4x versus a sibling plugin because the collector only accepted assistant/message events and read data.usage, while failed/retried/cancelled assistant/attempt events carry their usage only in the stream sample; the official usageOf takes the last usage chunk from data.stream for both event types, and is now mirrored exactly. Forked child sessions also no longer re-count their inherited parent history, by preferring ownEvents(). Known remaining gap, not addressed here: the plugin still has no session/event subscription and no storage persistence, so it only scans live sessions and resets on restart.

v1.1.16

Wording now matches the implementation. The tab-hiding preference used to say the page would show a notice instead of usage data, while it actually unregisters the whole tab; it now says the tab is hidden entirely and returns when you switch back to MiMo. The hidden-tab notice used to point at a settings section at the bottom of the page, which was removed when configuration moved to the plugin page; it now points to Settings - Plugins - dsh-mimo-extension.

v1.1.15

Keep the usage tab when the model probe has no data yet. The selection callback treated an empty provider/model (the probe first frame, before the projection resolves) as not-MiMo and unregistered the whole conversation view, so switching to a MiMo model with the hide-when-not-MiMo preference on left the tab missing. Empty selection now keeps the tab mounted, matching the documented conservative behaviour. Also moves the two plugin-page config slots out of ensureView so they register once instead of on every tab visibility re-evaluation.

v1.1.14

Register plugins.bundle.config (key = package name) in addition to plugins.row.config, so the plugin bundle detail page renders the configuration section directly. The platform decides with ledger.bundles.has(pkg.name), and that ledger only collects keys from plugins.bundle.config, so registering only the row slot left the detail page with no configuration area and forced an extra click into the contained row. Both slots now share one renderConfigForm().

v1.1.13

Fix settings still appearing to revert after the previous fix: configuration() inherited is the layer beneath the profile patch (roughly package defaults), not the effective value. Reads now use entry.options.config, the same field the platform write path edit() uses, which also fixes vision routing reading the llm-pi-ai providers.

v1.1.12

Fix settings appearing to revert after a successful save. In 0.2 the settings write goes through settingsService.update into the loader profile config, but currentMimo() still read userSettings.get(), and settings.register no longer exists in 0.2, so the scope was always null and every read returned defaults. Reads now use the same source as writes, via configEditor.configuration() inherited values.