@combos-fun/engine 0.0.34 → 0.0.35

package/agent-skill.md

@@ -120,7 +120,11 @@ A Component holds data + self-contained behaviour for one concern on one entity.
 
 2D display objects must come through `plugin-renderer-`* systems or a custom `Renderer` subclass registered via `rendererManager.register(this)`. 3D objects must come through `plugin-renderer-3d-`* systems or a custom `Renderer3D` subclass. No raw `new PIXI.Sprite(...)` / `new THREE.Mesh(...)` in bootstrap or plain Components.
 
-### Rule 6: Component configuration via params, not imperative calls
+### Rule 6: One render Component per GameObject
+
+A GameObject may carry at most one visible render Component. Do not attach multiple render Components such as `Img` + `Text`, `Graphics` + `Sprite`, or multiple sprite renderers to the same GameObject. Create child or sibling GameObjects for additional visible elements and use the Transform hierarchy to compose them. This keeps renderer ownership, bounds, picking, ordering, and destruction deterministic.
+
+### Rule 7: Component configuration via params, not imperative calls
 
 Configure Components through constructor params (e.g. `autoPlay: true`). If behaviour must be triggered at runtime, do it from another Component's lifecycle hook, not from bootstrap code.
 
@@ -300,4 +304,3 @@ After modifying engine code:
 ## See also
 
 - `@combos-fun/engine/plugin-authoring` — full spec for writing a new `@combos-fun/plugin-*` package, including Component / System / Renderer / Renderer3D subclassing, manifest format, and publish requirements.
-

package/dist/engine.cjs.js

@@ -1001,7 +1001,7 @@ class Scene extends GameObject {
 }
 
 /** Generated at build from package.json */
-const version = "0.0.34";
+const version = "0.0.35";
 
 /**
  * Sent to `window.parent` after each `System.init` completes during `Game.addSystem`