Raster unit art handoff

Status: active production contract. PNG art is authoritative for the units listed below. Their old SVG depictions, SVG fixtures, contact sheets, and vector fallback paths have been retired.

Authority boundary

The client intentionally supports both asset types:

PNG-backed units still need normalized rig data for anchors, selection and HP bounds, animation bindings, semantic part routing, recoil, shadows, and native effects. That data lives in client/src/renderer/rigs/raster_rig_definitions.js; it is not generated from or backed by SVG art. The shared animation and Pixi routing machinery consumes both SVG-compiled definitions and raster-native definitions.

A configured PNG unit must have its texture. Missing frame-strip or atlas textures fail closed and surface a renderer error instead of silently displaying obsolete vector art.

Production files

The Tank’s legacy vector contact-sheet pipeline is deliberately not part of the repository. Its checked-in PNG atlas and explicit raster metadata are the production source.

Raster art rules

Current notable assets

Validation

For changes to production raster rigs, run the focused contracts that cover the changed asset plus:

node tests/rig_schema.mjs
node tests/rig_runtime.mjs
node tests/client_contracts.mjs
node scripts/check-client-architecture.mjs
node scripts/check-deploy-assets.mjs

Review raster changes at RTS scale in the Lab. A raster unit rendering without its PNG is a defect; do not restore an SVG copy to conceal the texture or metadata failure.