v7

• 2026-09-30 "Human" → "supervisor" everywhere. The actor a workflow reports to is the supervisor — the human, or the session that spawned this one. Guides/Core/process-flow.md gains ## Supervisors (definition and reporting hierarchy; "operator" still means the agent executing a guide). Every guide with a ## Gates section inlines one sentence in ## Gates, added to the standard template: the supervisor is the human or authorized agent outside this workflow that resolves its discussion items and reviews its gates; the executing agent does not resolve or approve its own. Renamed with it: Human-owned / human-filled → project-owned (Integration template, installer); Human spec → Supervisor input (requirements and UI Map change items); {human response} → {supervisor response} (Integration template placeholder); triage label human-decision → supervisor-decision (findings logs keep the old label as history); ## Human-in-the-loop contract → ## Supervisor-in-the-loop contract (debugging guide); (LLM + human) → (agent + supervisor) (both retros). "human" remains only as plain English (human-readable, manual testing) and inside the definition. House style's terminology rule and two sanity-scan checks enforce it.
• 2026-09-30 Installer: agent instruction files are managed blocks. CLAUDE.md and .agents/AGENTS.md are project-owned; the installer owns only a BEGIN/END block inside them — created from the template if absent, otherwise only the block (and its marker date) is updated; a file with the old whole-file header is converted on the next adapter run. New Templates/agents/claudecode/CLAUDE.md (template.claude-instructions); Templates/agents/codex/AGENTS.md is block-form and drops its H1. Install/managed-header.md is reorganized by form — whole-file header, marker comment, delimited block — one rule each. The three runbooks' Classify step and Install/conflict-precedence-policy.md use three classes: managed file, managed block, not managed (legacy candidates proposed for cleanup). Symlink is no longer a managed form — no adapter creates them; existing symlinks into the submodule are legacy candidates.
• 2026-09-30 Installer: one prompt. The README's per-adapter prompts collapse into one pointing at new Install/install-update.md (runbook.install-update), which asks the supervisor which adapters to install — Claude Code / Cursor / Codex, defaulting to the one it runs in, pre-selecting any in skai/install-state.json — and runs each adapter runbook in full.
• 2026-09-27 New guide Guides/Requirements/requirements-baseline.md (guide.requirements-baseline), read from requirements-authoring.md when it infers Baseline mode: orient on the product before reading the implementation, draft cited files before their dependents, and why authoring is not delegated. requirements-authoring.md gains the Baseline pointer at Initiation step 5 and one sentence in Working a backfill.
• 2026-09-28 Repo layout. Maintainer runbooks → internal/ (guide.maintain-retro, guide.ticket-implementation keep their ids; new sourcePaths). Refinement findings logs and design specs → skai/refinement-reviews/; the refinement guide now names skai/refinement-reviews/<target>-design.md as where a target's spec lives, and the cold-review template's {{SPEC}} points there.

Migration:

1. Re-run every installed adapter. The inlined gates blocks, wrapper descriptions, and Integration template placeholders changed.
2. On that run, an existing CLAUDE.md or .agents/AGENTS.md with the old whole-file header is converted to block form; add your own content above the block afterwards.
3. Two assets moved: maintain-retro.md and maintain-tickets.md → internal/. A host that copied either re-copies from the new path; nothing else installs from these.
4. Two assets added: template.claude-instructions, guide.requirements-baseline; one runbook added: runbook.install-update. No asset ids changed.