okstra 0.102.0 → 0.102.1

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

@@ -0,0 +1,525 @@
+# 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-06-24-manual-user-test-section-design.md

@@ -11,19 +11,19 @@
 - implementation 딜리버러블의 테스트 섹션은 [final-report.template.md:458](../../../templates/reports/final-report.template.md) §5.7.6 Validation Evidence 하나뿐이며, 이는 `Phase | Command | Exit code | Output tail | TDD evidence` 구조의 **자동 검증 증거 전용**이다. 딜리버러블 명세 [_implementation-deliverable.md:19-20](../../../prompts/profiles/_implementation-deliverable.md) 의 Validation evidence / TDD evidence 도 전부 실행 명령 기반이다.
 - planning 의 stage 별 `Acceptance:` 도 "RED 스텝을 PASS 로 뒤집는 같은 테스트 명령"으로 정의된다([implementation-planning.md:73](../../../prompts/profiles/implementation-planning.md)). 사람 절차가 아니다.
 - final-verification 에는 사람 검증에 가까운 입력란이 있으나([final-verification-input.template.md:58](../../../templates/reports/final-verification-input.template.md) `Manual verification notes:`, `:70` `## Acceptance Criteria`), 이는 **검증 단계 입력**일 뿐 implementation 산출물로 흘러드는 "구현 직후의 테스트 절차"가 아니다.
-- 결정적으로 [okstra-container/SKILL.md](../../../skills/okstra-container/SKILL.md) 는 사람이 만져볼 환경을 docker 로 띄워주지만(`:9` "so a human can poke at the running build"), `prompts/`·`templates/` 어디에서도 참조되지 않는 고립 스킬이다. **환경은 띄워주는데, 띄운 다음 무엇을 어떻게 확인할지를 적어둘 자리가 리포트에 없는 단절** 상태다.
+- 결정적으로 [okstra-container-build/SKILL.md](../../../skills/okstra-container-build/SKILL.md) 는 사람이 만져볼 환경을 docker 로 띄워주지만(`:9` "so a human can poke at the running build"), `prompts/`·`templates/` 어디에서도 참조되지 않는 고립 스킬이다. **환경은 띄워주는데, 띄운 다음 무엇을 어떻게 확인할지를 적어둘 자리가 리포트에 없는 단절** 상태다.
 
 ## 2. 목표 / 비목표
 
 ### 목표
 - implementation 단계가 "Manual User Test" 절차 **초안**을 산출하고, final-verification 단계가 그 초안을 **실제로 수행해 결과를 확정**한다.
 - 관찰 가능한 변화가 있는 task 에 한해 절차를 요구한다(내부 전용 변경은 면제).
-- `okstra-container` 와 리포트를 조건부로 연결해 단절을 해소한다.
+- `okstra-container-build` 와 리포트를 조건부로 연결해 단절을 해소한다.
 
 ### 비목표 (YAGNI)
 - 자동 E2E/통합 테스트 프레임워크 도입 — 기존 자동 검증(§5.7.6 / verifier)은 그대로 둔다.
 - 모든 task 에 일괄 강제 — 관찰 불가 변경까지 N/A 스텁을 양산하지 않는다.
-- okstra-container 가 없는(=docker-compose 부재) 프로젝트에 컨테이너 사용 강요.
+- docker-compose 가 없는 프로젝트에 컨테이너 사용 강요.
 
 ## 3. 설계 결정 (확정)
 
@@ -31,7 +31,7 @@
 |---|---|---|
 | 위치 | implementation(초안) ↔ final-verification(실행·확정) **양쪽 연계** | 절차 작성 시점(구현 직후)과 실행 시점(검증)이 다름. 단일 소유자 분리: 초안=implementation, 결과=final-verification |
 | 범위 | 사람이 **관찰 가능한 변화**가 있을 때만 절차, 내부 전용이면 `사용자 테스트 불필요 — <사유>` 한 줄 | allowlist 방식으로 빈 섹션 노이즈 최소화 |
-| container 연계 | **조건부** — `docker-compose.yml` 있으면 `okstra-container up`, 없으면 일반 실행 명령 | 단절 해소 + compose 없는 프로젝트 과임 방지 |
+| container 연계 | **조건부** — `docker-compose.yml` 있으면 `/okstra-container-build` (`okstra container up <task-id>`), 없으면 일반 실행 명령 | 단절 해소 + compose 없는 프로젝트 과임 방지 |
 | 강제 | **validator 구조 강제** — 헤딩 존재 + (절차 또는 면제사유) 중 하나, 빈 스텁 거부 | "관찰 가능 여부"는 의미 판단이라 validator 자동 판정 불가 → 구조만 강제, 적절성은 교차검증 워커가 판단. CLAUDE.md "MUST 는 강제 지점 명시" 충족 |
 
 ## 4. 섹션 포맷 명세
@@ -42,7 +42,7 @@
 ```
 - 대상: <어떤 사용자-facing 동작/기능>
 - 환경 기동:
-  - (docker-compose.yml 있음) `okstra-container up <task-id>` → published port 접속
+  - (docker-compose.yml 있음) `/okstra-container-build` (`okstra container up <task-id>`) → published port 접속
   - (없음) <프로젝트 실행 명령, 예: npm start / 해당 바이너리 실행>
 - 확인 스텝:
   1. <사람이 하는 동작>
@@ -93,7 +93,7 @@ final-verification ──→ §5.8.x Manual User Test Results  [결과 단일
 | [templates/reports/final-report.template.md](../../../templates/reports/final-report.template.md) | §5.7 에 `Manual User Test (Draft)` 하위섹션 신설(Routing Recommendation 직전 배치, 이후 번호 +1), §5.8 에 `Manual User Test Results` 하위섹션 신설(Routing 직전) |
 | [templates/reports/final-verification-input.template.md](../../../templates/reports/final-verification-input.template.md) | `Manual verification notes:`(:58) 를 implementation 초안 인용 흐름과 통합 |
 | [validators/validate-run.py](../../../validators/validate-run.py) | 기존 §5.7/§5.8 deliverable 섹션 scan 리스트(:1145-1163)에 신설 섹션명 추가 + 빈 스텁/면제사유 거부 체크 |
-| [skills/okstra-container/SKILL.md](../../../skills/okstra-container/SKILL.md) | 리포트↔container 양방향 포인터 한 줄(이 절차 섹션에서 호출됨을 명시) |
+| [skills/okstra-container-build/SKILL.md](../../../skills/okstra-container-build/SKILL.md) | 리포트↔container 양방향 포인터 한 줄(이 절차 섹션에서 호출됨을 명시) |
 
 > 구현 후 `npm run build` 로 `runtime/` 동기화 필요. 엔드유저 반영은 `okstra install` 재실행.