dcc-mcp-speedtree 0.1.1__tar.gz

dcc_mcp_speedtree-0.1.1/MANIFEST.in

@@ -0,0 +1,3 @@
+recursive-include scripts *.py
+recursive-include docs *.md *.json *.png *.gif
+recursive-include skills *.md

dcc_mcp_speedtree-0.1.1/PKG-INFO

@@ -0,0 +1,119 @@
+Metadata-Version: 2.4
+Name: dcc-mcp-speedtree
+Version: 0.1.1
+Summary: Local-first DCC-MCP adapter for SpeedTree official capabilities
+Author-email: loonghao <hal.long@outlook.com>
+License-Expression: MIT
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Requires-Dist: dcc-mcp-core<1.0.0,>=0.20.22
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: ruff>=0.11; extra == "test"
+Requires-Dist: build>=1; extra == "test"
+
+# dcc-mcp-speedtree
+
+Create and edit native SpeedTree generator graphs, regenerate them with the
+licensed Modeler command-line exporter, and hand verified assets to another
+DCC-MCP adapter. Graph authoring uses the observed SPM/STT file format and is
+experimental; full live Modeler control is not yet available.
+
+## Native node showcase
+
+![Willow and grass created through successive generator operations](docs/images/native-node-workflow.gif)
+
+The willow grows from trunk to primary branches, drooping branches, and leaf
+cards. The grass adds stalk and frond generators, then edits the width curve
+to taper the blades. Each step is a new SPM, regenerated by **SpeedTree Modeler
+10.1.0**. The diagram comes from the saved generator IDs and links.
+
+| Native output | Generators | Vertices | Faces |
+| --- | ---: | ---: | ---: |
+| Willow | 5 | 7,092 | 6,166 |
+| Grass | 3 | 27,540 | 59,400 |
+
+These are procedural geometry studies. The images use unchanged exported OBJ
+geometry with display materials in headless Blender; they are not Modeler
+screenshots or native material acceptance. No UI automation builds either
+asset. [Reproduce the workflow](docs/node-authoring.md) ·
+[Operation and geometry evidence](docs/node-showcase-provenance.json) ·
+[Native capability matrix](docs/native-capability-matrix.md).
+
+## Start
+
+This is a source preview. Install the checkout with `python -m pip install -e .`,
+then configure the installed Modeler executable:
+
+```powershell
+$env:DCC_MCP_SPEEDTREE_EXECUTABLE = "C:/Applications/SpeedTree/SpeedTree_Modeler.exe"
+dcc-mcp-speedtree
+```
+
+The standalone service has its own lifetime and OS-assigned port. Discover it
+with `dcc-mcp-cli --gateway local list`, then search and describe its tools.
+Optional GUI binding uses `--pid <PID> --window-handle <HWND>` and validates
+that the window belongs to the named executable. GUI actions must use the
+project-owned `dcc-cua` / `ui-control` route with a fresh exact binding.
+
+## Agent workflow
+
+Read the [capability audit](docs/capability-audit.md) for the complete tool chain
+and the limits of modeling, materials, LOD, wind, collision, and cancellation.
+Use `inspect_capabilities` for a machine-readable scope report without a GUI.
+
+1. `discover_templates` and `inspect_authoring_catalog` enumerate installed
+   generator templates and their stored properties. `inspect_graph` and
+   `inspect_properties` read the selected source. `edit_graph` adds, duplicates,
+   removes, connects, disconnects, renames, hides, or changes properties and
+   existing curve components, writing a **new** SPM/STT.
+2. `discover_content` locates installed SPM samples and Games/VFX presets;
+   `inspect_preset` reports the selected settings.
+3. `plan_export` checks an SPM, preset, format, and **new** output directory.
+4. `export_batch` exports 1–16 SPMs through `-export_game` or `-export`, with
+   `-export_options`. Supported extensions are `st9`, `st`, `fbx`, `obj`,
+   `abc`, and `usd`; availability still depends on product version/license.
+5. `export_status` reads progress while Core runs the job; Core cancellation
+   stops the owned export process (`DELETE /v1/jobs/{id}` on the owning service). `verify_export` checks the recorded file hashes before handoff. Each tree
+   lives in its own directory with its textures and material sidecar.
+6. `plan_import` prepares a verified handoff. Discover the destination adapter's importer, import into a new destination,
+   and read back geometry, materials, dependencies, transforms, and animation.
+
+The [asset bundle contract](docs/asset-bundle.md) separates export evidence from
+target import evidence. [Format and target coverage](docs/compatibility.md)
+records the tested combinations and feature limits. The service never runs a
+caller-supplied executable or shell command. Existing output directories are
+rejected; timeout, failed exit, changed input, missing mesh, or missing explicit
+material dependency stops the batch and preserves a partial manifest.
+
+## Unreal
+
+![Real SpeedTree source and Unreal Engine result](docs/images/speedtree-to-unreal.png)
+
+The same Palm asset in Modeler 10.1 and UE 5.5, using native SpeedTree
+materials after explicit unit, UV, and texture repairs on a duplicate.
+The final mesh height is 12.34384 m; collision scale and dynamic wind remain unverified.
+[Capture provenance and repair notes](docs/showcase.md).
+
+Use the installed Unreal ST9 Games preset for a modern Unreal workflow.
+`.spm` is the authoring source, not a Content Browser import format.
+`inspect_unreal_project` reports descriptor entries only: a missing entry is
+`null` because engine plugin defaults may enable it. Check installation and
+loaded modules through `dcc-mcp-unreal`; configure missing plugins only after
+the user authorizes the concrete plan. Configuration and restarts belong to
+the target adapter. This service does not silently install or enable plugins.
+
+After importing each ST9 via `unreal-assets.import_asset`, read back the mesh
+and dependencies. Successful export or enabled plugins alone do not prove a
+usable imported asset, correct wind, collision, or rendered appearance.
+
+## Official references
+
+- [Command-line export](https://docs.unity3d.com/speedtree-modeler/manual/export-from-the-command-line.html)
+- [Games export options](https://docs.unity3d.com/speedtree-modeler/manual/games-export-options.html)
+- [VFX formats and options](https://docs.unity3d.com/speedtree-modeler/manual/vfx-export-options.html)
+- [Unreal integration](https://docs.unity3d.com/speedtree-modeler/manual/import-to-unreal.html)
+
+The repository contains no vendor binaries, licensed sample assets, SDK files,
+or licensing material. Generated vendor sidecars can contain source-machine
+paths; keep raw exports and diagnostics local unless reviewed for sharing.

dcc_mcp_speedtree-0.1.1/README.md

@@ -0,0 +1,105 @@
+# dcc-mcp-speedtree
+
+Create and edit native SpeedTree generator graphs, regenerate them with the
+licensed Modeler command-line exporter, and hand verified assets to another
+DCC-MCP adapter. Graph authoring uses the observed SPM/STT file format and is
+experimental; full live Modeler control is not yet available.
+
+## Native node showcase
+
+![Willow and grass created through successive generator operations](docs/images/native-node-workflow.gif)
+
+The willow grows from trunk to primary branches, drooping branches, and leaf
+cards. The grass adds stalk and frond generators, then edits the width curve
+to taper the blades. Each step is a new SPM, regenerated by **SpeedTree Modeler
+10.1.0**. The diagram comes from the saved generator IDs and links.
+
+| Native output | Generators | Vertices | Faces |
+| --- | ---: | ---: | ---: |
+| Willow | 5 | 7,092 | 6,166 |
+| Grass | 3 | 27,540 | 59,400 |
+
+These are procedural geometry studies. The images use unchanged exported OBJ
+geometry with display materials in headless Blender; they are not Modeler
+screenshots or native material acceptance. No UI automation builds either
+asset. [Reproduce the workflow](docs/node-authoring.md) ·
+[Operation and geometry evidence](docs/node-showcase-provenance.json) ·
+[Native capability matrix](docs/native-capability-matrix.md).
+
+## Start
+
+This is a source preview. Install the checkout with `python -m pip install -e .`,
+then configure the installed Modeler executable:
+
+```powershell
+$env:DCC_MCP_SPEEDTREE_EXECUTABLE = "C:/Applications/SpeedTree/SpeedTree_Modeler.exe"
+dcc-mcp-speedtree
+```
+
+The standalone service has its own lifetime and OS-assigned port. Discover it
+with `dcc-mcp-cli --gateway local list`, then search and describe its tools.
+Optional GUI binding uses `--pid <PID> --window-handle <HWND>` and validates
+that the window belongs to the named executable. GUI actions must use the
+project-owned `dcc-cua` / `ui-control` route with a fresh exact binding.
+
+## Agent workflow
+
+Read the [capability audit](docs/capability-audit.md) for the complete tool chain
+and the limits of modeling, materials, LOD, wind, collision, and cancellation.
+Use `inspect_capabilities` for a machine-readable scope report without a GUI.
+
+1. `discover_templates` and `inspect_authoring_catalog` enumerate installed
+   generator templates and their stored properties. `inspect_graph` and
+   `inspect_properties` read the selected source. `edit_graph` adds, duplicates,
+   removes, connects, disconnects, renames, hides, or changes properties and
+   existing curve components, writing a **new** SPM/STT.
+2. `discover_content` locates installed SPM samples and Games/VFX presets;
+   `inspect_preset` reports the selected settings.
+3. `plan_export` checks an SPM, preset, format, and **new** output directory.
+4. `export_batch` exports 1–16 SPMs through `-export_game` or `-export`, with
+   `-export_options`. Supported extensions are `st9`, `st`, `fbx`, `obj`,
+   `abc`, and `usd`; availability still depends on product version/license.
+5. `export_status` reads progress while Core runs the job; Core cancellation
+   stops the owned export process (`DELETE /v1/jobs/{id}` on the owning service). `verify_export` checks the recorded file hashes before handoff. Each tree
+   lives in its own directory with its textures and material sidecar.
+6. `plan_import` prepares a verified handoff. Discover the destination adapter's importer, import into a new destination,
+   and read back geometry, materials, dependencies, transforms, and animation.
+
+The [asset bundle contract](docs/asset-bundle.md) separates export evidence from
+target import evidence. [Format and target coverage](docs/compatibility.md)
+records the tested combinations and feature limits. The service never runs a
+caller-supplied executable or shell command. Existing output directories are
+rejected; timeout, failed exit, changed input, missing mesh, or missing explicit
+material dependency stops the batch and preserves a partial manifest.
+
+## Unreal
+
+![Real SpeedTree source and Unreal Engine result](docs/images/speedtree-to-unreal.png)
+
+The same Palm asset in Modeler 10.1 and UE 5.5, using native SpeedTree
+materials after explicit unit, UV, and texture repairs on a duplicate.
+The final mesh height is 12.34384 m; collision scale and dynamic wind remain unverified.
+[Capture provenance and repair notes](docs/showcase.md).
+
+Use the installed Unreal ST9 Games preset for a modern Unreal workflow.
+`.spm` is the authoring source, not a Content Browser import format.
+`inspect_unreal_project` reports descriptor entries only: a missing entry is
+`null` because engine plugin defaults may enable it. Check installation and
+loaded modules through `dcc-mcp-unreal`; configure missing plugins only after
+the user authorizes the concrete plan. Configuration and restarts belong to
+the target adapter. This service does not silently install or enable plugins.
+
+After importing each ST9 via `unreal-assets.import_asset`, read back the mesh
+and dependencies. Successful export or enabled plugins alone do not prove a
+usable imported asset, correct wind, collision, or rendered appearance.
+
+## Official references
+
+- [Command-line export](https://docs.unity3d.com/speedtree-modeler/manual/export-from-the-command-line.html)
+- [Games export options](https://docs.unity3d.com/speedtree-modeler/manual/games-export-options.html)
+- [VFX formats and options](https://docs.unity3d.com/speedtree-modeler/manual/vfx-export-options.html)
+- [Unreal integration](https://docs.unity3d.com/speedtree-modeler/manual/import-to-unreal.html)
+
+The repository contains no vendor binaries, licensed sample assets, SDK files,
+or licensing material. Generated vendor sidecars can contain source-machine
+paths; keep raw exports and diagnostics local unless reviewed for sharing.

dcc_mcp_speedtree-0.1.1/docs/asset-bundle.md

@@ -0,0 +1,49 @@
+# Asset bundle contract v1
+
+`export-manifest.json` uses `schema: speedtree.export-batch.v1`. File paths in
+`items[].mesh`, `items[].files[].path`, and material maps are relative to the
+manifest directory. Move the whole bundle; resolve paths under that directory
+and reject traversal. The tool response includes a local absolute manifest path.
+
+The producer records exporter/source/preset SHA256 and byte counts, requested
+format and preset mode, requested_units and requested_transform settings, requested tree count,
+per-item status/exit code, and an inventory of emitted files. These hashes
+identify inputs and detect changes; they do not certify licensing or trust.
+Each successful item has a recognizable mesh header and nonempty output.
+STMAT material records preserve map semantics and two-sided flags without
+copying vendor `Source` paths into the manifest. Binary references still need
+the target importer. Raw vendor sidecars are kept unchanged locally.
+
+`status: exported` and `verify_export.verified: true` mean file-level checks
+passed. `target_validation.status: not_run` is deliberately independent.
+`dependencies.status` is `sidecar_verified` when explicit STMAT File references
+exist, otherwise `requires_target_importer`. It never asserts full binary
+texture dependency coverage. Preset unit/axis settings are requests; a target
+must read its effective world bounds, units, and transforms back.
+
+## Consumer contract
+
+A destination adapter should consume the resolved mesh and adjacent files,
+import into a new destination by default, and produce a separate receipt keyed
+by manifest hash and mesh hash. Include target application/version, importer
+and plugin state, imported object identifiers, geometry/LOD counts, material
+slots, missing references, effective transform, warnings, and per-feature
+`verified`, `converted`, `unsupported`, or `not_checked` results. Do not rewrite
+the producer manifest to turn file validation into target validation.
+
+Use the target adapter's typed capability discovery rather than embedding
+application commands in this package. Example routes: Unreal asset import for
+ST9/ST, Blender interchange import for FBX/OBJ/Alembic/USD, and the discovered
+Maya or 3ds Max importer for a compatible format. Missing plugins yield a
+reviewable configuration plan; apply only within the target's user consent
+contract. Importing a mesh never restores the editable SpeedTree generator.
+
+## Jobs and cancellation
+
+The export tool runs as an asynchronous core job in process. Poll its returned
+core job id using the advertised core polling contract; never resubmit a timed
+out launch to poll it. `export_status` reads the atomic manifest for completed
+count and per-tree states during execution. Cancel through the owning service's documented `DELETE /v1/jobs/{id}` endpoint or the gateway cancellation contract. Core cancellation is checked
+before launch, between trees, and at most every 250 ms while waiting on the
+owned exporter. Cancellation or timeout kills and reaps only that child,
+leaves the partial output/manifest for diagnosis, and prevents the next tree.

dcc_mcp_speedtree-0.1.1/docs/capability-audit.md

@@ -0,0 +1,114 @@
+# Capability audit
+
+Audited against Modeler 10.1.0 on Windows; native graph coverage updated
+2026-09-10. This adapter covers experimental native file graph authoring,
+official file export and destination handoff, **not the whole Modeler**.
+`inspect_capabilities` reports implementation scope without requiring a GUI;
+it is not a live document or license probe.
+
+## Exposure and packaging
+
+Four packaged Skills contain sixteen adapter tools. Core job/skill lifecycle
+and UI tools are shared infrastructure and are not counted as Modeler features.
+Every listed tool has a committed input/output object schema and script in the
+wheel. `scripts/check_wheel.py` installs the built wheel outside the checkout,
+checks the imported module origin, discovers and loads all four Skills, and
+calls the capability entry point. CI runs this gate after building the sdist
+and wheel. The repository remains a source preview; building a wheel does not
+mean it has been published to a package index.
+
+The audit also replaced ineffective top-level safety fields with standard MCP
+`annotations` hints. Read operations are now identified as read-only, while
+batch export remains destructive and asynchronous. A registry-level regression
+test and the installed-wheel gate check these annotations and all tool scripts.
+
+| Implementation | Typed tool (Skill prefix omitted) | Skill | Runtime evidence / boundary |
+| --- | --- | --- | --- |
+| Capability status | `inspect_capabilities` | discovery | Available without a GUI; previously only reachable through GUI runtime inspection |
+| Installed samples and presets | `discover_content` | discovery | Games and VFX presets; VFX counts now included |
+| Asset fingerprint | `inspect_asset` | discovery | File size/hash; no SPM generator parsing |
+| Preset properties | `inspect_preset` | discovery | Read-only INI sections, including requested animation options |
+| Export preflight | `plan_export` | discovery | Existing SPM/preset and new output; does not prove license or preset effectiveness |
+| Exact GUI binding | `inspect_runtime` | discovery | PID/HWND identity only; no live model inspection; separate GUI binding required |
+| Unreal descriptor | `inspect_unreal_project` | discovery | Explicit entries only; absent plugin entry is unknown, not disabled |
+| Official export | `export_batch` | export | Six formats exported; bounded batch, hashes, atomic manifest and partial failure evidence |
+| Batch progress | `export_status` | export | Per-tree status; no vendor-internal percentage or restart recovery |
+| File verification | `verify_export` | export | Hashes, headers, explicit STMAT references; not full binary dependency or animation acceptance |
+| Destination handoff | `plan_import` | export | Verified files and required target readback; no destination mutation |
+| Native generator graph | `inspect_graph` | nodes | Actual SPM/STT generators and links; no live document state |
+| Generator properties | `inspect_properties` | nodes | Stored scalar fields and indexed spline components |
+| Installed templates | `discover_templates` | nodes | Generator STT and project SPM files, discovered from installation |
+| Generator catalog | `inspect_authoring_catalog` | nodes | 51 installed generator templates, 16 types; parse failures explicit |
+| File graph authoring | `edit_graph` | nodes | Atomic operation batches to new files; seven native-exported showcase stages |
+
+The routing-only `speedtree-official` Skill has no tools. It now declares the
+SpeedTree family and its discovery/export dependencies. Its repository mirror
+is retained for direct Skill consumers; the runtime reads the packaged copy.
+Core's Python API loads this routing guide, but CLI 0.20.22 with Core 0.20.21 reported a 502 for
+the zero-tool load even while the guide became loaded. This shared lifecycle
+issue is distinct from executable Skill loading and remains a shared runtime
+limitation; it is not masked by adding an artificial tool.
+`select_samples`, runtime lifecycle functions, hashing, and sidecar readers
+are library helpers, not missing independent editing features.
+
+## Feature limits
+
+| Feature | Official boundary reviewed | Adapter coverage | Acceptance |
+| --- | --- | --- | --- |
+| Modeling / generator graph | Observed SPM/STT XML; no supported live Modeler authoring SDK identified locally | Experimental generator, link, scalar and curve-component file edits | Willow and grass stages regenerated by licensed Modeler CLI; no live document edits |
+| Materials | CLI exports textures and STMAT; target scripts may reconstruct shaders | Sidecar inspection and file transport only | UE Palm required explicit material/UV repairs; no Modeler material editor |
+| LOD | Games presets can request existing source LODs | Preset inspection and export | Three UE Palm LODs read back; no LOD authoring or transition playback test |
+| Wind | VFX Wind preset requests point-cache animation; native games data is target-specific | Preset requests recorded; existing generator fields accessible | Dynamic output not established in the tests below; no Fan authoring |
+| Collision | Authoring and target runtime are separate from file verification | No collision editing tool | Post-unit-conversion collision not accepted |
+| Batch cancellation | Adapter owns the launched CLI child; Core owns the job | Core DELETE job route, no duplicate job manager | Active child termination verified; source GUI preserved in the prior live test |
+| Import / plugin setup | Destination adapter and user authorization own configuration | Handoff only | No silent plugin install; target availability must be discovered |
+
+Unsupported-by-this-adapter does not mean the vendor product lacks the feature.
+Shader include files and an SDK export preset are not a Modeler authoring API.
+No undocumented process injection or guessed function signatures are used.
+The [native capability matrix](native-capability-matrix.md) records application
+features beyond the generator graph and the verified entry needed for each gap.
+
+## Wind investigation
+
+The installed `Wind.ini` requests wind, 30 FPS, five seconds, looping, no gusts,
+and the current source wind strength. The existing `inspect_preset` tool reads
+these settings, and `export_batch` records them as `requested_animation` while
+leaving `animation_validation=requires_target_time_samples`.
+
+Using that preset, both Games Palm and VFX Palm exported valid Alembic meshes.
+Blender's official importer evaluated frames 1, 16, 31, 61, 91, and 151. All
+position hashes were identical within each asset, with maximum displacement
+zero; no mesh-sequence modifier was created. Games Palm FBX export produced
+no MCX point-cache file. Moving the official options before the export command
+also produced no cache. These results establish failure to obtain dynamic
+output for these requests, not the root cause or universal lack of vendor wind
+support. Source wind configuration, preset application, and target runtime wind
+must be investigated separately. A static screenshot is not wind acceptance.
+
+A separate UE 5.5 diagnostic used the unchanged native ST9 mesh data and
+isolated material copies. The imported wind switches and packed wind UVs were
+present, but sampled default driving scalars were zero. Explicit nonzero
+material parameters produced changes in 45,699 and 45,305 pixels across two
+fixed-camera frame pairs, confined to the tree with no background changes.
+The stable zero-wind control changed zero pixels. This proves diagnostic GPU
+wind activity after target-side overrides, not correct source wind export,
+source fidelity, or approved artistic motion. The new twelve mesh/material/
+texture packages were saved and reloaded with valid references.
+
+The earlier static showcase was captured in a live editor session. On reopening
+the original baseline, some material packages were missing; that capture must
+not be used as proof of persistent material dependencies. The new diagnostic
+uses separately saved dependencies and leaves the original baseline unchanged.
+
+Official references: [Modeler CLI](https://docs.unity3d.com/speedtree-modeler/manual/export-from-the-command-line.html),
+[VFX export and animation](https://docs.unity3d.com/speedtree-modeler/manual/vfx-export-options.html).
+See [target compatibility](compatibility.md) for measured units and materials.
+
+## Cleanup scope
+
+Only identified test/lint/bytecode caches and empty benchmark directories are
+eligible for local cleanup after containment and ownership checks. Dirty source
+files, source assets, exported bundles, acceptance records, distributable
+archives, existing environments, and routing Skill mirrors are retained.
+Local cleanup receipts are not included in the public package.

dcc_mcp_speedtree-0.1.1/docs/compatibility.md

@@ -0,0 +1,79 @@
+# Format and target coverage
+
+Observed with SpeedTree Modeler 10.1.0 on Windows, 2026-09-07. A successful
+run describes this licensed installation; it is not a guarantee for every
+edition, subscription, or source asset. Each permitted export format below
+was generated by the official CLI and checked for a recognizable file header,
+nonempty mesh, file inventory hashes, and explicit material sidecar references
+where present. Vendor assets and raw local logs are not distributed here.
+
+| Format | Export evidence | Unreal 5.5 | Blender 5.2 | Maya 2026 |
+| --- | --- | --- | --- | --- |
+| ST9 | Palm, Oak, Conifer + textures | 3 StaticMeshes and material dependencies read back | Requires conversion | Requires conversion |
+| ST | Palm + textures, through SpeedTree MCP | Not imported in this run | Requires conversion | Requires conversion |
+| FBX | Palm; 6 materials, 37 map references | Not checked | Mesh read back: 6,081 vertices, 8,498 faces, 6 material slots | Same mesh counts; saved and reopened |
+| OBJ | Palm; 6 materials, 37 map references | Not checked | Mesh read back: 6,081 vertices, 8,498 faces | Same mesh counts; saved and reopened |
+| Alembic | Palm; 6 materials, 37 map references | Not checked | Mesh read back: 6,081 vertices, 8,498 faces | Same mesh counts; saved and reopened |
+| USD | Palm; 6 materials, 37 map references | Not checked | Mesh read back: 6,081 vertices, 8,498 faces | Same mesh counts; saved and reopened |
+
+3ds Max/Houdini/Unity handoffs use the same bundle contract; destination validation is
+owned by their adapters and is not claimed by this baseline. USD, Alembic, and
+other importer availability must be discovered in the particular target.
+GLTF/GLB, legacy SRT, STE, and XML are not export tool options in this release;
+file discovery support does not imply verified export support.
+
+## Feature preservation
+
+| Feature | Native ST9/ST route | FBX/OBJ route | Alembic/USD route |
+| --- | --- | --- | --- |
+| Geometry | Three ST9 meshes read back in UE | FBX and OBJ geometry read back in Blender | Alembic and USD geometry read back in Blender |
+| Materials/textures | Engine importer generates materials | STMAT semantic maps retained; target shader conversion required | STMAT maps retained; shader conversion required |
+| Transparent leaves | Palm appearance checked after explicit UV/material repairs on a duplicate | Opacity maps and two-sided metadata present; rendered result not checked | Same; cache import alone does not build leaf shaders |
+| LOD | Palm has 3 UE mesh LODs: 8,498 / 5,396 / 2,346 triangles | Preset-dependent; no preservation claim for this VFX sample | No LOD preservation claim for this VFX sample |
+| Wind/animation | Runtime-specific; dynamic playback not checked | Static sample; no wind transfer claim. OBJ is static geometry | Static sample; animated cache export requires a separate preset/test |
+| Instances | No preservation claim | No preservation claim | No preservation claim |
+| Units/axes | Explicit vertex conversion gives 12.34384 m on the repaired Palm duplicate | FBX encodes feet and gives 12.34384 m Blender height; OBJ needs explicit consumer normalization | USD encodes feet and gives the same Blender world dimensions; Alembic needs consumer normalization |
+| Editable generators | Remain in original SPM | Not transferred | Not transferred |
+
+Official references: [CLI](https://docs.unity3d.com/speedtree-modeler/manual/export-from-the-command-line.html),
+[VFX options](https://docs.unity3d.com/speedtree-modeler/manual/vfx-export-options.html),
+[Games options](https://docs.unity3d.com/speedtree-modeler/manual/games-export-options.html),
+[Unreal integration](https://docs.unity3d.com/speedtree-modeler/manual/import-to-unreal.html).
+The feature table distinguishes configured intent and measured results; it
+must not be interpreted as an animation, visual, or game-runtime acceptance.
+
+## Acceptance findings that remain open
+
+All four interchange formats reconstruct the same Palm vertex geometry after
+explicit mathematical unit/axis normalization. FBX and USD encode feet and
+produce a 12.34384 m world height in Blender. OBJ and Alembic need consumer
+unit/axis configuration. This run's preset requests for centimeter/Z-up were
+not reflected in the output metadata; changing CLI argument order or setting
+TransformScale=30.48 did not change the ST9 bounds.
+
+UE 5.5 ST9 imports measured only 40.49815 cm tall. Its native ST9 factory path
+does not use the legacy TreeScale option. Source-unit conversion therefore
+requires a separately verified normalization step, not an assumed importer
+flag. The baseline native materials resolved textures but rendered fallback
+surfaces. A separate Palm duplicate now renders correct foliage after material
+instance refresh, a corrected Subsurface map, and UV0 V inversion on all three
+LODs. Build-scale settings alone did not survive the UV rebuild consistently;
+explicit conversion of all three LODs' source vertices by 30.48 produced final
+bounds of 1,234.383705 cm with build and actor scales both 1. Collision scale and
+dynamic wind were not tested. See the [real capture and repair notes](showcase.md).
+
+Blender detailed checks also found six empty Alembic material node graphs and
+invalid OBJ normal image references with a trailing MTL bump option. Existing
+sidecar references are complete, but this is not equivalent to correct target
+shader reconstruction. Vendor-provided DCC importer scripts may help, but
+must be discovered in the local installation and checked for target-version
+compatibility; they are not redistributed by this adapter.
+
+Maya 2026 independently measured the same 12.34384 m height for FBX and USD.
+In its centimeter scenes, OBJ and Alembic were approximately 0.40498 m tall
+along Z and require consumer unit/axis conversion. OBJ produced six invalid
+texture paths equal to `1`, consistent with the trailing bump option; Alembic
+used a default shader. USD's 23 image paths existed. FBX had 17 existing
+relative image references and one empty file node, with runtime texture
+resolution unverified. Saving and reopening preserved all four mesh counts;
+Maya rendering, wind, and LOD behavior were not accepted by this test.

dcc_mcp_speedtree-0.1.1/docs/native-capability-matrix.md

@@ -0,0 +1,58 @@
+# Native capability coverage
+
+Target: SpeedTree Modeler 10.1 on Windows. This inventory separates native
+file access, official commands, and live Modeler commands. It does **not**
+claim that every feature of the application has a callable authoring API.
+No UI automation is used to fill native gaps.
+
+## Entry points and evidence
+
+| Product capability | Native entry | Exposed implementation | Evidence / remaining boundary |
+| --- | --- | --- | --- |
+| Generator inventory | SPM/STT `Generators` | `inspect_graph`, `inspect_authoring_catalog` | 51 installed templates parsed; 16 generator types |
+| Generator create/copy/delete/name/visibility | Generator XML and GUIDs | `edit_graph` | Validated file operations; Modeler export required |
+| Generator connections | `Links` with source/target GUIDs | Connect/disconnect, cycle and reference checks | Reloaded output graph; staged exports |
+| Branches, fronds, leaves | Generator properties | All stored property/component names accessible | Willow and grass native export cases |
+| Base, reference, mesh branch, conversion, stitches | Installed generator templates | Template instantiation and stored properties | Structure exposed; separate geometry recipes not yet validated |
+| Caps, fins, knots, zones, decals, mesh detail, targets | Installed generator templates | Template instantiation and stored properties | Structure exposed; separate geometry recipes not yet validated |
+| Batched leaves | Installed generator template | Template instantiation and stored properties | Structure exposed; separate geometry recipe not yet validated |
+| Distribution and random seeds | `Generation:*`, `Random Seeds:*` properties | Existing scalar/component editing | Vendor enums/ranges are not published in the XML |
+| Profile and parent curves | Stored spline control points | Existing scalar control-point editing | No arbitrary curve point insertion/deletion yet |
+| Wind, seasons, growth, LOD, UVs, normals, vertex colors | Stored generator property groups | Existing generator fields accessible | Field readback does not prove dynamic evaluation or final quality |
+| Fan, global lighting, document controls | Separate SPM objects | Preserved, not exposed for mutation | Needs a typed object contract and host evaluation tests |
+| Materials, textures, meshes, displacements, asset sets | `Assets` and external files | Existing exports/sidecar inspection | No complete asset-authoring or material-assignment transaction |
+| Forces, hand drawing, individual generated-node edits | Separate authoring state / node overrides | Existing state preserved where unaffected | No callable live authoring integration verified |
+| Collision generation | Modeler operation / saved collision objects | No native command exposed | Requires a verified command bridge or documented SDK |
+| Ambient occlusion computation | Modeler operation | No native command exposed | Same boundary; export is not an AO command |
+| Save and reopen authoring files | SPM/STT files | Exclusive new-file writes and parse readback | Does not update an already open document |
+| VFX and games export | Official `-export`, `-export_game`, `-export_options` | Export, status, cancellation, verification | Six supported output extensions; product/license dependent |
+| Batch control | Owned Modeler child + Core jobs | Progress, timeout, active-job cancellation | No vendor-internal progress or session reconstruction |
+| Interactive viewport, selection, undo/redo, timeline playback | Live Modeler UI state | No native bridge verified | CUA canceled; not replaced by input automation |
+| Modeler screenshot/viewport rendering | No reviewed CLI command | Not exposed | Showcase visualization must label exported-geometry renders honestly |
+| Engine integration | Exported ST/ST9 and destination importer | Verified handoff/preflight | Destination owns import and acceptance |
+| Licensing, preferences, application updates | Vendor-owned lifecycle | Not exposed as authoring mutations | Not evidence of a missing generator API |
+
+`inspect_authoring_catalog` generates the installed generator inventory rather
+than hard-coding a list of node types. New or unreadable formats are reported
+as failures. Property enumeration reports stored fields, including components
+of curves; it does not infer undocumented property meanings or legal ranges.
+
+## C++ / C# bridge boundary
+
+The installed Modeler includes Qt libraries and external-DCC import scripts.
+The reviewed installation contains no Modeler authoring headers, plugin SDK,
+or documented command interface for live node mutations. Qt libraries are not
+proof of an authoring API. The [Runtime SDK](https://docs.unity3d.com/speedtree-runtime-sdk)
+is a separate runtime integration; an engine importer also cannot establish a
+Modeler authoring interface.
+
+A complete live bridge needs verified host commands and signatures, a version
+handshake, main-thread dispatch, document/revision identity, typed arguments,
+undo transactions, and authoritative post-operation state. Until that boundary
+is available and tested, full native application coverage remains incomplete.
+Adding a stub hook, guessed addresses, or synthetic success responses would
+not close these gaps.
+
+References: [Modeler manual](https://docs.unity3d.com/speedtree-modeler/manual/index.html),
+[official command-line export](https://docs.unity3d.com/speedtree-modeler/manual/export-from-the-command-line.html),
+[generator template commands](https://docs.unity3d.com/speedtree-modeler/manual/generation-editor-toolbar-reference.html).