fix: treat missing labels support as a warning instead of a compatibility error

Author: allison-truhlar

src/validator.test.ts

@@ -297,17 +297,18 @@ describe('validateViewer', () => {
   });
 
   describe('labels support', () => {
-    it('returns error when data has labels but viewer does not support them', () => {
+    it('returns warning when data has labels but viewer does not support them', () => {
       const viewer = createViewer({ labels: false });
       const metadata = createMetadata({
         labels: ['nuclei', 'cells']
       });
 
       const result = validateViewer(viewer, metadata);
 
-      expect(result.compatible).toBe(false);
-      expect(result.errors).toHaveLength(1);
-      expect(result.errors[0].capability).toBe('labels');
+      expect(result.compatible).toBe(true);
+      expect(result.warnings).toContainEqual(
+        expect.objectContaining({ capability: 'labels' })
+      );
     });
 
     it('returns compatible when viewer supports labels', () => {

src/validator.ts

@@ -113,11 +113,9 @@ export function validateViewer(
 
   // Check for labels
   if (metadata.labels && metadata.labels.length > 0 && !viewer.capabilities.labels) {
-    errors.push({
+    warnings.push({
       capability: 'labels',
-      message: 'Dataset has labels but viewer does not support them',
-      required: true,
-      found: false
+      message: 'Dataset has labels but viewer may not display them'
     });
   }