Unify operator-facing workflow projections and add drift guards

[danielbdyer]

Motivation

• Provide a single operator-facing workflow surface that aggregates projections and navigation so operators can move from hotspot → trace/evidence → proposal approval → rerun-plan without manual file hunting.
• Make provenance and governance explicit and consistent across generated projections (workflow, trace, review, graph) using the repository envelope contract.
• Emit deterministic next-action recipes for common operator actions and prevent drift between runtime trace and operator views.

Description

• Extended inspectWorkflow to collect latestRun, proposalBundle, and taskPacket context, and to produce a shared view model (sharedViews) keyed by scenario/run with resolutionMode, winningSource, lineage, governance, and nextActions.
• Added hotspotNavigation, projections (per-surface envelopes for workflow, trace, review, graph) and navigation.recipes to the workflow output, exposing consistent envelope fields (kind, version, stage, scope, ids, fingerprints, lineage, governance).
• Aligned operator command recipes to valid CLI entry points and normalized fallback behavior (e.g. inbox fallback for missing proposals).
• Updated unit tests to assert the new shared view model, navigation flow, projection envelope shapes, and cross-surface consistency of winning-source/governance during runs; small fingerprint lookup fix to prefer the task packet entry fingerprint.
• Files changed: lib/application/workflow.ts, tests/compiler.spec.ts.

Testing

• Ran npm run -s build, which completed successfully.
• Ran the focused test suite npm test -- tests/compiler.spec.ts and all tests passed (13 passed).
• Note: an earlier npm run -s typecheck run surfaced pre-existing, unrelated issues in tests/runtime-agent-pipeline.spec.ts; those failures were not caused by these changes and the focused spec used for this PR passed.

---

Codex Task