Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

ticket: dispatch plugin cli inspection review

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-19 20:03:57 +09:00
parent 83699e2011
commit 349a55fa33
No known key found for this signature in database
2 changed files with 30 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/00001KVFD3YSV/item.md
View File

@ -2,7 +2,7 @@
title: 'Plugin: add read-only CLI inspection list/show'
state: 'inprogress'
created_at: '2026-06-19T07:39:23Z'
updated_at: '2026-06-19T11:03:00Z'
updated_at: '2026-06-19T11:03:51Z'
assignee: null
readiness: 'implementation_ready'
risk_flags: ['plugin', 'cli', 'diagnostics', 'read-only', 'json-output', 'no-execution']

29
.yoi/tickets/00001KVFD3YSV/thread.md
View File

@ -184,3 +184,32 @@ Next action:
- 特に read-only/no-execution、JSON typed structure、bounded diagnostics、grant mismatch/no grant/invalid/ambiguous ref coverage、secrets leakage avoidance、product CLI / lower crate boundary、future host API extension point を確認する。
---
<!-- event: plan author: yoi-orchestrator at: 2026-06-19T11:03:51Z -->
## Plan
Review dispatch:
Reviewer Pod `yoi-reviewer-00001KVFD3YSV` を read-only scope で起動した。
Review target:
- worktree: `/home/hare/Projects/yoi/.worktree/00001KVFD3YSV-plugin-cli-inspection`
- branch: `impl/00001KVFD3YSV-plugin-cli-inspection`
- commit: `462de32a`
Reviewer focus:
- recorded intent / invariants / acceptance criteria に対する適合性。
- `yoi plugin list` / `yoi plugin show <ref>` と `--json` が read-only typed inspection surface になっていること。
- Plugin WASM / Tool code / hooks / services / ingress を実行していないこと。
- human output が typed report の thin formatting であり、JSON structure が stable であること。
- active / disabled / missing / rejected / partial の status vocabulary と package/tool-level outcome が適切であること。
- missing ref / ambiguous unqualified ref / invalid manifest / digest-version-source mismatch / missing grant-denied permission / unsupported permission diagnostics が bounded かつ安全であること。
- secrets/raw untrusted content leakage がないこと。
- product CLI ownership と lower-crate boundary が保たれていること。
- future `https` / `fs` host API Tickets が inspection output を拡張しやすいこと。
Next:
- Reviewer output を確認し、approve なら Orchestrator worktree へ merge/validation/cleanup/close-ready 処理へ進む。request_changes なら blocker を記録して Coder に戻す。
---