Skip to content

feat: list mochi from its own repository - #92

Merged
KiroCrewCaptain merged 1 commit into
mainfrom
feat/pin-mochi
Nov 18, 2026
Merged

KiroCrewCaptain merged 1 commit into
mainfrom
feat/pin-mochi

Conversation

@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

What

Flips mochi in catalog/official-registry.json from a builtin source to a git source in its own KiroCrewCaptain repository, pinned at the commit Kiro Crew's adoption pin table names for it in kirodotdev/KiroCrew#39043:

App Repository ref Version
mochi https://github.com/KiroCrewCaptain/kirocrew-app-mochi 5db17b967894c411621ea6dcfba294da262d4173 0.1.1

The row gets the same note the other adopted apps carry, naming Kiro Crew 0.14.0, and its Kiro Crew org author gains the https://github.com/KiroCrewCaptain URL. No other row changes.

The commit is the head of the repository's main, with green CI on ubuntu, macOS and Windows plus the reproducible-bundle, README and internal-content jobs. Its manifest declares the same permissions, agents, skills and MCP server as the built-in it replaces, and no desktop block: the Kiro Crew desktop app keeps drawing Mochi's pet and windows itself, over this app's routes.

Merge condition: right after the Kiro Crew pin PR

The Kiro Crew PR is kirodotdev/KiroCrew#39043. It adds the pin row and moves the wheel version. This PR is not set to auto-merge: the driver merges it once kirodotdev/KiroCrew#39043 has landed.

  • This PR merged first: no Kiro Crew build pins mochi yet, so a host that has the built-in is not moved, and the catalog entry and that host's install disagree until the pin lands.
  • The Kiro Crew PR merged first: a nightly host adopts at this commit while the published catalog still lists mochi as builtin, which gives an adopted record no install source for an update or a reinstall until this one lands.

Verification

  • tools/format.py: already normalized.
  • tools/validate.py: OK. The 3 warnings were already there, on other apps.
  • pytest tests/: 522 passed (with the jsonschema[format] validators installed, so the date-time and uri checks are active).
  • Kiro Crew's scripts/adoption_pin.py compute at this commit with --min-sdk-level 7 prints the pin PR's row byte for byte, and on the pin PR's tree every row, this one included, measures ok over the network.
  • The pin PR's upgrade smoke reinstalled the adopted app from the store against the published catalog with only this row changed: the trust prompt's grant bound to this repository, the install reached the pinned commit, and the watch list, settings, pins and packs were kept.

@github-actions

Copy link
Copy Markdown

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 4651a271b3612bff543346bc2caf734493cba0bf and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 4651a27

@github-actions

Copy link
Copy Markdown

Opus 5 Review — ✅ no blocking findings

Opus 5 completed its review of 4651a271b3612bff543346bc2caf734493cba0bf and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 4651a27

@github-actions

Copy link
Copy Markdown

App Readiness Review — ✅ no blocking findings

Every app repository this PR adds or re-pins passed the blocking readiness rules at 4651a271b3612bff543346bc2caf734493cba0bf.

Rules: review/app-readiness-rules.md (base-branch snapshot). This comment is updated in place on each push.

Review details

Verified against the checkout:

  • app.json read in full at repo root, well-formed.
  • R1: "entry": "dist/index.mjs" → ui/dist/index.mjs present (172936 bytes, ES module imports). assets/icon.png, assets/hero.jpg, assets/shot-1-gallery.png present. All 6 skills dirs contain SKILL.md. backend.hooks targets resolve (backend/routes.py:1069 def register_routes, backend/lifecycle.py:18/23). agents/mochi.json, agents/mochi-bg.json, backend/mcp_launch.py present. Root .gitignore and ui/.gitignore (only node_modules/) exclude nothing referenced. No setup block.
  • R2: permissions is a keyed object; every skills entry is a string; ui.entry is .mjs.
  • R3: no crons in the manifest and no cron message bodies in the tree; skill text contains no loopback address and no product-CLI credential command (the only 127.0.0.1/localhost hits are capture/, ui/tests/, and ui/src/shared/config.ts, none of them cron or skill text, and no backend.port: "auto" is declared).
  • R4: iconPath and repo-relative heroImage both present.
  • R5: no data/, .app_secret, installed.json, or app-crons.json committed; no credential-shaped matches.

No findings.

mochi @ 5db17b967894c411621ea6dcfba294da262d4173

No findings.

[APP-READINESS-REVIEWED] 4651a27

@KiroCrewCaptain
KiroCrewCaptain merged commit 8d0c020 into main Nov 18, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant