product-wiki growth (2026-07-26): recurrence question answered; superseded repo references corrected

product-wiki/Competitors/README.md

@@ -43,17 +43,97 @@ extension).
   right-click-selection or scheduling tools, not per-site structured extractors.
   No JSON-LD/microdata-aware competitor surfaced on Firefox/Edge either, so the
   structured-extraction niche is open cross-browser too, not just on Chrome.
+- **The structured-extraction lane was occupied once, at microformat scale, and
+  then vacated (checked 2026-07-26).** This sharpens the standing "still none
+  found" answer into something more useful than absence. The closest thing that
+  ever shipped was the **"Google Calendar" Chrome extension** — a hackathon
+  project *"encouraged by the Chrome and Calendar teams at Google"*, since
+  open-sourced and archived — which detected events on the page you were reading
+  via the **`hCalendar` microformat and derivative microformats** and offered a
+  one-click add. It is now **shut down**: the repo states *"This Chrome extension
+  is no longer available to install, though the source code is available here to
+  fork & modify"*, and the author's shutdown note cites request load from Google
+  teams outweighing his available time, not lack of demand — the extension had
+  **5MM+ users** at shutdown. The generic **"Microformats"** extension (exported
+  `hCalendar` → iCalendar / add to Google Calendar) is likewise reported delisted
+  and unmaintained since ~2014. Two readings, both worth carrying: the lane is
+  genuinely empty *today*, and its last occupant died of maintenance cost at
+  scale — the exact cost a rule-based per-site extractor set also accrues.
+- **Structured-data awareness and calendar creation are disjoint categories in
+  today's extension ecosystem.** JSON-LD-aware extensions are easy to find and
+  effectively commoditised — **JSON-LD Schema Extractor** (Chrome *and* Firefox),
+  **LD+JSON Extractor**, **JSON-LD Checker**, **SEO Schema Visualizer** — but every
+  one is an SEO/developer *inspection* tool: extract, pretty-print, validate, or
+  graph a page's structured data against schema.org. None turns an `Event` block
+  into a calendar entry. So the answer to "is anyone doing per-site structured
+  extraction?" is not that the capability is hard or rare — it is that nobody has
+  wired the commodity parsing side to the calendar side. That junction is
+  precisely this project's lane. (Caveat, same as the Safari findings: the store
+  listings themselves return HTTP 403 to this worker's fetcher, so these rest on
+  search-surfaced listing descriptions; the two GitHub sources below were read
+  end to end.)
+- **Safari, checked 2026-07-26, does not differ — and if anything leans further
+  from structured extraction.** Three layers, none of them a per-site markup
+  reader: (1) *browser extensions* — Smart Calendars AI is the one genuine
+  event-capture extension spanning Chrome and Safari, and its own description
+  puts it on **text and image recognition** plus select-text-on-a-page capture,
+  never schema.org/JSON-LD; Calendly ships a Safari extension through the Mac App
+  Store, but it is a scheduling-link tool, not an extractor. (2) *Standalone App
+  Store apps taking the image route* — EventShot (Image To Calendar) and
+  Screenshots to Calendar both turn a **screenshot** into an event (title, date,
+  time, location; the latter also claims recurring-event and
+  multiple-events-per-image detection). (3) *Apple's own OS-level path* is **Data
+  Detectors**, which recognises dates in text and offers to create a Calendar
+  event — but Apple documents it for Mac document apps (Mail, TextEdit, Preview),
+  not as a Safari webpage-markup feature. So the structured-extraction niche is
+  open on Safari too, and the Safari-native centre of gravity is OCR/text
+  detection — the opposite end of the ladder from JSON-LD.
+- **Screenshot/OCR capture is emerging as a distinct input axis.** Eventy already
+  advertised flyer/poster/screenshot input; the Safari scan turned up two more
+  image-first tools. This project has no answer to it by design — it reads the
+  page's markup, and a screenshot has none — but the two approaches fail on
+  opposite inputs, so this is a positioning question rather than a feature gap.
 
 ## Open questions (for the next growth pass)
 
 - Pull actual review counts / install counts where the Chrome Web Store exposes
