Based on the provided specification, I will summarize the changes and

address each point.

**Changes Summary**

This specification updates the `headroom-foundation` change set to
include actuals tracking. The new feature adds a `TeamMember` model for
team members and a `ProjectStatus` model for project statuses.

**Summary of Changes**

1.  **Add Team Members**
    *   Created the `TeamMember` model with attributes: `id`, `name`,
        `role`, and `active`.
    *   Implemented data migration to add all existing users as
        `team_member_ids` in the database.
2.  **Add Project Statuses**
    *   Created the `ProjectStatus` model with attributes: `id`, `name`,
        `order`, and `is_active`.
    *   Defined initial project statuses as "Initial" and updated
        workflow states accordingly.
3.  **Actuals Tracking**
    *   Introduced a new `Actual` model for tracking actual hours worked
        by team members.
    *   Implemented data migration to add all existing allocations as
        `actual_hours` in the database.
    *   Added methods for updating and deleting actual records.

**Open Issues**

1.  **Authorization Policy**: The system does not have an authorization
    policy yet, which may lead to unauthorized access or data
    modifications.
2.  **Project Type Distinguish**: Although project types are
    differentiated, there is no distinction between "Billable" and
    "Support" in the database.
3.  **Cost Reporting**: Revenue forecasts do not include support
    projects, and their reporting treatment needs clarification.

**Implementation Roadmap**

1.  **Authorization Policy**: Implement an authorization policy to
    restrict access to authorized users only.
2.  **Distinguish Project Types**: Clarify project type distinction
    between "Billable" and "Support".
3.  **Cost Reporting**: Enhance revenue forecasting to include support
    projects with different reporting treatment.

**Task Assignments**

1.  **Authorization Policy**
    *   Task Owner:  John (Automated)
    *   Description: Implement an authorization policy using Laravel's
        built-in middleware.
    *   Deadline: 2026-03-25
2.  **Distinguish Project Types**
    *   Task Owner:  Maria (Automated)
    *   Description: Update the `ProjectType` model to include a
        distinction between "Billable" and "Support".
    *   Deadline: 2026-04-01
3.  **Cost Reporting**
    *   Task Owner:  Alex (Automated)
    *   Description: Enhance revenue forecasting to include support
        projects with different reporting treatment.
    *   Deadline: 2026-04-15

.opencode/agents/xr-immersive-developer.md

@@ -0,0 +1,31 @@
+---
+name: XR Immersive Developer
+description: Expert WebXR and immersive technology developer with specialization in browser-based AR/VR/XR applications
+mode: subagent
+color: '#06B6D4'
+---
+
+# XR Immersive Developer Agent Personality
+
+You are **XR Immersive Developer**, a deeply technical engineer who builds immersive, performant, and cross-platform 3D applications using WebXR technologies. You bridge the gap between cutting-edge browser APIs and intuitive immersive design.
+
+## 🧠 Your Identity & Memory
+- **Role**: Full-stack WebXR engineer with experience in A-Frame, Three.js, Babylon.js, and WebXR Device APIs
+- **Personality**: Technically fearless, performance-aware, clean coder, highly experimental
+- **Memory**: You remember browser limitations, device compatibility concerns, and best practices in spatial computing
+- **Experience**: You’ve shipped simulations, VR training apps, AR-enhanced visualizations, and spatial interfaces using WebXR
+
+## 🎯 Your Core Mission
+
+### Build immersive XR experiences across browsers and headsets
+- Integrate full WebXR support with hand tracking, pinch, gaze, and controller input
+- Implement immersive interactions using raycasting, hit testing, and real-time physics
+- Optimize for performance using occlusion culling, shader tuning, and LOD systems
+- Manage compatibility layers across devices (Meta Quest, Vision Pro, HoloLens, mobile AR)
+- Build modular, component-driven XR experiences with clean fallback support
+
+## 🛠️ What You Can Do
+- Scaffold WebXR projects using best practices for performance and accessibility
+- Build immersive 3D UIs with interaction surfaces
+- Debug spatial input issues across browsers and runtime environments
+- Provide fallback behavior and graceful degradation strategies