AutoDoc: here's what auto-generated PR docs would look like for `ts-chart-sdk`

AutoDoc ran on ts-chart-sdk — here's what it would generate

Hi! I'm Mike from Paprika Labs. We're running a paid pilot of AutoDoc — a GitHub Action that automatically generates PR documentation from diffs on every merge.

I noticed this repo no ADR directory, no CHANGELOG, 5/5 recent PRs have sparse descriptions — the kind of documentation gap AutoDoc fills automatically.

I ran AutoDoc on your last 3 merged PRs to show you what it produces:

---

PR #238: add isSpotterContext in app config

Merged 2026-05-08 · undefined files changed (+undefined -undefined)

PR Summary (auto-generated)
The PR #238 updated the version of @thoughtspot/ts-chart-sdk from 2.13.0 to 2.13.1 in both package-lock.json and package.json. Additionally, a new property isSpotterContext was added to the AppConfig interface in src/types/common.types.ts, indicating whether the chart is rendered in a Spotter Frame.

Architecture Note (auto-generated)
Minor change — no ADR needed.

---

PR #233: SCAL-306523 Add event for overlap alert

Merged 2026-04-28 · undefined files changed (+undefined -undefined)

PR Summary (auto-generated)
Added event for overlap alert with new banner alert functionality, including ShowGlobalAlertBanner and HideGlobalAlertBanner events, and corresponding payload types. Updated package versions to 2.13.0 in package-lock.json and package.json.

Architecture Note (auto-generated)
Minor change — no ADR needed.

---

PR #237: SCAL-308602 add support for viz point click, doubleclick and right cl…

Merged 2026-04-24 · undefined files changed (+undefined -undefined)

PR Summary (auto-generated)
Updated the @thoughtspot/ts-chart-sdk package to version 2.12.0, adding support for viz point click, double-click, and right-click events. This change enables the SDK to dispatch embed events to the ThoughtSpot embed host for these interactions.

Architecture Note (auto-generated)
Minor change — no ADR needed.

---

What AutoDoc does

AutoDoc installs as a GitHub Action. Every time a PR is merged, it reads the diff and generates:

• A structured PR summary (what changed and why)
• An Architecture Decision Record note (when there's a meaningful design decision)
• Changelog entries ready to copy into your CHANGELOG

Zero manual input. Zero context-switching. The docs are there by the time the merge lands.

Install: github.com/paprika-org/autodoc
Landing page: autodoc.paprika-labs.app

Does this look useful for ts-chart-sdk? Happy to answer questions or customise the output format for your team's conventions.

---

If this isn't relevant to your project, feel free to close the issue. Sorry for the noise.

The issue does not identify a repository file, test, or concrete change to make; it presents AutoDoc's generated output and installation links. First determine whether the maintainers want to adopt a GitHub Action for PR documentation, then define the required configuration and acceptance criteria before implementation.