-  them, to gauge relative traction, not just star ratings.
-- Is there a competitor doing per-site *structured* extraction (JSON-LD/microdata
-  aware) rather than generic AI-on-raw-text? Still none found — now checked across
-  Chrome, Firefox, and Edge (see the cross-browser note above). Worth periodic
-  re-checks, since that's closest to this project's approach.
-- Safari-native tools weren't reachable in this pass (no store scan) — a later
-  cycle should confirm whether the Safari picture differs from Chrome/Firefox.
+  them, to gauge relative traction, not just star ratings. **Attempted
+  2026-07-26 and blocked, not answered:** both `chromewebstore.google.com`
+  listing pages and the third-party `chrome-stats.com` mirror return HTTP 403 to
+  the growth worker's fetcher, and web search surfaces the star ratings but not
+  install counts. This needs a different data route (a human spot-check, or a
+  source that publishes the numbers as text) — re-attempting the same two hosts
+  will just burn the next pass's budget.
+- ~~Is there a competitor doing per-site *structured* extraction (JSON-LD/microdata
+  aware) rather than generic AI-on-raw-text?~~ **Answered 2026-07-26**, in two
+  parts, having been checked across Chrome, Firefox, Edge, **and Safari**: none
+  live today, and the reason is sharper than absence — the capability is
+  commoditised on the SEO/inspection side and simply unwired from any calendar,
+  while the one microformat-aware calendar extension that did ship is shut down
+  (see the two notes under Positioning takeaways). Still worth a periodic
+  re-check, but not open in its old form.
+- **Why did the incumbent vacate, and does that predict our cost curve?** The
+  "Google Calendar" extension shut down over maintenance load at 5MM+ users, not
+  demand. Worth understanding whether that load came from the per-site/microformat
+  reader itself — a direct warning for this project's per-site extractor set — or
+  from its calendar-preview/OAuth surface, which this project deliberately lacks.
+  Surfaced 2026-07-26.
+- **Would a JSON-LD-era equivalent be re-tried by a platform player?** The prior
+  attempt predates JSON-LD's dominance (~41% of pages vs microformats' sub-1% —
+  see [`../Domain/`](../Domain/README.md)). If the lane is empty mainly for
+  historical reasons, platform re-entry is a live competitive risk to track.
+  Surfaced 2026-07-26.
+- ~~Safari-native tools weren't reachable in this pass (no store scan).~~
+  **Answered 2026-07-26** — see the Safari bullet under Positioning takeaways: the
+  picture does not differ, and skews to OCR/text detection. Evidence caveat: the
+  same 403 wall that blocked the install-count question also blocked direct
+  fetches of the App Store and vendor listings, so the Safari findings rest on
+  search-result summaries of those listings rather than the listings read end to
+  end. A pass with a working fetcher should confirm the two image-first apps.
+- Does the image/screenshot input axis (Eventy, EventShot, Screenshots to
+  Calendar) draw users this project would otherwise reach, or is it serving a
+  genuinely different moment — a photographed poster, not a page you're reading?
+  Surfaced 2026-07-26.
 
 ## Sources
 
