[kvlonge]

Why

Resource-level lifecycle facts do not identify which microbatch interval is currently active. Operators need bounded, append-only evidence to distinguish delayed, completed, and failed work, including concurrent and recovery execution.

Changes

• emit start, completion, and failure facts for each active microbatch interval
• include active and planned cursor bounds, batch progress, configured and effective sizes, strategy, run type, and recovery classification
• preserve version 1 lifecycle catalogs while extending version 2 and lifecycle-event sink filtering
• document the lifecycle contract and cover serial, concurrent, failure, cleanup, and capped out-of-order execution

Verification

• uv run pytest tests/unit/src/sqlbuild/runtime/observability tests/unit/src/sqlbuild/runtime/event_exporting/test_policy.py tests/unit/src/sqlbuild/runtime/event_exporting/test_sinks.py tests/unit/src/sqlbuild/executor/build/classes/test_build_scheduler_microbatch.py tests/integration/src/sqlbuild/executor/run/microbatch/test_microbatch_execution.py tests/integration/src/sqlbuild/executor/run/microbatch/test_microbatch_observability.py -n auto --dist loadfile
• make check-ci
• public repository hygiene scan