The catalog previously showed opaque icons or text fallbacks for the
seven digital employees, and source-pointer installs could still get
different avatars. This updates every catalog card to a 512×512
transparent portrait, bumps the listed releases, and pins the six source
repositories to commits that include the matching AgentFS avatar.
Validation: `validate_catalog_metadata.py --require-complete` (0
errors), `validate-i18n.py` (0 errors), and `translate.py --check`. All
seven WebP files have an alpha channel with fully transparent pixels and
are below 50 KB each.
## 变更说明 / What this changes
新增官方 Agent 条目「MiMo 模型余量检测」，以不可变 source pointer 形态收录，内容仓库为
`desirecore-agent/mimo-model-quota-monitor`。
- `agents/mimo-model-quota-monitor/entry.json` 指向已发布提交
`911c0a226346a8157f07d5218207f16e32ea82e0`。
-
`agents/mimo-model-quota-monitor/catalog-metadata.v1.json`：provenance、MIT
许可证证据、合规审查（`reviewedRef` 与内容 ref 一致），`availability: installable`。
- `requiredClientVersion: 10.0.156`：依赖该版本起的调度完成判据、调度权限上限与内嵌浏览器操作记录修复。
- `manifest.json`：Agent 计数与更新日期。
Agent 做什么：按计划（默认每小时）读取小米 MiMo 开放平台 Token Plan 余量，结构化写入 `latest.json`
与每轮一份历史文件，在余量偏低、消耗过快、即将重置或登录失效时提醒。只读、不执行命令；遇到验证码或短信验证时停下请人处理；登录凭据只经
DesireCore 加密凭据存储的占位符注入。
Adds the official "MiMo model quota monitor" Agent as an immutable
source pointer to `desirecore-agent/mimo-model-quota-monitor` at commit
`911c0a226346a8157f07d5218207f16e32ea82e0`, with a bilingual catalog
sidecar (provenance, MIT license evidence, compliance review with
`reviewedRef` equal to the content ref, `availability: installable`) and
`requiredClientVersion: 10.0.156`. The Agent reads the Xiaomi MiMo Token
Plan quota on a schedule, writes structured results, and alerts on low
quota, fast burn, upcoming reset or an expired login. It is read-only,
runs no shell commands, stops for CAPTCHA or SMS verification, and
receives credentials only through DesireCore's encrypted credential
placeholders.
## 校验 / Validation
- `uv run --quiet scripts/catalog/validate_catalog_metadata.py
--require-complete`：0 error（既有条目的 warning 未变）。
- 条目目录内所有 40
位十六进制值只有一个，即上面的提交号（`source.ref`、`provenance.content.ref`、`governance.compliance.reviewedRef`
三处一致）。
- 内容仓库：`agent.json` 通过 agentConfigSchema；`SKILL.md` frontmatter 通过技能
Schema；`HEARTBEAT.md` 被判为实质为空（心跳不会白调模型）；结果与账号 Schema 用样例和反例校验，共 19 项通过。
- 内容仓库共两个提交（首版 + SOP 失败分支表更新），不含账号标识、手机号或凭据。Git 提交元数据中的维护者邮箱是 DesireCore
组织所有公开提交一致使用的公开身份邮箱。
`validate_catalog_metadata.py --require-complete` reports 0 errors; the
entry directory contains exactly one 40-hex value, the pinned commit, in
all three places; the content repository passes agent config, skill
frontmatter, heartbeat and result/account schema checks (19 checks) and
has two commits (initial release plus the SOP failure-branch update)
without account identifiers or credentials.
## 真机验证 / Real-device verification
在 DesireCore dev 构建（10.0.156 之后的 dev，含
#2863/#2865/#2869）上安装本提交的内容，智能路由旗舰档，两个账号各一个每小时定时巡检，连续观察四轮：
| 轮次 | 结果 | 说明 |
|---|---|---|
| 账号 2 · 20:30 | ok | 经接口取到数据，`latest.json` 与本轮 history 文件通过
`result.schema.json`，history 先写、关闭会话、`latest.json` 最后写 |
| 账号 1 · 21:00 | blocked（`platform_unavailable`） |
本机网络间歇断连期间内置浏览器开不了会话；如实落盘，未新建浏览器环境、未反复填表，首轮不提醒 |
| 账号 2 · 21:30 | 失败 | 同一次断网里浏览器开不了会话，且 AI 审批上游持续 502，写 `latest.json`
被拒；平台按完成判据续跑一次后记为失败（已写入使用说明「已知限制」） |
| 账号 1 · 22:00 | blocked，已提醒 | 连续第二轮 `platform_unavailable`，按告警规则
`notify=true`、告警项 `blocked:platform_unavailable` |
四轮都没有执行任何命令，没有非预期工具调用，没有写出 `mimo-quota/` 与平台 Plan 目录以外的文件；每轮的结果文件都通过
Schema 校验。浏览器宿主把导航失败统一报成 `BROWSER_HOST_EXECUTION_FAILED` 的问题已在主仓 #2871
修复（10.0.157 起提供 `BROWSER_NAVIGATION_*` 闭集错误码），本提交的 SOP
失败分支表已随之更新：网络类失败按码重试一次、页面跳转顶替（ABORTED）先看停留页再分流、越出授权范围（ORIGIN_NOT_GRANTED
/ SCHEME_DENIED）不新建 space。旧客户端上这些码不会出现，条目行为退回原有兜底，不受影响。
Installed this commit's content on a DesireCore dev build (dev after
10.0.156, including #2863/#2865/#2869) with smart routing at the
flagship tier and one hourly schedule per account, and observed four
runs. Account 2 at 20:30 read the data through the API; `latest.json`
and the per-run history file passed `result.schema.json`, with history
written first, the session closed, and `latest.json` written last.
During a local network outage, account 1 at 21:00 could not open a
browser session and recorded `blocked` / `platform_unavailable` without
creating environments or retrying the login, and without notifying on
the first round; account 2 at 21:30 hit the same outage plus sustained
502s from the AI approval upstream, so its `latest.json` write was
denied and the run was recorded as failed after one platform
continuation (now listed under known limitations); account 1 at 22:00
was the second consecutive `platform_unavailable` and notified with
`blocked:platform_unavailable`. No run executed a command, called an
unexpected tool, or wrote outside `mimo-quota/` and the platform Plan
directory, and every result file passed schema validation. The browser
host reporting all navigation failures as
`BROWSER_HOST_EXECUTION_FAILED` was fixed in the main repository in
#2871 (closed-set `BROWSER_NAVIGATION_*` codes from 10.0.157), and the
SOP in this commit was updated accordingly: network-class failures retry
once by code, a navigation replaced by a page jump (ABORTED) inspects
the landed page before branching, and out-of-grant targets
(ORIGIN_NOT_GRANTED / SCHEME_DENIED) never create a new space. On older
clients these codes simply do not appear and the entry falls back to the
previous behavior.
