v0.9.2 — Spec Kit extension ships from catalogify

The first catalogify release on GitHub, and the first to ship the Spec Kit extension.

Spec Kit extension

The okf Spec Kit extension is now built from this repository and attached to every release as speckit-okf-<version>.zip. It used to live in alexcpn/speckit_okf, which is being retired; its last release there was 0.6.0.

specify extension add okf --from \
  https://github.com/alexcpn/catalogify/releases/download/v0.9.2/speckit-okf-0.9.2.zip

It provides /speckit.okf.generate, update, clarify, validate and verify. It runs the same scripts and follows the same workflow as this version of catalogify, and doesn't need catalogify installed. Config goes in .specify/extensions/okf/okf-config.yml.

Fixed compared with speckit_okf 0.6.0:

• The shell scripts failed with "permission denied" after a zip install. Spec Kit extracts archives without file modes, and the commands ran the scripts directly. They now run them through bash.
• specify extension add listed the commands with blank descriptions.
• The commands pick up two catalogify fixes that never reached speckit_okf: the shallow-clone warning below, and V4 verification narrowed to unambiguous identifiers (from 0.9.1).

History mining warns on a shallow clone

A shallow clone has almost no history to mine, and until now nothing said so. okf-history returned the few commits that had been fetched, so reverts and risky commits were simply missing, and the output looked like a quiet repository. This was found by auditing a published Airflow catalog: all 17 concepts had no gotchas and no citations because the clone that generated it was shallow.

okf-history now prints a warning that names the fix (git fetch --unshallow, or --deepen=2000). On a full clone it says nothing.

Docs

• The README explains how to use the agent workflows, and its Spec Kit section installs from this release.