close: pod orchestration guidance
This commit is contained in:
parent
b7cbf05305
commit
f858f48c34
|
|
@ -2,12 +2,12 @@
|
|||
id: 20260527-194421-pod-orchestration-system-guidance
|
||||
slug: pod-orchestration-system-guidance
|
||||
title: Pod orchestration tool availability に応じた system guidance
|
||||
status: open
|
||||
status: closed
|
||||
kind: feature
|
||||
priority: P2
|
||||
labels: [pod, workflow, prompt]
|
||||
created_at: 2026-05-27T19:44:21Z
|
||||
updated_at: 2026-06-01T01:24:27Z
|
||||
updated_at: 2026-06-01T01:24:59Z
|
||||
assignee: null
|
||||
legacy_ticket: null
|
||||
---
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
Merged and completed.
|
||||
|
||||
Implementation:
|
||||
- Added resource-backed Pod orchestration guidance at `resources/prompts/common/pod-orchestration.md`.
|
||||
- Registered the guidance through the prompt catalog and internal prompt resources.
|
||||
- Added conditional system prompt assembly based on registered Pod-management tool names.
|
||||
- Guidance is included for Workers with Pod management tools and omitted otherwise.
|
||||
- Guidance explicitly says Pod notifications are background signals handled at natural stopping points, that the parent does not need to keep a turn open solely to wait, and that agents should not use `sleep`/polling loops just to wait for Pod output.
|
||||
- Guidance also preserves evidence-before-completion and no scheduler/authorization-bypass constraints.
|
||||
|
||||
Review:
|
||||
- External reviewer approved with no blockers.
|
||||
|
||||
Validation after merge:
|
||||
- `cargo test -p pod pod_orchestration` passed.
|
||||
- `cargo test -p pod prompt::catalog` passed.
|
||||
- `cargo fmt --check` passed.
|
||||
- `./tickets.sh doctor` passed.
|
||||
|
|
@ -148,4 +148,30 @@ Reported validation from coder was considered sufficient:
|
|||
- `cargo fmt --check`
|
||||
|
||||
|
||||
---
|
||||
|
||||
<!-- event: close author: hare at: 2026-06-01T01:24:59Z status: closed -->
|
||||
|
||||
## Closed
|
||||
|
||||
Merged and completed.
|
||||
|
||||
Implementation:
|
||||
- Added resource-backed Pod orchestration guidance at `resources/prompts/common/pod-orchestration.md`.
|
||||
- Registered the guidance through the prompt catalog and internal prompt resources.
|
||||
- Added conditional system prompt assembly based on registered Pod-management tool names.
|
||||
- Guidance is included for Workers with Pod management tools and omitted otherwise.
|
||||
- Guidance explicitly says Pod notifications are background signals handled at natural stopping points, that the parent does not need to keep a turn open solely to wait, and that agents should not use `sleep`/polling loops just to wait for Pod output.
|
||||
- Guidance also preserves evidence-before-completion and no scheduler/authorization-bypass constraints.
|
||||
|
||||
Review:
|
||||
- External reviewer approved with no blockers.
|
||||
|
||||
Validation after merge:
|
||||
- `cargo test -p pod pod_orchestration` passed.
|
||||
- `cargo test -p pod prompt::catalog` passed.
|
||||
- `cargo fmt --check` passed.
|
||||
- `./tickets.sh doctor` passed.
|
||||
|
||||
|
||||
---
|
||||
Loading…
Reference in New Issue
Block a user