From 5f7f81bdde0e6d347ff31f7a6af18dd7e0587d6d Mon Sep 17 00:00:00 2001 From: Hare Date: Sat, 20 Jun 2026 13:54:09 +0900 Subject: [PATCH] ticket: accept plugin rust pdk templates --- .../artifacts/orchestration-plan.jsonl | 1 + .yoi/tickets/00001KVHKWNQA/item.md | 4 +- .yoi/tickets/00001KVHKWNQA/thread.md | 75 +++++++++++++++++++ 3 files changed, 78 insertions(+), 2 deletions(-) create mode 100644 .yoi/tickets/00001KVHKWNQA/artifacts/orchestration-plan.jsonl diff --git a/.yoi/tickets/00001KVHKWNQA/artifacts/orchestration-plan.jsonl b/.yoi/tickets/00001KVHKWNQA/artifacts/orchestration-plan.jsonl new file mode 100644 index 00000000..960f4dad --- /dev/null +++ b/.yoi/tickets/00001KVHKWNQA/artifacts/orchestration-plan.jsonl @@ -0,0 +1 @@ +{"id":"orch-plan-20260620-045332-1","ticket_id":"00001KVHKWNQA","kind":"accepted_plan","accepted_plan":{"summary":"Component Model Tool authoring用の first-party Rust PDK crate と embedded `rust-component-tool` template を追加する。PDK は guest-side only とし、raw pointer/length ABI を隠し、typed JSON helper / ToolError / ToolContext / WIT binding glue を提供する。crates.io 公開・remote template fetch・authoring CLI implementation は含めない。","branch":"impl/00001KVHKWNQA-plugin-rust-pdk-templates","worktree":"/home/hare/Projects/yoi/.worktree/00001KVHKWNQA-plugin-rust-pdk-templates","role_plan":"Orchestrator は queued acceptance を記録・commit 後、専用 implementation worktree を `.worktree/00001KVHKWNQA-plugin-rust-pdk-templates` に作成し、Coder をその child worktree への narrow write scope で起動する。Coder 実装後、Reviewer が PDK guest-only boundary、Component Model runtime compatibility、template/resource packaging、docs/tests/Nix impact を確認する。"},"author":"yoi-orchestrator","at":"2026-06-20T04:53:32Z"} diff --git a/.yoi/tickets/00001KVHKWNQA/item.md b/.yoi/tickets/00001KVHKWNQA/item.md index 050266a0..487d219d 100644 --- a/.yoi/tickets/00001KVHKWNQA/item.md +++ b/.yoi/tickets/00001KVHKWNQA/item.md @@ -1,8 +1,8 @@ --- title: 'Plugin: add Rust PDK and embedded authoring templates for Component Model Tools' -state: 'queued' +state: 'inprogress' created_at: '2026-06-20T04:16:14Z' -updated_at: '2026-06-20T04:52:58Z' +updated_at: '2026-06-20T04:54:04Z' assignee: null readiness: 'implementation_ready' risk_flags: ['plugin', 'pdk', 'component-model', 'authoring', 'templates', 'sdk', 'no-crates-io'] diff --git a/.yoi/tickets/00001KVHKWNQA/thread.md b/.yoi/tickets/00001KVHKWNQA/thread.md index d58dbfa9..e091d5a4 100644 --- a/.yoi/tickets/00001KVHKWNQA/thread.md +++ b/.yoi/tickets/00001KVHKWNQA/thread.md @@ -13,4 +13,79 @@ LocalTicketBackend によって作成されました。 Ticket を `workspace-panel` が queued にしました。 +--- + + + +## Decision + +Routing decision: implementation_ready + +Reason: +- Panel Queue により、この Ticket は Orchestrator routing 対象として明示許可された。 +- Ticket body は Rust PDK crate、guest-side only boundary、ergonomic Tool helpers、Component Model binding glue、embedded `rust-component-tool` template、docs/tests/validation/non-goals を実装可能な粒度で定義している。 +- Blocking dependency `00001KVG0HR96` Component Model runtime は closed。Component runtime は explicit `wasm-component` metadata、ToolRegistry path、grant enforcement、no ambient WASI、resource limits、WIT files を含めて完了済み。 +- Incoming dependency from `00001KVHKWNQS` は、この Ticket が将来の authoring CLI Ticket を unblock する関係であり、本 Ticket の blocker ではない。 +- Related Plugin CLI / HTTPS / FS Tickets は closed または non-blocking context。 +- 現在 queued はこの Ticket のみ、inprogress は 0 件、child implementation Pods はなし、matching branch/worktree はなし、Orchestrator worktree は clean。 +- Risk domain は plugin / pdk / component-model / authoring / templates / sdk / no-crates-io だが、Ticket は no crates.io publication、no remote template fetch、guest-side only、no ambient authority、host-side grants remain authority などの invariants を明示している。bounded context check 後も implementation 前に必要な追加 human decision は見つからなかった。 + +Evidence checked: +- Ticket `00001KVHKWNQA` body / thread / relations / artifacts。 +- `TicketRelationQuery(00001KVHKWNQA)`: outgoing `depends_on` target `00001KVG0HR96` is closed。incoming `00001KVHKWNQS depends_on this` is not a blocker。 +- `TicketOrchestrationPlanQuery(00001KVHKWNQA)`: no previous plan records; accepted plan was recorded now。 +- Workspace state: + - Orchestrator worktree clean at `9ca2f85b`。 + - queued: this Ticket only。 + - inprogress: 0。 + - visible Pods: self + peers only; spawned children 0。 + - no matching implementation branch/worktree。 +- Code/resource context: + - `resources/plugin/wit/yoi-plugin-tool-v1.wit` and `resources/plugin/wit/yoi-host-v1.wit` exist from the Component runtime work。 + - `docs/development/plugin-development.md` is the current Plugin development guide target。 + - Cargo workspace has no existing `crates/plugin-pdk` crate。 + +IntentPacket: + +Intent: +- Add a first-party Rust PDK for Component Model Tool Plugins and an embedded starter template so authors can implement Yoi Plugin Tools without raw pointer/length ABI plumbing or remote template fetches。 +- Position Component Model + PDK as preferred authoring path while keeping raw core-Wasm ABI as compatibility/transitional runtime support。 + +Binding decisions / invariants: +- PDK is guest-side only。It must not depend on host runtime crates such as `pod`, `llm-worker`, `tui`, or `client`。 +- PDK must not grant or imply authority。Host-side Plugin manifest grants remain the authority boundary for Tool execution / HTTPS / FS host APIs。 +- No ambient fs/network/env authority is introduced。 +- Do not publish to crates.io and do not implement remote template fetch。 +- Do not implement `yoi plugin new/check/pack` in this Ticket; embedded resources should be suitable for that future Ticket。 +- Template dependency policy must support checkout/dev local path dependency and document a future out-of-tree git `rev` pattern。 +- PDK should target the current Component Model Tool world (`yoi:plugin/tool@1.0.0`) and runtime ToolOutput JSON bridge。 +- Prefer minimal, testable helper APIs over broad macro magic。 + +Requirements / acceptance criteria: +- Add workspace crate `yoi-plugin-pdk` under `crates/plugin-pdk` or a justified equivalent。 +- Provide typed JSON input parsing, output serialization, structured/bounded `ToolError`, `ToolContext` with at least tool name, and helper equivalent to `run_json_tool` producing ToolOutput JSON accepted by the current runtime。 +- Provide WIT binding glue/re-export/wrapper enough that authors do not hand-write raw pointer/length ABI code。 +- Add embedded template under `resources/plugin/templates/rust-component-tool/` with `Cargo.toml`, `src/lib.rs`, `plugin.toml`, and README/next steps。 +- Include example or fixture Plugin using the PDK。 +- Update Plugin development docs and explain publication/template-fetch deferrals。 +- Tests cover PDK happy/error paths, template/sample fixture validation, runtime acceptance if feasible, and no host-runtime crate dependency。 +- Validation includes focused PDK/plugin tests, `cargo fmt --check`, relevant `cargo check`/`cargo test`, `git diff --check`, and `nix build .#yoi` because workspace/package/resources may change。 + +Escalate if: +- Current WIT/runtime shape cannot support a guest-side helper without changing the Component runtime contract。 +- A full sample component build requires external tooling that cannot be kept deterministic in this repo。 +- Keeping the PDK guest-only would require undesirable dependencies on host crates。 +- Template/resource packaging needs a broader CLI/resource architecture decision。 + +Next action: +- Record `queued -> inprogress` and commit Ticket records before creating the implementation worktree and spawning Coder。 + +--- + + + +## State changed + +Ticket body/thread, relation metadata, Component Model runtime dependency state, related completed Tickets, Orchestrator worktree state, visible Pods, existing branch/worktree, and bounded resource/code context were checked. Dependency `00001KVG0HR96` is closed, no inprogress/capacity blocker exists, and no missing planning decision was found. Accepting this queued Ticket for implementation before worktree/Pod side effects. + ---