50 lines
1.2 KiB
Markdown
50 lines
1.2 KiB
Markdown
<!-- event: create author: "yoi ticket" at: 2026-06-23T19:41:51Z -->
|
|
|
|
## 作成
|
|
|
|
LocalTicketBackend によって作成されました。
|
|
|
|
---
|
|
|
|
<!-- event: intake_summary author: hare at: 2026-06-25T16:34:15Z -->
|
|
|
|
## Intake summary
|
|
|
|
Marked ready by `yoi ticket state`.
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: "yoi ticket" at: 2026-06-25T16:34:15Z from: planning to: ready reason: cli_state field: state -->
|
|
|
|
## State changed
|
|
|
|
Marked ready by `yoi ticket state`.
|
|
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: "yoi ticket" at: 2026-06-25T16:38:49Z from: ready to: planning reason: cli_state field: state -->
|
|
|
|
## State changed
|
|
|
|
State changed to `planning`.
|
|
|
|
|
|
---
|
|
|
|
<!-- event: decision author: hare at: 2026-06-25T16:38:49Z -->
|
|
|
|
## Decision
|
|
|
|
Returned to planning because the ticket is too broad in the current Runtime direction.
|
|
|
|
Planning Ticket creation from Web UI should not be a direct form-to-file mutation that bypasses Intake. The intended flow likely needs Backend embedded Runtime + Intake Worker first, then Web Intake/Planning UI on top.
|
|
|
|
Suggested split:
|
|
1. Ticket read API / list-detail UI only.
|
|
2. Backend embedded Intake Worker on worker-runtime.
|
|
3. Web Intake Console / Planning Ticket creation through Intake.
|
|
|
|
|
|
---
|