The drawing declarations were exploratory scaffolding for the dxf engine
and outlived their purpose once the engine contracts landed; example
keeps only the 3D modeling chain (u_link/shell/assembly/export/verify).
Generated artifacts (dxf/png/diag/action-log) were already removed from
out/ — only 3D exports remain. Workflow doc now points at driving the
loop directly via SheetPlan (solve/evaluate/apply/render) with the
diag_png auto-diagnostic instead of the deleted driver script.
Mirror the single-part-modeling role architecture: Role 1 Drawing
Requirement Confirmer (blocking ask round -> DRAWING.md), Role 2 Sheet
Planner (view roster + R5 coverage ledger), Role 3 Layout Arbiter, Role 4
Visual Reviewer (delegated PNG verdict, repair: loop), Role 5 Drawing
Exporter — with the Role 3/4 alternation running per sheet.
Role 3 now carries the engine's core layout method as an explicit
validate-and-rollback cycle: viz colored review image (ok/unsolved/warn/
accepted + free-movement corridors) -> plan.evaluate() digested
violations/corridors -> action-log JSON (rad/dia/lin/lead/accept) ->
plan.apply() with reject-and-rollback residuals -> pixel diff of the two
replays -> repeat until warn=0. Record the division of labor (engine owns
deterministic truth, agent owns discrete arbitration) and the
action-log-as-decision-log invariant. Route evaluate/apply in the domain
API groups.
Add references/workflows/engineering-drawing.md (preliminary staged
workflow: preconditions -> declare views -> declare datums/dims -> solve
and audit -> render and visual review) and references/domains/
engineering-drawing.md (capability boundary, R1-R7 solver contract, API
groups, known engine limits, failure modes). Route the new goal in
SKILL.md.
Backfill docstrings for the dxf_engine public surface (declaration
dataclasses, SheetPlan, render_plan) so auto_docs_gen can produce their
API pages under references/docs/api/ with an Engineering Drawings index
section, following the inspect/brep sub-namespace pattern.