From 1af710e9982434a04ca1b31149a4fde1c9539053 Mon Sep 17 00:00:00 2001 From: Hare Date: Mon, 8 Jun 2026 07:43:30 +0900 Subject: [PATCH] ticket: route yaml frontmatter parsing preflight --- .../item.md | 6 ++- .../thread.md | 54 +++++++++++++++++++ 2 files changed, 58 insertions(+), 2 deletions(-) diff --git a/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/item.md b/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/item.md index 6c511015..692a9824 100644 --- a/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/item.md +++ b/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/item.md @@ -6,11 +6,13 @@ status: open kind: task priority: P1 labels: [ticket, yaml, parser, bug, panel] -workflow_state: intake +workflow_state: queued created_at: 2026-06-07T22:32:33Z -updated_at: 2026-06-07T22:32:33Z +updated_at: 2026-06-07T22:43:24Z assignee: null legacy_ticket: null +queued_by: workspace-panel +queued_at: 2026-06-07T22:43:03Z --- ## Background diff --git a/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/thread.md b/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/thread.md index 9c56f87d..b67f45be 100644 --- a/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/thread.md +++ b/.yoi/tickets/open/20260607-223233-parse-ticket-frontmatter-as-yaml/thread.md @@ -5,3 +5,57 @@ Created by LocalTicketBackend create. --- + + + +## Intake summary + +Existing Ticket is sufficiently specified and not a duplicate of another visible active Ticket. Intake classifies it as implementation_ready with needs_preflight=true because it changes durable Ticket frontmatter parsing and compatibility semantics. Risk flags: ticket-backend, yaml-parsing, compatibility, panel-regression. Scope is limited to YAML/null-aware Ticket item.md parsing, list/bool handling, preserving emitted format/doctor compatibility, and the workspace panel attention_required:null regression. Validation should include focused ticket parser tests, workspace_panel regression tests, cargo fmt --check, git diff --check, and relevant cargo test commands; final implementation should also consider the project-level nix build requirement. + +--- + + + +## State changed + +Intake completed: requirements, acceptance criteria, non-goals, affected fields, and validation are explicit enough for Orchestrator routing. Human queueing remains required before implementation starts. + +--- + + + +## State changed + +Ticket queued for Orchestrator routing. + + +--- + + + +## Decision + +Routing decision: preflight_needed + +Reason: +- The Ticket is well scoped and urgent, but it changes durable Ticket frontmatter parsing and compatibility semantics. +- Intake explicitly classified it as implementation-ready only with `needs_preflight=true`, with risk flags `ticket-backend`, `yaml-parsing`, `compatibility`, and `panel-regression` in the intake summary. +- YAML/null-aware parsing affects nullable strings, lists, booleans, doctor compatibility, existing fixture behavior, and workspace panel action derivation; a short design boundary check should precede coder delegation. + +Evidence checked: +- Ticket body requirements, candidate affected fields, non-goals, and acceptance criteria. +- Intake summary and `ready -> queued` event. +- Workspace state: `develop` has only this Ticket's queued item/thread modifications plus an unrelated untracked Ticket directory `20260607-224309-reduce-ticket-lifecycle-commit-noise`; no branch/worktree exists for this slug. +- Visible Pods: intake peer for this Ticket is idle; no coder/reviewer Pods are active for this Ticket. + +Next action: +- Run `ticket-preflight-workflow` before implementation delegation. +- Preflight should decide the parsing boundary: whether to deserialize `item.md` frontmatter through `serde_yaml::Value`/typed helpers or a narrower YAML-compatible layer; how to preserve emitted format; how to represent quoted literal `"null"` versus YAML null; and which tests cover Ticket parser plus workspace panel regression. +- Do not transition `queued -> inprogress`, create `.worktree/parse-ticket-frontmatter-as-yaml`, or spawn coder/reviewer Pods until preflight records implementation readiness. + +Escalate if: +- Existing Ticket records rely on raw-string parsing semantics that conflict with YAML behavior. +- Adding a YAML parser dependency has packaging/licensing implications not already acceptable for this crate graph. +- Fixing panel action derivation requires broader Ticket workflow/action model changes beyond parsing correctness. + +---