feat: add execution authorization examples

[rlippmann]

Summary

Adds generic Python and TypeScript execution-authorization examples.

The examples demonstrate that host-side expense approval actions are authorized only by explicit Context Compiler authoritative state. User wording, adversarial requests, and conflicting directives do not grant execution authority.

Why

Execution authorization is a distinct enforcement point.

These examples show that Context Compiler determines whether an action is authorized, while the host owns the action itself. The host executes the expense approval only when authoritative state permits it.

The examples also demonstrate that contradictory directives produce clarification behavior rather than silent overwrite or last-directive-wins semantics.

Example metadata

• Enforcement point: execution authorization
• Domain: expense approval
• Technology/runtime: generic Python, generic TypeScript
• Example type: minimal example
• 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

Both implementations cover:

• authorized state allows expense approval
• absent state blocks expense approval
• prohibited state blocks expense approval
• adversarial request text does not authorize execution
• contradictory directives produce clarification behavior
• host execution decisions depend on authoritative state and decision outcome, not user wording

TypeScript validation scripts were updated so the new example participates in repository validation.