ticket: accept next queued batch
This commit is contained in:
parent
095331b06e
commit
f709fc1000
|
|
@ -0,0 +1 @@
|
|||
{"id":"orch-plan-20260614-061002-1","ticket_id":"00001KTR81P9X","kind":"accepted_plan","accepted_plan":{"summary":"Implement feature-layer dynamic provider/service lifecycle and startup dynamic tool contribution substrate after HostAuthority cleanup, preserving normal ToolRegistry/permission/history paths and leaving MCP/Plugin policy out of scope.","branch":"ticket-00001KTR81P9X-feature-provider-api","worktree":"/home/hare/Projects/yoi/.worktree/feature-provider-api","role_plan":"Coder works on pod feature API and mock provider tests; Reviewer focuses on no authority-layer regression, dynamic schema stability, permission denial path, result bounding, and provider failure diagnostics."},"author":"orchestrator","at":"2026-06-14T06:10:02Z"}
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: 'Extend pod::feature API for external protocol-backed capability providers'
|
||||
state: 'queued'
|
||||
state: 'inprogress'
|
||||
created_at: '2026-06-10T07:48:14Z'
|
||||
updated_at: '2026-06-14T06:08:25Z'
|
||||
updated_at: '2026-06-14T06:10:45Z'
|
||||
assignee: null
|
||||
readiness: 'implementation_ready'
|
||||
risk_flags: ['feature-api', 'tool-registry', 'permission-scope', 'prompt-context', 'dynamic-registry', 'service-lifecycle']
|
||||
|
|
|
|||
|
|
@ -48,4 +48,37 @@ Marked ready by `yoi ticket state`.
|
|||
Ticket を `workspace-panel` が queued にしました。
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: decision author: orchestrator at: 2026-06-14T06:10:02Z -->
|
||||
|
||||
## Decision
|
||||
|
||||
Routing decision: implementation_ready
|
||||
|
||||
Reason:
|
||||
- Ticket is queued and requirements/acceptance criteria for feature-layer provider/service lifecycle and dynamic contributions are specified.
|
||||
- Outgoing `depends_on 00001KV0SP0TY` is satisfied: HostAuthority cleanup is done and merged.
|
||||
- Relation/orchestration plan checks show no remaining blocker.
|
||||
- Scope is API/contribution substrate only; Plugin/MCP permission/trust policy remains out of scope.
|
||||
|
||||
IntentPacket:
|
||||
- Extend `pod::feature` so protocol-backed providers can contribute startup-discovered tools/services/background lifecycle diagnostics through ordinary ToolRegistry / Worker / permission / history / bounded-result paths.
|
||||
|
||||
Binding invariants:
|
||||
- Do not introduce `HostAuthority` or replacement feature-layer authority grants.
|
||||
- Do not implement MCP protocol/trust policy or Plugin permission policy here.
|
||||
- Dynamic schemas must be stable for a run; provider metadata/output is untrusted; tool calls must go through normal permission/history/result paths.
|
||||
|
||||
Validation:
|
||||
- focused feature/provider tests, affected crate tests, `cargo fmt --check`, `git diff --check`, `cargo check --workspace --all-targets`, and `nix build .#yoi` if feasible.
|
||||
|
||||
---
|
||||
|
||||
<!-- event: state_changed author: orchestrator at: 2026-06-14T06:10:45Z from: queued to: inprogress reason: orchestrator_acceptance_unblocked field: state -->
|
||||
|
||||
## State changed
|
||||
|
||||
Ticket evidence, satisfied dependency on HostAuthority cleanup, relation records, orchestration plan, and clean workspace state were checked. No blockers remain; accept for implementation before worktree/spawn side effects.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -0,0 +1 @@
|
|||
{"id":"orch-plan-20260614-061002-1","ticket_id":"00001KTZY8HK2","kind":"accepted_plan","accepted_plan":{"summary":"Remove builtin use of `yoi.profile.extend`, establish import+Lua assignment profile inheritance pattern, and make extend fail/deprecate clearly without adding scope replacement semantics.","branch":"ticket-00001KTZY8HK2-profile-extend-removal","worktree":"/home/hare/Projects/yoi/.worktree/profile-extend-removal","role_plan":"Coder updates Lua profile API/resources/tests/docs; Reviewer focuses on intended profile behavior preservation and no hidden authority merge semantics."},"author":"orchestrator","at":"2026-06-14T06:10:02Z"}
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: 'Profile extend API を廃止して import + Lua 代入に寄せる'
|
||||
state: 'queued'
|
||||
state: 'inprogress'
|
||||
created_at: '2026-06-13T07:31:09Z'
|
||||
updated_at: '2026-06-14T06:08:28Z'
|
||||
updated_at: '2026-06-14T06:10:45Z'
|
||||
assignee: null
|
||||
readiness: 'implementation_ready'
|
||||
risk_flags: ['profiles', 'lua-api', 'builtin-resources', 'migration']
|
||||
|
|
|
|||
|
|
@ -50,4 +50,36 @@ LocalTicketBackend によって作成されました。
|
|||
Ticket を `workspace-panel` が queued にしました。
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: decision author: orchestrator at: 2026-06-14T06:10:02Z -->
|
||||
|
||||
## Decision
|
||||
|
||||
Routing decision: implementation_ready
|
||||
|
||||
Reason:
|
||||
- Ticket is queued and explicitly decides to deprecate/remove `yoi.profile.extend` in favor of `yoi.profile.import` plus explicit Lua assignment.
|
||||
- Relation checks show no blocker; related launch-policy Ticket `00001KV11DHGZ` is not a dependency for this implementation.
|
||||
- Risk is bounded to Lua Profile API/resources/tests.
|
||||
|
||||
IntentPacket:
|
||||
- Migrate builtin Profile resources away from `yoi.profile.extend`, keep `import`, and make `extend` fail clearly or emit a deprecation diagnostic. Remove docs/tests that suggest scope replacement APIs.
|
||||
|
||||
Binding invariants:
|
||||
- Do not solve concrete scope/delegation authority here; that belongs to `00001KV11DHGZ`.
|
||||
- Do not add ambiguous replacement/clear API as part of `extend`.
|
||||
- Builtin resources must use import + explicit Lua assignment.
|
||||
|
||||
Validation:
|
||||
- focused profile resolution tests, resource/profile tests, `cargo fmt --check`, `git diff --check`, `cargo build -p yoi`; `nix build .#yoi` if resource packaging is affected.
|
||||
|
||||
---
|
||||
|
||||
<!-- event: state_changed author: orchestrator at: 2026-06-14T06:10:45Z from: queued to: inprogress reason: orchestrator_acceptance_unblocked field: state -->
|
||||
|
||||
## State changed
|
||||
|
||||
Ticket evidence, related records, orchestration plan, and clean workspace state were checked. No blockers remain; accept for implementation before worktree/spawn side effects.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -0,0 +1,2 @@
|
|||
{"id":"orch-plan-20260614-061023-1","ticket_id":"00001KV11DHGZ","kind":"conflicts_with","related_ticket":"00001KTZY8HK2","note":"This Ticket changes Profile concrete scope / launch policy surfaces and is likely to overlap with `00001KTZY8HK2` profile API/resource migration. Start `00001KTZY8HK2` first; re-evaluate after it merges or if explicit override is requested.","author":"orchestrator","at":"2026-06-14T06:10:23Z"}
|
||||
{"id":"orch-plan-20260614-061023-2","ticket_id":"00001KV11DHGZ","kind":"waiting_capacity_note","note":"Queued batch routing started independent Tickets `00001KTR81P9X`, `00001KTZY8HK2`, and `00001KV12W2RT`. This Ticket remains queued due to profile-surface conflict/migration ordering with `00001KTZY8HK2`, not because of missing requirements. Re-evaluate after profile extend removal branch is integrated.","author":"orchestrator","at":"2026-06-14T06:10:23Z"}
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
title: 'Profile から concrete scope を外して launch policy で付与する'
|
||||
state: 'queued'
|
||||
created_at: '2026-06-13T17:45:32Z'
|
||||
updated_at: '2026-06-14T06:08:45Z'
|
||||
updated_at: '2026-06-14T06:10:23Z'
|
||||
assignee: null
|
||||
readiness: 'implementation_ready'
|
||||
risk_flags: ['scope', 'delegation-scope', 'profiles', 'launch-policy', 'orchestrator', 'spawnpod', 'restore']
|
||||
|
|
|
|||
|
|
@ -26,4 +26,21 @@ LocalTicketBackend によって作成されました。
|
|||
Ticket を `workspace-panel` が queued にしました。
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: decision author: orchestrator at: 2026-06-14T06:10:23Z -->
|
||||
|
||||
## Decision
|
||||
|
||||
Routing decision: queued_waiting_conflict
|
||||
|
||||
Reason:
|
||||
- Ticket is queued and appears implementation-ready, but it touches Profile concrete scope / launch policy surfaces.
|
||||
- `00001KTZY8HK2` was also queued and accepted in this routing pass for Profile API/resource migration (`extend` removal). Running both profile-surface migrations in parallel is likely to create merge conflicts and unclear review boundaries.
|
||||
- No missing requirement or dependency blocker was identified; this is a conflict/migration-order wait.
|
||||
|
||||
Next action:
|
||||
- Keep queued for now.
|
||||
- Re-evaluate after `00001KTZY8HK2` is merged/validated, or if human explicitly authorizes parallel work despite conflict risk.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -0,0 +1 @@
|
|||
{"id":"orch-plan-20260614-061002-1","ticket_id":"00001KV12W2RT","kind":"accepted_plan","accepted_plan":{"summary":"Implement two-line Workspace Panel Ticket rows with separated canonical state and derived gate/action information, preserving logical selection and mouse/wheel behavior.","branch":"ticket-00001KV12W2RT-panel-ticket-two-line-rows","worktree":"/home/hare/Projects/yoi/.worktree/panel-ticket-two-line-rows","role_plan":"Coder updates TUI row rendering/selection/tests; Reviewer focuses on lifecycle-state correctness, relation gate presentation, mouse click mapping, and E2E expectation updates."},"author":"orchestrator","at":"2026-06-14T06:10:02Z"}
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: 'Panel Ticket rows を2行表示にして gate 情報を分離する'
|
||||
state: 'queued'
|
||||
state: 'inprogress'
|
||||
created_at: '2026-06-13T18:10:57Z'
|
||||
updated_at: '2026-06-14T06:08:41Z'
|
||||
updated_at: '2026-06-14T06:10:45Z'
|
||||
assignee: null
|
||||
readiness: 'implementation_ready'
|
||||
risk_flags: ['tui', 'workspace-panel', 'ticket-relations', 'mouse-input', 'layout']
|
||||
|
|
|
|||
|
|
@ -13,4 +13,36 @@ LocalTicketBackend によって作成されました。
|
|||
Ticket を `workspace-panel` が queued にしました。
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: decision author: orchestrator at: 2026-06-14T06:10:02Z -->
|
||||
|
||||
## Decision
|
||||
|
||||
Routing decision: implementation_ready
|
||||
|
||||
Reason:
|
||||
- Ticket is queued and specifies a bounded Workspace Panel row layout change: two-line Ticket rows separating canonical state from derived gate/action/reason.
|
||||
- Relation checks show related examples only, no blockers. `00001KV10SN02` E2E mouse/wheel coverage is done and can be updated as needed.
|
||||
- Risk is TUI layout/mouse selection; acceptance criteria are concrete.
|
||||
|
||||
IntentPacket:
|
||||
- Render Ticket rows as two visual lines, use `|` selected grouping marker, show canonical state/title on line 1 and id/gate/action/reason on line 2, and adjust selection/mouse/scrolling logic accordingly.
|
||||
|
||||
Binding invariants:
|
||||
- Do not add persisted `waiting` state or change Ticket lifecycle.
|
||||
- Normal relation waits are gate information, not error/human-reply styling.
|
||||
- Mouse click on either visual line selects the same logical Ticket and does not dispatch actions.
|
||||
|
||||
Validation:
|
||||
- focused TUI row/layout/mouse tests, affected E2E if practical, `cargo build -p yoi`, `git diff --check`, `cargo fmt --check`; `nix build .#yoi` if feasible.
|
||||
|
||||
---
|
||||
|
||||
<!-- event: state_changed author: orchestrator at: 2026-06-14T06:10:45Z from: queued to: inprogress reason: orchestrator_acceptance_unblocked field: state -->
|
||||
|
||||
## State changed
|
||||
|
||||
Ticket evidence, related records, orchestration plan, and clean workspace state were checked. No blockers remain; accept for implementation before worktree/spawn side effects.
|
||||
|
||||
---
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user