docs: scaffold example integrations repository

[rlippmann]

Summary

• Establish the initial scaffold for context-compiler-example-integrations.
• Replace the initial MIT license with Apache-2.0 for Context Compiler ecosystem consistency.
• Add repository governance docs, contribution guidance, issue templates, and PR template.
• Add the enforcement-point-first README positioning and example catalog.
• Create placeholder Python and TypeScript example trees.
• Add minimal scaffold validation CI.
• Add mixed Python/TypeScript .gitignore.

Why

This repository exists to answer:

Where can authority be enforced?

The scaffold establishes the repo boundary before any examples are migrated or implemented:

• context-compiler: what is the authority contract?
• context-compiler-directive-drafter: how is authority acquired?
• context-compiler-example-integrations: where can authority be enforced?

This PR intentionally contains repository scaffolding and governance only.

Example metadata

• Enforcement point: Repository scaffolding / governance
• Domain: N/A
• Technology/runtime: GitHub repository infrastructure
• 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

Example-specific checklist items are satisfied as not applicable for this repository-maintenance scaffold. No examples are migrated or implemented in this PR.

Included:

• README / CONTRIBUTING / AGENTS / SECURITY / CODE_OF_CONDUCT
• GitHub issue and PR templates
• Apache-2.0 license
• minimal CI workflow
• Python and TypeScript placeholder directory trees
• mixed Python/TypeScript .gitignore

Not included:

• example migrations
• new example implementations
• package publishing
• TypeScript directive-drafter work
• runtime-specific integrations