Skip to content

AutoCAD Skills v1.2.0 - MCP Postconditions and Semantic DRC

Choose a tag to compare

View all tags
@beiming183-cloud beiming183-cloud released this 16 Jul 14:15
v1.2.0
716a1bf

Why this release

This release turns a failed engine-drawing prototype into hard runtime and release gates. Tool success is no longer accepted as entity correctness, and a DRC run without FAIL is no longer accepted as drawing correctness.

本版本重点修复放行逻辑：MCP 坐标串写或后置条件不一致时必须停止；拓扑 WARNING 必须逐实体归类；概念图不能以低精度名义掩盖飞线、未闭合边界、视图来源冲突或比例错误。

MCP postcondition contract

  • Add E_POSTCONDITION_MISMATCH as a hard failure.
  • Require immutable/self-contained requests and strict schema rejection of missing, mistyped, or extra fields.
  • Require per-operation requested, actual, and field-level diff, plus complete handle/document/transaction identity.
  • Read every created/modified entity back and compare type, layer/role, coordinates, parameters, associations, closure, and semantic ownership.
  • Roll back immediately on mismatch; after one failed recovery, switch to a verified backend such as a structured ezdxf path or report blocked.
  • Add a 100-cycle interleaved LINE/RECTANGLE/POLYLINE/MTEXT conformance fixture for cross-request state leakage, strict-field rejection, rollback, document naming, and plotting identity.
  • Distinguish legitimate idempotent already_satisfied operations from silent no-ops.

Semantic DRC

  • DANGLING_ENDPOINT
  • NEAR_MISS_CONNECTION
  • INTERIOR_CROSSING
  • UNOWNED_LINE
  • UNCLOSED_MATERIAL_BOUNDARY
  • PROTRUDING_OR_OCCLUDED_GEOMETRY
  • VIEW_SOURCE_CONSISTENCY
  • VIEW_SEMANTICS_CONSISTENCY
  • DELIVERABLE_SCOPE_IDENTITY
  • PLOT_SCALE_CONSISTENCY
  • FINAL_VISUAL_INTEGRITY

Every topology warning now records handle/location, component and line class, intentional-open/crossing basis, evidence, and disposition. Unresolved semantic warnings block release even when purely geometric checks have no FAIL.

Assembly and release integrity

  • Concept/teaching classification may reduce production annotations and analysis, but never basic topology, ownership, common-view-source, scale, or visual integrity.
  • Add a functional/component coverage matrix so a partial crank-slider mechanism cannot be titled as a complete four-stroke engine assembly.
  • Require a view mapping table with authoritative source revision and transforms.
  • Reject CUTAWAY/section labels without matching cut, hatch, visibility, and abstraction semantics.
  • Fit-to-page PDF output cannot carry a numeric 1:1 scale; use approved non-scale designation such as NTS and record plot mode FIT.
  • Release reports now list authoritative source, preserved original/backup, working copy, final copies, and cleanup/retention strategy.

Validation

  • Skill structure: valid
  • Required failure codes, rule IDs, evidence fields, fallback route, and cleanup contract verified
  • Release baseline is the commit attached to this tag

This release hardens the Skill contract. It does not claim that every AutoCAD MCP backend already implements the preferred strict request/response fields; unsupported backends must be treated as limited or blocked.

Assets 2
Loading