Skip to content

v1.6: Runtime Verification

Choose a tag to compare

View all tags
@KJ5HST KJ5HST released this 14 Mar 15:50
· 444 commits to main since this release
v1.6
a45d9cb

What's New

Runtime verification finding — Two consecutive sessions shipped code that compiled cleanly but broke at runtime due to plugin version collision and registration order. Both noted "no runtime verification" in self-assessment without treating it as a defect.

Changes

  • New finding in validation table: "Build success is not runtime verification" (Sessions 151-153)
  • Phase 6, step 2 expanded — runtime smoke test guidance for changes involving service registration, plugin loading, dependency injection, config resolution, or handler dispatch
  • New Phase 5 anti-pattern — "Treating build success as verification": a successful build proves compilation and dependency resolution, not that services register in the right order or that components don't shadow each other at load time
  • CLAUDE.md added (v1.5) — guidance for AI agents editing the methodology repo

Adopter Action

If you use SESSION_RUNNER.md, consider adding a runtime smoke test step to your close-out phase for deliverables that change runtime behavior. The starter kit will be updated in a future release.

Assets 2
Loading