draftwright 0.4.24__tar.gz → 0.4.26__tar.gz

{draftwright-0.4.24 → draftwright-0.4.26}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: draftwright
-Version: 0.4.24
+Version: 0.4.26
 Summary: Automated technical-drawing generation for build123d
 Project-URL: Homepage, https://github.com/pzfreo/draftwright
 Project-URL: Repository, https://github.com/pzfreo/draftwright
@@ -684,7 +684,7 @@ Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Requires-Python: <3.15,>=3.10
 Requires-Dist: antlr4-python3-runtime<4.10
-Requires-Dist: build123d-drafting-helpers>=0.14.2
+Requires-Dist: build123d-drafting-helpers>=0.15.1
 Requires-Dist: build123d<0.11,>=0.9.0; python_full_version < '3.13'
 Requires-Dist: build123d<0.12,>=0.11; python_full_version >= '3.13'
 Requires-Dist: cadquery-ocp-novtk!=7.9.3.1.1; python_full_version >= '3.13'
@@ -694,6 +694,7 @@ Requires-Dist: pillow>=10
 Requires-Dist: pypdfium2>=4
 Requires-Dist: quiddity==0.2.6
 Requires-Dist: reportlab>=4.0
+Requires-Dist: rich>=10.11
 Requires-Dist: steputils==0.1
 Requires-Dist: svglib>=1.5
 Requires-Dist: typer>=0.12
@@ -736,6 +737,10 @@ annotation placed by the engine.*
 pip install draftwright
 ```
 
+Already using a CAD project environment? Use a [separate drawing environment](docs/reference/isolated-execution.md)
+and pass an exported STEP file between the two. The guide includes interpreter, dependency and
+import checks for local Python and CAD MCP workflows.
+
 ### Command line
 
 Point it at a STEP file — that's the whole workflow:

{draftwright-0.4.24 → draftwright-0.4.26}/README.md

@@ -34,6 +34,10 @@ annotation placed by the engine.*
 pip install draftwright
 ```
 
+Already using a CAD project environment? Use a [separate drawing environment](docs/reference/isolated-execution.md)
+and pass an exported STEP file between the two. The guide includes interpreter, dependency and
+import checks for local Python and CAD MCP workflows.
+
 ### Command line
 
 Point it at a STEP file — that's the whole workflow:

{draftwright-0.4.24 → draftwright-0.4.26}/docs/reference/sheet.md

@@ -4,6 +4,142 @@
 are documented here because they are part of normal use even though their Python names begin
 with an underscore.
 
