@combos-fun/plugin-development-tool 0.1.1 → 0.1.2

package/README.md

@@ -4,8 +4,6 @@ Scene / tagged object tap development tool: canvas overlay (2D + 3D) and parent
 
 Keywords: `devtool`, `inspector`, `selection`, `outline`, `editor`, `debug`.
 
-Game `GameObject` nodes are tagged at build time by the repo-local `vite-plugin-development-target` Vite plugin (not on npm). Add that plugin to the **game** Vite config.
-
 ## Documentation
 
 - Per-package agent / developer notes: [`agent-skill.md`](./agent-skill.md)

package/agent-skill.md

@@ -2,16 +2,14 @@
 
 **Shared editor iframe picker** (2D and 3D). Outline, markers, and pick hit-testing are drawn on a transparent HTML canvas overlay with the Canvas 2D API. It does **not** depend on `plugin-renderer`, `plugin-renderer-event`, `plugin-renderer-graphics`, or any `plugin-renderer-3d*` package.
 
-Game authors do **not** mount Targets or write `payload.source`. `@combos-fun/vite-plugin-development-target` rewrites `new GameObject(...)`.
+Game authors do **not** mount Targets, call `attachDevelopmentTarget`, or write `payload.source`.
 
 ## When to read
 
-Read when integrating the Combos editor iframe, pick mode, Scene Edit messages, marker overlays, or the host Vite plugin.
+Read when integrating the Combos editor iframe, pick mode, Scene Edit messages, or marker overlays.
 
 ## Public API
 
-`attachDevelopmentTarget(go, { file, anchor })` is the runtime helper the Vite plugin inserts. It is idempotent.
-
 `CombosDevelopmentToolSystem` accepts:
 
 - `postMessageOrigin`: outbound parent `targetOrigin`, default `'*'`.
@@ -45,18 +43,7 @@ new Game({
 });
 ```
 
-In the **game** Vite config (host / Creator), not in game source:
-
-```ts
-import { defineConfig } from 'vite';
-import { combosDevelopmentTargetPlugin } from '@combos-fun/vite-plugin-development-target';
-
-export default defineConfig({
-  plugins: [combosDevelopmentTargetPlugin()],
-});
-```
-
-Do not add `CombosDevelopmentToolTarget` from game code. Opt out of a construct with `// combos-no-target`.
+Do not add `CombosDevelopmentToolTarget` from game code.
 
 ## Runtime behaviour
 
@@ -64,7 +51,7 @@ The System starts disabled. In pick mode it shows a full-canvas overlay (`pointe
 
 2D bounds come from `Transform2D` size plus `GameObject` hierarchy (position, origin, anchor, scale, rotation). Set `Transform2D.size` when the visual does not match a zero size. 3D bounds project `Transform3D` world position through the active `Renderer3DSystem` camera; a mesh bounding box is used when the Three object is available, otherwise a screen-space pad around the projected point.
 
-The marker overlay is independent of pick mode and mute. It currently draws a 28×28 canvas badge only for `Sound`; the owner still needs a Target for selection and persistence (the Vite plugin attaches that Target).
+The marker overlay is independent of pick mode and mute. It currently draws a 28×28 canvas badge only for `Sound`; the owner still needs a Target for selection and persistence.
 
 ## postMessage protocol
 
@@ -86,7 +73,7 @@ Inbound messages are origin-checked. `allowedMessageOrigins: ['localhost']` adds
 
 ## Scene Edit fields
 
-Snapshots expose described schema-backed `fieldDescriptors`, not raw fields. For authoritative `@Field` metadata rules, read `@combos-fun/inspector-decorator`. Persist lookup uses `payload.source.file` + `payload.source.anchor` injected by the Vite plugin.
+Snapshots expose described schema-backed `fieldDescriptors`, not raw fields. For authoritative `@Field` metadata rules, read `@combos-fun/inspector-decorator`. Persist lookup uses `payload.source.file` + `payload.source.anchor`.
 
 ## Common pitfalls
 
@@ -96,10 +83,9 @@ Snapshots expose described schema-backed `fieldDescriptors`, not raw fields. For
 - A covering overlay is still selected when it is the only hit under the pointer.
 - Parent messages require an iframe (`window.parent !== window`) and an allowed origin.
 - Structural replacement needs `refresh`; ordinary Target add/remove does not.
-- Persistence fails if the game build did not run `combosDevelopmentTargetPlugin`.
 - Markers are visual only and do not create a Target.
 - Creator-managed game code must not call `setEnabled` / `requestSceneRescan` or emit `combos-development-tool:*` control messages.
 
 ## Verification
 
-Run `pnpm --filter @combos-fun/plugin-development-tool run test` and `pnpm --filter @combos-fun/plugin-development-tool run build`. The host Vite plugin is the repo-local `vite-plugin-development-target` package (not published to npm).
+Run `pnpm --filter @combos-fun/plugin-development-tool run test` and `pnpm --filter @combos-fun/plugin-development-tool run build`.

package/dist/plugin-development-tool.cjs.js

@@ -1733,7 +1733,7 @@ var CombosDevelopmentToolSystem = CombosDevelopmentToolSystem$1;
 /** Auto-generated by scripts/build-package.mjs — do not edit. */
 Object.assign(CombosDevelopmentToolSystem, {
     packageName: "@combos-fun/plugin-development-tool",
-    packageVersion: "0.1.1",
+    packageVersion: "0.1.2",
 });
 
 function isInternalEditorGo(go) {
@@ -1751,8 +1751,7 @@ function sourceIsComplete(raw) {
  * Marks `go` for editor pick / persist. Idempotent: existing Targets keep a
  * complete `payload.source`; missing identity is filled from `source`.
  *
- * Inserted by `@combos-fun/vite-plugin-development-target`. Game code should
- * not call this by hand.
+ * Host tooling inserts this. Game code should not call this by hand.
  */
 function attachDevelopmentTarget(go, source) {
     if (!go || go.destroyed || isInternalEditorGo(go) || isSceneLike(go)) {