Extend doctor and validation diagnostics for compiled packages

## Problem statement When a compiled package fails after installation, users need diagnostics that connect the failure back to the compiled workflow, not just generic package or provider state. Existing `lineage doctor` (#52) and `lineage package validate` (#31) are the right places to surface those checks. ## Scope - Extend validation output with compiled-package metadata, model version, compiler version, and behavioral consistency status. - Extend `lineage doctor` to detect stale or incompatible compiled package state where relevant. - Check that Claude and Codex materialized context contains generated workflow summaries and ordered steps, building on #18 and #19. - Check workflow execution readiness through the `lineage workflow run` model from #49 without requiring a live provider in default tests. ## Acceptance criteria - `lineage package validate` identifies compiled packages and reports model/artifact consistency status. - `lineage doctor` reports actionable fixes for stale compiled package materialization or missing provider-visible context. - Diagnostics cross-reference package name, workflow name, provider, and missing artifact. - Tests cover clean compiled package, stale materialization, missing context block, and missing workflow step. ## Dependencies - Builds on #18, #19, #31, #49, and #52. - Depends on round-trip fixtures and compile-time consistency checks. ## Non-goals - No live provider invocation. - No registry UI or website diagnostics. - No replacement for existing doctor checks. ## Sequencing Final child issue in behavioral validation. This ties compiled-package validation into the existing receiver-facing diagnostic surface.