The repository moved to the PhySpace org: pyproject project.urls
(carry into wheel metadata on the next release) and the README star
history charts now reference the new location.
- blend garbage-volume assertion checks the contract (kernel returned
more material than the 1000 input) rather than the macOS-specific
1036 value; Linux OCC reports ~1039 for the same r=6 fillet
- sca init shell-integration test pins SHELL=/bin/zsh; the .zshenv
target follows SHELL (or an existing .zshenv), and CI runs bash
test_render_screenshot_multiview patched _render_polydata_views, which
after the prepare/execute split is only the synchronous wrapper used by
the STEP inspection path; the SDK screenshot path now enters the grid
engine at _prepare_polydata_render.
The evidence render ran on a daemon thread that imported VTK and, on
non-macOS, executed in-process GL — a native crash there killed the whole
process mid-test-suite (observed on CI), and under load the 15s budget
turned into silently missing evidence.
The screenshot pipeline now splits into prepare (validate + tessellate,
main thread) and execute (render plan: in-process or crash-isolated
worker subprocess). The diagnostic evidence channel prepares on the
calling thread and always executes worker_isolated, so its daemon thread
only ever orchestrates a subprocess.
A render that cannot finish within its budget now reports a named
'render-unavailable' evidence entry instead of vanishing; the budget is
tunable via SCA_DIAGNOSTIC_RENDER_BUDGET (tests: 60s, default: 15s).
Also updates two addon tests to the 2.1.3 runtime-state contract:
remove deletes three recorded locations (payload, skill, runtime dir)
and effective_command takes runtime_dir.
CHANGELOG added; version bumped to 2.1.3 across pyproject, skill
frontmatter, and README current-release lines; generated skill docs
refreshed via tools/auto_docs_gen.py.
The wheel force-includes the uncompiled docs/skill source tree and
skillproj.toml as package resources; compilation happens at install
time on the user's machine, so no repository checkout is needed.
The compiler moves to simplecadapi.skill.compiler; tools/skillbuild.py
stays as the maintainer-side wrapper over the same code.
'sca skill install' compiles into <skills-dir>/simplecadapi (location
resolved through the existing addon config/env chain, default
~/.agents/skills; no sca init required) and refuses to overwrite
without --force, which only permits replacing a directory whose
SKILL.md declares the same skill name.
- per-addon runtime dirs (~/.sca/runtimes/<name>), created at install,
untouched by update, removed with the addon; {runtime_dir} placeholder
in command_prefix and check_cmd alongside {addon_dir}
- 'sca addon check [name]': re-probe the installed runtime NOW and
refresh the cached registry record (install-time probe is a cache,
not truth); list shows cached state with its timestamp
- sca addon use exports SCA_RUNTIME_DIR for self-locating provisioning
- update replaces the payload wholesale but preserves a legacy in-payload
.venv (pre-runtime_dir addons keep working)
- remove: records without runtime_dir delete nothing extra — never
interpret the missing field as Path('') == CWD (regression test pins
the exact failure that motivated this guard)
- docs: Payload vs runtime state section, check verb, updated examples
- version 2.1.3b4
- simplecad-cache/simplecad-export entry points are gone (hard cut):
the same commands live under the unified dispatcher
(simplecadapi.cli) as 'sca cache ...' and 'sca export ...', each
group registered at parser level so per-group --help works
- sca init now wires the shell by default (--no-shell skips): a
~/.sca/bin/sca shim (Windows sca.cmd) execs the installing venv's
console script — the venv bin itself never goes on PATH — and the
shim dir lands on PATH via a marked, removable block in ~/.zshenv
(read by non-interactive shells, so agents see the command),
~/.bashrc, fish conf.d, or the Windows user PATH registry value
with a change broadcast; rc files are created only for the login
shell or when they already exist; re-running init refreshes the
shim (target discovery is symlink-safe, no resolve() out of venv)
- addon/cache/export cli modules expose configure(subparsers) +
_execute(args); module run() keeps the CLI-shaped argv
- docs: sca namespace across evergreen docs, shell-integration
section, 'never writes shell profiles' contract line retired
- tests: +17 (dispatcher groups, shell integration, entry-point
absence); cache/export suites moved to group-token argv
- 'sca init' replaces 'sca addon init' (init configures the machine, it
is not an addon operation); guidance text, config comment, and docs
follow; the 2.1.3b1 changelogs keep the historical command name
- version 2.2.0 -> 2.1.3b3 (pyproject + uv.lock)
- local installs ignore virtualenvs and tool caches (.venv, venv,
.pytest_cache, .mypy_cache, .ruff_cache, .tox): a real addon checkout
carried a full .venv straight into the addon home
- validated end to end against sca-connectors-addone 0.6.0: prerelease
compat floor parses, git-origin name consistency passes, probe runs
through command_prefix in the final installed layout, use dispatch
exports SCA_ADDON_DIR, update re-probes after wiping a provisioned
.venv (loud FAILED warning, non-blocking)
- standard: repository name == [addon].name == SKILL.md frontmatter name,
enforced at add/update (GitHub repo slug, or local git-origin basename
falling back to directory name); skill dirs install as sca-<name>
without doubling a leading sca-
- [runtime].command_prefix (optional): shell prelude joined in front of
check_cmd and every use dispatch; single {addon_dir} placeholder,
unknown placeholders rejected at descriptor load
- sca addon use NAME [CMD...]: run cmd inside the addon's declared
environment (SCA_ADDON_DIR exported, exit code propagates, --capture
for programmatic output); bare 'use NAME' reports prefix + dir
- runtime probe now executes AFTER the payload is committed, in the
final installed layout, so prefixes referencing {addon_dir} resolve;
failing probe remains a loud non-blocking warning
- use argv is shell-quoted per element so quoted args survive sh -c
- docs: descriptor reference, naming standard, use; SDK 2.1.2 -> 2.2.0
- tests: 12 new (descriptor prefix validation, name consistency, use
flows, prefixed probe); addon suites 73 green
P1 family 5 (sweep/loft): open-wire profiles now report the measured gap
(endpoint pair, distance, chain count) instead of a bare closedness
complaint - extrude_rsolid and make_face_from_wire_rface raise points
rewired through diagnose_open_wire (endpoint-pairing union-find, tolerance
scaled to wire extent; a lone segment reports its own length as the gap).
Kernel loft failures (loft_rsolid + loft_rshell, which report a wordless
'build did not complete') get a section compatibility verdict: coincident
consecutive stations (the empirically dominant cause), edge-count
mismatch, open section wires, and backtracking station order, with a
per-station S1..Sn inventory (edges/closure/planarity/centroid).
Wire evidence renders through a new 2D plan schematic
(render_wire_plan_evidence): the 3D VTK pipeline cannot mesh bare wires
('no renderable triangles'), so edges are parameter-sampled to
polylines, PCA-projected onto the best-fit plane, and drawn matplotlib -
same ink/palette language as the sketch diagnostics. Open-wire evidence
highlights the two gap-end edges and pins P1/P2; loft evidence
highlights the implicated stations.
Family 6 audit conclusion recorded in the review table: knot uniqueness
and trim bounds are already guarded, offset_wires was never implemented;
the one real gap (bspline fit silent garbage exit) needs curvature
probes and stays queued as mechanism-E work.
Error-language contract regression: test_error_harness pins English-only
error text (CJK masked in technical details) - all Chinese repair lines
from this branch's earlier rounds are translated to English, figure text
stays ASCII (DejaVu has no CJK glyphs), each new family test pins a
CJK-free assertion, and the legacy extrude guidance test now asserts the
structured gap contract (gap == 1.0 for a single open segment).
Full suite 1858 passed, 5 skipped; ty clean on changed modules.
P1 family 7 (assembly solve): the solver's five strict raise sites emitted
one-line ValueErrors that discarded the residual and connectivity data
already in hand. Residual failures (forwarded + final pass) now carry
measured translation/angular errors against both tolerances, a
per-constraint inventory (exceeded/ok with numeric deltas), and a
worst-first repair that targets connector frame definitions instead of
component placements, plus the closed-loop overconstraint escape (break
the loop or solve it inside a subassembly). Structural failures
(unresolvable loop / no grounded path / unsolved components) carry the
connectivity verdict as inventory (grounded/reachable/unsolved with
constraint-reference counts). The public wrapper surfaces them unchanged
via the SimpleCADError passthrough.
P1 family 8 (render export): the zero-hit highlight_tags guard now lists
the tags actually available on the shapes (solid + face level, capped at
24 + count row), so the typo question is answerable from the error
itself; _RenderTagMismatch promotes the payload to what_happened
(mechanism-A surgical promotion).
Tests: 3 assembly cases (15 mm residual asserted, connectivity verdict,
wrapper passthrough) + 1 render guard case (missing + available tags in
the headline). Full suite 1852 passed, 5 skipped; ty unchanged.
P0 family 4 (sketch solve): Sketch.solve's two bare ValueErrors replaced
by structured diagnosis. The solver already names failing constraints;
they now surface as measurements (constraint/entity/DOF counts, failed
constraint values), inventory rows (failed / near miss = direct conflict
partners sharing target entities / ok), parameterized repair (conflict
pairs named; dimension-type constraints relaxed before geometric ones),
and a 2D matplotlib schematic following the diag_png pattern (implicated
entities orange, related purple, failing constraint ids badged at their
first target; extents include circle/arc/ellipse extremes; single view
- planes have no occlusion). New module sketch_diagnostics.py sits
beside sketch.py importing only errors (operators must never be imported
from the sketch layer). SimpleCADError subclasses ValueError so legacy
handlers keep working; raise_harness_error passes it through untouched,
so inspect/wire-promotion paths surface the payload intact.
Mechanism E (blend exit check): fillet/chamfer may only remove material
on convex edges - observed: all-edge r=6 on a 10-cube 'succeeds' with
volume 1036.35 > 1000. assert_blend_volume_monotonic names it at the
exit; BlendVolumeViolation leads what_happened (kernel refused vs kernel
lied) with probe diagnosis appended. Concave edges legitimately add
material (bolt underhead fill = quarter-circle deficit x circumference,
verified +1.28 mm^3) so the increase check requires a provably all-convex
selection via a new side-probe convexity test (n_a - n_b lands in
material iff concave; the bisector probe is 90/270-blind).
Tests: 8 sketch cases (text axiom, pixel-verified render, ValueError
compatibility, passthrough) + 3 mechanism-E cases (r=6 garbage caught,
legit fillet passes, concave-edge regression). Full suite 1848 green,
ty unchanged from baseline.
Three user-ruled corrections to the evidence renders:
- Highlighted edges are CRISP LINES, not marker cylinders: the render
core already had an unused highlighted_edge_groups line-actor channel
(4.5 px colored lines exactly on the edge); it is now exposed as the
public render_screenshot_rpath(highlight_edges=...) parameter and used
by every blend/QL diagnosis. No marker geometry covers the model.
- Evidence views are FOUR AXONOMETRIC positions (30 deg elevation,
azimuth 45/135/225/315), not one iso plus three orthographic panels
and not a single view: a highlighted feature hidden behind the model
in one iso is visible in another (the demo's back-most edge was fully
hidden in the previous single view).
- Edge ink is bolder in diagnostics (edge_width_scale 0.0035) and
highlight lines outweigh it (8 px). Boolean operand evidence drops
leader-line callouts: solid-tag anchors sit inside the solids and
occlusion re-anchoring can land on the face nearest the OTHER
operand, making the label point at the wrong body — legend colors and
the caption carry the mapping instead.
Diagnostic renders stay supersample=1 (fixed-width lines don't need
SSAA; keeps the 15 s watchdog comfortable). 1837 passed, 5 skipped.
The evidence renders were geometrically correct but visually useless:
marker tubes rendered in the same gray as the model. Evidence now drives
the render's highlight channel — tagged faces/solids get palette colors,
a legend, and callout labels:
- fillet/chamfer: the failing edge is a thick orange tagged tube
("failing edge" legend + callout). Two latent marker bugs fixed on the
way: a wrong relative-import depth and a missing TopoDS.Vertex_s cast
had silently killed every marker (and the edge_start/edge_end
measurements) behind the best-effort guard.
- boolean: the two operands render as tagged wrapper copies in
orange/purple — the user's own objects are never tagged (verified by
a pollution test).
- QL: matched faces highlight orange, up to three near-miss faces
purple, on a wrapper copy of the scope; matching is by kernel IsSame,
not Python shape ids (which differ across wrapper copies).
Highlight visibility is asserted at the pixel level (palette-color
sampled pixel counts), not by eyeballing. 1836 passed, 5 skipped.
Fillet/chamfer failures classify at raise time against the accumulated
degeneration catalog (repo history + OCC ecosystem): sliver edges in the
selection, tangent adjacent faces (dihedral probe via surface projection
— a G1 junction has no corner to blend for any size), blend size vs face
room (boundary-inclusive: r == room degenerates the strip, empirically
verified on a bore mouth where OCC accepts r=5 but fails at r=6 == the
6 mm annulus), partially selected smooth chains on periodic faces (the
boolean-seam split), crowded/mixed-convexity corner vertices, and the
2x-size tangency-critical interaction. Generic corner-blend conflict
goes last so specific explanations win; three same-convexity edges at a
box corner are routine and no longer shadow them.
QL cardinality violations now raise structured errors carrying the
selection-trust contract: an inventory (hit + near_miss with surface
parameters and axial spans, so split pieces of one surface stay
distinguishable in text), logical-surface grouping (faces on one
underlying quadric are one logical face the kernel split — pieces need
not be adjacent), parameterized repair naming the group, and one
rendered evidence view with boundary rods outlining the matched faces.
Symbol numbering follows the candidate enumeration so text and image
share one naming.
1835 passed, 5 skipped; ty clean on changed modules.
Benchmarking the failure path surfaced two defects:
1. Nearest-disjoint-PAIR reporting misattributed failures: two operands
not touching each other may still be transitively connected through
a third, so the ring case reported an internal 2.29 mm pair instead
of the real 7.8 mm hub-to-ring separation. Diagnosis now unions
touching operands into clusters (gap <= tol) and reports the nearest
inter-cluster pair; a single cluster that failed to fuse reports the
touch-without-overlap pair as non-manifold contact. Beyond the pair
probe cap it reports nothing rather than guess.
2. Evidence rendering was unbounded on the failure path: the render
worker allows 180s x 6 attempts, and identical agent retries re-paid
~5s each. Diagnostic renders are now downgraded single-view, deduped
per failure signature (same unmoved gap renders once per process),
and abandoned after a 15s watchdog — the error always goes out
immediately, measurements first (text axiom).
Failure-path costs after this: probes 4 ms (2 small solids) to 86 ms
(70-face plate) on top of the kernel's own failed attempt; evidence
render ~5 s once per distinct failure, ~15 ms on retries.
ErrorGuidance gains measurements / evidence / repair / inventory; every
measurement renders into the error text (text axiom), rendered evidence
images land next to the part-cache root and their paths appear in the
text. Legacy call sites emit byte-identical output while the new fields
are empty.
Boolean union/cut/intersect failures now classify at raise time:
disjoint operands report the exact min gap, closest points, closure
vector, and an operation-specific parameterized repair; edge/vertex/
tangent-only contact is distinguished from positive-volume overlap via
an intersection-volume probe. Evidence rendering is default-on for
failures (SCA_NO_DIAGNOSTIC_RENDER to disable); the test suite opts out
in conftest with dedicated render tests opting back in.
SimpleCADMessageError now keeps the display message separate from the
programmatic .message attribute (ArtifactValidationError str() had
drifted; 6 suite failures traced to match= assertions on it).
1825 passed, 5 skipped.
SimpleCADMessageError bridge base: message-style raise sites keep their
legacy call shape and plain str() while gaining guidance/to_dict. All 24
module-level exception classes now form a single root; CacheLockTimeout
stays catchable as TimeoutError via dual inheritance. Emitted-script
shims (freecad/solidworks runtime fragments, fusion _script_helpers
template) stay RuntimeError by design and are marked as such.
1814 passed, 5 skipped; ty diagnostics unchanged.
Reported by the OmniSim evaluation of the public u-link example
(2026-09-11): pip install + export.py on Windows died three times in
the build layer before any geometry was built.
- Binary-mode opens: every byte-exact os.open site now sets O_BINARY
via _internal/os_compat.with_binary_flag. autocrlf=true clones read
builder sources in text mode, stripped CR, and aborted with a false
file_input_changed (25579-byte u_link.py read back as 25092); the
same hazard expanded LF on cache writes and would corrupt CAS
hashes. Sites: build/dependencies.py, artifacts/feature_graph.py,
scene/archive.py, cache/store.py (object/record writes, lock
create), artifacts/interface.py (lock create).
- Directory fsync is POSIX-only: os.open(<dir>)+fsync raised
PermissionError on Windows in cache/store.py and
artifacts/interface.py; both now no-op off POSIX via one helper.
- Stale-lock recovery by evidence: a lock whose recorded owner pid is
provably dead is recovered immediately (unreadable owners still wait
out the age gate, live owners are never broken). Windows liveness
probing uses OpenProcess/GetExitCodeProcess — os.kill(pid, 0) maps
to TerminateProcess there and kills the process being probed.
- Console hardening at import: non-UTF strict streams are reconfigured
to backslashreplace so a cp1252 console cannot raise
UnicodeEncodeError from a diagnostic print inside an error handler
and mask the real failure.
- .gitattributes: byte-exact by default, LF pinned for text formats,
so builder-source digests stop depending on core.autocrlf.
Tests: test_os_compat.py (15) + dead-owner immediate recovery in
test_cache_store.py; full suite 1799 passed, 5 skipped. ty: zero new
diagnostics.
viewer/server/runtime.py lists MAX_ENTITIES_PER_ANNOTATION in __all__, but
the name is not defined in the module -- it appears nowhere else in the
repository. The other 8 entries all resolve.
`from viewer.server.runtime import *` therefore fails with
AttributeError: module has no attribute 'MAX_ENTITIES_PER_ANNOTATION'.
Add the drawing inspection namespace and its parser, calibration, section and
independent acceptance dependencies on the current dev architecture.
Protect input BREP during material fusion and sectioning. Bind dimensions,
annotations and visual reviews to source identities and measured geometry.
Connect the workflow and generated API docs to all seven skill build targets.
Make standalone verifier tests work with the pytest console entry point.
Validation: 186 drawing, documentation, skill-target and public API tests;
16 non-render BREP query tests; compileall and skillbuild --check.