draftwright 0.4.30__tar.gz → 0.4.32__tar.gz

{draftwright-0.4.30 → draftwright-0.4.32}/CHANGELOG.md

@@ -4,6 +4,81 @@
 
 ### Added
 
+- A hash-pinned AP242 CTC-01 canary now proves the full Pareto-first layout loop against
+  a reviewed 80-measurement denominator: read typed finding remedies, apply only two public
+  declaration-side overrides, replay once, and establish legibility-only dominance while 12
+  unresolved claims remain carried and certification remains unavailable (#1753). Detailed
+  diagnostic prose remains optional presentation derived from structured evidence, never a
+  comparison identity or decision input.
+- Declared slot width and length dimensions now expose bounded, feature-relative lanes through
+  `DimensionIntent.place(lane=...)` and declaration-scoped
+  `layout_override(..., parameter=..., lane=...)`. Generated scripts and report-v8 evidence
+  retain the layout-only policy; the shared solver admits only wholly interior or exterior,
+  page-safe, ink-clear candidates and reports bounded blocker evidence when a requested lane is
+  infeasible. Automatic drawings and scripts without lane intent remain unchanged (#1757).
+- Declared sheets now support append-only, build-scoped `layout_override(..., side=...)`
+  edits plus structured capability and validation queries. Overrides select only a semantic
+  corridor, retain declaration identity through generated-script replay, and appear as
+  layout-only resolution evidence in declared report v8; coordinates and engineering meaning
+  remain unchanged, and sheets without overrides preserve existing behaviour (#1757).
+- Raw automatic report assessments now include a typed remediation projection that separates
+  contradictions, missing carriers, layout, importer/lowering, source ambiguity, and unavailable
+  evidence. It retains affected evidence identities, names preservation invariants, advertises
+  only bounded public actions, and leaves unknown findings unclassified without guessing (#1759).
+- Raw automatic reports now lead agents with a vector-first `lint.assessment`: per-axis status,
+  affected counts, available denominators, unavailable reasons, and stable structured reasons
+  for every `needs-attention` verdict. Its human summary is rendered from the same reason rows,
+  while legacy lint scores remain compatibility-only diagnostics and cannot select status
+  (#1609, #1618).
+- Replay comparison now matches unresolved measurement evidence by its serialized annotation,
+  table cell, or ownerless parameter identity and classifies it as carried, resolved,
+  introduced, changed, or ambiguous. Carried uncertainty keeps certification unavailable but
+  no longer erases an otherwise Pareto-dominant layout improvement; new, changed, or duplicate
+  identities fail closed (#1753).
+- Assessment comparison v2 reports independently evidenced requirement, completeness,
+  fidelity, legibility, and restraint axes plus their Pareto relation. Dominance,
+  equivalence, domination, incomparability, and unavailable evidence are derived from concrete
+  transitions rather than any legacy diagnostic, component, or audited-completeness score
+  (#1609). The v1 `decision` remains temporarily as a deprecated compatibility policy result.
+- Stadium through-slots now retain Quiddity 0.3.2's proved end radius through detection,
+  declared `Sheet` scripts, compiled measurement identity, placement, and completeness. A
+  normal-to-arc `2× R…` leader distinguishes an obround from an equal-sized rectangular slot
+  without introducing coordinate placement (#1752).
+- The Quiddity 0.3.2 adoption also retains corrected overall extents for rounded-corner
+  rectangular slots. Hole-pattern records whose members differ only along the drilling axis
+  are explicitly refused at the drafting boundary, preserving their ordinary grouped-hole
+  requirements instead of emitting a coincident, undrawable pitch pattern.
+- Feature-leader placement now has one coordinate-free drawing policy across
+  `build_drawing`, `make_drawing`, `Sheet`, generated scripts, and the CLI. The default
+  `auto` policy keeps the shared interior/exterior solve, `interior` requires proved
+  interior candidates for eligible unconstrained families, and `exterior` restores the
+  historical exterior-only layout for existing diagrams.
+- The standard title block now states drawing `UNITS` (`mm`) and the effective sheet `FORMAT`
+  (for example `A2`). Dimension-specified A-series pages receive the standard designation;
+  non-standard pages state their actual `WIDTHxHEIGHT`. Its rows share a four-line column grid,
+  avoiding visually offset dividers between adjacent fields.
+- A bounded real-part canary now proves the complete agent improvement loop on NIST CTC-01
+  (#1716): inspection-to-declaration joins, traced baseline, one sanctioned `Sheet` layout edit,
+  replay assessment, fixed-denominator comparison, and fail-closed deletion/owner/provenance
+  checks. It performs exactly two CAD builds in the existing single PR canary lane.
+- Replay assessments v2 now retain exact confirmed compiled measurement meanings, and
+  `compare_assessments()` evaluates two same-source replays as separate semantic, lint,
+  completeness, fidelity, layout, and availability deltas (#1712). Caller-fixed requirements
+  expose shared omissions; authorised design changes remain separate; no composite score is
+  produced.
+- Generated scripts now atomically write a versioned post-build replay assessment beside their
+  outputs (#1715). It binds the exact STEP and edited Python bytes, producer/run options, output
+  hashes, declaration/representation map, layout evidence, and lint from the same finalized
+  drawing. Failed replays clear only stale Draftwright-owned assessments; `--no-report` opts out.
+- Declared drawing report schema v8 publishes page/view geometry, named annotation ink and
+  public line segments, raw-lint joins, semantic remedy choices, and explicit opt-in solver
+  evidence (#1711). Coordinates are review evidence only; editable links remain final-IR
+  declarations, and an untraced or partially traced build says so instead of appearing clear.
+- STEP inspection schema v4 projects a deterministic report-local source-face roster and
+  Quiddity 0.3.1's closed graph rooted at rejected candidates (#1726). Accepted occurrences and
+  candidates carry exact defining/constituent face links; rejected roots and direct relationships
+  reconcile with aggregate lifecycle counts. The report still states that this is diagnostic
+  evidence, not precision, recall, missed-feature truth, or persistent topology identity.
 - Circular-seat recognition, declared features, and generated-script replay (#1613).
   Diameter, open run, arc sweep, and three datum-to-axis coordinates retain each physical
   seat's measurement identities, including counted coaxial callouts and shared axis marks.
@@ -13,6 +88,20 @@
 
 ### Fixed
 
+- Assessment comparison now rejects an apparent resolution of measurement uncertainty when the
+  declaration carrying that unresolved annotation was removed. Deleting crossed GD&T ink can no
+  longer masquerade as evidence improvement; genuine resolution with the carrier retained still
+  compares normally (#1753).
+- Imported upper/lower limit dimensions now retain their typed absolute interval through the
+  compiled evidence boundary. Both bounds together satisfy the owned nominal claim, while a
+  changed/missing bound or two coincidental numbers around the nominal still produces
+  `claimed_value_absent`; count and through requirements remain separate (#1759).
+- Adopt Quiddity 0.3.1 and require its public rejected-candidate reference in the
+  evidence contract (#1726). The provider now suppresses rectangular recess candidates
+  that are not material-empty and restores passage discovery used during rotational
+  reconciliation; Draftwright's recognition and real-part regression corpora retain
+  their reviewed expectations.
+
 - Direct and generated builds use the same final IR step ladder for page layout (#1592).
   Raw face levels owned by another feature no longer reserve a phantom step corridor at
   the title-block clearance threshold.

{draftwright-0.4.30 → draftwright-0.4.32}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: draftwright
-Version: 0.4.30
+Version: 0.4.32
 Summary: Automated technical-drawing generation for build123d
 Project-URL: Homepage, https://github.com/pzfreo/draftwright
 Project-URL: Repository, https://github.com/pzfreo/draftwright
@@ -692,7 +692,7 @@ Requires-Dist: numpy>=1.24
 Requires-Dist: ocp-gordon<0.3
 Requires-Dist: pillow>=10
 Requires-Dist: pypdfium2>=4
-Requires-Dist: quiddity==0.2.9
+Requires-Dist: quiddity==0.3.3
 Requires-Dist: reportlab>=4.0
 Requires-Dist: rich>=10.11
 Requires-Dist: steputils==0.1
@@ -757,14 +757,17 @@ draftwright my_part.step --format pdf,dxf     # also: svg, all
 draftwright my_part.step --no-report          # opt out of the JSON sidecar
 draftwright my_part.step --scale 2 --page A3  # override the auto scale / page
 draftwright my_part.step --scale 1 --page A4 --scale-policy strict
+draftwright my_part.step --leader-region exterior  # historical exterior-only callouts
 draftwright my_part.step --script             # write an editable declarative Sheet script
 draftwright /parts/my_part.step --out-dir .   # explicitly write into the working directory
 draftwright my_part.step --out-dir drawings   # create/use a separate output directory
 ```
 
 CLI outputs default to the directory containing the STEP input, including an absolute or
-nested input path. `--script` writes its Python file and inspection sidecar there too; the
-script retains that output destination when run from another directory. Use `--out-dir DIR`
+nested input path. `--script` writes its Python file and recognition-inspection sidecar there;
+replaying the script writes the requested drawings and a distinct current-build assessment,
+then prints that assessment path. The script retains that output destination when run from
+another directory. Use `--out-dir DIR`
 to choose a directory, or `--out PREFIX` to choose a basename as well (these options are
 mutually exclusive). Relative overrides use the current working directory. Live object
 scripts (`module:part`) default to `drawing.py` in the working directory.
@@ -974,6 +977,10 @@ completeness = crit["quality"]["completeness"]
 # became a requirement. (Recognized nothing auditable at all? available is False, not 1.0.)
 audited = completeness["audited_score"]
 assert completeness["scope"] == "audited_recognized_requirements"
+# An aggregate outcome whose physical count is unknown makes the denominator and score
+# indeterminate rather than treating its placeholder row as one requirement.
+completeness["known_requirement_count"]
+completeness["unknown_cardinality_rows"], completeness["unknown_cardinality"]
 completeness["excludes"]                     # what the denominator cannot see
 completeness["unrecognised_geometry_reports"]  # a floor on that gap, never a measure
 legibility = crit["quality"]["legibility"]
@@ -1002,6 +1009,9 @@ engineering-correct; plain deletion is not an accepted-waiver mechanism.
 can audit, how many were placed?" — so a part can score 1.0 with whole features missing from the
 drawing, if recognition never identified them. Gate on issue codes and severities, and read
 `excludes` and `unrecognised_geometry_reports` for what the denominator cannot account for.
+If any producer reports unknown physical cardinality, `requirements` and `audited_score` are
+`None`, `coverage` is `"indeterminate"`, and `unknown_cardinality` identifies the aggregate
+family/parameter outcomes requiring review.
 
 Each `LintIssue` carries a domain-meaningful `code` and, when computable, a
 ready-to-apply `suggestion`. See `docs/adr/` for the design (deterministic

{draftwright-0.4.30 → draftwright-0.4.32}/README.md

@@ -54,14 +54,17 @@ draftwright my_part.step --format pdf,dxf     # also: svg, all
 draftwright my_part.step --no-report          # opt out of the JSON sidecar
 draftwright my_part.step --scale 2 --page A3  # override the auto scale / page
 draftwright my_part.step --scale 1 --page A4 --scale-policy strict
+draftwright my_part.step --leader-region exterior  # historical exterior-only callouts
 draftwright my_part.step --script             # write an editable declarative Sheet script
 draftwright /parts/my_part.step --out-dir .   # explicitly write into the working directory
 draftwright my_part.step --out-dir drawings   # create/use a separate output directory
 ```
 
 CLI outputs default to the directory containing the STEP input, including an absolute or
-nested input path. `--script` writes its Python file and inspection sidecar there too; the
-script retains that output destination when run from another directory. Use `--out-dir DIR`
+nested input path. `--script` writes its Python file and recognition-inspection sidecar there;
+replaying the script writes the requested drawings and a distinct current-build assessment,
+then prints that assessment path. The script retains that output destination when run from
+another directory. Use `--out-dir DIR`
 to choose a directory, or `--out PREFIX` to choose a basename as well (these options are
 mutually exclusive). Relative overrides use the current working directory. Live object
 scripts (`module:part`) default to `drawing.py` in the working directory.
@@ -271,6 +274,10 @@ completeness = crit["quality"]["completeness"]
 # became a requirement. (Recognized nothing auditable at all? available is False, not 1.0.)
 audited = completeness["audited_score"]
 assert completeness["scope"] == "audited_recognized_requirements"
+# An aggregate outcome whose physical count is unknown makes the denominator and score
+# indeterminate rather than treating its placeholder row as one requirement.
+completeness["known_requirement_count"]
+completeness["unknown_cardinality_rows"], completeness["unknown_cardinality"]
 completeness["excludes"]                     # what the denominator cannot see
 completeness["unrecognised_geometry_reports"]  # a floor on that gap, never a measure
 legibility = crit["quality"]["legibility"]
@@ -299,6 +306,9 @@ engineering-correct; plain deletion is not an accepted-waiver mechanism.
 can audit, how many were placed?" — so a part can score 1.0 with whole features missing from the
 drawing, if recognition never identified them. Gate on issue codes and severities, and read
 `excludes` and `unrecognised_geometry_reports` for what the denominator cannot account for.
+If any producer reports unknown physical cardinality, `requirements` and `audited_score` are
+`None`, `coverage` is `"indeterminate"`, and `unknown_cardinality` identifies the aggregate
+family/parameter outcomes requiring review.
 
 Each `LintIssue` carries a domain-meaningful `code` and, when computable, a
 ready-to-apply `suggestion`. See `docs/adr/` for the design (deterministic

{draftwright-0.4.30 → draftwright-0.4.32}/docs/reference/recogniser-capabilities.md

@@ -70,11 +70,33 @@ issue. The contract test derives package record outputs, converter registries, l
 and emitter branches independently, so copying a new name into the declaration alone cannot make CI
 pass.
 
-### Quiddity 0.2.9 runtime contract
+### Quiddity 0.3.3 runtime contract
 
-The runtime pins the published `quiddity==0.2.9` package, following the 0.2.4 adoption in
+The runtime pins the published `quiddity==0.3.3` package. This release adds material-side
+reconstruction facts to fillets, planar chamfers and angled steps, paired ramps, and open-section
+profiles. Draftwright consumes these records to describe and annotate the recognised part; it does
+not reconstruct a cut solid from them, so the new `side`, `corner`, `opening_direction`,
+`half_width`, and `material_side` fields do not enter the drafting IR. The exact consumer schema
+declarations advance with the provider, and the section-recess adapter accepts document schema 4
+while continuing to reject unknown later schemas.
+
+Version 0.3.2 followed the 0.2.4 adoption in
 [#1486](https://github.com/pzfreo/draftwright/pull/1486) and the migration in
-[#1471](https://github.com/pzfreo/draftwright/issues/1471). 0.2.7 is a patch adoption: it requires
+[#1471](https://github.com/pzfreo/draftwright/issues/1471). It advanced the public
+`Slot` record to schema 2: `end_radius` distinguishes two semicircular stadium ends and
+`corner_radius` distinguishes rounded rectangular corners. Draftwright consumes
+`end_radius` for through-slot radius requirements; rounded-corner rectangular slots remain a
+separate drafting-policy decision, although their corrected overall extents feed the existing
+width/length grammar. A published hole-pattern relation whose members differ only along their
+drilling axis is retained as recognition evidence but refused as a drawing pattern: its axes
+coincide in the required end view, so Draftwright keeps the ordinary grouped-hole owner instead.
+Version 0.3.1 retained the same 29 families and record
+schemas while tightening material-empty gating for rectangular recesses,
+restoring passage discovery during rotational reconciliation, and adding the public opaque
+`CandidateRef` evidence surface delivered by
+[quiddity#688](https://github.com/pzfreo/quiddity/issues/688). Draftwright requires that symbol
+in the released evidence manifest before consuming candidate-level evidence. 0.2.7 was a patch
+adoption that required
 circumferential cylinder support to establish a turned-profile axis line, so rounded plate corners
 and parallel offset cylinders no longer form a false stepped shaft
 ([quiddity#586](https://github.com/pzfreo/quiddity/issues/586), [#1555](https://github.com/pzfreo/draftwright/issues/1555)).
@@ -102,7 +124,14 @@ and untested. Its public `quiddity`, `quiddity.evidence` and
 reads. There is one recognition aggregate per build; consumers project that result rather than
 calling the document builder to obtain another run.
 
-The manifest has 27 families. One `section-recesses` family replaces the former pockets, pocket
+The manifest has 29 families. The `gusset-ribs` family proves rib thickness, support legs and
+body occurrence, while `gusset-rib-patterns` relates accepted ribs as arrays or mirror pairs.
+Draftwright preserves those exact member relations in dedicated `GussetRibFeature` IR, exposes
+the same facts through `Sheet.gusset_rib(...)` and generated scripts, and places one correlated
+solver-owned callout carrying thickness, both legs and the proven pitch or mirror spacing. The
+completeness ledger follows each physical member and the group relation independently (#1705).
+
+One `section-recesses` family replaces the former pockets, pocket
 patterns, channels, rectangular and round-bottom blind slots, passages and prismatic pockets.
 `RecognitionResult.section_recesses` contains the immutable occurrences;
 `section_recess_patterns` relates them by run-local occurrence indices; `section_recess_refusals`

{draftwright-0.4.30 → draftwright-0.4.32}/docs/reference/sheet.md

@@ -56,6 +56,12 @@ beyond each centreline. Without an explicit width, the existing widths remain 12
 A4 and 150 mm on larger ISO sheets, with the existing extra 1 mm right/bottom clearance.
 Revision defaults also remain unchanged.
 
+The standard title block derives two read-only fields from the settled drawing: `UNITS` is
+`mm`, matching Draftwright's drawing and export coordinate convention, and `FORMAT` is the
+effective A-series designation (for example `A2`). A non-standard page states its physical
+`WIDTHxHEIGHT` instead. These are derived after automatic page selection, so they cannot drift
+from the sheet that was actually rendered.
+
 CLI parameters carry the same options into rendered drawings and generated scripts:
 
 ```sh
@@ -145,6 +151,31 @@ SVG, PDF and DXF export the same resolved ink. Unsupported values raise `ValueEr
 The choices affect rendering and its placement footprint, not feature measurements
 or tolerances. These are explicit rendering choices, not a claim of standards conformity.
 
+## Feature-leader region policy
+
+Feature callouts may use proved whitespace inside a projected view without exposing raw page
+coordinates. The drawing-wide `leader_region` policy is accepted by `Sheet(...)`,
+`build_drawing()`, `make_drawing()`, and generated scripts:
+
+```python
+sheet = Sheet(part, leader_region="exterior")
+# or: build_drawing(part, leader_region="interior")
+```
+
+- `"auto"` is the default and preserves the normal solve: eligible feature families offer
+  interior candidates while retaining their established exterior fallback.
+- `"interior"` requires an interior candidate for an eligible, unconstrained feature. It does
+  not invent interior geometry for unsupported families; those remain exterior. If no proved
+  interior candidate fits, the eligible callout drops and lint reports it.
+- `"exterior"` removes all interior candidates and restores the historical exterior-only
+  feature-leader layout.
+
+The CLI spelling is `--leader-region auto|interior|exterior`. Generated `--script` output
+retains a non-default selection in its `Sheet(...)` constructor. A feature carrying an explicit
+`side="left"|"right"|"above"|"below"` remains exterior because authored placement intent is
+stronger than the drawing-wide preference. The policy affects feature leaders only—not linear
+dimensions, free notes, tables, or view placement—and never supplies coordinates.
+
 ## Through-hole wording
 
 The optional argument to a hole handle's `through()` controls its printed indicator:
@@ -192,6 +223,76 @@ The token associates features; it does not specify an annotation position or add
 Generated scripts preserve this association using Draftwright-owned tokens instead of provider
 keys. A groove can still be declared when the authored set omits all of that body's steps.
 
+## Build-scoped declaration selectors
+
+An editable script can give a feature a declaration identity and later address that intent
+without a list position:
+
+```python
+hole = sheet.hole(diameter=6, at=(0, 0, 0), axis="z").identify("declaration:1")
+sheet.dimension(sheet.by_declaration("declaration:1"), "bore.diameter")
+```
+
+The identity follows fluent replacements such as `.depth()` and identity-preserving list
+reorders. Assigning another feature into its public `sheet.features` slot or deleting it
+withdraws the identity; it never transfers to the new occupant. Live IDs must be unique.
+Generated scripts use this build-scoped selector to join assessment evidence back to editable
+intent. It is not a persistent feature, face or topology ID and makes no correspondence promise
+across recognition runs. Recognition occurrence IDs, when present, remain local to the exact
+generation run recorded by the declaration.
+
+### Declaration-scoped layout overrides
+
+An agent editing a generated script can append a bounded layout override without changing the
+original feature declaration or supplying page coordinates:
+
+```python
+options = sheet.layout_options("declaration:57")
+check = sheet.validate_layout_override("declaration:57", side="above")
+if check["supported"]:
+    sheet.layout_override("declaration:57", side="above")
+
+lane_options = sheet.layout_options(
+    "declaration:9", parameter="slot_width.length"
+)
+lane_check = sheet.validate_layout_override(
+    "declaration:9", parameter="slot_width.length", lane=3
+)
+if lane_check["supported"]:
+    sheet.layout_override(
+        "declaration:9", parameter="slot_width.length", lane=3
+    )
+```
+
+Without `parameter=`, `layout_options()` reports the declaration's current side and supported
+values. With an exact declared parameter it reports dimension-lane capability. A lane is an
+integer from 1 through 8: a one-based drafting-spaced rank from that dimension's physical
+witness, not a distance. The shared measured-candidate solve may resolve it into proven
+whitespace inside or outside the view and records that candidate's region explicitly. The
+current lane-capable slice is the linear width/length dimensions of slots. Capability is
+declared in one compiler-owned registry so another dimension family is added deliberately, not
+by teaching each renderer a private spelling.
+
+The side surface accepts `above`, `below`, `left`, and `right`;
+`validate_layout_override()` returns
+structured `invalid_declaration`, `unsupported_declaration`, `unsupported_control`, or
+`unsupported_value` refusals, plus `invalid_control_combination` when side and lane addressing
+are mixed, without mutating the sheet. Both documents say
+`requires_build_validation: true`: support means that the declaration and vocabulary are valid,
+not that the final sheet has enough space. `build()` and `lint()` remain the authority for
+feasibility and collision-free placement.
+
+`layout_override()` accepts either keyword-only `side`, or an exact `parameter` plus `lane`, and
+rejects duplicate overrides for the same target. Side chooses a feature corridor; lane ranks a
+parallel position for one referential dimension. Neither is pinning or priority, and neither moves
+an annotation to a caller-supplied coordinate or changes its measurement, tolerance, datum, or
+other engineering semantics. Generated scripts
+emit the override as a separate line after the identity-bearing declarations. A declared report
+records the requested and resolved value under `layout.overrides` with
+`intent_class: "layout-only"`; lane rows also retain `parameter_id`. An infeasible lane drops
+honestly with the requested lane in the lint message. Omitting the override retains the existing
+placement behaviour.
+
 ## Checking dimension placement rules
 
 Call `handle.dimension_ids()` to find the measurements a declared feature exposes, then
@@ -625,6 +726,23 @@ callout. More general ordered operation stacks remain tracked by issue #1360. Un
 requirement has a structured parameter, use a feature-linked `note(..., satisfies=(...))` only
 for parameter ids the handle actually exposes; free prose does not satisfy coverage.
 
+Generated scripts and editing agents use `structured_note(...)` when the note declaration
+itself needs a stable selector:
+
+```python
+note = sheet.structured_note(
+    "BORE DIAMETER VERIFIED",
+    stack,
+    satisfies=("bore.diameter",),
+).identify("declaration:note", provenance="structured-note")
+same_note = sheet.by_declaration("declaration:note")
+```
+
+It declares the same solver-placed manufacturing note as `note(...)`, but returns the note's
+own feature handle rather than returning the `Sheet` for chaining. The handle controls intent,
+not page coordinates. Final reports can therefore link the declaration to its exact placed ink
+while separately crediting the physical feature and parameter named by `satisfies`.
+
 ### Straight and circular Blend chains
 
 When recognition accepts a complete schema-v3 straight or circular rolling-ball Blend path that is
@@ -811,6 +929,15 @@ drop, or missing ink is not hidden by the ownership choice.
     options:
       filters: public
 
+### Axis-aligned through-slots
+
+`Sheet.slot(...)` declares the independently addressable `slot_width.length` and
+`slot_length.length` measurements. Pass `end_radius=` only for a stadium/obround slot; this adds
+`slot_end_radius.radius`, rendered as a solver-placed `2× R…` leader whose arrow remains normal
+to either end arc. Leaving it unset preserves the rectangular-slot grammar. The declared radius
+must equal half the width, and generated Sheet scripts retain the field when recognition proved
+semicircular ends.
+
 ## GD&T control builder
 
 ::: draftwright.sheet._Control

{draftwright-0.4.30 → draftwright-0.4.32}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "draftwright"
-version = "0.4.30"
+version = "0.4.32"
 description = "Automated technical-drawing generation for build123d"
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -23,7 +23,7 @@ dependencies = [
     # published wheels, not only uv's development resolver constraints.
     "cadquery-ocp-novtk!=7.9.3.1.1 ; python_full_version >= '3.13'",
     "build123d-drafting-helpers>=0.15.4",
-    "quiddity==0.2.9",
+    "quiddity==0.3.3",
     "numpy>=1.24",
     # PNG raster export (SVG→PDF→PNG). Both permissively licensed (Pillow HPND; pypdfium2
     # Apache-2.0 wrapping Google PDFium BSD-3) and ship pre-built wheels with NO native system
@@ -96,6 +96,7 @@ timeout = 300
 # across its compatibility matrix.
 markers = [
     "slow: end-to-end integration builds, including CTC fixtures (deselected by default)",
+    "ctc04: scheduled tests that construct the CPU-heavy NIST CTC-04 drawing",
     "scheduled: compatibility and broad-corpus contracts selected by the scheduled tier",
     "real_part_canary: bounded real STEP semantic/export gate, selected once in PR CI",
     "smoke: curated build-light subset for a fast local check (~30 s)",

{draftwright-0.4.30 → draftwright-0.4.32}/src/draftwright/__init__.py

@@ -37,6 +37,7 @@ _LAZY = {
     "InspectionUnavailableError": "draftwright.inspection",
     "inspect_step": "draftwright.inspection",
     "Sheet": "draftwright.sheet",
+    "LeaderRegionPolicy": "draftwright.leader_policy",
     "Document": "draftwright.document",
     "DocumentResult": "draftwright.document",
     "DocumentBuildError": "draftwright.document",
@@ -103,6 +104,7 @@ if TYPE_CHECKING:  # static analysers / IDEs — no runtime import, no kernel co
         InspectionUnavailableError,
         inspect_step,
     )
+    from draftwright.leader_policy import LeaderRegionPolicy
     from draftwright.linting import lint_feature_coverage
     from draftwright.pmi import (
         PmiExtractionReport,
@@ -137,6 +139,7 @@ __all__ = [
     "SoftDeprecationWarning",
     "FeatureInfo",
     "InspectionUnavailableError",
+    "LeaderRegionPolicy",
     "PmiExtractionReport",
     "PmiRecord",
     "PmiSourceEntity",