okstra 0.8.0 → 0.9.0

package/runtime/templates/reports/release-handoff-input.template.md

@@ -0,0 +1,73 @@
+# OKSTRA Release Handoff Input
+
+## Identity
+
+- Project ID:
+- Task Group:
+- Task ID:
+- Related Tasks:
+- Issue / Ticket:
+- Task Type: `release-handoff`
+- Requested Outcome:
+
+## Source Verification Report
+
+- Path (project-relative) to the `final-verification` final-report whose verdict authorises this handoff:
+- Verbatim quoted line from that report's `## 2. Final Verdict` (MUST read exactly `accepted`):
+- Run timestamp of that final-verification run:
+
+> If this section is empty or cites a verdict other than `accepted`, the lead MUST end the run immediately and route back to `final-verification`. Release-handoff never operates on `conditional-accept` or `blocked` outcomes.
+
+## Working-Tree Snapshot (filled at run start)
+
+- Feature branch (`git rev-parse --abbrev-ref HEAD`):
+- `git status --short` output at run start:
+- Existing PR for this head, if any (`gh pr list --head <branch> --state open --json url --jq '.[0].url'`):
+
+## Candidate PR Base Branches
+
+- Default options offered to the user: `staging` | `preprod` | `prod` | `main` | `dev` | 직접 입력
+- Repo-specific preference, if known (e.g. `main` is the integration branch):
+- Branches that MUST NOT be used as a base in this repo (security / freeze rules):
+
+## Commit Message Drafter Inputs
+
+- Commit type convention this repo follows (`release-please` types, plain conventional commits, free-form):
+- `git diff <base>..HEAD --stat` (or equivalent change summary) for the drafter to ground its message on:
+- Files known to be part of the prior `implementation` run's approved plan:
+- Files appearing in the diff that were in the prior run's `Out-of-plan edits` block:
+
+## PR Body Drafter Inputs
+
+- Linked issues / tickets the PR should reference (URLs):
+- Test plan items the prior `implementation` run already validated:
+- Reviewer hints (teams or individuals the PR should request review from):
+
+## User-Selection Defaults (advisory only — the user still chooses interactively)
+
+- Suggested action (Q1): `commit only` | `commit + PR` | `skip`
+- Suggested base (Q2): one of the candidate base branches above
+- Suggested message handling (Q3): `use as-is` | `edit then proceed`
+
+> These suggestions help the lead phrase its `AskUserQuestion` prompts. They are NOT pre-approvals — every mutating command still requires an explicit user pick at run time.
+
+## Out of Scope
+
+- Actions deliberately excluded from this handoff:
+- Items that look related but belong to a separate handoff or release task:
+- Reason for exclusion (different release window, separate owner, deferred decision):
+
+> The lead MUST NOT extend handoff actions into items listed here. If an excluded item should ship in this PR, edit this section before the run starts — do not silently fold it in.
+
+## Questions for Drafter Worker
+
+1. What commit type and scope best describe the cumulative diff?
+2. What single subject line summarises the change in under 72 characters?
+3. What changed at a behavioural level (not just file-level) that reviewers need to know?
+4. Which prior commits in this feature branch should be referenced or amended by this commit?
+5. Does the diff include any change that requires a follow-up PR (migration squash, config split, etc.) — and if so, should that be noted in the PR body's `## Follow-ups` block?
+
+## Conversion Note
+
+- This input can be used as the release-handoff brief before creating `okstra-task-brief.md`.
+- Reuse the same `Task Group` and `Task ID` as the originating implementation / final-verification runs so the handoff stays attached to the same task history.

package/runtime/templates/reports/task-brief.template.md

@@ -9,6 +9,7 @@
 - Task Key: `<project-id>:<task-group>:<task-id>`
 - Related Tasks:
 - Issue / Ticket:
+  - 값이 비면 워커는 `Task ID`로 폴백한다 (prefix 없이 `8852`처럼). 한 run이 여러 ticket을 동시에 다루면 콤마로 구분 (`TICKET-123, TICKET-456`). 어느 쪽으로도 식별 불가하면 `unknown`을 허용한다.
 - Task Type:
 - Requested Outcome:
 - Owner:
@@ -96,6 +97,10 @@
 2.
 3.
 
+### Standing Ticket-Tagging Rule (always applied by every worker)
+
+- 모든 항목 및 표 행에 ticket을 명시한다. 표 형식은 `Ticket ID` 컬럼, bullet/번호목록·섹션 헤더는 `[TICKETID: <id>]` 태그를 사용한다. 채움 우선순위·폴백·다중 ticket 규칙은 `okstra-team-contract` SKILL의 Ticket Tagging 절을 따른다.
+
 ### Standing Scope-Discipline Questions (always answered by every worker)
 
 - Which adjacent changes did you consider and **deliberately exclude** from this run? List each with a one-line reason.

package/runtime/validators/validate-run.py

@@ -37,7 +37,11 @@ def default_next_phase(task_type: str) -> str:
         "error-analysis": "implementation-planning",
         "implementation-planning": "implementation",
         "implementation": "final-verification",
-        "final-verification": "done-or-follow-up",
+        # final-verification 의 다음 phase 는 verdict 에 따라 갈리므로
+        # 정적 매핑은 `pending-release-handoff` 로 두고, 실제 진입은
+        # release-handoff profile 의 entry gate (`accepted` 확인) 에서 강제한다.
+        "final-verification": "pending-release-handoff",
+        "release-handoff": "done-or-follow-up",
     }
     return mapping.get(task_type, "unknown")
 
@@ -84,6 +88,7 @@ def update_workflow_metadata(
             "implementation-planning",
             "implementation",
             "final-verification",
+            "release-handoff",
         ]
 
     phase_states = workflow.get("phaseStates", {})