* wip(render): reconcile completed material and image pipeline source with 0.20 (#5493) Source-only integration reference for staged review, not a merge-ready aggregate. Donor: 0xlillith/solidcraft@aea20b0115. Upstream:858e5995d6. Retain original CPU/material contracts and explicit GPU donor provenance in docs/render-materials-lab.md (#2067, #2191, #2780, #3306). Preserve released format migrations and current navigation/startup/shell behavior. New saved records use pending descriptors. The physical-card descriptor follows the maintainer's material-engineering-cards naming request, with a legacy-lab format-29 regression. Replace raw new panel hosts with shared containers. Repository checks, complete workspace/all-target Clippy, and the independent physical/resource authoring checks pass for this source. The fresh full local CI invocation has reached test compilation and is not yet complete. Do not transfer donor native output or prior test totals to this integration. Generated review screenshots, video, package ZIP and machine logs remain at the immutable personal evidence pin. Uncommitted geometric displacement is backed up separately, not silently included. No kernel/vendor change, direct main write, release or independent contributor-branch rewrite. Co-authored-by: Christian Svensson <blue@cmd.nu> * test(cli): pin the Compact camera-sample admission diagnostic (#5493) The bounded request still refuses 1024x1024x64 samples before host initialization and writes no output. Update only the stale expected diagnostic to the existing Compact budget wording; production limits and code are unchanged. Exact-tree CLI regression suite: 14 passed, 0 failed. The full repository gate has been invoked separately and is not yet complete. * Normalize UI container violation paths across platforms Report repository-relative paths with forward slashes so diagnostics and the existing nested-package regression assertions agree on Windows and Unix. Keep the container detection rules unchanged. Validation: official ui-containers gate and all seven focused xtask tests passed; rustfmt and diff checks passed. Only xtask/dependencies were compiled; no application build or heavy tests. (cherry picked from commit44b58d8e10) * fix(render): preserve camera contracts and correct acceptance regressions (#5493) Preserve Design view.apply semantics with a separate strict Render camera command. Retain existing translations when English-only aliases collide; add material-axis entries and camera-specific pitch labels. Compare complete validated engineering cards and retain job handles before cancellation. Focused and native acceptance is pinned to treef8a423b21f. Full CI has been invoked separately and is not claimed green. Landing follows the render integration policy in #5493. * fix(render): resolve showcase licence and upstream resource hygiene (#5493) Record SychPL's explicit MIT OR Apache-2.0 grant, retaining source/model bytes and the Ubuntu lettering notice. Remove 80 absent attribution rows, personal fork records, dead delivery attributes and three fork/resource-only workflows. Existing xtask assets now performs bounded offline hash checks and rejects orphan render attribution; no parallel draft CI or package installation. Original authoring reproduction remains explicit. Scoped xtask tests, assets, Clippy, formatting and prepared SELENE validation pass; no application or renderer-wide result is inferred. * fix(render): align saved bounds and progressive sample resolution (#5493) Address review r4364211669/r4364211677/r4364211681/r4364211691/r4364211695. Persisted light/frame domains respect the existing 1e9 document bound; related LED/rectangle/direction cases use the same bound. Workstation primary resolve shares the 4096 admission cap and film counters use checked conversions. Exact candidate: 485 CPU render tests, 21 render document tests and strict scoped Clippy pass, including positive boundary round trips and 2048/4096 end-to-end checkpoints. No released format/migration edits, relaxed test limits or full-stack acceptance claim. * wip(render): isolate optional resources and harden sample handling (#5493) Review work in progress: opt-in encoded render library with reproducible runtime catalog exports; native-only robust dependency through the workspace; checked bloom slices; per-sample point-light diagnostics; independent area-light spatial/film keys. Resource-module binaries in both configurations, generation, Cargo production feature graphs and attribution checks pass. Full engine/render regression and combined acceptance are pending: do not merge this donor as a constituent or treat scoped resource proof as runtime acceptance. * fix(gpu): preserve donor allocations through the scope-safety repair (#5722) Port the native-validated #5723 scope-cleanup correction into the experimental donor, retaining its adaptive, volume, aging, photographic and bloom allocations. Same reverse-drain helper and regression cases; the donor combination still needs its own compile/test gate and is not covered retroactively by render-base results. * claim: #1369 * Reject unknown pending concepts after format folding (#1369) * test(render): close bounded sampling and bloom review regressions (#5493) Validate the optional-resource/lighting/dependency donor at its exact tree. Required Vulkan GPU 127/0/3; CPU renderer 487/0; engine Render 72/0; document render 21/0; lean library 7/0; strict scoped Clippy, assets/layers/lists/containers and lean-engine WASM pass. Preserve original failed controller/typing attempts. This is the draft donor/disposition source, not a replacement for constituent render PRs or final main acceptance. * wip(render): preserve stable aging target validation candidate Exact staged source from prior review work on donor3b892eab5e. This is a recovery/review checkpoint, NOT accepted delivery. An actual command-path regression currently fails because the selected executor refuses ordered surface aging. No assertion, capability or admission limit is weakened. Native/UI/full combination acceptance remains pending. Saved/runtime split adds one pending descriptor and retains original file scope; no main/render branch is changed. * test(render): preserve numeric setup intent at the admitted coordinate bound Follow up jyviko review on #5494 without weakening the corrected saved-coordinate contract. The positive clicked fixture uses 1e9 instead of inadmissible 2e9; explicit out-of-range cases still refuse, and the full saved setup round-trips through JSON and the native container. Exact-source Render workspace 95/0 and strict all-target UI Clippy pass. This does not incorporate the separately failing stable-aging candidate or claim full current-render acceptance. * test(render): use the real GPU executor for saved aging Move successful native cold-reopen Check/Start coverage from the CPU-backed protocol fixture into the production GPU executor tests. Verify capture-index changes preserve the stable target and that enabling aging changes both PNG and raw EXR output. Retain explicit, allocation-free refusal coverage for executors without aging support. Production capabilities and admission checks are unchanged. * fix(render): persist stable identities for targeted aging (#5493) Separate saved RenderBodyTarget identities from captured mesh ordinals. Reject legacy ambiguous targets, resolve Check/Start after visibility changes and preserve native reopening, copies and undo. Unsupported executors still refuse; real AMD Vulkan regression completes saved aging after reordered capture. Source tree6b84c8adpasses document 23, engine Render 75, GPU effects 5 and Render UI 95 with no failures; scoped strict Clippy, WASM and repository gates pass. Fresh CLI/native reopen and clean/aged GPU exports pass with identical physical totals and inspected actual images. Whole current-render integration is separate. * fix(render): reconcile combined CPU/GPU contracts on current upstream Unify captured resources/status and CPU-vs-GPU request schemas after the real two-parent integration; remove obsolete duplicate Vulkan selector and retain combined platform-filter regression. Deduplicate only identical or superseded test definitions, retaining the stronger card metadata and reserved-executor assertions. No assertions, admission limits or feature refusals are weakened. All targets of render dependencies, GPU, engine, UI, CLI and native app pass cargo check with raytrace-cpu and bundled-render-library at treec70d00d1. Native executable tests and full current-source acceptance remain pending. This is a private integration rehearsal for subsequent constituent PRs, not an aggregate official render/main merge. * test(render): retain one complete host lifetime regression set Deduplicate byte-identical DropProbe/task-lifetime tests and retain the adapted environment/texture ownership regressions with every assertion and complete memory estimate. Keep the registered-geometry admission regression once; only struct field order differed. Replace a one-element diagnostic loop with its equivalent block, preserving all wrap/width assertions. Test-only integration repair. Formatting and diff checks pass; refreshed executable validation is required. No production behavior, limits, assertions or ignores changed. * fix(doc): recognize the proven format-29 card descriptor alias Normalize only the historical format-29 physical-material-cards spelling, and only when material-engineering-cards is registered. Admission and migration de-duplication use the same identity. Unknown concepts, wrong versions and incapable readers still refuse before mutation. Six controlled-history Rust regressions and actual CLI migration/no-clobber acceptance pass. No version, released migration or CI changes. Refs #5793, #1369, #5493. * test(render): preserve grounding refusal before explicit instance moves Update the two Render binding fixtures for upstream first-occurrence grounding. Verify grounded movement refuses without changing document/history, then explicitly unground through the public command before the intended move. Retain every target, resource, copy and persistence assertion. Refs #5493. --------- Co-authored-by: Christian Svensson <blue@cmd.nu> Co-authored-by: Victor Santos Oliveira <56417388+Vittuu@users.noreply.github.com> Co-authored-by: cfaulkingham <colin.faulkingham@gmail.com>
Sourced physical material references
Expanded data checkpoint: 2026-10-22. Physical engineering data is maintained separately from the authored render appearance. The original source files below are authoritative; exported native cards are reproducible projections, not a second independently edited dataset.
Delivered coverage
| Collection | Current coverage |
|---|---|
| Named reference profiles | 59, with 416 numerical records covering 46 quantity types |
| Public primary source records | 50, with locators, retrieval date and review limitations |
| Material concept specifications | 600/600 have an explicit physical role, identification requirements and unknowns |
| Concepts with reference candidates | 306; these can be substrate, constituent, comparison or named-grade candidates |
| Concepts still requiring a specific formulation | 294; no unrelated numerical material is substituted |
| Authored PBR surface associations | 48/48 linked to reviewed reference candidates and explicit physical-role rules |
| Schema-1 native projections | 59 envelopes: 48 nonempty, 11 extended-only, 113 native property blocks |
| References eligible for material creation | 46 have a supported point density; other references do not acquire an invented mass density |
A surface reference association is not identification of a manufactured part. A metallic-looking coating is not a metal substrate; a fibre is not a laminate; feedstock is not an isotropic printed part; loose granular density is not grain density. References remain explicitly named and require grade, processing and conditions to match the intended application. No physical material is silently assigned to a body, and no appearance edit changes its engineering data.
Data and relationships
- profiles.json: the 59 exact material identities, numerical values/ranges, original units, SI conversion, measurement conditions and limits.
- sources.json: primary-source URLs, selected locators and review records. Public availability is not a redistribution licence or authentication.
- quantities.json: units, dimensions and bounds. Hardness scales, thermal transitions, frequencies and directional measurements remain distinct.
- bindings.json: all 600 concept specifications and 48 authored surface relationships, including substrate/stack/recipe dependencies.
- exports/native-cards.json: conservative native schema-1 projections, with every excluded property identified and retained in the extended profiles. This is not itself a native library import file.
- exports/coverage.json: generated coverage and exclusions.
The references cover metals and solders, engineering polymers, silicones and resins, additive-manufacturing feedstock and specimens, woods, cork/MDF, glass and ceramics, PCB and composite constituents, coatings and terrestrial lunar simulants. New named references include PMMA sheet, PVC stock, Kevlar 49 fibre, cured epoxy, UV epoxy and specific alkyd, stoving-enamel and acrylic coatings.
Properties preserved
Mechanical records include density, Young/shear/Poisson measurements, tensile, yield, compression, shear, flexural properties, elongation, fracture/tear data and explicitly identified hardness scales where published. Thermal records include conductivity, expansion, heat capacity, glass transition, melting, decomposition and qualified service-temperature statements. Electrical records retain frequency-specific permittivity/loss, resistivity and dielectric strength. Optical, moisture, granular and application-thickness records retain their own units and meaning; they are not reinterpreted as native elastic constants.
Each numerical record preserves a source, original value/unit, conversion, qualifier, condition fields and limitations. A range is not reduced to its midpoint; a lower-bound strength is not a typical value. Missing conditions and uncertainties remain null/unknown. Per-property cure schedules survive native projection. An isotropic elastic block refuses mismatched source, temperature, moisture, rate, state or direction rather than combining unrelated constants.
Some new coating profiles contain only published temperature or film-thickness information. Their cured density, modulus and strength remain unknown. In particular, liquid/mixed-resin density and package weight are not cured-film material properties. See source review.
Validate and inspect
All tools use Python 3.11+ standard-library code. From the repository root:
python -B assets/render/physical/tools/physical.py validate
python -B -m unittest discover -s assets/render/physical/tools -p 'test_*.py'
python -B assets/render/physical/tools/check_physical.py --cli /trusted/solidcraft-cli
python -B assets/render/physical/tools/physical.py resolve SURF-001
python -B assets/render/physical/tools/physical.py prepare steel-c45 --acknowledge-reference
The native check calls the read-only material.properties.validate command. It
checks numerical admission and property preservation, not source authenticity,
material assignment, solver correctness, persistence or library import. Evidence
and executable hashes stay in ignored target/physical-material-review/.
Native library export without data loss
Generate a non-executing plan for all point-density references:
python -B assets/render/physical/tools/export_library.py --acknowledge-reference
With a trusted runtime that actually supports physical-card persistence and library v2, create and verify a separate reference library:
python -B assets/render/physical/tools/export_library.py \
--acknowledge-reference --cli /trusted/card-capable/solidcraft-cli
Optional repeated --profile ID arguments restrict the selection. The exporter
first verifies the command contract, then uses a fresh CLI design with no
geometry, writes a native v2 library and design into a new target/ directory,
checks every card/source/condition/density, asks the native library inspector to
verify content revisions, and cold-reopens/re-exports the design. It does not
manually approximate Rust's canonical revision serialization. Existing files,
live GUI sessions, user models and body assignments are untouched.
The baseline Pegasus CLI validates cards but cannot persist them in materials; the exporter therefore refuses it before creating anything. Unit tests and that refusal are not a successful end-to-end v2 export. A successful modern-runtime run writes its own receipt; no such runtime receipt is implied by the authored data. The complete extended dataset must accompany the narrower native library. Electrical, hardness, ranges, directional measurements and unsupported quantities must not be claimed to have been embedded in schema 1 merely because a profile has a native projection.
Integration and publication
Use INTEGRATION.md to connect the records to the separate Render
branch. runtime_assignment remains false until actual target selection and
application acceptance are performed. No native document migration, material-card
schema expansion, rendering shader, solver, model, appearance texture or optical
preset is changed here. Full workspace CI remains a separate integration gate.
All new curation, validators and tooling are original contributor work under MIT OR Apache-2.0. Publisher data remains attributed to its sources; supplier brand/grade names do not imply affiliation or certification. Selected numerical facts are documented without bundling supplier tables, PDFs, artwork or code.