Shipped and released
Now
Page 14 of 14. Every release ever published is still here — across these pages, in theAtom feed, and at its own permanent link. Nothing is dropped as it ages.
Released highlights, page 14
- Pack installers can now provide a useful manual next step without forcing a first-run prompt. Level A packs may add an optional
Next:instruction, giving adopters a deterministic handoff when runtime hooks do not execute.
- Pack installers can now provide a useful manual next step without forcing a first-run prompt. Level A packs may add an optional
- Core now adapts to a repository's own development context instead of expecting the repository to adopt the pack's document layout. The doctor finds existing architecture, contributor, command, and scoped guidance, labels inference honestly, and proposes only approved root or subtree deltas.
- Architecture design now starts from the repository's existing sources and implementation idioms, wherever they live. A custom
DESIGN.md, scoped guidance, or repository-owned framework primitive can steer the design without first being copied intodocs/architecture/reference.md.
- Architecture design now starts from the repository's existing sources and implementation idioms, wherever they live. A custom
- Nested OKF corpora now compile and check consistently on Windows. Generated index paths use the bundle’s portable POSIX form instead of inheriting the host path separator, so Windows no longer reports clean nested indexes as stale.
- You can now turn a broad “assess this repository’s architecture” request into a correctable current-state model, an evidence-backed attention map, focused drill-downs, and a sequenced action plan. The assessment starts with a read-only survey, lets you correct its map before deeper investigation, and can progressively examine assurance, optimization, growth, transformation, or disposition without confusing repository conventions with architectural evidence.
- Work-loop commands now run from the project root without path discovery. The skill resolves its own installed directory before invoking the loop engine, cohort, or freshness scripts, so Codex and Claude Code no longer lose a turn searching for a repository-root
scripts/directory that does not exist.
- Work-loop commands now run from the project root without path discovery. The skill resolves its own installed directory before invoking the loop engine, cohort, or freshness scripts, so Codex and Claude Code no longer lose a turn searching for a repository-root
- Catalogue builders can now reason about package formats independently of runtime adapters. The installed CLI exposes a validated contract for the existing APM and Claude-plugin routes, including their layouts, component support, admission, marketplace, and lifecycle behavior.
- The changelog rule now says who "user-visible" means, so you can tell whether your change needs an entry. An entry is required when a pull request bumps a released artifact's version — a pack or a published package — and repository tooling that ships in no release needs none. The old wording asked for an entry on "any user-visible behavior change", which read as covering maintainer-only tooling and offered no heading to write it under.
- Writing an RFC or an ADR now files its reusable lessons for you, and only once the decision is actually settled. Supporting lessons are handed to project knowledge at clean handoff and accepted-decision points, so a draft you abandon leaves nothing behind. If project knowledge is not installed, authoring proceeds unchanged and writes no stand-in file.