feat: publish coverage-aware migration runtime

Author: prathamesh-git9

README.md

@@ -20,7 +20,7 @@ steps:
     with:
       fetch-depth: 0
       persist-credentials: false
-  - uses: prathamesh-git9/patchpilot-action@v0.14.0
+  - uses: prathamesh-git9/patchpilot-action@v0.17.0
     id: patchpilot
     with:
       spec: api/openapi.yaml
@@ -47,6 +47,8 @@ PatchPilot writes:
 - `migration.patch`, applicable with Git;
 - `migration-bundle.zip`, containing the report, patch, manifest, and migrated source tree.
 
+Missing `operationId` values and safe changes that cannot be tied to a supported source literal are emitted as coverage gaps, exposed through the `coverage_gaps` output, and counted as manual review. PatchPilot never treats an unlocated change as proof that the consumer is migrated.
+
 The Action never executes repository source. It performs parser-level syntax validation and removes temporary files after every run.
 
 ## Trust boundary

action.yml

@@ -69,6 +69,8 @@ outputs:
     description: Number of provider-authored safe contract changes.
   manual_changes:
     description: Number of contract changes requiring manual migration.
+  coverage_gaps:
+    description: Number of operations or safe changes PatchPilot could not map with supported evidence.
   patched_files:
     description: Number of files with generated patches.
   applied_files: