Clarify bounded CTO supervision and actionable findings for 6.2.1

CHANGELOG.md

@@ -2,6 +2,44 @@
 
 All notable changes to SkipHow 2.x and later appear in this file. Earlier release notes remain available on [GitHub Releases](https://github.com/mzored/SkipHow/releases).
 
+## 6.2.1 (2026-10-04)
+
+Clarify the existing CTO responsibility to assess material risks and recurring costs across the authorized project,
+question the fit of current solutions, and resolve supported engineering findings at safe boundaries, including
+fast-fixes iteration. The owner's outcome stays first and further improvement must justify its total cost. Authority,
+read-only requests, protected actions, and the local delivery boundary remain unchanged.
+
+Make feasible authorized repair in this run the default. An issue preserves genuinely unfinished work and cannot
+replace a feasible repair. Deferral needs a concrete decision, protected action, blocker, or evidenced cost that
+would materially compromise the owner's outcome, with its reason and resume condition retained. Separability or
+an existing issue alone is no reason to leave the work for a later agent.
+
+Reuse one task-writing contract for plan and genuinely deferred implementation issues. The issue carries context,
+evidence, authority, constraints, observable acceptance, dependencies, and return proof for an executor without this
+conversation. A short bug or ordinary SkipHow launch references the issue; blocked preparation stays explicitly
+blocked. Small findings do not inherit the full planning workflow.
+
+Design guidance compares retention, simplification, replacement, and removal, preserves complete required behavior,
+and accounts for callers and superseded responsibilities. Verification permits evidenced consolidation or replacement
+of pre-existing redundant checks while preserving unique proof and legitimate fixed product examples. Frequent cheap
+checks remain useful. Triggered guidance is recovered before its act when absent after compaction.
+
+Extend the unrun corpus with a project opportunity outside a small CLI edit, old coupled tests, and a compacted live
+feedback stream. Validate the export oracle against different complete and incomplete repairs. Remove a setup oracle's
+unnecessary requirement to apply every available remedy and correct reversed billing defect metadata. No paid model
+comparison was run; new behavior, savings, activation, and continuity remain `UNVERIFIED`. The package structure and
+installation mechanism are unchanged, so new clean-install experiments are not required.
+
+Repair an observed checker bottleneck: exact-spelling validation now enumerates native entry names instead of
+constructing a `Path` for every sibling in each ancestor directory. Exact case, Unicode spelling, symlink handling,
+and failure behavior remain unchanged. Focused boundary tests and the full local gate pass with the existing
+120-second limit; no timeout was raised or coverage removed.
+
+Independent isolated Codex source review approved the runtime candidate with no qualifying findings or wording
+suggestions. A narrow independent review approved the checker substitution. The optional Claude source review
+could not authenticate and remains `UNVERIFIED`; its strict schema validator passed. Behavioral effects and savings
+remain `UNVERIFIED`.
+
 ## 6.2.0 (2026-10-03)
 
 ### Changed

README.md

@@ -37,7 +37,7 @@ This is a responsibility handoff, not a fixed development pipeline. A small requ
 | More autonomy risks losing product control | The owner still decides visible behavior, scope, cost, risk, privacy, rollout, and protected actions. |
 | Every request becomes a ceremony | Process scales with the work. Specs, tickets, TDD, worktrees, subagents, and review appear only when the request or project needs them. |
 | "Done" means the agent stopped | Completion needs fresh evidence. Anything blocked or unverified stays visible. |
-| Important engineering problems wait for you to notice them | During ordinary work, the lead assesses material risks and accumulating costs even when the requested behavior and checks pass, then fixes the engineering ones once your change is delivered and records the rest where your project tracks work, rather than leaving them as suggestions for you to start. |
+| Important engineering problems wait for you to notice them | The lead looks for material risks and recurring costs across the authorized project, questions whether current solutions still fit, and repairs engineering findings at safe boundaries, including during iteration. Your outcome stays first; further improvement must justify its cost. The rest receives explicit disposition in your project's work records. |
 | You need a different command for every kind of work | One entry covers questions, decisions, research, bugs, changes, iterations you want to look at first, project status, reconciliation, cleanup, delivery, pause, and resume. |
 | Long or delegated work becomes your coordination job | Continuity, reconciliation, integration, and any tracking your project calls for remain engineering work for the agent. |
 | Autonomy widens side effects | Production, releases, credentials, access, material deletion, and other protected actions require an explicit grant. |

VERSION

@@ -1 +1 @@
-6.2.0
+6.2.1