Scene refact3 to dev

.agent/current_task.md

@@ -1,30 +1,32 @@
-# Current Task: Entry/Exit Implementation & Camera Snapping
+# Current Task: 3D Spatial Audio & SoundManager Implementation
 
 ## Status: COMPLETED ✅
 
 ## What was done this session
 
-### 1. Game.ts Decomposition ✅
-- **InventoryManager** moved to `src/systems/`.
-- **GameSemanticAPI** extracted to `src/systems/`.
-- MONOLITH reduced from 80KB to 40KB.
+### 1. SoundManager Architecture ✅
+- Implemented `SoundManager.ts` using **Web Audio API**.
+- Support for **3D Spatial Audio** (HRTF panning), **Convolution Reverb**, and **Delay** effects.
+- Dynamic **Proximity EQ** (+6dB bass boost at 250Hz) and **Reverb Scaling**.
 
-### 2. Universal Exit/Entry Components ✅
-- Implemented `Exit` and `Entry` components working on ANY object type (Entities, Triggerboxes, Quads).
-- Supported **Same-Scene Teleportation** (empty `targetSceneId`).
-- Automated collision-based transitions in `ComponentSystem`.
-- Verified actor transfer and state persistence (NPCs & Player).
+### 2. 2.5D Spatial Logic ✅
+- Developed a physically grounded 2.5D sound model:
+    * `Parallax 1.1` = Head Level (Z=0).
+    * `Parallax 1.0` = Foreground (Z=-400).
+    * `Parallax 0.0` = Infinity (Z=-10000).
+    * `Parallax < 0` = Behind Listener (+Z).
+- Integrated **Camera Zoom** scaling: Z-depth is attenuated by `1/zoom`.
 
-### 3. Camera Snap ✅
-- Implemented `scene.snapCameraToPlayer()` for instant positioning after transition.
-- Fixed bug where camera would "stick" to old player reference after scene load.
+### 3. Engine Integration ✅
+- Synchronized `SoundManager` update loop in `Game.ts`.
+- Exposed complete Audio API through `ScriptAPI.ts` (`api.playSoundAttached`, `api.loadReverbIR`, etc.).
+- Created a demo script and scene for visual/auditory validation.
 
-### 4. Verification ✅
-- `npm run typecheck` passed.
-- `npm run test` passed: 18 files, 205 tests.
-- Restored storage/semantic runtime contracts after a partial API rewrite caused PUT/DROP and inventory regressions.
+### 4. Documentation & Memory ✅
+- Wrote comprehensive technical documentation in `SoundSys.md`.
+- Persisted architectural facts in `agent_memory`.
 
 ## Next Steps
-1. **Feature Development**: Resume gameplay features as per `GDD.md`.
-2. **Architecture Audit**: Review remaining "any" casts in `ComponentSystem.ts`.
-3. **Browser QA**: Optionally verify instant camera snap visually in the editor/runtime.
+1. **Performance Tuning**: Monitor `ConvolverNode` overhead in high-density scenes.
+2. **SFX Library**: Start populating the `/public/sounds/` directory with production assets.
+3. **Gameplay Mechanics**: Integrate sound triggers into common object prefabs (Doors, Switches).

.agent/rules/kairo.md

@@ -0,0 +1,41 @@
+---
+trigger: always_on
+---
+
+## Kairo TaskOps Skill
+
+Use Kairo CLI for task tracking and status reconciliation in the Scanline Engine project.
+
+### Core Workflow
+
+1. **Check Context**: At the start of a session, run `kairo api list --proj quest` to understand the current backlog and active tasks.
+2. **Reconcile**: If the user's request matches an existing task, update its status to `doing` using `kairo api update --id <id> --status doing`.
+3. **Track Progress**: For tasks that span multiple turns, keep the description updated with key findings.
+4. **Wrap-up**: When a task is finished, mark it as `done` and store any durable knowledge (decisions, runbooks, incidents) in `agent_memory`.
+
+### CLI Command Reference
+
+- **List Project Tasks**:
+  `kairo api list --proj quest` (filters tasks carrying the `proj:quest` tag)
+- **Create New Task**:
+  `kairo api create --title "[Quest] <action phrase>" --description "Owner: <codex|user|gemini>\nContext: <details>\nExpected outcome: <outcome>" --tag "proj:quest" --tag "owner:codex" --tag "type:<bug|feature|chore|research>" --priority <0-3>`
+- **Update Task Status**:
+  `kairo api update --id <id> --status <todo|doing|done|blocked>`
+- **Mark as Done**:
+  `kairo api update --id <id> --status done`
+
+### Standard Tagging Taxonomy
+
+- `proj:quest`: Mandatory for all project-related tasks.
+- `owner:<codex|gemini|antigravity|user>`: Who is responsible for the task.
+- `type:<bug|feature|research|docs|chore|test|decision|review|followup>`: Category of work.
+- `area:<parser|scene|systems|ui|core|infra|movement|pathfinding|gdd|llm>`: Specific subsystem.
+- `source:<chat|review|test|notebooklm|memory|gdd|user>`: Where the task originated.
+- `status-meta:<blocked|needs-user|needs-acceptance|waiting|delegated>`: Additional status metadata.
+- `session:<YYYY-MM-DD>`: The session date when the task was created or updated.
+
+### Integration with agent_memory
+
+- Kairo is for **tasks** (the "what" and "status").
+- `agent_memory` is for **durable knowledge** (the "how", "why", and "what was learned").
+- Always cross-reference: mention the Kairo task ID in memory entries and commit messages when relevant.

.agent/rules/wrap-up.md

@@ -0,0 +1,24 @@
+---
+trigger: always_on
+---
+
+## Wrap-up Protocol
+
+When the user requests a `wrap-up` or `wrap-up-session`:
+
+1.  **Summarize the Session**: Create a comprehensive summary of the current session, including:
+    -   **Session Goal**: What was the primary objective?
+    -   **What Was Implemented**: Detailed list of features, fixes, and changes.
+    -   **Architecture/Runtime Decisions**: Any key decisions made and their rationale.
+    -   **Parser/Mechanics/Scene Changes**: Specific updates to core subsystems.
+    -   **Tests Run**: Outcomes of `npm test`, `npx vitest`, or specific manual checks.
+    -   **Commits Created**: List hashes and messages of commits made during the session.
+    -   **Current State**: Summary of the project status at the end of the session.
+    -   **Remaining Work / Next Steps**: Actionable tasks for the next session.
+    -   **Risks / Caveats**: Any known issues, technical debt, or open questions.
+2.  **Update `Sessions.md`**: Append the summary to the end of `Sessions.md` in the project root, using the established `## Session Entry - YYYY-MM-DD HH:mm [Timezone]` format.
+3.  **Persist Knowledge**:
+    -   Store high-value, durable knowledge in `agent_memory` (facts, decisions, runbooks).
+    -   Update `.agent/context.md` and `.agent/current_task.md` to reflect the new state.
+4.  **Kairo Cleanup**: Close completed tasks in Kairo and create follow-up tasks for the `Remaining Work`.
+5.  **Final Report**: Provide the user with a brief confirmation that the wrap-up is complete and point them to the updated `Sessions.md`.