docs: describe the flat DAG and physical export instead of the removed logical export

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W7qG9aFyPij5uWsyAJCxDW

Author: zzylol

crates/types/src/lib.rs

@@ -3,8 +3,8 @@
 //! - [`ir`] — the unified operator IR (#511): one operator DAG before and
 //!   after ASAP optimization ([`ir::OperatorNode`]), arranged by #511 section
 //!   ([`ir::operator`], [`ir::scalar`], [`ir::schema`], [`ir::properties`]),
-//!   plus its passes (canonicalize, CSE, timing) and the wire export
-//!   ([`ir::export`]). No execution logic lives in this crate (issue #190).
+//!   plus its passes (canonicalize, CSE, timing), the flat DAG
+//!   ([`ir::flat`]) and the physical export ([`ir::physical_export`]). No execution logic lives in this crate (issue #190).
 //! - [`workload`] — planner inputs (#509): query and data workloads, the
 //!   lowered [`workload::parsed_workload`], and [`workload::resources`].
 //! - [`deployment`] — the deployment's capabilities, a planner input (#509)

docs/develop_docs/library-api.md

@@ -275,9 +275,8 @@ optional also does not guarantee every planning operation can succeed without it
 | Function/type | Purpose |
 | --- | --- |
 | `asap_types::ir::apply_materialization_timings(&root, &assignment, &mut TimingMemo::new())` | Write execution timing into every node from a `MaterializationAssignment` (default: all query time) and validate the data-state edges; `PlanOutput::execution_timed_dag()` applies the default to a planned workload |
-| `asap_types::ir::export::compile_logical_asap_dag(&root)` | Export a DAG as a `LogicalASAPDAG` for inspection; not a physical plan |
-| `LogicalASAPDAGDocument::new(dag)` and `.validate()` | Versioned envelope and explicit validation; constructing it alone does not validate |
-| `asap_types::ir::export::compile_physical_asap_dag(&timed_root)` | Export a timed DAG as the `PhysicalASAPDAG` a deployment binds; rejects an untimed node |
+| `asap_types::ir::flat::flatten(&roots)` | A DAG as a flat, serializable node list (`FlatDag`, children as node ids) for inspection; not a physical plan |
+| `asap_types::ir::physical_export::compile_physical_asap_dag(&timed_root)` | Export a timed DAG as the `PhysicalASAPDAG` a deployment binds; rejects an untimed node |
 
 Choose the export matching your intended handoff, and preserve the selection
 report a downstream needs instead of exporting only a bare DAG. For public