Skip to content

v0.2.0 — structure, security & evidence

Choose a tag to compare

@hellOoSaksit hellOoSaksit released this 20 Jun 11:18
4922dcb

Second release. Everything since v0.1.0, focused on structure, security, and proof.

Highlights

  • OpenSSF Best Practices passing badge (project 13318) + a green docs-lint CI workflow (scripts/docs-lint.sh + Markdown link check) running on every push/PR.
  • Guided intake in the scaffolder: asks new vs refactor first, then name + logic, then a tiered stack interview (recommendation + reason for each — the stack is never fixed in the prompt; it's a per-project, job-by-job choice).
  • AI key/secret-handling rule in both prompts (applies to any source, not only .env) + a Security & secret-handling section in the README.
  • Backup / clean-git-tree guardrail before refactoring (and a prominent backup warning in the README) — every change one undo away.
  • Token economics + anti-drift README sections, backed by real, recorded evidence in docs/evidence/measurements.md (verbatim tiktoken numbers — 83–96% less context per task on a real 42-doc project — and a docs-lint pass/fail demo) plus research citations.

Changed

  • Repo tidied: kit files → kit/, community-health files → .github/ (still auto-detected). Links + badge URLs updated.

See CHANGELOG.md.