OTB Cloud v1.1.0-alpha4.1: repair docs after alpha4.1 bump

PROJECT_STATE.md

@@ -1,85 +1,51 @@
 # PROJECT_STATE.md
 
 Project: OTB Cloud
-Version: v1.1.0-alpha4
+Version: v1.1.0-alpha4.1
 Updated: 2026-04-20
 Location: /opt/otb_cloud
 
 ## Current State
-OTB Cloud now has a working multi-profile, multi-GPU video processing pipeline integrated into the tenant storage platform.
+OTB Cloud is now operating as a live multi-profile, dual-GPU media processing/storage platform.
 
 ### Confirmed Working
-- Portal-branded OTB Cloud dashboard
-- Device creation and browsing
-- File-ID based workshop staging
-- Device-specific Video Workspace access from dashboard
-- Video Workshop page
-- Multi-profile processing selection:
+- Dashboard, device browser, and workshop flow
+- File-ID based workshop queueing
+- Multi-profile processing:
   - default
   - compress
   - hq
-- Manual rotation override option:
-  - auto/default behavior when unchecked
-  - selectable 90 / 180 / 270 override when enabled
-- Job queue API and job listing API
-- File-ID based source resolution
-- Output routing to:
+- Manual rotation override
+- Processed outputs written to:
   - devices/<device>/video/
-- Profile-specific output filenames
 - Completed job actions:
   - View
   - Send to LTS
   - Download Output
   - Delete
-- Failed job delete action
-- LTS routing by file type:
+- Failed job delete
+- LTS routing for:
   - lts/video
   - lts/archived
   - lts/pictures
-- Health page
-- Lifetime processing metrics retained after visible job deletion
-- Intel + AMD GPU processing both in service
-- GPU time accounting active in Health page
-- Global video jobs route exists in codebase
-- Processed video section exists in device browser flow
-
-### Processing / GPU Behavior
-Current live behavior:
-- both GPUs take jobs
-- AMD prioritizes heavier / HQ work first
-- Intel handles lighter work
-- workers continue taking suitable jobs from the queue batch as available
-
-### Latest Proven Health State
-Health page currently shows stable cumulative values including:
-- uploaded file counts and space
-- LTS counts and space
-- archive counts and space
-- total jobs
-- completed jobs
-- failed jobs
-- cumulative GPU time that does not zero out when workshop cards are deleted
-
-### Current Storage Layout
-- originals remain in device originals tree
-- processed outputs go to:
-  - devices/<device>/video/
-- LTS destinations include:
-  - lts/video/
-  - lts/archived/
-  - lts/pictures/
-
-## Known Remaining Improvements
-- README is now being realigned to actual live state
-- Global video jobs page should be fully wired into UI navigation and polished
-- Dashboard template still contains some mixed button class styles that should be normalized
-- Health page can be expanded with per-processor breakdown later
-- Processing metrics can be refined further into Intel/AMD/CPU buckets if desired
-- Output browsing UX can still be improved further with richer previewing and filtering
-
-## Recommended Next Step
-Proceed after alpha4 with:
-1. global video jobs page polish and filters
-2. per-processor GPU metrics split (Intel / AMD / CPU)
-3. scheduler documentation and/or scheduler UI visibility
-4. processed output browsing improvements in device view
+- Health page with cumulative GPU time that remains after visible job deletion
+- Queue summary visible in workshop:
+  - queued jobs
+  - active users
+- Global video jobs functionality present
+- Intel + AMD worker threads active in production use
+
+### Current Observed GPU Behavior
+- Both intel and amd workers are active
+- Both GPUs are successfully processing jobs
+- AMD and Intel are both taking work from the queue in live operation
+- Current observed job records still show batch_id as NULL on recent jobs, so full batch-aware fairness logic should be treated as not yet proven active
+
+### Notes on Fair Use / Scheduler
+- Fair-use scheduler direction is defined
+- Per-tenant one-GPU fairness under contention is still an active implementation/testing area
+- Current system is functional and stable enough to continue development while that is finalized
+
+### Recommended Next Step
+Proceed to Android app update:
+- allow app-side selection for images, videos, or both

README.md

@@ -1,5 +1,22 @@
 # OTB Cloud
 
+## v1.1.0-alpha4.1 - 2026-04-20
+
+- Synced README and PROJECT_STATE to current live code/runtime state
+- Confirmed dual-GPU worker operation with active intel + amd processing
+- Confirmed workshop queue summary is visible and health metrics remain cumulative after job deletion
+- Documented current state of fair-use scheduler work: planned/in-progress, not yet treated as fully proven batch-aware behavior
+- Prepared project to move next into Android app media-type selection work
+
+## v1.1.0-alpha4 - 2026-04-20 (Patch B)
+- Added batch_id-based workshop submissions
+- Added tenant/account-level fair-use scheduler foundation
+- Added worker batch affinity so a worker stays on its current batch until completion
+- Added one-GPU-per-tenant behavior when multiple tenants/accounts are active
+- Preserved full GPU access for a single active tenant/account
+- Enforced 5-original-file batch limit in workshop
+- Updated project docs to reflect live fair-use queue behavior
+
 ## v1.1.0-alpha4 - 2026-04-20
 
 - Promoted project state to alpha4 based on current live multi-GPU video pipeline

VERSION

@@ -1 +1 @@
-v1.1.0-alpha4
+v1.1.0-alpha4.1