ticket: close merged queued tickets
This commit is contained in:
parent
e6bae0429f
commit
208f7b3eaa
|
|
@ -2,13 +2,13 @@
|
|||
id: 20260607-035710-ticket-orchestration-plan-tool
|
||||
slug: ticket-orchestration-plan-tool
|
||||
title: Ticket orchestration plan tool
|
||||
status: open
|
||||
status: 'closed'
|
||||
kind: task
|
||||
priority: P1
|
||||
labels: [ticket, orchestrator, planning, workflow, tools]
|
||||
workflow_state: 'inprogress'
|
||||
workflow_state: 'done'
|
||||
created_at: 2026-06-07T03:57:10Z
|
||||
updated_at: '2026-06-08T13:23:45Z'
|
||||
updated_at: '2026-06-08T23:36:49Z'
|
||||
assignee: null
|
||||
queued_by: 'workspace-panel'
|
||||
queued_at: '2026-06-08T11:21:13Z'
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
Implemented, reviewed, merged, and validated.
|
||||
|
||||
Summary:
|
||||
- Added a lightweight Ticket-domain orchestration plan/note surface.
|
||||
- Added per-Ticket typed JSONL artifact storage at `artifacts/orchestration-plan.jsonl`.
|
||||
- Added backend append/query APIs for orchestration plan records.
|
||||
- Added LLM tools `TicketOrchestrationPlanRecord` and `TicketOrchestrationPlanQuery`.
|
||||
- Query is available in the read-only Ticket tool set; record creation is in the mutating/lifecycle Ticket tool set.
|
||||
- Supported plan kinds cover ordering, dependency, conflict, waiting/capacity notes, and accepted-plan summaries.
|
||||
- Updated Orchestrator routing workflow guidance to consult and record orchestration plan records before queued acceptance where relevant.
|
||||
|
||||
Implementation:
|
||||
- Coder commit: `b28b775 ticket: add orchestration plan tools`
|
||||
- Reviewer approved with no blocking findings.
|
||||
- Merge commit: `b3eab44 merge: add ticket orchestration plan tools`
|
||||
|
||||
Validation after merge:
|
||||
- `cargo fmt --check`
|
||||
- `git diff --check`
|
||||
- `cargo run -q -p yoi -- ticket doctor`
|
||||
- `cargo check --workspace`
|
||||
- `nix build .#yoi`
|
||||
|
|
@ -338,4 +338,43 @@ Residual risks / notes:
|
|||
- This is intentionally execution-plan metadata, not intrinsic project-level Ticket relations. `typed-ticket-relation-metadata` remains separate.
|
||||
- Final merge/close/cleanup is intentionally not performed here without explicit merge approval.
|
||||
|
||||
---
|
||||
|
||||
<!-- event: state_changed author: hare at: 2026-06-08T23:36:49Z from: inprogress to: done reason: closed field: workflow_state -->
|
||||
|
||||
## State changed
|
||||
|
||||
Ticket closed; workflow_state を done に設定しました。
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: close author: hare at: 2026-06-08T23:36:49Z status: closed -->
|
||||
|
||||
## 完了
|
||||
|
||||
Implemented, reviewed, merged, and validated.
|
||||
|
||||
Summary:
|
||||
- Added a lightweight Ticket-domain orchestration plan/note surface.
|
||||
- Added per-Ticket typed JSONL artifact storage at `artifacts/orchestration-plan.jsonl`.
|
||||
- Added backend append/query APIs for orchestration plan records.
|
||||
- Added LLM tools `TicketOrchestrationPlanRecord` and `TicketOrchestrationPlanQuery`.
|
||||
- Query is available in the read-only Ticket tool set; record creation is in the mutating/lifecycle Ticket tool set.
|
||||
- Supported plan kinds cover ordering, dependency, conflict, waiting/capacity notes, and accepted-plan summaries.
|
||||
- Updated Orchestrator routing workflow guidance to consult and record orchestration plan records before queued acceptance where relevant.
|
||||
|
||||
Implementation:
|
||||
- Coder commit: `b28b775 ticket: add orchestration plan tools`
|
||||
- Reviewer approved with no blocking findings.
|
||||
- Merge commit: `b3eab44 merge: add ticket orchestration plan tools`
|
||||
|
||||
Validation after merge:
|
||||
- `cargo fmt --check`
|
||||
- `git diff --check`
|
||||
- `cargo run -q -p yoi -- ticket doctor`
|
||||
- `cargo check --workspace`
|
||||
- `nix build .#yoi`
|
||||
|
||||
|
||||
---
|
||||
|
|
@ -2,13 +2,13 @@
|
|||
id: '20260608-103133-tui-chat-markdown-table-rendering'
|
||||
slug: 'tui-chat-markdown-table-rendering'
|
||||
title: 'TUI chat view should render Markdown tables'
|
||||
status: 'open'
|
||||
status: 'closed'
|
||||
kind: 'bug'
|
||||
priority: 'P2'
|
||||
labels: ['tui', 'chat', 'markdown', 'rendering', 'ux']
|
||||
workflow_state: 'inprogress'
|
||||
workflow_state: 'done'
|
||||
created_at: '2026-06-08T10:31:33Z'
|
||||
updated_at: '2026-06-08T13:29:26Z'
|
||||
updated_at: '2026-06-08T23:36:49Z'
|
||||
assignee: null
|
||||
risk_flags: ['tui-rendering', 'markdown']
|
||||
queued_by: 'workspace-panel'
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
Implemented, reviewed, merged, and validated.
|
||||
|
||||
Summary:
|
||||
- Enabled Markdown table parsing in the existing TUI chat/conversation Markdown renderer.
|
||||
- Rendered ordinary pipe tables as readable monospace rows with separators and alignment-aware padding.
|
||||
- Kept the change in display/rendering code only; no Pod history, session logs, worker history, prompt context, or stored message text mutation.
|
||||
- Added focused tests for readable table rendering, ragged/wide table safety, and non-table pipe text regression.
|
||||
|
||||
Implementation:
|
||||
- Coder commit: `f767ec7 tui: render markdown pipe tables in chat`
|
||||
- Reviewer approved with no blocking findings.
|
||||
- Merge commit: `e6bae04 merge: render tui markdown tables`
|
||||
|
||||
Validation after merge:
|
||||
- `cargo fmt --check`
|
||||
- `git diff --check`
|
||||
- `cargo run -q -p yoi -- ticket doctor`
|
||||
- `cargo check --workspace`
|
||||
- `nix build .#yoi`
|
||||
|
|
@ -198,4 +198,40 @@ Residual risks / notes:
|
|||
- This is intentionally a pragmatic table renderer, not a full GFM table compatibility project.
|
||||
- Final merge/close/cleanup is intentionally not performed here without explicit merge approval.
|
||||
|
||||
---
|
||||
|
||||
<!-- event: state_changed author: hare at: 2026-06-08T23:36:49Z from: inprogress to: done reason: closed field: workflow_state -->
|
||||
|
||||
## State changed
|
||||
|
||||
Ticket closed; workflow_state を done に設定しました。
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: close author: hare at: 2026-06-08T23:36:49Z status: closed -->
|
||||
|
||||
## 完了
|
||||
|
||||
Implemented, reviewed, merged, and validated.
|
||||
|
||||
Summary:
|
||||
- Enabled Markdown table parsing in the existing TUI chat/conversation Markdown renderer.
|
||||
- Rendered ordinary pipe tables as readable monospace rows with separators and alignment-aware padding.
|
||||
- Kept the change in display/rendering code only; no Pod history, session logs, worker history, prompt context, or stored message text mutation.
|
||||
- Added focused tests for readable table rendering, ragged/wide table safety, and non-table pipe text regression.
|
||||
|
||||
Implementation:
|
||||
- Coder commit: `f767ec7 tui: render markdown pipe tables in chat`
|
||||
- Reviewer approved with no blocking findings.
|
||||
- Merge commit: `e6bae04 merge: render tui markdown tables`
|
||||
|
||||
Validation after merge:
|
||||
- `cargo fmt --check`
|
||||
- `git diff --check`
|
||||
- `cargo run -q -p yoi -- ticket doctor`
|
||||
- `cargo check --workspace`
|
||||
- `nix build .#yoi`
|
||||
|
||||
|
||||
---
|
||||
Loading…
Reference in New Issue
Block a user