okstra 0.102.2 → 0.102.3

package/docs/superpowers/plans/2026-06-24-okstra-container-build-rename.md

@@ -1,525 +0,0 @@
-# okstra-container-build Rename Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Rename the public okstra container skill from `okstra-container` to `okstra-container-build` without changing the `okstra container` CLI or container runtime trace names.
-
-**Architecture:** The public skill surface remains driven by `src/lib/skill-catalog.mjs` and `.claude-plugin/plugin.json`. Install copy/link mode reads skill directories by exact `USER_SKILL_NAMES`, so the source directory and frontmatter must move together. Upgrade cleanup uses an exact obsolete-name allowlist so old `/okstra-container` directories are pruned without wildcard deletion.
-
-**Tech Stack:** Node.js ES modules, Python pytest contract tests, Markdown skill/docs sources, `tools/build.mjs` runtime sync.
-
-## Global Constraints
-
-- Public skill name becomes exactly `okstra-container-build`.
-- Old public skill name `okstra-container` is removed from installed skill manifests and pruned from agent skill homes.
-- CLI command remains exactly `okstra container <up|status|logs|stop-watcher|down>`.
-- Runtime tmux/docker trace prefix remains exactly `okstra-container-<slug>`.
-- Do not wildcard-delete `okstra-*`; cleanup must use exact names only.
-- Do not hand-edit `runtime/`; run `npm run build` after source edits.
-- Preserve historical `CHANGES.md` / `CHANGELOG.md` entries except adding a new current entry.
-
----
-
-## File Structure
-
-- `skills/okstra-container-build/SKILL.md`: renamed public skill source. Keeps `okstra container ...` command examples.
-- `src/lib/skill-catalog.mjs`: public/obsolete skill name SSOT.
-- `.claude-plugin/plugin.json`: secondary skills channel manifest.
-- `src/commands/lifecycle/install.mjs`: install copy/link exact-name prune path.
-- `src/commands/lifecycle/uninstall.mjs`: legacy fallback cleanup names.
-- `tests-js/skill-catalog.test.mjs`: catalog/plugin/obsolete-name contract.
-- `tests-js/install-runtime.test.mjs`: install target manifest plus old skill prune regression.
-- `tests-js/uninstall-runtime.test.mjs`: manifest-missing fallback cleanup regression.
-- `tests/contract/test_docs_runtime_contract.py`: plugin manifest contract mirror.
-- `README.md`, `README.kr.md`, `docs/kr/architecture.md`, `docs/project-structure-overview.md`, `docs/kr/container.md`: live user/internal docs.
-- `docs/for-ai/README.md`, `docs/for-ai/skills/okstra-container-build.md`, `docs/for-ai/skills/okstra-inspect.md`: AI routing manuals.
-- `prompts/profiles/_implementation-deliverable.md`, `prompts/profiles/final-verification.md`: live phase prompt references.
-- `docs/superpowers/specs/2026-06-24-manual-user-test-section-design.md`, `docs/superpowers/plans/2026-06-24-manual-user-test-section.md`: active manual-test design/plan references.
-- `CHANGES.md`: current user-visible change entry.
-
-### Task 1: Public Skill Contract Rename
-
-**Files:**
-- Move: `skills/okstra-container` -> `skills/okstra-container-build`
-- Modify: `skills/okstra-container-build/SKILL.md`
-- Modify: `src/lib/skill-catalog.mjs`
-- Modify: `.claude-plugin/plugin.json`
-- Modify: `src/commands/lifecycle/install.mjs`
-- Modify: `tests-js/skill-catalog.test.mjs`
-- Modify: `tests/contract/test_docs_runtime_contract.py`
-
-**Interfaces:**
-- Produces: `USER_SKILL_NAMES` contains `okstra-container-build`, not `okstra-container`.
-- Produces: `OBSOLETE_SKILL_NAMES` contains old `okstra-container`.
-- Produces: plugin manifest entry `./skills/okstra-container-build`.
-
-- [ ] **Step 1: Write failing catalog contract tests**
-
-Update `tests-js/skill-catalog.test.mjs` import and tests to this shape:
-
-```js
-import assert from "node:assert/strict";
-import { readFileSync } from "node:fs";
-import test from "node:test";
-
-import {
-  OBSOLETE_SKILL_NAMES,
-  USER_SKILL_NAMES,
-} from "../src/lib/skill-catalog.mjs";
-
-function readJson(path) {
-  return JSON.parse(readFileSync(path, "utf8"));
-}
-
-test("public skill catalog matches Claude plugin manifest", () => {
-  const plugin = readJson(".claude-plugin/plugin.json");
-  const pluginNames = plugin.skills.map((entry) => entry.replace("./skills/", ""));
-  assert.deepEqual(pluginNames, [...USER_SKILL_NAMES]);
-});
-
-test("obsolete skill names do not overlap public skills", () => {
-  for (const name of OBSOLETE_SKILL_NAMES) {
-    assert.equal(USER_SKILL_NAMES.includes(name), false, name);
-  }
-});
-
-test("container skill rename keeps old public name prunable", () => {
-  assert.equal(USER_SKILL_NAMES.includes("okstra-container-build"), true);
-  assert.equal(USER_SKILL_NAMES.includes("okstra-container"), false);
-  assert.equal(OBSOLETE_SKILL_NAMES.includes("okstra-container"), true);
-});
-```
-
-Update `tests/contract/test_docs_runtime_contract.py` public skill list:
-
-```python
-USER_FACING_PLUGIN_SKILLS = [
-    "./skills/okstra-setup",
-    "./skills/okstra-brief",
-    "./skills/okstra-run",
-    "./skills/okstra-memory",
-    "./skills/okstra-inspect",
-    "./skills/okstra-schedule",
-    "./skills/okstra-container-build",
-]
-```
-
-- [ ] **Step 2: Run failing contract tests**
-
-Run:
-
-```bash
-node --test tests-js/skill-catalog.test.mjs
-python3 -m pytest tests/contract/test_docs_runtime_contract.py::test_plugin_manifest_exposes_only_user_facing_skills -q
-```
-
-Expected: FAIL because `OBSOLETE_SKILL_NAMES` is not exported yet and `.claude-plugin/plugin.json` still lists `./skills/okstra-container`.
-
-- [ ] **Step 3: Rename skill source and public catalog**
-
-Run:
-
-```bash
-git mv skills/okstra-container skills/okstra-container-build
-```
-
-Edit `skills/okstra-container-build/SKILL.md` frontmatter/title:
-
-```markdown
----
-name: okstra-container-build
-description: |
-  Use to bring up, inspect, or tear down the okstra user-test container runtime for an implementation task — the docker-compose group okstra deploys from a task's worktree so a human can poke at the running build. Trigger words include "okstra container", "okstra container up", "okstra container down", "컨테이너 띄워", "컨테이너 올려", "컨테이너 내려", "컨테이너 상태", "컨테이너 로그", "유저 테스트 환경", "user test environment", "docker compose 띄워줘", "이 task 컨테이너로 띄워", "watcher 멈춰", "stop watcher", "감시 종료".
----
-
-# OKSTRA Container Build
-```
-
-Edit `src/lib/skill-catalog.mjs` public and obsolete exports:
-
-```js
-export const USER_SKILL_NAMES = Object.freeze([
-  "okstra-setup",
-  "okstra-brief",
-  "okstra-run",
-  "okstra-memory",
-  "okstra-inspect",
-  "okstra-schedule",
-  "okstra-container-build",
-]);
-
-// Names okstra used to install as skills before they were renamed or moved
-// into the runtime resource tree. Install prunes these exact directories from
-// each target skill home so upgrades do not leave stale slash commands behind.
-// Exact-name only — never wildcard.
-export const OBSOLETE_SKILL_NAMES = Object.freeze([
-  "okstra",
-  "okstra-context-loader",
-  "okstra-team-contract",
-  "okstra-convergence",
-  "okstra-report-writer",
-  "okstra-coding-preflight",
-  "okstra-container",
-]);
-
-export function userSkillNames() {
-  return [...USER_SKILL_NAMES];
-}
-
-export function obsoleteSkillNames() {
-  return [...OBSOLETE_SKILL_NAMES];
-}
-```
-
-Edit `.claude-plugin/plugin.json`:
-
-```json
-{
-  "name": "okstra",
-  "description": "Multi-agent cross-verification orchestrator (Claude lead + Codex/Antigravity workers).",
-  "skills": [
-    "./skills/okstra-setup",
-    "./skills/okstra-brief",
-    "./skills/okstra-run",
-    "./skills/okstra-memory",
-    "./skills/okstra-inspect",
-    "./skills/okstra-schedule",
-    "./skills/okstra-container-build"
-  ]
-}
-```
-
-Edit `src/commands/lifecycle/install.mjs` import and prune helper names:
-
-```js
-import { OBSOLETE_SKILL_NAMES, USER_SKILL_NAMES } from "../../lib/skill-catalog.mjs";
-```
-
-```js
-const pruned = await pruneObsoleteSkills(target, opts);
-```
-
-```js
-// Remove former skill directories left by older installs. Exact-name only
-// (OBSOLETE_SKILL_NAMES) — never wildcard-delete okstra-*.
-async function pruneObsoleteSkills(target, opts) {
-  let pruned = 0;
-  for (const name of OBSOLETE_SKILL_NAMES) {
-    const path = join(target.skillsDir, name);
-    if (!(await pathEntryExists(path))) continue;
-    pruned += 1;
-    if (opts.dryRun) {
-      process.stdout.write(`[dry-run] rm ${path}\n`);
-      continue;
-    }
-    await fs.rm(path, { recursive: true, force: true });
-  }
-  return pruned;
-}
-```
-
-Apply the helper call rename in both `installSkillsCopy()` and `installSkillsLink()`.
-
-- [ ] **Step 4: Run catalog tests to verify pass**
-
-Run:
-
-```bash
-node --test tests-js/skill-catalog.test.mjs
-python3 -m pytest tests/contract/test_docs_runtime_contract.py::test_plugin_manifest_exposes_only_user_facing_skills -q
-```
-
-Expected: PASS.
-
-- [ ] **Step 5: Commit Task 1**
-
-```bash
-git add skills/okstra-container-build src/lib/skill-catalog.mjs src/commands/lifecycle/install.mjs .claude-plugin/plugin.json tests-js/skill-catalog.test.mjs tests/contract/test_docs_runtime_contract.py
-git commit -m "fix(container): rename public container skill to build"
-```
-
-### Task 2: Install/Uninstall Upgrade Cleanup
-
-**Files:**
-- Modify: `tests-js/install-runtime.test.mjs`
-- Modify: `tests-js/uninstall-runtime.test.mjs`
-- Modify: `src/commands/lifecycle/uninstall.mjs`
-
-**Interfaces:**
-- Consumes: `OBSOLETE_SKILL_NAMES` includes `okstra-container`.
-- Produces: install removes old `okstra-container` skill dirs during upgrade.
-- Produces: uninstall fallback can remove both `okstra-container-build` and old `okstra-container`.
-
-- [ ] **Step 1: Write failing install prune regression**
-
-In `tests-js/install-runtime.test.mjs`, extend `install copies skills to existing Claude and Agent homes and records targets` after the `.claude` / `.agent` roots are created:
-
-```js
-  for (const providerRoot of [join(root, ".claude", "skills"), join(root, ".agent", "skills")]) {
-    mkdirSync(join(providerRoot, "okstra-container"), { recursive: true });
-    writeFileSync(join(providerRoot, "okstra-container", "SKILL.md"), "old container skill\n");
-  }
-```
-
-Extend the provider-root assertions:
-
-```js
-    assert.equal(existsSync(join(providerRoot, "okstra-container-build", "SKILL.md")), true);
-    assert.equal(existsSync(join(providerRoot, "okstra-container", "SKILL.md")), false);
-```
-
-- [ ] **Step 2: Write failing uninstall fallback regression**
-
-Add this test to `tests-js/uninstall-runtime.test.mjs`:
-
-```js
-test("uninstall fallback removes renamed and legacy container skills", () => {
-  const { root, env } = makeInstallEnv();
-  mkdirSync(join(root, ".okstra"), { recursive: true });
-  mkdirSync(join(root, ".claude", "skills", "okstra-container"), { recursive: true });
-  mkdirSync(join(root, ".claude", "skills", "okstra-container-build"), { recursive: true });
-
-  const uninstall = runCli(["uninstall", "-y"], env);
-  assert.equal(uninstall.code, 0, uninstall.stderr);
-
-  assert.equal(existsSync(join(root, ".claude", "skills", "okstra-container")), false);
-  assert.equal(existsSync(join(root, ".claude", "skills", "okstra-container-build")), false);
-});
-```
-
-- [ ] **Step 3: Run failing install/uninstall tests**
-
-Run:
-
-```bash
-node --test tests-js/install-runtime.test.mjs tests-js/uninstall-runtime.test.mjs
-```
-
-Expected: FAIL until `src/commands/lifecycle/uninstall.mjs` fallback names include both container skill names and install prune is wired to `OBSOLETE_SKILL_NAMES`.
-
-- [ ] **Step 4: Implement fallback cleanup names**
-
-Edit `src/commands/lifecycle/uninstall.mjs` `FALLBACK_SKILL_NAMES`:
-
-```js
-const FALLBACK_SKILL_NAMES = [
-  "okstra",
-  "okstra-setup",
-  "okstra-brief",
-  "okstra-run",
-  "okstra-memory",
-  "okstra-inspect",
-  "okstra-schedule",
-  "okstra-container-build",
-  "okstra-container",
-  "okstra-context-loader",
-  "okstra-team-contract",
-  "okstra-convergence",
-  "okstra-report-writer",
-  // Pre-merge names — kept so uninstall on an upgraded machine still cleans
-  // them out of ~/.claude/skills/ once the user runs `okstra uninstall`.
-  // Safe to drop after a few releases when nobody has them installed.
-  "okstra-status",
-  "okstra-history",
-  "okstra-logs",
-  "okstra-report-finder",
-  "okstra-time-summary",
-];
-```
-
-- [ ] **Step 5: Run install/uninstall tests to verify pass**
-
-Run:
-
-```bash
-node --test tests-js/install-runtime.test.mjs tests-js/uninstall-runtime.test.mjs
-```
-
-Expected: PASS.
-
-- [ ] **Step 6: Commit Task 2**
-
-```bash
-git add src/commands/lifecycle/uninstall.mjs tests-js/install-runtime.test.mjs tests-js/uninstall-runtime.test.mjs
-git commit -m "fix(install): prune legacy container skill on rename"
-```
-
-### Task 3: Docs, Prompts, and User-Visible Changelog
-
-**Files:**
-- Move: `docs/for-ai/skills/okstra-container.md` -> `docs/for-ai/skills/okstra-container-build.md`
-- Modify: `README.md`
-- Modify: `README.kr.md`
-- Modify: `docs/kr/architecture.md`
-- Modify: `docs/project-structure-overview.md`
-- Modify: `docs/kr/container.md`
-- Modify: `docs/for-ai/README.md`
-- Modify: `docs/for-ai/skills/okstra-container-build.md`
-- Modify: `docs/for-ai/skills/okstra-inspect.md`
-- Modify: `prompts/profiles/_implementation-deliverable.md`
-- Modify: `prompts/profiles/final-verification.md`
-- Modify: `docs/superpowers/specs/2026-06-24-manual-user-test-section-design.md`
-- Modify: `docs/superpowers/plans/2026-06-24-manual-user-test-section.md`
-- Modify: `CHANGES.md`
-- Test: `tests/contract/test_docs_runtime_contract.py`
-
-**Interfaces:**
-- Consumes: public skill name `okstra-container-build`.
-- Produces: user-facing slash command docs use `/okstra-container-build`.
-- Produces: prompt guidance uses `/okstra-container-build` for skill invocation and `okstra container up ...` for CLI execution.
-
-- [ ] **Step 1: Write failing docs scan command**
-
-Run:
-
-```bash
-rg -n -P '/okstra-container(?!-build)\\b|okstra-container up|okstra-container-build[[:alpha:]]' README.md README.kr.md docs/kr/architecture.md docs/project-structure-overview.md docs/kr/container.md docs/for-ai prompts/profiles/_implementation-deliverable.md prompts/profiles/final-verification.md docs/superpowers/specs/2026-06-24-manual-user-test-section-design.md docs/superpowers/plans/2026-06-24-manual-user-test-section.md
-```
-
-Expected before edits: matches showing old slash-command/prompt references and zero `builder` references after the corrected spec.
-
-- [ ] **Step 2: Rename AI manual file and update live references**
-
-Run:
-
-```bash
-git mv docs/for-ai/skills/okstra-container.md docs/for-ai/skills/okstra-container-build.md
-```
-
-Apply these text rules:
-
-```text
-/okstra-container -> /okstra-container-build
-`okstra-container` as public skill name -> `okstra-container-build`
-skills/okstra-container.md -> skills/okstra-container-build.md
-skills/okstra-container/SKILL.md -> skills/okstra-container-build/SKILL.md
-```
-
-Do not change these runtime strings:
-
-```text
-okstra container
-okstra-container-<slug>
-@okstra_container_run
-```
-
-In `prompts/profiles/_implementation-deliverable.md`, replace the environment line with:
-
-```markdown
-- **Manual user test draft**: when this run produces a user-observable change (UI / API / CLI / artifact), write `target / environment / steps / expected result` per change into §5.7.9 (data field `implementation.manualUserTest`, `applicable=true` with `items`). Environment line: if the project has a `docker-compose.yml`, use `/okstra-container-build` (which runs `okstra container up <task-id>`) then connect to the published port; otherwise the project's run command (e.g. `npm start`). When there is no user-observable change, set `applicable=false` and give a one-line `exemptionReason` instead of items. Base the steps on the approved plan's `Acceptance:` and this run's actual diff — these are the steps a human (or `final-verification`) re-runs by hand, NOT the automated validation commands in `Validation evidence`.
-```
-
-In `prompts/profiles/final-verification.md`, replace the manual test example with:
-
-```markdown
-  - **Manual user test results**: take each item from the source implementation report's §5.7.9 Manual User Test (Draft), execute the ones reproducible in this environment (e.g. `/okstra-container-build`, which runs `okstra container up`, then the documented steps), and record `result` (`pass` / `fail` / `blocked`) + observed value in §5.8.7 (data field `finalVerification.manualUserTest`). Steps that need human-only interaction this run cannot perform are recorded as `blocked` with the reason (handed to the user), never silently skipped. A failed manual test is an Acceptance Blocker. If the draft was an exemption (`applicable=false`), reaffirm the reason in one line (`applicable=false` + `exemptionReaffirm`).
-```
-
-- [ ] **Step 3: Add current CHANGES entry**
-
-Under `## 2026-06-24`, add this entry above the existing entries:
-
-```markdown
-### fix(container): 공개 컨테이너 스킬명을 okstra-container-build 로 변경
-
-- **배경**: 컨테이너 유저 테스트 기능의 공개 slash command 이름을 `okstra-container` 에서 `okstra-container-build` 로 바꾸기로 결정했다. CLI 명령 `okstra container ...` 와 런타임 tmux/docker trace prefix `okstra-container-<slug>` 는 컨테이너 런타임 계약이므로 유지한다.
-- **해결**: 공개 skill catalog, 플러그인 manifest, 설치/업그레이드 cleanup, README/architecture/AI manual/phase prompt 의 사용자-facing 표기를 `okstra-container-build` 로 동기화한다. 옛 `okstra-container` skill directory 는 exact-name obsolete cleanup 으로 재설치 시 제거한다.
-- 사용자 영향: 재설치 후 slash command 는 `/okstra-container-build` 로 노출된다. 기존 `okstra container up/status/logs/stop-watcher/down` CLI 와 실행 중 container watcher trace 이름은 그대로 유지된다. (설치 환경은 `okstra install` 로 런타임 갱신 후 적용.)
-```
-
-- [ ] **Step 4: Run docs scans and contract test**
-
-Run:
-
-```bash
-rg -n -P '/okstra-container(?!-build)\\b|okstra-container up|okstra-container-build[[:alpha:]]' README.md README.kr.md docs/kr/architecture.md docs/project-structure-overview.md docs/kr/container.md docs/for-ai prompts/profiles/_implementation-deliverable.md prompts/profiles/final-verification.md docs/superpowers/specs/2026-06-24-manual-user-test-section-design.md docs/superpowers/plans/2026-06-24-manual-user-test-section.md
-python3 -m pytest tests/contract/test_docs_runtime_contract.py -q
-```
-
-Expected: `rg` exits 1 with no matches; pytest PASS.
-
-- [ ] **Step 5: Commit Task 3**
-
-```bash
-git add README.md README.kr.md docs/kr/architecture.md docs/project-structure-overview.md docs/kr/container.md docs/for-ai/README.md docs/for-ai/skills/okstra-container-build.md docs/for-ai/skills/okstra-inspect.md prompts/profiles/_implementation-deliverable.md prompts/profiles/final-verification.md docs/superpowers/specs/2026-06-24-manual-user-test-section-design.md docs/superpowers/plans/2026-06-24-manual-user-test-section.md CHANGES.md
-git commit -m "docs(container): rename container skill docs to build"
-```
-
-### Task 4: Runtime Build and Full Verification
-
-**Files:**
-- Generated: `runtime/` via `npm run build` (gitignored, do not hand-edit)
-- Test: `tests-js/*.test.mjs`
-- Test: `tests/`
-- Test: `validators/validate-workflow.sh`
-
-**Interfaces:**
-- Consumes: source skill directory `skills/okstra-container-build`.
-- Produces: generated `runtime/skills/okstra-container-build/SKILL.md`.
-- Produces: no generated `runtime/skills/okstra-container/SKILL.md`.
-
-- [ ] **Step 1: Run build**
-
-Run:
-
-```bash
-npm run build
-```
-
-Expected: exit 0. Output includes `skills -> runtime/skills` sync. `runtime/` remains untracked/ignored.
-
-- [ ] **Step 2: Verify runtime skill sync**
-
-Run:
-
-```bash
-test -f runtime/skills/okstra-container-build/SKILL.md
-test ! -e runtime/skills/okstra-container/SKILL.md
-rg -n "name: okstra-container-build" runtime/skills/okstra-container-build/SKILL.md
-```
-
-Expected: all commands exit 0.
-
-- [ ] **Step 3: Run targeted test suite**
-
-Run:
-
-```bash
-node --test tests-js/skill-catalog.test.mjs tests-js/install-runtime.test.mjs tests-js/uninstall-runtime.test.mjs tests-js/doctor-runtime.test.mjs
-python3 -m pytest tests/contract/test_docs_runtime_contract.py -q
-```
-
-Expected: PASS.
-
-- [ ] **Step 4: Run project check**
-
-Run:
-
-```bash
-npm run check
-```
-
-Expected: exit 0.
-
-- [ ] **Step 5: Run final identifier audit**
-
-Run:
-
-```bash
-rg -n "okstra-container-build[[:alpha:]]|container-build[[:alpha:]]" .
-rg -n "okstra-container" .
-```
-
-Expected:
-- First command exits 1 with no matches.
-- Second command still reports historical changelog/old design-plan references and runtime prefix tests such as `okstra-container-<slug>`, but not live public skill catalog, plugin manifest, README slash-command rows, AI routing manuals, or live phase prompt instructions.
-
-- [ ] **Step 6: Record verification-only status**
-
-Run:
-
-```bash
-git status --short
-```
-
-Expected: no new tracked source changes from Task 4. `runtime/` may have been regenerated by `npm run build` but remains ignored. Do not create a commit for this task unless a tracked verification fixture changed.

