@particle-academy/google-slides-js 0.2.0 → 0.3.1

package/CHANGELOG.md

@@ -8,6 +8,65 @@ The four packages share one version, because they are generated from one
 `provider/` definition and a version that meant something different in each
 would be a version nobody could reason about.
 
+## [0.3.1] — 2026-08-24
+
+### Fixed
+
+- **`@particle-academy/google-slides-js` now accepts a RANGE of `@particle-academy/google-slides-ui`, not one exact version.**
+
+It peer-depended on `@particle-academy/google-slides-ui` at exactly the release it shipped with. That is the
+strict form of the thing the kit's own rule forbids — a first-party sibling gets
+a range — and the same block applied the rule correctly to its other two
+dependencies. It was this one pair that slipped.
+
+What it cost: ship `@particle-academy/google-slides-ui` with a fixed help string and every consumer on the
+previous `@particle-academy/google-slides-js` had an **unmet peer**, which npm 7+ errors on. A documentation
+patch could not be delivered without a matching runtime release, and a routine
+`npm update` that moved the ui package alone broke the install.
+
+The coupling is real and is not being loosened away. The ui package emits the
+config schema and the js package implements against it, so a ui that adds a
+field to a js that ignores it is silently wrong. But a PATCH is non-additive by
+definition and a MINOR is where a field can appear — so `>=0.3.1 <0.4.0` is the
+coupling that actually exists rather than the strictest one expressible.
+
+Nothing else changed. `particle-academy/google-slides-php` and `fancy-google-slides` are unaffected; neither has an
+equivalent edge.
+
+## [0.3.0] — 2026-08-24
+
+### Added
+
+- **The README now says how to SET THIS CONNECTOR UP**, in the package itself.
+
+Until now it explained what the four packages are, what they cost and why the
+repo is generated — and said nothing about credentials, scopes, sandboxes or
+operations. Somebody who installed it could not learn from it which credentials
+a connection needs, where a human GETS them, which scopes to request, or what
+the connector can actually do. All of that was already in the definition; the
+one document a consumer reads was the one that omitted everything actionable.
+
+The new **Setting it up** section carries:
+
+- every credential, with the text saying where the value comes from, whether it
+  is **per installation** or **per connected account**, and whether it is secret;
+- the OAuth authorize and token URLs and the exact scopes, verbatim;
+- the access-token lifetime, and where refresh tokens ROTATE, the two things a
+  host must not do — retry a failed refresh, or refresh concurrently — because a
+  replay revokes the entire grant and nothing in the failure says why;
+- the estate in this provider's own terms, including the cases where a
+  successful-looking run reaches nobody, or reaches the real one;
+- every action and trigger with its method, path, inputs, and whether it is safe
+  to replay;
+- a trigger's provider-side setup, which nobody can derive from anything else.
+
+It is **generated from `provider/manifest.json`**, so it cannot drift from what
+the packages do — which is the point at a few hundred providers, where a
+hand-written setup section is a few hundred documents going quietly stale.
+
+No code changed. This release exists because a registry and an installing agent
+read the PUBLISHED artifact, and the artifact carried the old README.
+
 ## [0.2.0] — 2026-08-24
 
 ### Changed
@@ -59,3 +118,5 @@ can create a second presentation and the action is honestly
 
 [0.1.0]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.1.0
 [0.2.0]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.2.0
+[0.3.0]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.3.0
+[0.3.1]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.3.1

package/README.md

@@ -27,6 +27,54 @@ dependencies.
 subject to the kit's full approval bar, and one per provider is hundreds of
 dependencies nobody is tracking.
 
+## Setting it up
+
+Everything below is generated from `provider/manifest.json`, so it cannot disagree with what the packages do.
+
+### Credentials
+
+A Google Slides connection holds 4 values.
+
+**Two kinds of value, and mixing them up matters.** A `provider` credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An `account` credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.
+
+| Field | Scope | Secret | Where it comes from |
+|---|---|---|---|
+| **OAuth client ID** | per installation | not secret | From Google Cloud Console -> APIs & Services -> Credentials. ONE value for the whole installation, not per connected account. |
+| **OAuth client secret** | per installation | **secret** | The client secret for the same OAuth app. One value for the whole installation. |
+| **Access token** | per connected account | **secret** | Per connected Google account, and it expires after ONE HOUR. The host refreshes it with the refresh token. |
+| **Refresh token** | per connected account | **secret** | Per connected Google account. Google issues one only when the consent request asks for offline access; without it the connection dies within the hour. |
+
+### Authorising
+
+Google Slides uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.
+
+- **Authorize URL** — https://accounts.google.com/o/oauth2/v2/auth
+- **Token URL** — https://oauth2.googleapis.com/token
+- **Scopes** — `https://www.googleapis.com/auth/presentations`
+- **Access token lifetime** — 3600 seconds (1 hours). A host that never refreshes works all afternoon and is broken by morning.
+
+The refresh tokens do **not** rotate: the same one is reusable, so a refresh may safely be retried and may run concurrently. Stated rather than assumed, because the opposite — a provider that spends the token and revokes the grant on a replay — looks identical until it happens.
+
+### The estate
+
+**Google Slides has no test estate, and somebody checked.** Everything this connector does is real. Use the faker to build against it.
+
+> Google has no sandbox for Slides. A test presentation is a real one in a real Drive, so every create is real -- use the faker while developing and clean up any live test presentations.
+
+## What it can do
+
+### Actions
+
+#### `presentation_create` — Google Slides presentation
+
+Create a blank Google Slides presentation.
+
+`POST /v1/presentations` · **unsafe to replay** — a retried durable run does it TWICE
+
+| Input | Required | What it is |
+|---|---|---|
+| `title` | yes | The title of the new blank presentation. |
+
 ## Run it before you have credentials
 
 Every operation ships a **faker**, whether or not Google Slides has a sandbox. Set a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@particle-academy/google-slides-js",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Google Slides for Node — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP on @particle-academy/fancy-connector-core; no vendor SDK.",
   "repository": {
     "type": "git",
@@ -52,7 +52,7 @@
   },
   "peerDependencies": {
     "@particle-academy/fancy-flow": ">=0.47.1 <2.0",
-    "@particle-academy/google-slides-ui": "0.2.0"
+    "@particle-academy/google-slides-ui": ">=0.3.0 <0.4.0"
   },
   "peerDependenciesMeta": {
     "@particle-academy/fancy-flow": {