fix: this change introduces strict versioning for docs

[zcstarr]

This change adds strict versioning for docs from the markdown gen. This means that the markdown generator will properly support specific versions and will need to be extended explicitly if we have a version change

This introduction allows us to be more intentional about what tool supports what version

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
markdown-gen	Ready	Preview, Comment	Feb 26, 2026 5:44am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.64%. Comparing base (220d782) to head (f67b9fd).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #58   +/-   ##
=======================================
  Coverage   83.64%   83.64%           
=======================================
  Files           3        3           
  Lines        1137     1137           
=======================================
  Hits          951      951           
  Misses        186      186           

Files with missing lines	Coverage Δ
packages/markdown-generator/src/humanize.ts	51.74% <ø> (ø)
packages/markdown-generator/src/lib.ts	77.57% <ø> (ø)
packages/markdown-generator/src/schema.ts	92.15% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[shanejonas]

do we need all this if we have spec types?

[zcstarr]

yeah all consumers have to opt into joint types , perhaps in the future we publish an omni type , not sure if that will be always useful is the only concern there. Maybe as we expand we can work that out