§20 family: 3DFACE, SOLID, TRACE and the ACIS entities (§20.4.32, §20.4.35, §20.4.36, §20.4.41) #145

Spec: ODA Open Design Specification for .dwg files v5.4.1, §20.4.32, §20.4.35, §20.4.36, §20.4.41.

Sections and their state on main (2026-10-21)

closes comes from the boundary checks on the local 19-file corpus (STATUS.md, 2026-08-30). It is re-measured on the public corpus in CI by the 0.2.0 measurement epic, and no section is complete until its values equal AutoCAD's own DXF export.

Acceptance, for every section above

• Every field of its prescription is read, with every version branch the section names
• Where the section prints an example, its bytes are a committed fixture and decode to the values printed
• The field list ends on the record's exact data-stream boundary (and string/handle-stream boundaries on R2007+) on every corpus record of the type, on every release band
• Every value equals AutoCAD's DXF export of the same drawing, matched by handle (DXF group 5), with the scorer from the oracle epic
• The corpus holds at least one record of the type on each release band, R13 to R2018; a band without one is recorded on the corpus epic, not assumed
• Its row in docs/spec-coverage.md moves to complete, with the evidence linked

Subtasks

• §20.4.32 3DFACE (28)
  • R13
  • R14
  • R2000
  • R2004
  • R2007
  • R2010
  • R2013
  • R2018
• §20.4.35 SOLID (31)
  • R13
  • R14
  • R2000
  • R2004
  • R2007
  • R2010
  • R2013
  • R2018
• §20.4.36 TRACE (32)
  • R13
  • R14
  • R2000
  • R2004
  • R2007
  • R2010
  • R2013
  • R2018
• §20.4.41 REGION (37), 3DSOLID (38), BODY (39)
  • R13
  • R14
  • R2000
  • R2004
  • R2007
  • R2010
  • R2013
  • R2018

A subtask becomes its own issue when someone picks it up; that issue quotes the section's field list and names the corpus records it is measured on.

Parent: #138