WillTools 2026-09-09 -- clean snapshot of the development repo for review

History-free snapshot of the private development repository at 77a82eb. Code, docs and the public catalogue only: no plant or job knowledge layers, no client, job or producer names (tools/scrub.py clean against the widened term list; a second word-level grep clean). The intro deck is left out because its slide images cannot be checked for job drawings.
2026-09-09 08:35:15 -05:00
commit 25592fa6c2
406 changed files with 223435 additions and 0 deletions
@@ -0,0 +1,27 @@
+title: Ticket QC
+# DEV. A fresh IronPython engine for every press: `lib/vibe` is re-imported
+# on each click, so an edit to a module this button uses is visible without
+# a Revit restart. It trades press latency (engine construction instead of
+# engine reuse) for restart-freedom, and it is the hottest button here --
+# 51 commits to its six modules in the seven days to 2026-08-30.
+#
+# Read docs/architecture-migration.md section 8 before trusting or removing
+# this. Two things it says that are not obvious: pyRevit's DEFAULT is already
+# a clean engine, and this extension gets one today only because
+# extension.json has no `url:` and so is never registered as a package --
+# add a url and every button silently switches to the shared engine. This key
+# is the pin against that, not a new capability.
+#
+# REMOVE IT PER BUTTON as that button stabilises: delete the two lines below.
+engine:
+  clean: true
+# No tooltip and no author on purpose. pyRevit renders both on hover;
+# the owner wants nothing there. Guarded by
+# WillTools.extension/tests/test_button_tooltips.py -- do not add them back.
+#
+# MOVED 2026-09-05 into the new Modeling.pulldown (see
+# Tools.panel/Modeling.pulldown/bundle.yaml), where this used to be one of
+# four large icons on Tools.panel. One line, no `\n`: a pulldown row renders
+# as text beside a 16px icon and the dropdown grows to fit the longest row,
+# so the title is free to say what it means -- unlike a large button, which
+# is as wide as its widest line.
@@ -0,0 +1,32 @@
+# -*- coding: utf-8 -*-
+#
+# Check shop tickets against their design spec.
+#
+# Reads the specs written by Extract Design plus the project's knowledge.yaml,
+# then compares every piece of the chosen design numbers against them.
+#
+# Every CHECK here is pure arithmetic - the same model always gives the same
+# answer, and every row of the checklist table is computed. One thing in the
+# report is not: with the run-time option `vision_escalation` on, the checks
+# code cannot settle (5.5) are escalated to a small model reading one rendered
+# view. That result is quarantined - its own list, its own codes, its own
+# section, and it can never set a checklist row. See vibe.ticketvision and
+# docs/ticket-checklist.md section 8bis.
+#
+# Read-only. Nothing here opens a transaction, including the image export.
+#
+# THE WHOLE BUTTON MOVED into `lib/vibe/ticketqc_run.py` on 2026-09-05, so
+# the new Reinforcing QC button could reuse it instead of these 765 lines
+# being copy-pasted -- see that module's own header for exactly what is
+# shared and what differs. This script is `mode='ticket'`, which is BYTE
+# FOR BYTE what used to live here: nothing about Ticket QC's own behaviour
+# changed in the move.
+
+# pylint: disable=import-error,invalid-name,broad-except
+__title__ = 'Ticket QC'
+
+from pyrevit import revit
+
+from vibe import ticketqc_run
+
+ticketqc_run.run(revit.doc, revit.uidoc, mode='ticket')