+## Projection convention
+
+Use `Sheet(part, projection="first")` or `build_drawing(part, projection="first")`
+for first-angle layout and its matching projection symbol. The CLI equivalent is
+`--projection first`. Explicit `"third"` selects third-angle layout and its symbol;
+omitting `projection` keeps third-angle layout without a symbol.
+
+View names retain their physical viewing directions in the working part frame. Changing
+convention changes sheet relationships, not which side of the part a name shows:
+
+| View | Viewed from | Page directions | Third-angle position | First-angle position |
+|---|---|---|---|---|
+| `front` | Negative Y | X right, Z up | Reference | Reference |
+| `plan` | Positive Z | X right, Y up | Above front | Below front |
+| `side` | Positive X | Y right, Z up | Right of front | Left of front |
+
+The resolved convention is available as `drawing.view_plan.convention`. Generated scripts
+retain the requested convention. Annotation footprints, scale/page selection and measured
+repacking use the same convention. An authored relation contradicting the principal layout
+fails before projection; a whole-view pin must preserve the convention's relationships.
+
+## Dimension text style
+
+### Title fields and notes at paper size
+
+Keep title-block values concise and put longer engineering information in a `notes()` block.
+`title_field_overflow` identifies text wider or taller than its title-block cell, even when the
+text remains inside the page. This is a legibility warning, like overlapping annotations;
+text outside the drawable page remains an `annotation_out_of_bounds` error. The full value
+stays rendered; the diagnostic does not truncate it, shrink the font or invent an abbreviation.
+`lint_summary()["passed"]` checks errors only, so inspect warnings and the legibility component
+as well. A title warning does not prevent scale recovery from restoring missing measurements.
+
+<!-- issue-1536-notes-example -->
+```python
+from build123d import Box
+from draftwright import Sheet
+
+sheet = Sheet(
+    Box(30, 20, 10), page="A4", scale=2,
+    title="FRAME - DFM REVIEW", number="REVIEW", material="SEE NOTES",
+    detail_view=False,
+)
+sheet.authored_dimensions()
+envelope = sheet.envelope()
+for parameter in envelope.dimension_ids():
+    sheet.dimension(envelope, parameter)
+sheet.notes([
+    "QUOTATION / DFM REVIEW - NOT RELEASED",
+    "Material: TITANIUM - GRADE TBD",
+    "Hinge fit and pin retention: engineering decision required",
+], prefer="tr")
+drawing = sheet.build()
+for issue in drawing.lint():
+    print(issue.severity, issue.code, issue.message)
+```
+<!-- /issue-1536-notes-example -->
+
+`page` and `scale` control the sheet and model size. The current annotation preset has a fixed
+3 mm nominal paper font size; changing scale does not enlarge notes. `Sheet.notes()` and
+`Sheet.table()` have no font-size option. `text_position` and `text_orientation` below control
+dimension style, not note size. A smaller model scale makes notes larger relative to the part;
+a smaller page changes how much of the page they occupy. Neither changes their printed size.
+For the A2 frame trial, retain A2 and the requested scale unless the full package fits the new
+constraints with its required measurements intact; the small box example is not proof that
+the frame fits A4.
+
+`prefer="tr"` ranks available table positions near the top-right corner. The shared placement
+solve still measures the whole notes block and checks all occupied regions. If it cannot fit,
+`table_dropped` reports the failure. Split long prose into authored lines or choose an appropriate
+page; do not remove engineering content merely to silence a diagnostic. General notes remain
+uncredited text: they do not automatically satisfy missing dimensions or unsupported features.
+
+### Dimension position and reading direction
+
+Position and reading direction are independent drawing-wide settings:
+
+```python
+sheet = Sheet(part, text_position="above", text_orientation="horizontal")
+# Declare features and dimensions as usual, then build.
+drawing = sheet.build()
+```
+
+`text_position="inline"` (the default) leaves a gap for the value in the dimension
+line; `"above"` keeps the line continuous and offsets the full value and tolerance.
+For angular dimensions, above means outside the arc. `text_orientation="aligned"`
+(the default) follows the dimension line or arc tangent; `"horizontal"` keeps text
+horizontal on the sheet. An aligned vertical value reads from the right. Short
+spans use outside arrows while retaining their complete text.
+
+The same options are accepted by `build_drawing()`, `make_drawing()`,
+`emit_sheet_script()` and `generate_sheet_script()`. The CLI flags are
+`--text-position` and `--text-orientation`. Generated scripts retain these settings;
+SVG, PDF and DXF export the same resolved ink. Unsupported values raise `ValueError`.
+The choices affect rendering and its placement footprint, not feature measurements
+or tolerances. These are explicit rendering choices, not a claim of standards conformity.
+
+## Through-hole wording
+
+The optional argument to a hole handle's `through()` controls its printed indicator:
+
+```python
+hole.through()                # default THRU
+hole.through("THRU")          # explicit wording
+hole.through("")              # omit the printed indicator
+hole.through("THROUGH ALL")   # alternative wording
+```
+
+Each declares a through hole and clears any blind depth. Diameter, tolerances, fits and
+measurement identities remain unchanged. The empty string is an explicit display omission;
+it remains visible in the suppression ledger and does not count as a printed through
+qualifier. `.depth(4)` makes the hole blind and clears the override; a later `.through()`
+returns to the default.
+
+The override is also accepted as `through_indicator=` by `Sheet.hole()` and the IR `hole()`
+constructor, including pattern members. Generated scripts preserve the difference between
+no override, explicit default wording and an empty string. Callouts and hole tables measure
+the selected wording before placement. Compatible holes can share a callout when their
+resolved wording, machining specifications and placement constraints agree; original feature
+owners and measurement identities remain separate. Removing one owner of a shared callout
+rebuilds the survivors through the placement solver.
+
+## Feature schedules
+
+`sheet.schedule([(feature, ("bore.diameter", "location"))], name="holes")` declares a measured
+table through the same IR/compiler as ordinary dimensions. Features may be fluent handles or
+exact owned IR objects. Values, tolerances, units and through/blind wording come from the
+compiler. `location` expands the addressable member coordinates; explicit canonical IDs select
+individual components. Use `prefer="tr"`, `"tl"`, `"br"` or `"bl"` to rank the existing table
+placement candidates.
+
+Schedules establish authored dimension intent. Add `sheet.dimension(...)` declarations when a
+measurement should also appear beside a view. Ordinary `table(...)` text has no measurement
+authority. See [shared drawing documents](document.md#feature-schedules) for an executable
+recipe, verified cell evidence and the document report contract.
+
 ## Grooves on coaxial bodies
 
 When different turned bodies share an axis line, give their steps distinct `profile_group`
@@ -234,17 +370,108 @@ View declarations are semantic constraints. They name projections, relationships
 anchors; the layout solve owns the resulting page positions. Authored views must be paired with
 authored dimensions so a deliberately omitted view cannot strand planner-selected annotations:
 
+This runnable example includes the part, feature declarations, dimension discovery,
+three principal views and section A–A. The bore's location dimensions are deliberately
+omitted, and lint keeps those omissions visible.
+
+<!-- example: authored-section -->
+```python
+from build123d import Box, Cylinder, Pos
+from draftwright import Sheet
+
+bore_tool = Pos(12, 0, 0) * Cylinder(3, 12)
+part = Box(60, 40, 12) - bore_tool
+sheet = Sheet(part, page="A3", scale=1, projection="third")
+sheet.authored_dimensions().authored_views()
+
+envelope = sheet.envelope(part)
+for parameter_id in envelope.dimension_ids():
+    sheet.dimension(envelope, parameter_id)
+bore = sheet.hole(bore_tool)
+print(bore.dimension_ids())  # discover this handle's Sheet measurement IDs
+sheet.dimension(bore, "bore.diameter")
+
+for name in ("front", "plan", "side"):
+    sheet.view(name)
+sheet.section_view("A", through=bore)  # or at=0 for an explicit model-space Y plane
+
+drawing = sheet.build()
+issues = drawing.lint()
+for issue in issues:
+    print(issue.severity, issue.code, issue.message)
+# drawing.export("build/section", formats=("pdf", "svg"))
+```
+
+On a Sheet handle, `dimension_ids()` lists dotted measurement IDs; use
+`sheet.dimension(bore, "bore.diameter")`. On a built Drawing, the second argument to
+`drawing.dimension(envelope_feature, "length", role="width")` is a parameter kind,
+with `role=` distinguishing measurements of the same kind. Hole diameter and depth
+are callout content: use `drawing.callout(bore_feature)` for those, not
+`drawing.dimension(...)`. These are different vocabularies.
+
+#### Augmenting automatic views
+
+`view()` and `section_view()` specify complete authored sets. `add_view()` and
+`add_section_view()` instead augment an explicitly automatic set. Choose the source
+before adding views; an authored set cannot be switched to automatic in place.
+
+This separate, runnable example keeps automatic principal and derived views and
+adds a section at model-space Y=0. Its dimensions are still explicitly authored:
+
+<!-- example: automatic-section -->
 ```python
-s = Sheet(part).authored_dimensions().authored_views()
-front = s.view("front")
-plan = s.view("plan").above(front, gap=4).align_x(front)
-s.view("iso").scale(0.75)
-
-section = s.section_view("A", through=hole)
-detail = s.detail_view("B", around=hole).scale(2)
-dwg = s.build()
+from build123d import Box
+from draftwright import Sheet
+
+part = Box(60, 40, 12)
+sheet = Sheet(part, page="A3", scale=1).authored_dimensions()
+envelope = sheet.envelope(part)
+for parameter_id in envelope.dimension_ids():
+    sheet.dimension(envelope, parameter_id)
+sheet.auto_views()
+sheet.add_section_view("A", at=0)
+drawing = sheet.build()
+issues = drawing.lint()
+for issue in issues:
+    print(issue.severity, issue.code, issue.message)
 ```
 
+`auto_views()` emits `SoftDeprecationWarning`: it remains supported and has no removal
+date. The notice recommends the editable authored surface; it does not mean the
+augmentation example is invalid. Automatic dimensions remain supported too, but they
+cannot be paired with a complete authored view set.
+
+`Sheet.section()` is deprecated with removal targeted at 0.6.0. For an authored
+workflow replace it with `section_view("A", through=feature)` or `section_view("A", at=y)`;
+for automatic augmentation use `auto_views()` followed by `add_section_view(...)`.
+`Drawing.section()` is a separate automatic post-build operation and may add no section
+when the geometry does not warrant one.
+
+
+Rear views are explicitly requested. `s.view("rear")` includes rear in an authored
+view set; `s.auto_views().add_view("rear")` adds it to the automatic baseline.
+Rear looks toward the part from +Y with Z upward, so increasing world X runs left
+on the page. This physical direction is the same under both projection conventions.
+When side is also present, rear sits beyond side in the unfolding direction: left
+for first-angle, right for third-angle.
+
+Y-axis hole and hole-pattern callouts, locations and pitch dimensions can use rear,
+as can overall width and height. For example:
+
+```python
+s = Sheet(part, projection="first").authored_dimensions()
+hole = s.hole(diameter=6, at=(10, 20, 5), axis="y").through("THRU")
+s.dimension(hole, "bore.diameter")
+s.dimension(hole, "location")
+s.view("rear")
+drawing = s.build()
+```
+
+Dimensions still use the shared placement solve. An unsupported measurement/view
+combination is refused; a required depth extent, for example, needs side. Rear is
+never added automatically to improve visibility, coverage or hidden lines. Generated
+scripts preserve an explicit rear request.
+
 `view(...)`, `section_view(...)` and `detail_view(...)` define complete authored sets;
 omission suppresses a view. `add_view(...)`, `add_section_view(...)` and
 `add_detail_view(...)` augment an explicitly selected `auto_views()` source. `row(...)` and
@@ -403,7 +630,7 @@ geometry cannot prove a complete chain or the provider aggregate's Fillet preced
 referential `DimensionIntent`. The handle never carries a replacement nominal and never chooses
 page coordinates. Use `format(decimals=n)` to preserve between 0 and 15 decimal places in the
 printed nominal while reconciliation, tolerance, suppression and provenance continue to read the
-numeric parameter from the feature. Optional `view="front|plan|side"` and
+numeric parameter from the feature. Optional `view="front|plan|side|rear"` and
 `side="above|below|left|right"` arguments select a supported semantic corridor when authored
 routing must override the derived default; the normal placement solve still chooses coordinates
 and reports capacity/crossing failures. Trailing zeroes are intentional manufacturing display text:

{draftwright-0.4.24 → draftwright-0.4.26}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "draftwright"
-version = "0.4.24"
+version = "0.4.26"
 description = "Automated technical-drawing generation for build123d"
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -22,7 +22,7 @@ dependencies = [
     # This novtk release lacks OCP.GccEnt on macOS. The exclusion must reach
     # 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.14.2",
+    "build123d-drafting-helpers>=0.15.1",
     "quiddity==0.2.6",
     "numpy>=1.24",
     # PNG raster export (SVG→PDF→PNG). Both permissively licensed (Pillow HPND; pypdfium2
@@ -38,6 +38,7 @@ dependencies = [
     "antlr4-python3-runtime<4.10",
     "svglib>=1.5",
     "typer>=0.12",
+    "rich>=10.11",
     # PEP 702 @deprecated: stdlib `warnings.deprecated` lands in 3.13; backport for 3.10–3.12.
     "typing_extensions>=4.5 ; python_full_version < '3.13'",
 ]
@@ -90,7 +91,7 @@ timeout = 300
 # (minutes each), deselected by default. `smoke` is a curated, build-light subset
 # (~30 s) for a quick local "did I break something obvious" check — run it with
 # `uv run pytest -m smoke`. The default run is the full fast tier (`-m 'not slow'`,
-# runtime depends on worker count). CI runs one real-part canary before merge,
+# runtime depends on worker count). CI runs bounded real-part canaries before merge,
 # the full slow tier after merge, and the fast tier across its compatibility matrix.
 markers = [
     "slow: end-to-end integration builds, including CTC fixtures (deselected by default)",

{draftwright-0.4.24 → draftwright-0.4.26}/skills/SKILL.md

@@ -29,9 +29,9 @@ verbs existed then, and the dotted parameter ids in Step 2 are new in 0.4.0.)
 everything automatically** (placement is constraint-based; you never compute page
 coordinates). When the first pass isn't perfect, you drive a **build → critique
 → fix** loop (Step "Lint → critique → fix" below), not a hand-layout edit. The
-rationale lives in `docs/adr/`: 0001 (deterministic generation over an editable
-DSL), 0002 (the lint critique → domain-repair loop), 0003 (the constraint-based
-layout engine). Edit through the domain API; treat `Placeable`/page mechanics as
+rationale lives in the five current records in `docs/adr/`: ADR 1 (compiler pipeline),
+ADR 2 (layout and view planning), ADR 3 (recognition), ADR 4 (declared intent), and
+ADR 5 (trust and honest failure). Edit through the domain API; treat `Placeable`/page mechanics as
 internals.
 
 ---
@@ -145,19 +145,26 @@ rather than the bare family role (`"width"`): the bare spelling is deprecated,
 because it is what let a single call silently declare two dimensions.
 
 `place_dim(p1, p2, side, view, …)` still exists for raw page coordinates, but it is
-the **escape hatch of last resort** (ADR 0012) and is deprecated: it bypasses the
+the **escape hatch of last resort** (ADR 4) and is deprecated: it bypasses the
 layout solve, so nothing re-flows around it.
 
-**Add a diameter callout on a hole the auto-pass missed** — find the bore in the
-model IR and hand it to `callout()`. This is what the `feature_not_dimensioned`
-lint suggestion hands you (it emits `dwg.callout(f)` — say *what*, not *where*):
+**Add a callout on a hole the auto-pass missed** — inspect its semantic requirement
+finding first. Equal diameters can belong to different axes, blind depths, threads
+or fits; a diameter-total warning never authorises increasing a callout count.
 
 ```python
-for f in dwg.model().features:
-    if f.kind == "hole" and abs(f.diameter - 4.0) < 0.2:
-        dwg.callout(f)                   # engine picks the view, leader and elbow
+for issue in dwg.lint():
+    if issue.code.startswith("hole_requirement_"):
+        print(issue.message)
+        if issue.suggestion:
+            print(issue.suggestion)
 ```
 
+For a verified missing bore on an automatic model, the suggestion targets the exact
+feature with `dwg.callout(...)` through the shared solve. It applies to that Drawing;
+re-run lint after rebuilding. Authored omissions, unverified ownership and conflicting
+counts require inspection of the declared operation rather than an automatic count edit.
+
 **Free text** at a chosen point is `note()` — a domain verb, not an escape hatch:
 
 ```python
@@ -183,24 +190,56 @@ warn from 0.4.0. See `docs/deprecations.md`.
 `make_drawing(...)` is `build_drawing(...).export(formats=("svg", "dxf"))`, unpacked to a
 tuple — not a bare `.export()`, which is the deprecated shape above.
 
-**Section views** come from the section verb rather than from projecting a view by
-hand. The two entry points are *not* equivalent:
+**Authored section views** use `section_view()` alongside an explicit dimension and
+view set. This complete example declares the bore diameter and overall extents;
+it deliberately leaves the bore's location dimensions unrequested:
 
+<!-- example: authored-section -->
 ```python
+from build123d import Box, Cylinder, Pos
 from draftwright import Sheet
 
-# Sheet.section() FORCES a cut, wherever you point it.
-cut = Sheet.from_part(part, number="DWG-042").section().build()
-"section_aa" in cut.views                 # True
-# section(feature) cuts through that feature; section(at=y) at an explicit Y.
-
-# Drawing.section() adds only the AUTOMATIC A–A, which fires just for qualifying
-# hidden internal geometry (a counterbore, spotface, or blind bottom). It returns
-# the placed annotation names, or [] when no section is warranted — so on a plain
-# through-holed block it does nothing at all.
-dwg.section()
+bore_tool = Pos(12, 0, 0) * Cylinder(3, 12)
+part = Box(60, 40, 12) - bore_tool
+sheet = Sheet(part, page="A3", scale=1, projection="third")
+sheet.authored_dimensions().authored_views()
+
+envelope = sheet.envelope(part)
+for parameter_id in envelope.dimension_ids():
+    sheet.dimension(envelope, parameter_id)
+bore = sheet.hole(bore_tool)
+print(bore.dimension_ids())  # discover this handle's Sheet measurement IDs
+sheet.dimension(bore, "bore.diameter")
+
+for name in ("front", "plan", "side"):
+    sheet.view(name)
+sheet.section_view("A", through=bore)  # or at=0 for an explicit model-space Y plane
+
+drawing = sheet.build()
+issues = drawing.lint()
+for issue in issues:
+    print(issue.severity, issue.code, issue.message)
+# drawing.export("build/section", formats=("pdf", "svg"))
 ```
 
+`dimension_ids()` lists the Sheet handle's dotted IDs: use `"bore.diameter"` here.
+Drawing.dimension instead takes a kind and optional role, such as `"length"` with
+`role="width"` for an envelope. Hole diameter/depth use Drawing.callout, not
+Drawing.dimension. Inspect `issues`: authored omissions
+remain visible, so a successfully built section does not prove a complete drawing.
+
+`view()` and `section_view()` define complete authored principal and derived sets.
+To augment automatic views instead, start a new Sheet, explicitly select
+`auto_views()`, and use `add_section_view("A", through=...)` or `at=...`.
+That mode remains supported; `auto_views()` emits a soft-deprecation notice with
+no removal date. Do not switch an already-authored view set to `auto_views()`.
+See the runnable augmentation example in `docs/reference/sheet.md`.
+
+`Sheet.section()` is deprecated with removal targeted at 0.6.0. Migrate it to the
+method for your view source above. `Drawing.section()` remains the automatic
+post-build section operation: it may return no section when the geometry does not
+warrant one. It does not replace an explicit authored section request.
+
 Arbitrary **auxiliary** views have no public verb: `add_view()` was the way to
 project one and is deprecated, so a custom viewing direction is not currently part
 of the supported surface.
@@ -311,7 +350,7 @@ for i in dwg.lint():
 dwg.repair()
 
 # Pin a deliberate placement so repair won't move it (the constraint solver will
-# honour it too as it lands — ADR 0003):
+# honour it too as it lands — ADR 2):
 dwg.pin(name)             # name from dwg.annotations(); dwg.unpin(name) to release
 ```
 

{draftwright-0.4.24 → draftwright-0.4.26}/src/draftwright/__init__.py

@@ -27,6 +27,9 @@ _LAZY = {
     "ScaleIncompatibilityError": "draftwright.builder",
     "make_drawing": "draftwright.builder",
     "Drawing": "draftwright.drawing",
+    "BuildEvent": "draftwright.progress",
+    "BuildCancelled": "draftwright.progress",
+    "observe_build": "draftwright.progress",
     "FeatureInfo": "draftwright.drawing",
     "ReportUnavailableError": "draftwright.reporting",
     "INSPECTION_SCHEMA": "draftwright.inspection",
@@ -34,6 +37,9 @@ _LAZY = {
     "InspectionUnavailableError": "draftwright.inspection",
     "inspect_step": "draftwright.inspection",
     "Sheet": "draftwright.sheet",
+    "Document": "draftwright.document",
+    "DocumentResult": "draftwright.document",
+    "DocumentBuildError": "draftwright.document",
     "lint_feature_coverage": "draftwright.linting",
     "PmiExtractionReport": "draftwright.pmi",
     "PmiRecord": "draftwright.pmi",
@@ -89,6 +95,7 @@ if TYPE_CHECKING:  # static analysers / IDEs — no runtime import, no kernel co
     from draftwright._warnings import ScaleCompletenessWarning, SoftDeprecationWarning
     from draftwright.builder import ScaleIncompatibilityError, build_drawing, make_drawing
     from draftwright.compose import choose_scale
+    from draftwright.document import Document, DocumentBuildError, DocumentResult
     from draftwright.drawing import Drawing, FeatureInfo
     from draftwright.inspection import (
         INSPECTION_SCHEMA,
@@ -104,6 +111,7 @@ if TYPE_CHECKING:  # static analysers / IDEs — no runtime import, no kernel co
         extract_pmi,
         extract_pmi_report,
     )
+    from draftwright.progress import BuildCancelled, BuildEvent, observe_build
     from draftwright.reporting import ReportUnavailableError
     from draftwright.sheet import Sheet
     from draftwright.view_plan import ViewConstraints, ViewPlanIncomplete, ViewSpec
@@ -117,9 +125,15 @@ def __dir__():
 
 
 __all__ = [
+    "BuildEvent",
+    "BuildCancelled",
+    "observe_build",
     "INSPECTION_SCHEMA",
     "INSPECTION_SCHEMA_VERSION",
     "Drawing",
+    "Document",
+    "DocumentResult",
+    "DocumentBuildError",
     "SoftDeprecationWarning",
     "FeatureInfo",
     "InspectionUnavailableError",