fix: repair published package links

[rlippmann]

Summary

• bump the Python and TypeScript package versions to 0.1.1
• switch the published TypeScript README links to absolute GitHub URLs for registry-safe rendering
• correct the Python package README note to match the actual base dependency floor

Why

The July 16, 2026 0.1.0 package pages exposed broken or misleading published documentation:

• npm rendered README links that did not resolve correctly from the package page
• the PyPI README claimed the base dependency floor was context-compiler>=0.8.0 even though package metadata requires context-compiler>=0.8.3

Example metadata

• Enforcement point: N/A
• Domain: package publishing
• Technology/runtime: PyPI, npm, GitHub release packaging
• Example type: repository maintenance
• Does this use directive drafter? should normally be no: no
• Does this derive state from model output? must be no for primary examples: no

Checklist

• Repository scaffolding / governance change
• One primary enforcement point
• Explicit authoritative state
• No model-derived state mutation
• Adversarial stub or equivalent test
• Observable runtime behavior change
• Domain vocabulary is natural
• Framework is secondary to the enforcement point
• Docs updated
• Tests/smoke checks added where practical

Notes

• Verified with uv build from the repo root
• Verified with npm pack --dry-run from typescript/
• This is a packaging and published-documentation repair release for 0.1.1