build: prepare Python and TypeScript packages for publication

[rlippmann]

Summary

Prepare the Python and TypeScript discovery packages for first publication by polishing documentation, tightening package contents, and aligning packaging with the current Context Compiler architecture.

Why

The repository now has distinct GitHub, PyPI, and npm documentation surfaces. This change also makes the published artifacts match the intended discovery-first experience by reducing required dependencies, removing repository-only content, and ensuring clean install layouts for both Python and TypeScript.

Example metadata

• Enforcement point: N/A (repository maintenance)
• Domain: Packaging / documentation
• Technology/runtime: Python packaging (Hatchling), npm
• 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

• Python packaging now targets context-compiler>=0.8.0 with optional extras for example-specific integrations.
• The Python wheel installs under context_compiler_example_integrations/ instead of a top-level python/ directory.
• The TypeScript discovery package has a dedicated publishable package with a constrained npm package surface.
• Package READMEs are now language-specific (python/README.md for PyPI and typescript/README.md for npm), while the repository README remains the GitHub landing page.