ticket: migrate open tickets to planning state

This commit is contained in:
2026-06-08 19:22:03 +09:00
parent 603af8bd3b
commit 07f8b3cb8a
30 changed files with 84 additions and 52 deletions
@@ -8,7 +8,7 @@ priority: P1
labels: [ticket, workflow-state, orchestrator, panel, intake, planning]
workflow_state: 'done'
created_at: 2026-06-07T22:54:48Z
updated_at: '2026-06-08T09:19:17Z'
updated_at: '2026-06-08T10:19:05Z'
assignee: null
legacy_ticket: null
queued_by: 'workspace-panel'
@@ -464,4 +464,23 @@ Residual notes:
- Historical `.yoi/tickets/**` records still contain old `Preflight`, `preflight_needed`, and `needs_preflight` text as durable audit/history artifacts; they were intentionally not rewritten.
- `ticket-preflight-workflow` filename remains as a compatibility slug, but its content now explicitly describes planning/requirements sync rather than a separate workflow state/lane/long-lived operation.
---
<!-- event: decision author: hare at: 2026-06-08T10:19:05Z -->
## Decision
## Local migration and compatibility direction
After the local Ticket record migration, do not preserve long-term compatibility for state-as-`intake` or `needs_preflight` / `preflight_needed` records.
Direction:
- migrate open local Ticket records to explicit `workflow_state: planning`;
- remove legacy preflight frontmatter fields from open Ticket records;
- treat any remaining historical mentions in thread logs as audit history, not current workflow inputs;
- update code/prompts/workflows toward the new model rather than adding broad compatibility branches for the old local data shape.
Compatibility should be limited to bounded migration/error diagnostics where needed, not a permanent runtime surface.
---