Fix: Add required protocol and capabilities fields to metadata-loader tests

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Author: Copilot

packages/spec/src/kernel/metadata-loader.test.ts

@@ -332,11 +332,19 @@ describe('MetadataLoaderProtocol', () => {
     it('should validate loader contract', () => {
       const contract = {
         name: 'filesystem',
+        protocol: 'file',
+        capabilities: {
+          read: true,
+          write: true,
+          watch: false,
+          list: true,
+        },
         supportedFormats: ['json', 'yaml', 'typescript'] as const,
       };
 
       const validated = MetadataLoaderContractSchema.parse(contract);
       expect(validated.name).toBe('filesystem');
+      expect(validated.protocol).toBe('file');
       expect(validated.supportsWatch).toBe(false); // default
       expect(validated.supportsWrite).toBe(true); // default
       expect(validated.supportsCache).toBe(true); // default
@@ -345,13 +353,21 @@ describe('MetadataLoaderProtocol', () => {
     it('should allow custom capabilities', () => {
       const contract = {
         name: 'http',
+        protocol: 'http',
+        capabilities: {
+          read: true,
+          write: false,
+          watch: false,
+          list: false,
+        },
         supportedFormats: ['json'] as const,
         supportsWatch: false,
         supportsWrite: false,
         supportsCache: true,
       };
 
       const validated = MetadataLoaderContractSchema.parse(contract);
+      expect(validated.protocol).toBe('http');
       expect(validated.supportsWrite).toBe(false);
       expect(validated.supportsCache).toBe(true);
     });