Skip to content

feat: list agent-worlds and ops-mission-control from their own repositories - #86

Merged
KiroCrewCaptain merged 1 commit into
mainfrom
feat/pin-agent-worlds-omc
Nov 17, 2026
Merged

KiroCrewCaptain merged 1 commit into
mainfrom
feat/pin-agent-worlds-omc

Conversation

@bolichen97

Copy link
Copy Markdown
Collaborator

What

Flips agent-worlds and ops-mission-control in catalog/official-registry.json from a builtin source to a git source in their own KiroCrewCaptain repositories, each pinned at the commit Kiro Crew's adoption pin table names for it in kirodotdev/KiroCrew#38443:

App Repository ref Version
agent-worlds https://github.com/KiroCrewCaptain/kirocrew-app-agent-worlds 433c1e48900b816aa7ff87f400adc6d5dec2eff4 1.0.2
ops-mission-control https://github.com/KiroCrewCaptain/kirocrew-app-ops-mission-control 92e26de80e09f5ce1cbb2051eab43bd5c919eb31 0.1.2

Each 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.

Each commit is the head of its repository's main, with green CI on ubuntu, macOS and Windows plus the reproducible-bundle, README and internal-content jobs.

Merge condition: right after the Kiro Crew pin PR

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

  • This PR merged first: no Kiro Crew build pins either app 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 these commits while the published catalog still lists both as builtin, which gives an adopted record no install source for an update or a reinstall until this one lands.

Verification

  • tools/format.py --check: 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).
  • Kiro Crew's scripts/adoption_pin.py compute at each commit prints the row the pin PR commits.
  • The pin PR's upgrade smoke ran reinstall of each adopted app against the published catalog with only that app's row changed as here: both reached the pinned commit, kept their data (and Ops Mission Control its provider token), and left one record.

…tories

Both former built-ins switch from a builtin source to a git source in
their KiroCrewCaptain repositories, pinned at the commits Kiro Crew's
adoption pin table names for them in kirodotdev/KiroCrew#38443:
agent-worlds 433c1e48900b (1.0.2) and ops-mission-control
92e26de80e09 (0.1.2). Each row gets the note the other adopted apps
carry and the KiroCrewCaptain author URL.
@github-actions

Copy link
Copy Markdown

GPT 5.6 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] adf8aaf

@github-actions

Copy link
Copy Markdown

Opus 5 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] adf8aaf

@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 adf8aaf0f2b0a8427d10b6690cfaa480e6a7c535.

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

Review details

Both manifests verified against every rule. Summary of what I probed:

  • agent-worlds/app.json — valid JSON; ui.entry: "dist/index.mjs" → agent-worlds/ui/dist/index.mjs present; ui/.gitignore is node_modules/ only (dist not excluded); permissions is a dimension-keyed object; iconPath: "assets/icon.png" and heroImage/heroImageDark/detail variants all exist repo-relative; no skills/backend/setup/crons; no data/, .app_secret, installed.json, app-crons.json.
  • ops-mission-control/app.json — valid JSON; ui.entry → ui/dist/index.mjs present; skills: ["skills/ops-mission-control"] is a plain string and that dir contains SKILL.md; permissions object; backend.hooks.routes: "backend.routes:register_routes" (not a top-level backend.routes) and register_routes is defined at backend/routes.py:491; all four crons carry "silent": true and "persistent_session": false; no 127.0.0.1:<port> and no manifest backend.port; no CLI+credential-verb instruction and no "if blocked by security policy" hedge in any cron message or SOP; iconPath/heroImage present and repo-relative; no install-time state artifacts; the only credential-shaped strings are AWS's published [REDACTED-AWS-KEY-ID] documentation placeholder and fake tokens inside redaction tests.

No findings.

agent-worlds @ 433c1e48900b816aa7ff87f400adc6d5dec2eff4

No findings.

ops-mission-control @ 92e26de80e09f5ce1cbb2051eab43bd5c919eb31

No findings.

[APP-READINESS-REVIEWED] adf8aaf

@KiroCrewCaptain
KiroCrewCaptain merged commit 52c80a6 into main Nov 17, 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.

2 participants