chore(package): rename package to exojs

Author: Exoridus

README.md

@@ -2,14 +2,14 @@
 
 ExoJS is a TypeScript-first browser multimedia and rendering framework built around a clean `Application` entrypoint, a scene-driven runtime model, and explicit advanced backend surfaces when you need them.
 
-The normal user path is package-based ESM usage through `exo-js-core`.
+The normal user path is package-based ESM usage through `exojs`.
 Advanced backend-specific access lives under dedicated subpaths.
 
 ## Package Surface
 
-- Core package: `exo-js-core`
-- Advanced WebGL2 surface: `exo-js-core/webgl2`
-- Advanced WebGPU surface: `exo-js-core/webgpu`
+- Core package: `exojs`
+- Advanced WebGL2 surface: `exojs/webgl2`
+- Advanced WebGPU surface: `exojs/webgpu`
 
 ## Current Built-In Runtime Features
 
@@ -34,15 +34,15 @@ ExoJS now treats WebGPU as the preferred built-in backend when available, with a
 Normal users typically do not need to choose a backend explicitly:
 
 ```ts
-import { Application } from 'exo-js-core';
+import { Application } from 'exojs';
 
 const app = new Application();
 ```
 
 If you need to force a backend:
 
 ```ts
-import { Application } from 'exo-js-core';
+import { Application } from 'exojs';
 
 const webGpuApp = new Application({ backend: { type: 'webgpu' } });
 const webGlApp = new Application({ backend: { type: 'webgl2' } });
@@ -54,21 +54,21 @@ const autoApp = new Application({ backend: { type: 'auto' } });
 Install:
 
 ```bash
-npm install exo-js-core
+npm install exojs
 ```
 
 Minimal example:
 
 ```ts
-import { Application, Color, Graphics, Scene } from 'exo-js-core';
+import { Application, Color, Graphics, Scene } from 'exojs';
 
 class DemoScene extends Scene {
     private readonly graphics = new Graphics()
         .beginFill(Color.white)
         .drawRect(-64, -64, 128, 128)
         .endFill();
 
-    public override draw(renderBackend: import('exo-js-core').RenderBackend): void {
+    public override draw(renderBackend: import('exojs').RenderBackend): void {
         this.graphics.rotation += 0.01;
         this.graphics.render(renderBackend);
     }
@@ -113,13 +113,13 @@ Use advanced backend-specific APIs only when you actually need them.
 WebGL2 advanced surface:
 
 ```ts
-import { RenderManager, SpriteRenderer } from 'exo-js-core/webgl2';
+import { RenderManager, SpriteRenderer } from 'exojs/webgl2';
 ```
 
 WebGPU advanced surface:
 
 ```ts
-import { WebGpuRenderManager, type WebGpuRenderAccess } from 'exo-js-core/webgpu';
+import { WebGpuRenderManager, type WebGpuRenderAccess } from 'exojs/webgpu';
 ```
 
 These subpaths exist for custom renderers and backend-specific systems. They are not required for normal `Application`-centric usage.

docs/ai/repo-map.md

@@ -3,7 +3,7 @@
 Last updated: 2026-03-09 (Codex initialization pass)
 
 ## 1) Package and build surface
-- Package: `exo-js-core` (`package.json`)
+- Package: `exojs` (`package.json`)
 - Published files: `dist`, `README.md`
 - Main artifacts:
   - `main`: `dist/exo.js` (CJS)

docs/api/Application.md

@@ -29,7 +29,7 @@ new Application({ backend: { type: 'auto' } })
 ## Typical usage
 
 ```ts
-import { Application } from 'exo-js-core'
+import { Application } from 'exojs'
 
 const app = new Application()
 await app.start(scene)

docs/api/README.md

@@ -19,5 +19,5 @@ Use these pages as the source of truth for examples and application code:
 
 Advanced backend-specific access remains under the package subpaths:
 
-- `exo-js-core/webgl2`
-- `exo-js-core/webgpu`
+- `exojs/webgl2`
+- `exojs/webgpu`

docs/api/Renderer.md

@@ -29,5 +29,5 @@ Normal code should work through drawables and scenes:
 
 Backend-specific renderer/runtime work lives under:
 
-- `exo-js-core/webgl2`
-- `exo-js-core/webgpu`
+- `exojs/webgl2`
+- `exojs/webgpu`

package-lock.json

@@ -1,5 +1,5 @@
 {
-  "name": "exo-js-core",
+  "name": "exojs",
   "description": "A lightweight, flexibile and powerful multimedia framework.",
   "version": "1.1.0",
   "files": [