Umut CANandClaude Opus 5
b03a7615b1
Tool count 131 -> 154; 474 -> 1242 collected tests. The release exists for two measured reasons. A 149-tool catalog costs a client ~40,300 tokens before it has asked for anything, and a drafter searching the way drafters think -- FILLET, BPOLY, QSELECT, WBLOCK -- scored df=0 against the stock index, because those words were simply not in the data. Discovery and batching - DISCOVERY_MODE=search replaces the catalog with search_tools + call_tool, ranked over an AutoCAD command and synonym corpus (discovery/aliases.py) on top of fastmcp's BM25 index. Measured: 40,305 -> 356 tokens advertised. - cad_batch runs a step list in one round trip; fields= projects result-heavy responses. The `core` profile is gone -- discovery replaced it. Honesty debt (Tier 0) - OCS/ECS: `extrusion` appeared nowhere in this codebase, so mirrored and rotated geometry reported coordinates that were quietly wrong. backends/ocs.py translates at the backend boundary; every tool coordinate is WCS on both engines, and a tilted plane refuses rather than answering with a number that looks fine. - drawing_save_as(fmt="dwg") wrote DXF bytes to a .dwg path. drawing_audit never repaired. analysis_measure_area shoelaced points the caller typed in. - ezdxf calls gained a per-call timeout, so one hung call can no longer wedge a server whose document lock is a single asyncio.Lock. Architecture - The 1854-line backend ABC is 19 contract modules; @capability(key, reason=) makes optional methods declarative and a gate fails on undeclared holes. - 8 layout/viewport tools, CHSPACE, CAD_PROGID escape hatch. - Wave A: selection filters, boundary tracing, hatch depth, annotation objects, measurement -- 13 tools of a planned 39. The REGION and 2D-boolean family was cut on evidence: add_region() yields zero ACIS bytes and the greiner_hormann substitute loses 28.2% of the area on a square with one semicircular edge. Verified against a live AutoCAD 2026, which found four COM defects no amount of reading would have caught -- AcadPViewport has no ViewCenter, and the line that set it had been swallowed by a bare except since v1.4. Benchmark v3 (15 tasks) and what it caught - v2 scored this server 10/10, which carried no information: every task in it exercised something the server was built around. Five tasks were added because they can fail, and three did while being written -- a hatch could not be measured though the refusal listed HATCH as measurable, the boundary tools and the measure tool disagreed about the same shape (139.2177 vs 139.2699), and a circle stored as two bulged vertices measured 0.0. - Competitor reports are NOT re-scored. They are pinned v1.4 runs against v2 and were never asked these five questions; the chart shows those rows `not run`. - Correctness A/B: 21/24 -> 24/24, zero regressions. Performance, stated plainly The published v1.4 perf report was recorded on CPython 3.14 and the new one on 3.11.15, so the apparent 2-6x speedup is the interpreter, not this release. Re-measured on one interpreter, v1.5.0 is 28% slower creating entities and 22% slower on the 10k roundtrip. Fully attributed: EZDXF_CALL_TIMEOUT=0 restores v1.4.0's exact numbers. That is the deadlock fix being paid for, the knob is documented, and winning it back is on the 1.6 roadmap. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
80 lines
2.7 KiB
Python
80 lines
2.7 KiB
Python
"""ACIS solids (live AutoCAD only).
|
|
|
|
Split out of the single 1854-line ``AutoCADBackend`` ABC in v1.5.0 (M7).
|
|
``AutoCADBackend`` composes every contract in this package, so importing
|
|
``backends.base.AutoCADBackend`` is unchanged for callers.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from abc import ABC, abstractmethod
|
|
|
|
|
|
class SolidContract(ABC):
|
|
@abstractmethod
|
|
async def solid_box(
|
|
self, cx: float, cy: float, cz: float, length: float, width: float, height: float
|
|
) -> dict:
|
|
"""Create a 3D solid box centered at (cx, cy, cz)."""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def solid_cylinder(
|
|
self, cx: float, cy: float, cz: float, radius: float, height: float
|
|
) -> dict:
|
|
"""Create a 3D solid cylinder centered at (cx, cy, cz)."""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def solid_extrude(
|
|
self, profile_handle: str, height: float, taper_angle: float = 0.0
|
|
) -> dict:
|
|
"""Extrude a closed profile (circle/closed polyline) into a solid."""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def solid_revolve(
|
|
self,
|
|
profile_handle: str,
|
|
axis_x1: float,
|
|
axis_y1: float,
|
|
axis_x2: float,
|
|
axis_y2: float,
|
|
angle: float = 360.0,
|
|
) -> dict:
|
|
"""Revolve a closed profile around an axis into a solid."""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def solid_boolean(self, target_handle: str, tool_handle: str, operation: str) -> dict:
|
|
"""Boolean two solids: operation is union | subtract | intersect."""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def drawing_audit(self) -> dict:
|
|
"""Audit the drawing, applying every repair the backend can make.
|
|
|
|
This MUTATES the drawing. Returns ``{"ok", "repaired", "fixes",
|
|
"fix_count", "errors", "error_count"}``, where ``fixes`` are problems
|
|
already repaired and ``errors`` are problems that could not be; both are
|
|
lists of ``{"code": int, "name": str, "message": str, "handle": str |
|
|
None}``.
|
|
|
|
A backend that repairs but cannot observe its own result reports
|
|
``repaired``/``fix_count``/``error_count`` as ``None`` — never ``0``,
|
|
which would claim nothing was wrong — plus ``"detail": "unavailable"``
|
|
and ``"capability": "audit_detail"`` so a client can pre-check the
|
|
boundary. Any implementation that repairs MUST mark the document dirty,
|
|
or the repair is discarded the next time the document is closed.
|
|
"""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def drawing_close(self, save: bool = True) -> dict: ...
|
|
|
|
@abstractmethod
|
|
async def drawing_undo(self) -> dict: ...
|
|
|
|
@abstractmethod
|
|
async def drawing_redo(self) -> dict: ...
|