fix(w3c/headers): don't require crEnd for CRD status (#5126)

Author: marcoscaceres

src/w3c/headers.js

@@ -554,7 +554,7 @@ export async function run(conf) {
     showError(msg, name);
   }
 
-  if (conf.isCR && !conf.crEnd) {
+  if (conf.isCR && !conf.isCRDraft && !conf.crEnd) {
     const msg = docLink`${"[specStatus]"} is "CR", but no ${"[crEnd]"} is specified in the ${"[respecConfig]"}.`;
     showError(msg, name);
   }

tests/spec/w3c/headers-spec.js

@@ -194,6 +194,17 @@ describe("W3C — Headers", () => {
       expect(result2).toBeTruthy();
     });
 
+    it("does not require crEnd for CRD", async () => {
+      const ops = makeStandardOps({
+        specStatus: "CRD",
+        group: "webapps",
+      });
+      const doc = await makeRSDoc(ops);
+      const errors = headerErrors(doc);
+      const crEndError = errors.find(e => e.message.includes("crEnd"));
+      expect(crEndError).toBeUndefined();
+    });
+
     describe("specStatus - base", () => {
       it("doesn't add 'w3c' to header when status is base", async () => {
         const ops = makeStandardOps({