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.
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
- @scad.part/@scad.assemble anchor defaults to the builder script's own
directory: cache + interface state land beside the source, standalone
scripts run anywhere, and the pyproject.toml walk-up requirement is
gone (explicit project_root still relocates the anchor)
- file_input() paths resolve relative to the anchor; in-repo examples
rewritten to script-relative declarations
- HistCAD translator emits keyword-form sketch-family calls (corpus
self-documentation), pinned by tests; booleans stay positional by
*solids signature
- both translators emit project_root=Path(__file__).parent explicitly;
examples/histcad_demo regenerated (STEP volume reconciliation held)
- FTC convention documents @scad.part parameters and the cache contract
- version stamps 2.1.2 + bilingual update notes
Tooling patch: SDK API unchanged. Adds the CadQuery→FTC translator toolset
with snapshot constraint recovery (merged in #49) and its bilingual update
notes; version stamps updated in pyproject+lock, SKILL frontmatter, and
both READMEs.
hatchling emits Metadata-Version 2.5, which twine 6.x (the whole 6.x line,
as of 6.1.0 in our lock) rejects during 'twine check' — the v2.1.0 release
run failed at Verify distributions. Publish metadata at 2.4 until the twine
line accepts 2.5.
Replaces the AGPL-3.0 license text with the canonical Apache License 2.0
and updates every reference: pyproject trove classifier, both README
license sections, and the skill frontmatter. The article drafts under
docs/ are untracked and were updated separately.
- render_screenshot_rpath now accepts raw TopoDS_Shape entries alongside
SDK solids: the STEP inspection family renders through the same public
entry with the same edge ink, supersampling and (for solids) tag
highlights/callouts — one API at SDK level, one engine below it
- edge ink + supersampling pushed DOWN into the shared multi-view grid
engine (_render_polydata_views_in_process): the default 4-panel
diagnostic grid and render_shape_views_rpath (inspect channel) now
draw tubed BRep edges with LANCZOS supersampling like the single-view
path; grid review score 9/10 (was thin 1px lines)
- render_shape_views_rpath keeps its signature as the inspect-family
convenience entry (dpi sizing contract preserved: 3240x2160) and gains
the 0.04mm edge deflection cap; it is no longer the only way to render
raw shapes
- ty config: unresolved-import ignored repo-wide — OCP/VTK ship no .pyi
stubs and examples import sibling modules, so import resolution was
~900 diagnostics of environmental noise (verified: zero real defects
in the class); replaces the duck-typing workaround with natural
isinstance(TopoDS_Shape) checks
- gates: 13/13 render tests, mixed [Solid, raw] input smoke, grid visual
review, API docs regenerated, step-inspection domain doc notes the
unified entry
Interactive re-mode (re.html) plus a local case server implementing the
ppt-master handshake: the human selects faces / draws regions / labels intent
on the original STEP, the browser composes a submission with server-side
entity context, and a waiting agent reconstructs per the existing
reconstruction contract and writes artifacts the UI polls back.
- viewer/server (stdlib-only): STEP -> synthesized Scene 2.0 projection
(GLB + entity sidecars, same shape as package scenes), region resolve
(centroid projection + front-facing filter), entity descriptors,
atomic submissions, ndjson side recording, --daemon/--wait/--wait-only/
--shutdown CLI with lockfile and 590s budget
- viewer/src: extract shared cad-three/entity-facts modules (main.ts now
consumes them), new SceneView class (assembly/picking/highlight) reused
by both studio viewports
- re-mode UI: annotation canvas (circle/lasso), intent palette, context
preview, submit flow, rebuilt v3 package loading, comparison image,
feature tree, evaluation tab
- governance: only the browser writes submission.json; UI never edits
geometry — code stays the single source of truth
- tests: 6 server tests (scene contract, region math, submission context
+ named failures, wait handshake exit codes, HTTP endpoints)
translator/freecad_translator/runtime/**.py are exec'd inside
FreeCAD's embedded interpreter; GRAPH_NODES / App / Part and ~80 other
names are runtime-injected globals by design. An overrides section
silences unresolved-import/unresolved-reference for those files only,
cutting 495 known-noise diagnostics from the baseline.
Removes src/simplecadapi/verifier (current-pose mesh penetration checks
via python-fcl), its test, and the planetary-reducer collision probe
example. Collision verification now lives in an external implementation
outside this SDK.
The python-fcl>=0.7.0.11 dependency is dropped with it: the verifier
module was its only consumer.
BREAKING CHANGE: scad.verifier and check_collision_rcollisionreport are
no longer exported. Workflow docs mentioning 'verifier' refer to the
Verifier Planner role, not this module, and are unchanged.
Full suite: 1425 passed, 5 skipped.
Add simplecadapi.dxf_engine: a declarative 2D drawing pipeline (SheetDecl/
ViewDecl/DimDecl/DatumDecl/CenterDecl/LeaderDecl) that plans views, runs
hidden-line removal, and renders annotated sheets to DXF/PDF via ezdxf +
pymupdf. Include the u_link_motor_mount drawing scripts as the worked
example.
The wheel now contains code only: generated skill docs live in docs/skill
(built by tools/auto_docs_gen.py + tools/skillbuild.py) and ship as the
Agent Skill archive instead of polluting site-packages with a top-level
docs package. Remove the stale sandbox entries from sdist/ty config.
* feat(skill): replace skill-pack with per-harness conditional compiler
skillbuild compiles the skill tree into per-target harness builds:
- <!-- skill:if omp,!claude --> blocks include text only for matching
targets; name-list conditions only, no else/nesting, fail-loud on
unknown targets and unpaired/nested directives
- fence-aware: directive-looking lines inside code fences are literal
- layout is the filesystem; tree root configured in skillproj.toml
- post-build assertion: zero directive residue, SKILL.md frontmatter
name check
Migration to the new model:
- docs/skill/ becomes the self-contained source root (SKILL.md,
references/, generated api/stdlib/core/guides now under
references/docs/; SDK_OVERVIEW/LICENSE/inspect are ordinary tree
files)
- auto_docs_gen output redirected into the tree (docs/api ->
docs/skill/references/docs/api, likewise stdlib)
- skills/simplecadapi/ is now the compiled omp target output;
dist/generic/simplecadapi the generic target
- dropped skill-pack entry point (plus dangling evolve/make-export
entries and their orphaned test), release workflow builds via
skillbuild + tar; README updated
First real conditional block: harness reading paths in SKILL.md
(skill:// mount on omp vs disk-relative on generic).
Verified: 59 tests pass (skillbuild 31, auto_docs_gen 19, persistence
regression 9); both targets build; outputs residue-clean; full suite
collects (1376 tests).
* refactor(tools): auto_docs_gen moves out of the installed package
tools/ scripts are repo-checkout dev scripts, not packaged CLIs:
- auto_docs_gen.py now lives in tools/ beside the other generators;
auto_tools/ package removed entirely
- path resolution simplifies: repo root = parent of tools/, fail-loud
if pyproject.toml missing; site-packages/cwd fallback branches were
dead code once the script stopped shipping in the wheel
- auto-docs-gen console script dropped from [project.scripts];
release.yml and README invoke python tools/auto_docs_gen.py
- MANIFEST.in stale src/auto_tools include removed; CadQuery-free
runtime scan no longer needs the auto_tools filter
- run_examples.py retired (user removal): README example-runner text
updated to direct examples/ scripts; dangling runner-contract test
(runpy.run_path into the deleted script) removed
Verified: 53 tests pass (auto_docs_gen + skill_build + ocp runtime
scan) and test_example_model_contract passes; regeneration from
tools/ is byte-identical (zero docs drift).
* refactor(skill): strip harness and build-tool content from the skill tree
The skill is plain harness-neutral content again:
- SKILL.md 'Reading skill files' section removed (the omp skill://
mount block and its !omp complement were the only conditional
blocks; the tree compiles identically for every target now)
- references/README.md: build-tool meta removed ('per-harness
conditional compilation', skillbuild packaging/validation claims —
link validation was never implemented, so the claim was false)
- live test now asserts the tree stays harness-neutral (zero blocks)
- skillproj.toml targets aligned with the user's output table
(omp -> skills/simplecadapi-omp, opencode -> skills/simplecadapi-opencode;
leftover 'generic' entry had no output and failed the build)
- compiled outputs are regenerable artifacts: skills/simplecadapi/
untracked from git, skills/simplecadapi-*/ gitignored, release.yml
and README build via skillbuild and tar the omp output directly
(bsdtar has no --transform; inner dir keeps its suffixed name)
Verified: 49 tests pass; both targets build 372 files with zero
conditional blocks; no omp/conditional/directive residue in the tree
or outputs.
* chore(docs): drop stale architecture review and design notes
Route union through CadQuery-style fuse defaults, emit a clear warning when solids remain separated beyond tolerance, and document the updated behavior. Bump the package and skill runtime references to 2.0.8 for the next PyPI release.
Document that STEP and STL exports accept mixed shape inputs and direct List[Solid] outputs from boolean operations, so downstream agents do not collapse results to a single solid unnecessarily. Refresh the generated docs and skill references and bump the runtime/version references to 2.0.7.