@@ -66,6 +146,20 @@ extension).
 - [20 Best Google Calendar Extensions for Chrome (SavvyCal)](https://savvycal.com/articles/google-calendar-extension/)
 - [Create a Google Calendar Event — Firefox Browser Add-ons](https://addons.mozilla.org/en-US/firefox/addon/create-a-google-calendar-event/)
 - [Checker Plus for Google Calendar — Firefox Browser Add-ons](https://addons.mozilla.org/en-US/firefox/addon/checker-plus-for-calendar/)
+- [Calendly: Browser Extension — Mac App Store](https://apps.apple.com/us/app/calendly-browser-extension/id6746816242?mt=12) — the Safari extension is a scheduling-link tool, not an extractor
+- [How to install Calendly for Safari — Calendly Help](https://calendly.com/help/how-to-install-calendly-for-safari)
+- [EventShot — Image To Calendar (App Store)](https://apps.apple.com/us/app/-/id6747011235) — screenshot → event
+- [Screenshots to Calendar (App Store)](https://apps.apple.com/app/id6757425886) — screenshot → event, incl. recurring and multi-event images
+- [Detect dates, contacts, and more in documents on Mac — Apple Support](https://support.apple.com/guide/mac-help/detect-dates-contacts-documents-mac-mh35744/mac) — Data Detectors, Apple's OS-level date→Calendar path
+- [Safari Extensions — Apple Developer](https://developer.apple.com/safari/extensions/)
+- [chimbori/google-calendar-crx — the shut-down "Google Calendar" Chrome extension (archived; shutdown notice, "encouraged by the Chrome and Calendar teams at Google", 5MM+ users)](https://github.com/chimbori/google-calendar-crx)
+- [thanhpd/google-calendar-crx — fork documenting its hCalendar/hResume microformat event detection](https://github.com/thanhpd/google-calendar-crx)
+- [JSON-LD Schema Extractor — Chrome Web Store](https://chromewebstore.google.com/detail/json-ld-schema-extractor/njmjjilneheaknlfjidccmnceidcjnop)
+- [JSON-LD Schema Extractor — Firefox Browser Add-ons](https://addons.mozilla.org/en-US/firefox/addon/json-ld-schema-extractor/)
+- [LD+JSON Extractor — Chrome Web Store](https://chromewebstore.google.com/detail/ld+json-extractor/ndkafkinnogfnhllmidiflkgdcijgdnn)
+- [JSON-LD Checker — Chrome Web Store](https://chromewebstore.google.com/detail/json-ld-checker/jdddgiebgdijpopfapkocdnnbgkhddln)
+- [SEO Schema Visualizer — JSON-LD graph](https://www.shtros.com/seo-schema-visualizer/)
+- [Microformats — Chrome extension listing (chrome-stats)](https://chrome-stats.com/d/oalbifknmclbnmjlljdemhjjlkmppjjl)
 
 ## Growth log
 
@@ -76,3 +170,32 @@ extension).
   none per-site structured. No JSON-LD-aware rival on Firefox/Edge either.
   Resolved the cross-browser question; narrowed the structured-extraction one to
   "Safari still unchecked".
+- **2026-07-26** — attempted the install/review-count open question and recorded
+  the negative result rather than guessing: the Chrome Web Store and
+  chrome-stats.com both refuse the growth worker's fetcher (HTTP 403), so no
+  traction numbers were obtainable this pass. Noted in the open question so the
+  next run tries a different route. No competitor-landscape claims changed.
+- **2026-07-26 (same pass, second half)** — closed the "Safari still unchecked"
+  question, the one open question this page could still answer without the blocked
+  hosts. Safari has no per-site structured extractor either: Smart Calendars AI
+  (Chrome + Safari) is text/image recognition, Calendly's Safari extension is
+  scheduling-only, the App Store's event tools (EventShot, Screenshots to
+  Calendar) are screenshot-to-event apps rather than browser extensions, and
+  Apple's own date→Calendar path is Data Detectors, an OS text feature documented
+  for document apps rather than Safari page markup. Added the Safari and
+  screenshot/OCR bullets with six sources, recorded the same 403 evidence caveat,
+  and surfaced a follow-up on whether the image-input axis competes for the same
+  moment.
+- **2026-07-26 (third pass)** — answered the long-standing structured-extraction
+  question rather than re-recording "none found". Historically the lane *was*
+  occupied: the Google-encouraged "Google Calendar" Chrome extension read
+  `hCalendar`/derivative microformats off the page and one-click-added the event;
+  it is archived and no longer installable, shut down over maintenance load at
+  5MM+ users rather than lack of demand (the "Microformats" hCalendar→iCalendar
+  extension is likewise delisted). Today, JSON-LD awareness is commoditised but
+  disjoint from calendars — JSON-LD Schema Extractor (Chrome+Firefox), LD+JSON
+  Extractor, JSON-LD Checker and SEO Schema Visualizer are all SEO/dev inspection
+  tools, none of which creates an event. Retired the old question and opened two
+  sharper ones (why the incumbent vacated; whether a JSON-LD-era platform
+  re-entry is a risk). Same 403 caveat on the store listings; the two GitHub
+  sources were read end to end.