Skip to content

v0.10.26

Choose a tag to compare

View all tags
@hyoshi hyoshi released this 15 Jul 01:30
v0.10.26
c8ad3d6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Added

  • Extensions can contribute a DashboardCard to the Reports tab (#425).
    BUILTIN_CARD_GROUPS previously allowed only "advanced", where operator settings live. "reports" is now a second accepted group, so an extension can place an operator reporting action — "refresh every client's numbers now", a cross-client daily-check — beside the built-in report cards rather than under Advanced or in a whole separate tab. Purely additive: "advanced"-only extensions are unaffected, and a DashboardCard(group="reports") raises ValueError on an older mureo, so a downstream extension version-gates on this release. Same safety contract as before (no inline-executable HTML; behaviour ships as StaticAsset scripts/styles).

Fixed

  • The configure dashboard detects the basic-setup parts on disk instead of recalling them from a flag file (#423 / #424). Every other row on the status snapshot is read off the filesystem, but the three basic-setup rows (mureo MCP, credential-guard hook, workflow skills) came from setup_state.json — a record only the dashboard's own actions ever wrote. So skills installed with mureo setup, or by hand, read as not installed while present; and, in the dangerous direction, a component deleted after a dashboard install kept reading as installed while absent. Each part is now detected on every read: the hook by the credential guard's own tag on the host's real hook surface, the skills by presence in the host's skills directory, and the mureo MCP block by the same registry read that already reports every other provider. setup_state.json is no longer written or read; one left behind by an older mureo is ignored.

Full changelog: v0.10.25...v0.10.26

Assets 2
Loading