chore: follow up review protocol and build compatibility

Author: vicary

docs/ReviewProtocol.md

@@ -51,6 +51,9 @@ request and review feedback needs to be handled systematically.
    - If all reviews under a higher-level comment/review wrapper are handled,
      hide that umbrella comment with reason `resolved` when GitHub permissions
      and tooling allow it.
+   - If replies were added through a pending personal review, explicitly submit
+     that review so the comments are visible to reviewers and no replies remain
+     stuck in `PENDING` state.
 
 6. Re-check live review state.
    - Query GitHub again.
@@ -64,6 +67,8 @@ request and review feedback needs to be handled systematically.
 
 8. Request a fresh review.
    - Request a new Copilot review on the PR after the fixes are pushed.
+   - If GitHub rejects the request because you still have a pending review,
+     submit the pending review first, then retry the fresh-review request.
 
 9. Report status.
    - Include:

src/config.ts

@@ -35,9 +35,17 @@ export class ConfigLoadError extends Error {
     message: string,
     options: { cause?: unknown; code: ConfigLoadErrorCode },
   ) {
-    super(message, { cause: options.cause });
+    super(message);
     this.name = "ConfigLoadError";
     this.code = options.code;
+    if (options.cause !== undefined) {
+      Object.defineProperty(this, "cause", {
+        value: options.cause,
+        writable: true,
+        configurable: true,
+        enumerable: false,
+      });
+    }
   }
 }