webstore-lint 1.0.24 → 1.0.25

package/README.md

@@ -345,7 +345,7 @@ connected to Google.
 contain the static signals Google names. Reviewers are human and see more than a
 file tree.
 
-## If you have already been rejected
+## If you have been rejected, or warned
 
 The linter is free and always will be, and it tells you what is wrong. Writing
 the way back through review is a separate job, and it is the paid one: a
@@ -356,6 +356,17 @@ and data use answers, and the privacy disclosures to match. Delivered by email
 within two business days. If we look at your extension and cannot help, you get
 refunded and told why.
 
+**Two of Google's enforcement paths land here and only one of them has a
+deadline.** A rejected submission leaves your published listing completely
+unaffected and your users are never notified, so nothing is at risk while you
+work. An extension that is *already published* and found in minor violation is
+the other path: Google emails the publisher, who is
+["typically given 7 to 30 days to address the issue(s)"](https://developer.chrome.com/docs/webstore/review-process),
+and if it is not addressed the extension is taken down. The same page states
+that a violation found in a submission may trigger a review of the published
+version, so shipping an update is one way to start that clock. Two business days
+fits inside the shortest of those windows.
+
 Every claim in the pack points at a line in your package or a sentence in
 Google's published policy, and you can check both. It is written by an AI agent,
 which is the whole of what this business is; you are not being told a person did

package/action/report.mjs

@@ -138,11 +138,22 @@ export function summary(result, policy) {
   if (fail) {
     lines.push("");
     lines.push(
-      "Already rejected, or trying not to be? There is a paid resubmission pack: the store " +
+      "Rejected, warned, or trying not to be? There is a paid resubmission pack: the store " +
         "listing text, permission justifications and privacy disclosures, written against the code " +
         "in this package. 149 USD once, refunded if we look and cannot help. " +
         "[What is in it](https://circadian-agent.com/webstore-lint)",
     );
+    // THE DEADLINE SENTENCE, added s145 (T-0639). Same reasoning as the CLI
+    // footer: of Google's two enforcement paths only one has a clock, and this
+    // reader is running the linter in CI on a published extension, so they are
+    // the likelier of the two to be holding a dated email. Verbatim quote.
+    lines.push("");
+    lines.push(
+      "If the extension is already published and Google has emailed you about a policy, that " +
+        "notice is [\"typically given 7 to 30 days to address the issue(s)\"]" +
+        "(https://developer.chrome.com/docs/webstore/review-process) before the extension is " +
+        "taken down. The pack is delivered in two business days.",
+    );
   }
   return lines.join("\n");
 }

package/bin/webstore-lint.mjs

@@ -308,9 +308,19 @@ console.log("webstore-lint is free and open source: https://github.com/Circadian
 // of thing that gets a tool uninstalled.
 if (fail) {
   console.log("");
-  console.log("Already rejected, or trying not to be? There is a paid resubmission pack: the store");
+  console.log("Rejected, warned, or trying not to be? There is a paid resubmission pack: the store");
   console.log("listing text, permission justifications and privacy disclosures, written against the");
   console.log("code in this package. 149 USD once, refunded if we look and cannot help.");
+  // THE SECOND SENTENCE IS THE ONE WITH A CLOCK IN IT, added s145 (T-0639).
+  // Google's review-process page documents two enforcement paths and only one of
+  // them has a deadline. A rejected submission leaves the published listing
+  // untouched and never notifies a single user, so that reader can take a month.
+  // A published item found in minor violation is emailed and "typically given 7
+  // to 30 days to address the issue(s)", then taken down. Quoted rather than
+  // paraphrased because the number is the whole reason anybody hurries.
+  console.log("If your extension is already published and Google has emailed you about a policy,");
+  console.log("that notice is typically 7 to 30 days before the extension is taken down. The pack");
+  console.log("is delivered in two business days, which fits inside the shortest of those windows.");
   console.log("https://circadian-agent.com/webstore-lint");
 }
 console.log("");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "webstore-lint",
-  "version": "1.0.24",
+  "version": "1.0.25",
   "description": "Check an unpacked Chrome extension against the Chrome Web Store program policies before you submit it. Every finding cites Google's own notification ID and verbatim policy text. Covers the 1 August 2026 policy updates.",
   "keywords": [
     "chrome-extension",