@sandgarden/miranda 0.1.88 → 0.1.90

package/collector/stub.sh

@@ -44,15 +44,15 @@
 # now downloads the same release from "sandgardenhq/plugins" with the
 # "miranda-collector" prefix (#813). They stay placeholders rather than
 # literals so the release host can move without editing this file.
-BUILD_VERSION="d9f84d746201"
-RELEASE_TAG="collector-d9f84d746201"
+BUILD_VERSION="898a3aeb70f0"
+RELEASE_TAG="collector-898a3aeb70f0"
 RELEASE_REPO="sandgardenhq/plugins"
 ASSET_PREFIX="miranda-collector"
-CHECKSUM_DARWIN_ARM64="a7bcd2b373d1862764c693f9a806549ab8dac83c5e51e4c14d65d842b83d4214"
-CHECKSUM_DARWIN_X64="4a94c252717e69ec1113a9b17c7478949229b9b402f5ab62f4bba2d4977048ca"
-CHECKSUM_LINUX_X64="453fcff80977921ef6b2ab799f88339c23e4d6ad744410d8dfc2caab239814c5"
-CHECKSUM_LINUX_ARM64="0eaa33f9cf12ae3cf5d41ecd2d1516499bd25958b360c24d07f54ed383616f26"
-CHECKSUM_WINDOWS_X64="b5a7034625929c1517bca0923396e10bc6a97564a946a6a4e678e7cd5d359d85"
+CHECKSUM_DARWIN_ARM64="634e7fcfcdaf31dbc634c05c376cf7cb06faf39cbaed6dd97cc294795419433f"
+CHECKSUM_DARWIN_X64="bf72e11cdd05607323e9519c255ad934c8b50ab9c7893f3938832a1dd5187d11"
+CHECKSUM_LINUX_X64="adcdb67e25f025a604582e8346728692995121bbef5325db7dc227c6bbebc111"
+CHECKSUM_LINUX_ARM64="ab06c59c86067b622374f725f45e87c3cb68287f55534a8fd2dd6ff5c32871e1"
+CHECKSUM_WINDOWS_X64="826194a0fc0ab7af0c32b1405e9ffb82603e66033c26fe1e45dc2f61e8786d5f"
 
 # A download lock older than this is a downloader that died mid-run: take it
 # over (mirrors the collector's sweep-lock staleness cutoff).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sandgarden/miranda",
-  "version": "0.1.88",
+  "version": "0.1.90",
   "type": "module",
   "description": "Miranda OpenCode plugin — token-usage tracking skill + the gloria.dev MCP server's scoped /miranda tools.",
   "main": "index.js",

package/skills/setting-up-usage-tracking/SKILL.md

@@ -321,14 +321,29 @@ spend stops landing in Unassigned. Use the `miranda` MCP tools only.
    attached to a project is that project's as much as its primary is. If a
    project matches, name the existing project — its name and slug (all of
    them, if more than one matches) — say spend from this repository is
-   already attributed to it, and register nothing.
+   already attributed to it, and register nothing. Never overwrite an existing
+   description, even a blank or weak one: a person may have written it, and
+   they can edit it on the project's page.
 
 4. **Register when nothing matches.** Call `register_project` with
-   `{ "project": { "slug": …, "name": …, "repoUrls": [<normalized URL>] } }`:
+   `{ "project": { "slug": …, "name": …, "description": …, "repoUrls": [<normalized URL>] } }`:
    - `name` — the repository name: the last path segment of the normalized
      URL (`https://github.com/sandgardenhq/gloria.dev` → `gloria.dev`);
    - `slug` — that name lowercased, every run of characters outside `a-z0-9`
-     replaced by `-`, leading and trailing `-` trimmed (`gloria-dev`).
+     replaced by `-`, leading and trailing `-` trimmed (`gloria-dev`);
+   - `description` — one or two plain sentences, at most about 300
+     characters, saying what this project is and what it does, written from
+     what you can read at the repo root: the README first, then the manifest's
+     own description (`package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`
+     and the like), the agent instruction file, and the top-level layout. Be
+     specific: say who or what it serves and the main things it does, e.g.
+     "Next.js dashboard and Cloudflare Workers API that monitors a team's
+     third-party service dependencies and alerts on outages." Not the
+     project's name or its URL restated, no boilerplate ("A software
+     project", "This repository contains code"), no markdown. Never claim a
+     capability, user or integration the files don't show. If they show too
+     little to say anything concrete, omit `description` rather than guess.
+     The developer can edit it on the project's page afterwards.
 
    `register_project` **upserts by slug**: sending a slug some other project
    already has overwrites that project's name and repository. So if
@@ -353,6 +368,8 @@ spend stops landing in Unassigned. Use the `miranda` MCP tools only.
    `backfill`:
    - the `slug` it registered under (and the name, when it isn't the same as
      the slug);
+   - the description it saved, quoted, so the developer can correct it on the
+     project's page — or that you sent none, and why;
    - `backfill.status` `"ran"` with `sessionCount` above 0 — that many earlier
      sessions moved from Unassigned onto the project, worth `spendMicros` ÷
      1,000,000 dollars (round to cents), the earliest from `earliestSessionAt`