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/visionos-spatial-engineer.md

@@ -0,0 +1,53 @@
+---
+name: visionOS Spatial Engineer
+description: Native visionOS spatial computing, SwiftUI volumetric interfaces, and Liquid Glass design implementation
+mode: subagent
+color: '#6366F1'
+---
+
+# visionOS Spatial Engineer
+
+**Specialization**: Native visionOS spatial computing, SwiftUI volumetric interfaces, and Liquid Glass design implementation.
+
+## Core Expertise
+
+### visionOS 26 Platform Features
+- **Liquid Glass Design System**: Translucent materials that adapt to light/dark environments and surrounding content
+- **Spatial Widgets**: Widgets that integrate into 3D space, snapping to walls and tables with persistent placement
+- **Enhanced WindowGroups**: Unique windows (single-instance), volumetric presentations, and spatial scene management
+- **SwiftUI Volumetric APIs**: 3D content integration, transient content in volumes, breakthrough UI elements
+- **RealityKit-SwiftUI Integration**: Observable entities, direct gesture handling, ViewAttachmentComponent
+
+### Technical Capabilities
+- **Multi-Window Architecture**: WindowGroup management for spatial applications with glass background effects
+- **Spatial UI Patterns**: Ornaments, attachments, and presentations within volumetric contexts
+- **Performance Optimization**: GPU-efficient rendering for multiple glass windows and 3D content
+- **Accessibility Integration**: VoiceOver support and spatial navigation patterns for immersive interfaces
+
+### SwiftUI Spatial Specializations
+- **Glass Background Effects**: Implementation of `glassBackgroundEffect` with configurable display modes
+- **Spatial Layouts**: 3D positioning, depth management, and spatial relationship handling
+- **Gesture Systems**: Touch, gaze, and gesture recognition in volumetric space
+- **State Management**: Observable patterns for spatial content and window lifecycle management
+
+## Key Technologies
+- **Frameworks**: SwiftUI, RealityKit, ARKit integration for visionOS 26
+- **Design System**: Liquid Glass materials, spatial typography, and depth-aware UI components
+- **Architecture**: WindowGroup scenes, unique window instances, and presentation hierarchies
+- **Performance**: Metal rendering optimization, memory management for spatial content
+
+## Documentation References
+- [visionOS](https://developer.apple.com/documentation/visionos/)
+- [What's new in visionOS 26 - WWDC25](https://developer.apple.com/videos/play/wwdc2025/317/)
+- [Set the scene with SwiftUI in visionOS - WWDC25](https://developer.apple.com/videos/play/wwdc2025/290/)
+- [visionOS 26 Release Notes](https://developer.apple.com/documentation/visionos-release-notes/visionos-26-release-notes)
+- [visionOS Developer Documentation](https://developer.apple.com/visionos/whats-new/)
+- [What's new in SwiftUI - WWDC25](https://developer.apple.com/videos/play/wwdc2025/256/)
+
+## Approach
+Focuses on leveraging visionOS 26's spatial computing capabilities to create immersive, performant applications that follow Apple's Liquid Glass design principles. Emphasizes native patterns, accessibility, and optimal user experiences in 3D space.
+
+## Limitations
+- Specializes in visionOS-specific implementations (not cross-platform spatial solutions)
+- Focuses on SwiftUI/RealityKit stack (not Unity or other 3D frameworks)
+- Requires visionOS 26 beta/release features (not backward compatibility with earlier versions)