okstra 0.102.1 → 0.102.3

package/docs/superpowers/plans/2026-06-15-internal-skill-migration-final-fixups.md

@@ -1,342 +0,0 @@
-# Internal Skill Migration Final Fixups 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:** Finish the internal-skill migration by making `ensure-installed`, executor instructions, and runtime prompt-resource wording match the new resource-based contract model.
-
-**Architecture:** Keep the public skill surface fixed at the six plugin-listed user skills. Treat the routed coding-preflight pack as a required installed runtime asset: `ensure-installed` must validate every routed pack file that `overview.md` can select. All executor/verifier instructions must use the generated launch prompt's resolved `Coding preflight pack:` absolute path, never a hardcoded `~/.okstra` path. Lead runtime resources must refer to moved internals as contracts/resources, not skills.
-
-**Tech Stack:** Node.js ES modules for install drift checks and JS tests, Python pytest contract tests for prompt/docs invariants, markdown prompt resources, existing `npm run build` runtime sync.
-
----
-
-## Current failing checks
-
-These gaps were observed after the previous fix pass:
-
-1. `okstra ensure-installed` restores a missing `prompts/` directory, but still reports OK when a routed language file such as `prompts/coding-preflight/languages/python.md` is missing.
-2. `_implementation-executor.md` and `claude-worker.md` still mention `~/.okstra/prompts/coding-preflight/` directly.
-3. `okstra-lead-contract.md` still says `convergence skill` in the plan-body verification section.
-4. Existing contract tests do not scan the files where items 2 and 3 survive.
-
-## File map
-
-- `src/install.mjs` — owns install/ensure drift detection. Add every routed coding-preflight resource to the required prompt-resource allowlist.
-- `tests-js/install-runtime.test.mjs` — add a regression that removes a single language resource and verifies `ensure-installed` restores it.
-- `prompts/profiles/_implementation-executor.md` — remove hardcoded default preflight path from executor-side guidance.
-- `agents/workers/claude-worker.md` — remove hardcoded default preflight path from Claude executor guidance.
-- `prompts/lead/okstra-lead-contract.md` — replace stale `convergence skill` wording with `convergence contract` / `convergence resource`.
-- `tests/test_docs_runtime_contract.py` — extend path and wording guards so these regressions fail in tests.
-- `runtime/` — generated by `npm run build`; do not edit directly.
-
-## Task 1: Require the full routed coding-preflight pack in `ensure-installed`
-
-**Files:**
-- Modify: `src/install.mjs`
-- Modify: `tests-js/install-runtime.test.mjs`
-
-- [ ] **Step 1: Extend `REQUIRED_PROMPT_RESOURCE_FILES`**
-
-In `src/install.mjs`, extend the existing `REQUIRED_PROMPT_RESOURCE_FILES` allowlist so it covers every resource listed by `prompts/coding-preflight/overview.md`.
-
-Replace the current block with:
-
-```js
-const REQUIRED_PROMPT_RESOURCE_FILES = Object.freeze([
-  ["prompts", "lead", "okstra-lead-contract.md"],
-  ["prompts", "lead", "context-loader.md"],
-  ["prompts", "lead", "team-contract.md"],
-  ["prompts", "lead", "convergence.md"],
-  ["prompts", "lead", "report-writer.md"],
-  ["prompts", "coding-preflight", "overview.md"],
-  ["prompts", "coding-preflight", "clean-code.md"],
-  ["prompts", "coding-preflight", "languages", "javascript-typescript.md"],
-  ["prompts", "coding-preflight", "languages", "python.md"],
-  ["prompts", "coding-preflight", "languages", "rust.md"],
-  ["prompts", "coding-preflight", "languages", "java.md"],
-  ["prompts", "coding-preflight", "languages", "kotlin.md"],
-  ["prompts", "coding-preflight", "languages", "sql.md"],
-  ["prompts", "coding-preflight", "frameworks", "node-server.md"],
-  ["prompts", "coding-preflight", "architectures", "hexagonal.md"],
-]);
-```
-
-Keep this as an exact allowlist. Do not replace it with a recursive directory check; missing routed files should produce explicit `missing <path>` reasons.
-
-- [ ] **Step 2: Add a single-file resource-drift regression test**
-
-In `tests-js/install-runtime.test.mjs`, add a test after `ensure-installed repairs missing runtime prompt resources`:
-
-```js
-test("ensure-installed repairs a missing routed coding preflight language resource", () => {
-  const { root, env } = makeInstallEnv();
-  mkdirSync(join(root, ".claude"), { recursive: true });
-
-  const install = runCli(["install", "--quiet"], { ...env, OKSTRA_RUNTIME_HOST: "external" });
-  assert.equal(install.code, 0, install.stderr);
-
-  const pythonResource = join(root, ".okstra", "prompts", "coding-preflight", "languages", "python.md");
-  rmSync(pythonResource, { force: true });
-
-  const ensure = runCli(["ensure-installed"], { ...env, OKSTRA_RUNTIME_HOST: "external" });
-  assert.equal(ensure.code, 0, ensure.stderr);
-  assert.match(ensure.stderr, /okstra runtime needs install:/);
-  assert.equal(existsSync(pythonResource), true);
-});
-```
-
-This covers the failure where `overview.md` and `clean-code.md` exist but a selectable language rule target is missing.
-
-- [ ] **Step 3: Verify focused JS behavior**
-
-Run:
-
-```bash
-node --test tests-js/install-runtime.test.mjs
-```
-
-Expected: all install-runtime subtests pass, including the new single-file resource-drift regression.
-
-## Task 2: Remove hardcoded preflight paths from executor/worker instructions
-
-**Files:**
-- Modify: `prompts/profiles/_implementation-executor.md`
-- Modify: `agents/workers/claude-worker.md`
-- Modify: `tests/test_docs_runtime_contract.py`
-
-- [ ] **Step 1: Rewrite executor sidecar preflight pointer text**
-
-In `prompts/profiles/_implementation-executor.md`, replace the parenthetical that currently says `skill-file pointers (~/.okstra/prompts/coding-preflight/)` with resolved-resource wording:
-
-```markdown
-- **Coding-conventions preflight (BLOCKING — runs before the first `Edit` / `Write`, and binds the TDD loop below).** The gate body is a single source at `prompts/profiles/_coding-conventions-preflight.md` (sibling of this sidecar): resolved `Coding preflight pack:` runtime-resource path usage, project review rule packs, the always-binding language-agnostic principles, and graceful degradation. Do NOT re-type that content from memory — deliver it by file so it cannot drift or be dropped:
-```
-
-Do not mention `~/.okstra` in this file.
-
-- [ ] **Step 2: Rewrite Claude worker preflight instruction**
-
-In `agents/workers/claude-worker.md`, replace the sentence that starts with `Read ~/.okstra/prompts/coding-preflight/overview.md` with launch-resource wording:
-
-```markdown
-   - **Executor coding-conventions preflight (BLOCKING, before your first `Edit` / `Write`):** when dispatched as the `Executor`, you MUST run the coding-conventions preflight defined in the executor sidecar (`prompts/profiles/_implementation-executor.md` → "Pre-implementation context exploration") before writing any code. Use the `Coding preflight pack:` absolute path from the lead prompt's `## Okstra Runtime Resources` block; read that pack's `overview.md` and `clean-code.md`, then follow the routed pack's language → framework → architecture stages, iterating every rule and loading every matching resource (for example `frameworks/node-server.md` and `architectures/hexagonal.md` when their conditions match). The preflight pack is a runtime resource, not an auto-invoked skill; read the files via the Read tool by absolute path.
-```
-
-Do not mention `~/.okstra` in this file.
-
-- [ ] **Step 3: Extend hardcoded preflight path contract test**
-
-In `tests/test_docs_runtime_contract.py`, update `test_profile_sidecars_use_resolved_coding_preflight_pack_path` to scan both newly identified files:
-
-```python
-def test_profile_sidecars_use_resolved_coding_preflight_pack_path():
-    for relative_path in [
-        "prompts/profiles/_coding-conventions-preflight.md",
-        "prompts/profiles/_implementation-verifier.md",
-        "prompts/profiles/_implementation-executor.md",
-        "agents/workers/claude-worker.md",
-    ]:
-        text = _read_doc(relative_path)
-        assert "~/.okstra/prompts/coding-preflight" not in text, relative_path
-
-    for relative_path in [
-        "prompts/profiles/_coding-conventions-preflight.md",
-        "prompts/profiles/_implementation-verifier.md",
-        "agents/workers/claude-worker.md",
-    ]:
-        text = _read_doc(relative_path)
-        assert "Coding preflight pack:" in text, relative_path
-```
-
-`_implementation-executor.md` delegates the actual preflight body by file and may only mention the heading name indirectly; the test should require absence of hardcoded path there, not duplicate the full router wording.
-
-- [ ] **Step 4: Verify focused Python behavior**
-
-Run:
-
-```bash
-python3 -m pytest tests/test_docs_runtime_contract.py::test_profile_sidecars_use_resolved_coding_preflight_pack_path
-```
-
-Expected: test passes.
-
-## Task 3: Replace stale `convergence skill` wording in the lead contract
-
-**Files:**
-- Modify: `prompts/lead/okstra-lead-contract.md`
-- Modify: `tests/test_docs_runtime_contract.py`
-
-- [ ] **Step 1: Rewrite the two stale references**
-
-In `prompts/lead/okstra-lead-contract.md`, update the plan-body verification numbered list:
-
-```markdown
-1. Extract `P-*` plan items from the draft report's `## 5.4 Implementation Plan Deliverables` per the prefix → source-section mapping in the convergence contract.
-2. Dispatch a single plan-body reverify round to every analyser worker in the roster (`claude`, `codex`, and `gemini` when opted in). `Report writer worker` is NOT a participant in this round.
-3. Aggregate verdicts and resolve the gate result to one of `passed` / `passed-with-dissent` / `blocked-by-disagreement` / `aborted-non-result`.
-4. Write `runs/<task-type>/state/plan-body-verification.json` (schema in the convergence contract).
-```
-
-Only the words `convergence skill` change. Do not alter phase semantics.
-
-- [ ] **Step 2: Extend stale wording scan to the lead contract**
-
-In `tests/test_docs_runtime_contract.py`, add `prompts/lead/okstra-lead-contract.md` to `scanned_files` in `test_live_docs_do_not_describe_internal_contracts_as_skills`:
-
-```python
-"prompts/lead/okstra-lead-contract.md",
-"prompts/lead/context-loader.md",
-"prompts/lead/convergence.md",
-"prompts/lead/report-writer.md",
-"prompts/lead/team-contract.md",
-```
-
-Also add exact forbidden fragments for this regression:
-
-```python
-"convergence skill",
-"schema in the convergence skill",
-```
-
-Keep existing public-skill wording allowed; this guard is only for internal contract/resource naming.
-
-- [ ] **Step 3: Verify focused stale-wording behavior**
-
-Run:
-
-```bash
-python3 -m pytest tests/test_docs_runtime_contract.py::test_live_docs_do_not_describe_internal_contracts_as_skills
-```
-
-Expected: test passes and would fail if `convergence skill` returns to the lead contract.
-
-## Task 4: Final verification and runtime sync
-
-**Files:**
-- Generated: `runtime/` via `npm run build`
-
-- [ ] **Step 1: Build runtime**
-
-Run:
-
-```bash
-npm run build
-```
-
-Expected: build exits 0 and syncs `prompts/`, `agents/`, `skills/`, `validators/`, and runtime scripts into `runtime/`.
-
-- [ ] **Step 2: Re-run focused tests**
-
-Run:
-
-```bash
-node --test tests-js/install-runtime.test.mjs
-python3 -m pytest tests/test_docs_runtime_contract.py tests/test_lead_runtime_marker.py
-```
-
-Expected: all listed tests pass.
-
-- [ ] **Step 3: Re-run the single-file coding-preflight resource smoke**
-
-Run:
-
-```bash
-TMP_HOME=$(mktemp -d)
-mkdir -p "$TMP_HOME/.claude"
-HOME="$TMP_HOME" OKSTRA_HOME="$TMP_HOME/.okstra" OKSTRA_RUNTIME_HOST=external node bin/okstra install --quiet
-node --input-type=module -e "
-  import { rmSync } from 'node:fs';
-  import { join } from 'node:path';
-  rmSync(join(process.argv[1], '.okstra', 'prompts', 'coding-preflight', 'languages', 'python.md'), { force: true });
-" "$TMP_HOME"
-HOME="$TMP_HOME" OKSTRA_HOME="$TMP_HOME/.okstra" OKSTRA_RUNTIME_HOST=external node bin/okstra ensure-installed
-node --input-type=module -e "
-  import assert from 'node:assert/strict';
-  import { existsSync } from 'node:fs';
-  import { join } from 'node:path';
-  const home = process.argv[1];
-  const resource = join(home, '.okstra', 'prompts', 'coding-preflight', 'languages', 'python.md');
-  assert.equal(existsSync(resource), true);
-  console.log('single routed preflight resource restore smoke ok');
-" "$TMP_HOME"
-```
-
-Expected: `ensure-installed` prints `okstra runtime needs install: ... python.md ...`, reinstalls, and the final Node assertion passes.
-
-- [ ] **Step 4: Search for live stale references**
-
-Run repository searches for these strings and classify results:
-
-```text
-~/.okstra/prompts/coding-preflight
-convergence skill
-schema in the convergence skill
-This skill governs
-When this skill says
-Information to be obtained after executing this skill
-If you are reading this skill
-During Phase 6 of the OKSTRA skill
-During Phase 7 of the OKSTRA skill
-During okstra Skill Phases
-When the okstra skill Phase
-Project rules override this skill
-project-level Python style skill
-rust-guidelines skill
-skills/okstra-context-loader
-skills/okstra-team-contract
-skills/okstra-convergence
-skills/okstra-report-writer
-skills/okstra-coding-preflight
-```
-
-Expected:
-
-- No matches in live runtime prompts, worker templates, README, architecture docs, CLI docs, install code, or tests except test forbidden-fragment literals.
-- Matches inside dated historical plans and `agents/TODO.md` are acceptable only when they are historical/archival, not active runtime instructions.
-
-- [ ] **Step 5: Run full suite**
-
-Run:
-
-```bash
-npm run check
-```
-
-Expected: build, JS tests, Python tests, and workflow validator pass.
-
-- [ ] **Step 6: Assert runtime skill surface**
-
-Run:
-
-```bash
-node --input-type=module -e "
-import assert from 'node:assert/strict';
-import { readdirSync, existsSync } from 'node:fs';
-import { join } from 'node:path';
-import { USER_SKILL_NAMES, OBSOLETE_INTERNAL_SKILL_NAMES } from './src/skill-catalog.mjs';
-const names = readdirSync('runtime/skills', { withFileTypes: true })
-  .filter((entry) => entry.isDirectory())
-  .map((entry) => entry.name)
-  .sort();
-assert.deepEqual(names, [...USER_SKILL_NAMES].sort());
-for (const name of OBSOLETE_INTERNAL_SKILL_NAMES) {
-  assert.equal(existsSync(join('runtime/skills', name)), false, name);
-}
-assert.equal(existsSync('runtime/prompts/lead/okstra-lead-contract.md'), true);
-assert.equal(existsSync('runtime/prompts/coding-preflight/overview.md'), true);
-assert.equal(existsSync('runtime/prompts/coding-preflight/languages/python.md'), true);
-console.log('runtime surface ok');
-"
-```
-
-Expected: exit code 0 and `runtime surface ok`.
-
-## Completion criteria
-
-This work is complete only when all of these are true:
-
-- `ensure-installed` restores any missing required coding-preflight resource selected by the router.
-- No live executor/worker instruction hardcodes `~/.okstra/prompts/coding-preflight/`.
-- No live lead runtime resource describes moved internal contracts as skills.
-- Public skill surface remains exactly the six plugin-listed user skills.
-- Focused tests, targeted smoke, stale-reference search, `npm run check`, and runtime surface assertion pass freshly.

package/docs/superpowers/plans/2026-06-15-internal-skill-migration-fixups.md

@@ -1,258 +0,0 @@
-# Internal Skill Migration Fixups
-
-## Purpose
-
-The internal-skill migration is not ready to merge. The standard suites pass, but smoke checks found real install/render path gaps. This document lists the fixes required before the migration can be considered complete.
-
-## Current Passing Evidence
-
-- `npm run check` completed successfully after the migration:
-  - JS: 106 passed
-  - Python: 1614 passed, 2 skipped
-  - workflow validator passed
-- `runtime/skills` contains only the six public skills after `npm run build`.
-- `runtime/prompts/lead/okstra-lead-contract.md` and `runtime/prompts/coding-preflight/clean-code.md` exist after `npm run build`.
-
-Passing suites are not sufficient because the custom install/render smoke checks below expose uncovered paths.
-
-## Required Fixes
-
-### 1. Link-mode install must expose runtime prompt resources
-
-**Problem:** `okstra install --link` does not install or symlink the `prompts/` tree into `OKSTRA_HOME` / `~/.okstra`, so generated prompts point at files that do not exist in dev-link installs.
-
-**Evidence:**
-
-- Link install currently installs skills, agents, settings, and manifests, but no `prompts/` resource tree: `src/install.mjs:319`, `src/install.mjs:329`.
-- Copy mode does install the prompt resources: `src/install.mjs:775`, `src/install.mjs:781`.
-
-**Required change:**
-
-- In `installRuntimeLink`, add link-mode handling for `prompts/`:
-  - source: `<repo>/prompts`
-  - destination: `<OKSTRA_HOME>/prompts`
-  - behavior: symlink in link mode, matching existing link-mode style.
-- Keep copy mode unchanged.
-- Ensure link mode still refreshes public skills and agents as before.
-
-**Regression coverage:**
-
-- Add JS test for `install --link .` with temp `HOME` / `OKSTRA_HOME`:
-  - `~/.okstra/prompts/lead/okstra-lead-contract.md` exists.
-  - `~/.okstra/prompts/coding-preflight/overview.md` exists.
-  - public skills exist under detected agent home.
-  - obsolete internal skill dirs do not exist.
-
-**Smoke command after fix:**
-
-```bash
-TMP_HOME=$(mktemp -d)
-mkdir -p "$TMP_HOME/.claude"
-HOME="$TMP_HOME" OKSTRA_HOME="$TMP_HOME/.okstra" OKSTRA_RUNTIME_HOST=external node bin/okstra install --link .
-node --input-type=module -e "
-  import assert from 'node:assert/strict';
-  import { existsSync } from 'node:fs';
-  import { join } from 'node:path';
-  const home = process.argv[1];
-  assert.equal(existsSync(join(home, '.okstra', 'prompts', 'lead', 'okstra-lead-contract.md')), true);
-  assert.equal(existsSync(join(home, '.okstra', 'prompts', 'coding-preflight', 'overview.md')), true);
-" "$TMP_HOME"
-```
-
-### 2. Runtime resource paths must honor `OKSTRA_HOME`
-
-**Problem:** generated lead prompts still use `Path.home() / ".okstra"` for lead contracts and coding-preflight resources. This breaks non-default installs and tests that isolate `OKSTRA_HOME`.
-
-**Evidence:**
-
-- `build_context` seeds `OKSTRA_LEAD_CONTRACT_PATH`, `OKSTRA_TEAM_CONTRACT_PATH`, and `OKSTRA_CODING_PREFLIGHT_DIR` from `Path.home() / ".okstra"`: `scripts/okstra_ctl/paths.py:211`, `scripts/okstra_ctl/paths.py:214`, `scripts/okstra_ctl/paths.py:229`.
-- Render fallback repeats the same hardcoded home path: `scripts/okstra_ctl/render.py:1670`, `scripts/okstra_ctl/render.py:1686`, `scripts/okstra_ctl/render.py:2037`, `scripts/okstra_ctl/render.py:2044`.
-
-**Required change:**
-
-- Add one Python runtime-home resolver and reuse it wherever Okstra runtime resources are addressed:
-
-```python
-def okstra_home() -> Path:
-    raw = os.environ.get("OKSTRA_HOME", "").strip()
-    return Path(raw).expanduser() if raw else Path.home() / ".okstra"
-```
-
-- Use that resolver for:
-  - `WORKER_PROMPT_PREAMBLE_PATH`
-  - `OKSTRA_LEAD_CONTRACT_PATH`
-  - `OKSTRA_CONTEXT_LOADER_PATH`
-  - `OKSTRA_TEAM_CONTRACT_PATH`
-  - `OKSTRA_CONVERGENCE_PATH`
-  - `OKSTRA_REPORT_WRITER_PATH`
-  - `OKSTRA_CODING_PREFLIGHT_DIR`
-- Apply it in both `scripts/okstra_ctl/paths.py` and `scripts/okstra_ctl/render.py` fallback paths.
-
-**Regression coverage:**
-
-- Add Python test that sets `OKSTRA_HOME` to a temp path, renders a Claude lead prompt, and asserts:
-  - `<temp>/prompts/lead/okstra-lead-contract.md` is present.
-  - `<Path.home()/.okstra/prompts/lead/okstra-lead-contract.md>` is absent when different from temp.
-
-**Smoke command after fix:**
-
-```bash
-TMP_HOME=$(mktemp -d /private/tmp/okstra-home.XXXXXX)
-OKSTRA_HOME="$TMP_HOME/.okstra-home" OKSTRA_SKIP_INSTALL_CHECK=1 PYTHONPATH=scripts python3 - <<'PY'
-import os
-import tempfile
-from pathlib import Path
-from okstra_ctl import run
-repo = Path.cwd()
-project = Path(tempfile.mkdtemp(dir="/private/tmp")).resolve()
-brief = project / "brief.md"
-brief.write_text("# Brief\n", encoding="utf-8")
-out = run.prepare_task_bundle(run.PrepareInputs(
-    workspace_root=repo,
-    project_root=project,
-    project_id="proj",
-    task_group="group",
-    task_id="task",
-    task_type="error-analysis",
-    brief_path=brief,
-    lead_runtime="claude-code",
-    render_only=True,
-))
-expected = os.environ["OKSTRA_HOME"] + "/prompts/lead/okstra-lead-contract.md"
-assert expected in out.prompt_text
-assert str(Path.home() / ".okstra" / "prompts" / "lead" / "okstra-lead-contract.md") not in out.prompt_text
-PY
-```
-
-### 3. Obsolete internal skill pruning must remove symlinks, including dangling symlinks
-
-**Problem:** prune checks only `dirExists(path)`. A stale link-mode install can leave dangling internal skill symlinks in the agent skill home, and `dirExists` skips them.
-
-**Evidence:**
-
-- Prune uses `dirExists(path)` before `fs.rm`: `src/install.mjs:622`, `src/install.mjs:626`.
-- Exact-name prune is required because former internal contracts now ship as runtime resources, not agent skills: `src/install.mjs:619`.
-
-**Required change:**
-
-- Replace `dirExists` check in `pruneObsoleteInternalSkills` with an lstat-based entry check:
-
-```js
-async function pathEntryExists(path) {
-  try {
-    await fs.lstat(path);
-    return true;
-  } catch (err) {
-    if (err.code === "ENOENT") return false;
-    throw err;
-  }
-}
-```
-
-- Use `pathEntryExists` before `fs.rm(path, { recursive: true, force: true })`.
-- Keep exact-name allowlist from `OBSOLETE_INTERNAL_SKILL_NAMES`; do not wildcard-delete `okstra-*`.
-
-**Regression coverage:**
-
-- Add JS test where `~/.claude/skills/okstra-team-contract` is a dangling symlink before install.
-- Run `okstra install`.
-- Assert `lstat` fails for that path after install.
-
-**Smoke command after fix:**
-
-```bash
-TMP_HOME=$(mktemp -d)
-mkdir -p "$TMP_HOME/.claude/skills"
-ln -s "$TMP_HOME/missing-source" "$TMP_HOME/.claude/skills/okstra-team-contract"
-HOME="$TMP_HOME" OKSTRA_HOME="$TMP_HOME/.okstra" OKSTRA_RUNTIME_HOST=external node bin/okstra install
-node --input-type=module -e "
-  import assert from 'node:assert/strict';
-  import { lstatSync } from 'node:fs';
-  import { join } from 'node:path';
-  const path = join(process.argv[1], '.claude', 'skills', 'okstra-team-contract');
-  let exists = true;
-  try { lstatSync(path); } catch { exists = false; }
-  assert.equal(exists, false);
-" "$TMP_HOME"
-```
-
-### 4. Verifier preflight must use the same staged router as executor preflight
-
-**Problem:** executor preflight now routes via `overview.md` with language -> framework -> architecture stages, but verifier preflight still hardcodes language + `clean-code.md` + hexagonal overlay. It can miss `frameworks/node-server.md` and the router semantics.
-
-**Evidence:**
-
-- Router defines three ordered stages and all-rule accumulation: `prompts/coding-preflight/overview.md:12`, `prompts/coding-preflight/overview.md:16`, `prompts/coding-preflight/overview.md:27`, `prompts/coding-preflight/overview.md:35`.
-- Executor prompt tells workers to read `overview.md` and route through the staged pack: `prompts/profiles/_coding-conventions-preflight.md:18`.
-- Verifier prompt still says `languages/<lang>.md` + `clean-code.md` + `architectures/hexagonal.md`: `prompts/profiles/_implementation-verifier.md:91`.
-
-**Required change:**
-
-- Update verifier preflight text to require:
-  - read `~/.okstra/prompts/coding-preflight/overview.md` first;
-  - read `clean-code.md`;
-  - run the same three-stage route as executor: language, framework, architecture;
-  - iterate every rule in each stage and accumulate all matching resources;
-  - record resources loaded or `resource-unavailable` degradation.
-
-**Regression coverage:**
-
-- Add doc/contract test that `_implementation-verifier.md` contains:
-  - `overview.md`
-  - `frameworks/node-server.md`
-  - `iterate` / `accumulate` semantics
-- Add negative assertion that verifier no longer instructs only direct `languages/<lang>.md` + `architectures/hexagonal.md` loading.
-
-### 5. Remove stale “internal skill” wording from docs and worker templates
-
-**Problem:** user-facing docs and worker template still call internal resources “skills”, contradicting the new install surface.
-
-**Evidence:**
-
-- README EN still says `visible user skills + hidden internal support skills`: `README.md:79`.
-- Architecture doc still says lead/support internal skills are installed with `user-invocable: false`: `docs/kr/architecture.md:21`.
-- CLI wrapper template still calls `team-contract` a skill and authoritative source: `agents/workers/_cli-wrapper-template.md:158`, `agents/workers/_cli-wrapper-template.md:170`, `agents/workers/_cli-wrapper-template.md:172`.
-
-**Required change:**
-
-- Replace stale wording with runtime-resource language:
-  - `team-contract resource`
-  - `prompts/lead/team-contract.md`
-  - `prompts/lead/okstra-lead-contract.md`
-  - `prompts/coding-preflight/*`
-- README EN storage map should match README KR:
-
-```text
-└── okstra-*/SKILL.md            user-facing skills only (setup/brief/run/memory/inspect/schedule)
-```
-
-- Architecture “At a glance” should say public skills only are copied to agent homes; lead/support contracts are runtime resources under `~/.okstra/prompts/` and are not skill-discovery targets.
-
-**Regression coverage:**
-
-- Add/extend docs contract test to fail on live references to:
-  - `hidden internal support skills`
-  - `team-contract skill`
-  - `okstra-convergence skill`
-  - `okstra-report-writer skill`
-  - `user-invocable: false` as the described install mechanism for internal Okstra contracts
-
-## Verification Checklist After Fixes
-
-Run these in order:
-
-```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/test_docs_runtime_contract.py tests/test_lead_runtime_marker.py
-bash validators/validate-workflow.sh
-npm run check
-```
-
-Then run the three smoke commands from Fixes 1-3. The migration is complete only when all automated tests and all smoke commands pass.
-
-## Non-Goals
-
-- Do not reintroduce hidden/internal skills under agent skill homes.
-- Do not add compatibility aliases for old internal skill names.
-- Do not wildcard-delete `okstra-*` directories; prune only names in `OBSOLETE_INTERNAL_SKILL_NAMES`.
-- Do not inline all coding-preflight files into launch prompts. The router must keep lazy, situation-based loading.