[TEMP] Unity Spring Bones

[RocioCM]

Summary

Update wearable preview version to support spring bones simulation on Unity Wearable Preview.

Testing

Spring Bones Section:

• Load a wearable with existing spring bone nodes -> The wearables on the preview should have spring bone physics when playing emotes or rotating the avatar.
• Add a new spring bone via "Add a Bone" button -> The wearable on the preview should update with the new spring bone physics automatically.
• Remove a spring bone via the card menu -> The spring bone physics for that bone should disappear automatically from the wearable on the preview.
• Click Reset -> spring bones physics should revert to the last saved state on the preview.
• Save the item -> spring bones parameters should be saved correctly (reload the page to check, spring bone physics should work)
• Adjust stiffness, gravity power, drag force sliders -> wearable preview physics should update automatically after around 1 second.
• Edit stiffness, gravity power, drag force sliders or gravity direction values using the inputs (not the sliders) -> verify the values commit on blur. Wearable preview physics should update automatically after around 1 second.
• Use the center node dropdown to assign/clear a center bone from the hierarchy picker -> wearable preview physics should update automatically after around 1 second (probably there's no perceptible change, but it should not break anything at least).

Body shapes:

• On a wearable with the same model for both body shapes (male & female), switch body shapes —verify spring bones settings share the same values for both representations.
• Test with separate male/female GLB models — verify that the spring bones physics for both models are independent and preview body shape updates when switching tabs (male/female)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
builder	Ready	Preview, Comment	Apr 23, 2026 9:37pm

[coveralls]

Coverage Report for CI Build 24860034992

Coverage increased (+1.1%) to 50.867%

Details

• Coverage increased (+1.1%) from the base build.
• Patch coverage: 39 uncovered changes across 5 files (280 of 319 lines covered, 87.77%).
• 1 coverage regression across 1 file.

Uncovered Changes

File	Changed	Covered	%
src/modules/editor/reducer.ts	48	32	66.67%
src/modules/editor/sagas.ts	16	4	25.0%
src/modules/item/sagas.ts	35	27	77.14%
src/modules/editor/actions.ts	21	19	90.48%
src/modules/editor/types.ts	2	1	50.0%

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
src/modules/editor/reducer.ts	1	45.4%

---

Coverage Stats

Relevant Lines:	12406
Covered Lines:	6932
Line Coverage:	55.88%
Relevant Branches:	5405
Covered Branches:	2128
Branch Coverage:	39.37%
Branches in Coverage %:	Yes
Coverage Strength:	31.82 hits per line

---

💛 - Coveralls