[warren830]

Lists aidlc-studio as a git-source entry in catalog/official-registry.json.

AI-DLC Studio is the visual operating surface for AI-DLC Workflows. Every AI-DLC approval gate, structured question and recovery decision across the owner's registered repositories lands in one Action Center, with the produced artifacts, acceptance criteria and reviewer findings shown beside it. It also provides a five-phase Workflow Map, a plan composer and a transactional installer for the bundled AI-DLC Kiro harness. Decisions travel through the intent's own conversation, and Studio never edits AI-DLC's state, audit or cursor files.

What I verified

I cloned https://github.com/warren830/kirocrew-app-aidlc at v1.0.1 (26b36c4) with --depth 1 --branch v1.0.1 and read the app.json the store will bake its copy from. Display copy is therefore absent from this entry by contract.

• R1: installable by plain clone. Every manifest-referenced path is committed at that tag: ui/dist/index.mjs (ui.entry), ui/icon.svg (ui.pages[].iconUrl), backend/routes.py and backend/hooks.py for the three backend.hooks entry points, and agents/advisor.json. ui/dist/ is not gitignored. There are no skills and no setup scripts, and no build step runs at install time.
• R2: shapes. permissions is a dimension-keyed object, and ui.entry names an .mjs ES module.
• R4: assets. All are raster and repo-relative. assets/icon-512.png is 512×512 (2.8 KiB). assets/hero-{light,dark}.png are 1600×900 and assets/hero-detail-{light,dark}.png are 1600×384 (25:6), each 33–152 KiB. Three screenshots are 120–200 KiB each. The published summary is the manifest description's first sentence, 189 characters, under SUMMARY_MAX.
• R5: hygiene. No data/, .app_secret, installed.json or app-crons.json in the tree.
• Real resolve and bake. I ran publish.build_registry on this entry alone, with the real resolve_commit and fetch_manifest. It returned zero errors and zero warnings, ref resolved to 26b36c4a4ab0a73088a09c5a0e93a60260699e30, and the hero, detail and screenshot refs were all picked up.

Gate

python tools/validate.py        # OK: catalog is valid (3 warnings)
python tools/format.py --check  # all 3 file(s) normalized
pytest tests/ -q                # 521 passed, 1 failed

The 3 validator warnings are pre-existing on main and concern other apps' secondary categories. This entry adds none.

The one failing test, test_publish_fails_closed_without_a_key, runs a real publish() over the whole catalog. On my network, git ls-remote against GitHub intermittently fails with LibreSSL SSL_ERROR_SYSCALL, and each run failed on a different, already-listed repository (launchdarkly-kiro-crew-app, then kirodotdev/KiroCrew), never on this entry. The same suite passed in full (522) on an earlier run. CI should give the clean verdict.

Notes for the curator

• The primary category is developer-tools, and it is the only one, so the rail stays a partition.
• The entry pins the v1.0.1 release tag, not a branch, so the pin cannot move under the app-readiness review.
• This app is not read-only. It installs the bundled AI-DLC harness into repositories the owner explicitly registers, transactionally, with a receipt per owned file and rollback. When the owner confirms a decision, it sends the owner's gate decision text to the intent's chat session from the owner's own dashboard session. It registers in-gateway Python backend routes, so it needs a trust grant (agent.apps_trusted) for aidlc-studio only. No blanket third-party trust is asked for anywhere.
• Declared permissions beyond its own routes are /api/chat (the human-submission lane), /api/ask-question (reading pending question cards), events, storage and spawn. spawn is for an on-demand Advisor agent whose only tool is thinking. network: false, cron: false, no MCP server.
• It never runs a git write. An argv allowlist refuses git writes at call time, and a static grep in the app's own test suite keeps them out of the backend.
• The bundled third-party content is the AI-DLC Workflows 2.7.1 Kiro distribution (MIT-0), inventoried with SHA-256 in payload/manifest.json. Studio's local compatibility patches are listed in THIRD_PARTY_NOTICES.md.
• Validated on macOS. Linux has not been validated end to end, and the README says so.
• I am the app's author, so treat the author block as a proposal and adjust it if the curated form should differ.