package/docs/superpowers/specs/2026-05-12-ticket-id-in-reports-design.md

@@ -1,131 +0,0 @@
-# Ticket ID in Worker / Lead / Report Outputs — Design
-
-- Date: 2026-05-12
-- Scope: okstra phases `requirements-discovery`, `error-analysis`, `implementation-planning`, `implementation`
-- Status: Implemented
-- Implementation plan: `docs/superpowers/plans/2026-05-12-ticket-id-in-reports.md`
-
-## 1. 목적
-
-okstra의 작업 단위는 보통 외부 트래커의 ticket과 1:1로 묶이지만, 현재 워커·lead·report-writer 산출물은 보고서 헤더의 `Task Key` 한 곳에서만 ticket을 식별한다. 항목별로 어떤 ticket을 다루고 있는지 추적할 수 없어, 한 run이 여러 ticket을 동시에 다룰 때 항목·ticket 매핑이 누락된다.
-
-본 변경은 워커가 작성하는 모든 항목과 final report의 본문 섹션에 ticket 식별자를 박아 trace를 ticket 단위로 동기화한다.
-
-## 2. Ticket ID 채움 규칙 (모든 산출물 공통)
-
-1. 입력 템플릿의 `Issue / Ticket` 값을 우선 사용한다.
-2. 비어 있으면 `Task ID`로 폴백한다. 폴백 표기에는 prefix를 붙이지 않는다 (예: `8852`).
-3. `Issue / Ticket`도 비고 `Task ID`도 사용할 수 없는 예외 상황에 한해 `unknown` 표기를 허용한다.
-4. 한 항목이 여러 ticket을 동시에 다루면 쉼표로 구분한다 (예: `TICKET-123, TICKET-456`).
-
-## 3. 표기 규칙
-
-### 3.1 표 형식 섹션
-표 형식 섹션은 `Ticket ID` 컬럼을 추가한다. 컬럼은 표의 가장 왼쪽 ID 컬럼 바로 다음에 위치한다.
-
-### 3.2 비-표 섹션 (bullet / 번호 목록 / 섹션 헤더)
-항목 또는 섹션 헤더의 타이틀에 `[TICKETID: <id>]` 태그를 강제한다.
-
-- 항목 예: `- F-001 [TICKETID: TICKET-123] — <summary> (path:line)`
-- 헤더 예: `### 4.5.3 Recommended Option [TICKETID: TICKET-123]`
-
-태그는 ID 직후, 본문 텍스트 앞에 위치한다. 한 줄 안에서 태그가 보이지 않으면 contract violation이다.
-
-## 4. 변경 파일
-
-### 4.1 `skills/okstra-team-contract/SKILL.md`
-- Worker Output Contract 섹션에 "Ticket Tagging" 항목 신설.
-- 섹션 1 Findings, 2 Missing Information / Assumptions, 3 Safe or Reasonable Areas, 4 Uncertain Points, 5 Recommended Next Actions 모두에 적용된다는 점을 명시.
-- bullet 항목은 `[TICKETID: ...]` 태그 강제, 표 항목은 `Ticket ID` 컬럼 강제.
-- 폴백/다중 ticket/`unknown` 규칙을 본 spec과 동일한 문구로 인용.
-
-### 4.2 `skills/okstra-convergence/SKILL.md`
-- Round 0 (Parse worker results)에 ticket 추출 절차 추가.
-- finding 그룹핑 시 ticket이 다르면 의미가 유사해도 별도 그룹으로 처리해 과병합을 방지한다는 규칙 추가.
-- 컨버전스 상태 아티팩트에 각 finding의 `ticketId` 필드를 함께 기록.
-
-### 4.3 `templates/reports/final-report.template.md`
-- 보고서 상단(`## Summary of the Problem or Verification Target` 직후)에 `## Ticket Coverage` 표 신규 추가.
-
-  | Ticket ID | 등장 섹션 | 관련 항목 IDs |
-  |-----------|-----------|---------------|
-
-  - 한 run에 ticket이 0~1개면 단일 행으로 채우거나 `- Single ticket run: <id>` 한 줄로 대체 가능.
-  - 다중 ticket이면 ticket마다 한 행씩 작성하고, `등장 섹션` 컬럼에는 본문에서 해당 ticket이 나타나는 섹션 번호를 콤마 구분으로, `관련 항목 IDs` 컬럼에는 `F-001`, `A1`, `Q1` 등 항목 ID를 콤마 구분으로 적는다.
-
-- `1.1 Consensus`, `1.2 Differences` → bullet에서 표로 전환.
-
-  | ID | Ticket ID | Statement | Supporting workers | Evidence |
-  |----|-----------|-----------|--------------------|----------|
-
-- `3.1 Primary Evidence`, `3.2 Secondary Evidence or Alternate Interpretations` → 표로 전환.
-
-  | ID | Ticket ID | Evidence | Source (path:line / log / worker) |
-  |----|-----------|----------|------------------------------------|
-
-- `4. Missing Information and Risks` → 표로 전환.
-
-  | ID | Ticket ID | Item | Risk if ignored |
-  |----|-----------|------|-----------------|
-
-- `4.5.1 Option Candidates`: 옵션별 File Structure 표에 `Ticket ID` 컬럼 추가.
-- `4.5.2 Trade-off Matrix`: 컬럼 변경 없음 (옵션 단위 매트릭스이며 옵션 자체가 ticket scope를 가로지를 수 있다).
-- `4.5.4 Stepwise Execution Order`: 각 step 행에 `Ticket ID` 컬럼 추가 (현재 번호 목록이라면 표로 전환).
-- `4.5.6 Validation Checklist`: pre/mid/post 각 체크 행에 `Ticket ID` 컬럼 추가.
-- `5.1 추가 자료 요청`, `5.2 사용자 확인 질문`: 기존 표에 `Ticket ID` 컬럼을 두 번째 위치로 삽입 (`자료 ID` / `질문 ID` 다음).
-
-### 4.4 입력 템플릿
-대상 파일:
-- `templates/reports/error-analysis-input.template.md`
-- `templates/reports/implementation-planning-input.template.md`
-- `templates/reports/implementation-input.template.md`
-- `templates/reports/quick-input.template.md`
-
-변경:
-- `Identity` 섹션의 `Issue / Ticket:` 줄 바로 아래에 한 줄 가이드 추가.
-  > `Issue / Ticket` 값이 비면 워커는 `Task ID`로 폴백한다 (예: `8852`). 한 run에서 여러 ticket을 동시에 다루는 경우 쉼표로 구분한다 (`TICKET-123, TICKET-456`).
-
-### 4.5 `templates/reports/task-brief.template.md`
-- `Identity` 섹션에 동일한 폴백/다중 ticket 가이드 한 줄 추가.
-- `Questions for Workers > Standing Scope-Discipline Questions` 직전에 한 줄 추가: "모든 항목 및 표 행에 ticket을 명시해야 한다. 표 형식은 `Ticket ID` 컬럼, bullet/번호목록·섹션 헤더는 `[TICKETID: ...]` 태그를 사용한다. 자세한 규칙은 `okstra-team-contract` SKILL을 참조."
-
-### 4.6 워커 프롬프트
-대상 파일:
-- `agents/workers/claude-worker.md`
-- `agents/workers/codex-worker.md`
-- `agents/workers/gemini-worker.md`
-
-변경:
-- `Worker Output Structure` 절 끝에 한 단락 추가. 표기 규칙은 team-contract가 authoritative source임을 명시하고, 표/비-표 두 가지 형식과 폴백·다중 ticket·`unknown` 규칙을 한 번에 인용.
-
-### 4.7 `agents/workers/report-writer-worker.md`
-- final-report 작성 의무 절에 한 줄 추가: "워커 산출물의 `Ticket ID` 컬럼 및 `[TICKETID: ...]` 태그를 보존하고, 상단 `## Ticket Coverage` 표를 본 spec 규칙대로 채울 것."
-
-## 5. 손대지 않는 곳
-
-- 기존 `F-001`, `A1`, `Q1` 등 ID 카운터 체계 (전역 유일성 그대로 유지).
-- `User Approval Request` 체크박스, validator의 영문 키워드 매칭(`Option Candidates`, `Trade-off`, `Recommended Option`, `Stepwise Execution Order`, `Dependency`, `Validation Checklist`, `Rollback`, `User Approval Request`).
-- `release-handoff`, `final-verification` 산출물 및 그 phase의 워커/lead 출력.
-- 토큰 사용량 표, Execution Status 표 등 ticket scope와 무관한 메타 표.
-
-## 6. 영향과 위험
-
-- **convergence 파서**: bullet 한 줄 안에 ticket 태그가 함께 들어가 정규식 변경이 필요. ticket이 finding의 그룹핑 키 일부가 되므로 동일 root cause라도 ticket이 다르면 별도 그룹으로 처리된다. 의도된 동작.
-- **기존 보고서 호환성**: 본 변경은 신규 run에만 적용. 과거 보고서는 마이그레이션하지 않는다.
-- **워커가 ticket을 못 채우는 경우**: `unknown` 표기를 허용하지만, 이는 입력 템플릿이 잘못 채워졌다는 신호이므로 lead가 `Missing Information` 항목으로 함께 기록한다.
-- **다중 ticket 콤마 구분 vs 정규식**: ticket ID 자체에 콤마가 들어가는 경우는 없다고 가정한다. JIRA/GitHub/Linear 모두 콤마 미사용. 만약 향후 콤마를 포함한 ticket ID가 나오면 별도 escape 룰을 추가한다 (현재 spec에는 포함하지 않음).
-
-## 7. 검증
-
-- 신규 run 1건씩 phase별로 실행해 다음을 수동 확인:
-  - 입력 템플릿 가이드가 노출되는지.
-  - 워커 출력의 bullet 항목 전부에 `[TICKETID: ...]` 태그가 붙는지.
-  - 표 섹션에 `Ticket ID` 컬럼이 채워지는지.
-  - final report 상단 `## Ticket Coverage` 표가 본문 항목과 정합한지 (수동 cross-check).
-- `validators/` 디렉토리에 ticket 태그/컬럼 누락을 잡는 정적 체크를 추가하는 것은 후속 작업(이번 spec 범위 밖).
-
-## 8. 후속 작업 (이번 spec 범위 밖)
-
-- `validators/`에 ticket 표기 강제용 정적 검증기 추가.
-- `final-verification`, `release-handoff` phase에도 동일 규칙 확장 여부 결정.
-- `okstra-convergence` 상태 아티팩트 스키마에 `ticketId` 정식 필드화 (현재는 분류 키로만 사용).