Fix analysis path and retire legacy code

[reiase]

What changed

• fix training plan correctness around output dependencies, TP=1 accounting, RS+AG divisibility, and strategy binding
• connect inference application entry points to CostResolver/CostQueryContext and propagate task uncertainty/provenance
• add Chrome Trace export and an explicit one-click Perfetto action without replacing the existing analysis page
• move floating-point analysis into the primary NiceGUI workbench
• add dedicated training, inference evidence, Chrome Trace, float-analysis, and UI regression coverage
• retire unused tracing/framework adapters, event types, simfloat, stale pages/examples, compatibility shims, duplicate dependency manifests, and unused dependencies
• align bilingual design/status documentation with the implemented boundary

Why

The portable plan path had several P0 correctness and integration gaps: parts of the training DAG did not express the intended dataflow, evidence imported through the resolver was not reachable from the default application path, and the UI exposed only a dependency projection without a portable trace handoff. The repository also retained multiple disconnected framework hooks, pages, examples, and package dependencies after their replacement paths were established.

Impact

The canonical workload facts remain target-neutral. Inference evidence now reaches reports through the unified resolver path, training lowering rejects or represents previously silent mismatches, and users can export the current dependency-projected timeline to Perfetto while retaining all existing analysis content.

The exported Perfetto trace is deliberately labeled as a dependency projection. It is not yet a resource-scheduled SimulationTraceIR or an executable timeline.

Validation

• uv run pytest -p no:cacheprovider — 143 passed
• Ruff on active Blueprinting paths and tests — passed
• python scripts/check_docs_i18n.py — 31 bilingual pairs passed
• mkdocs build --strict — passed
• git diff --check — passed