@particle-academy/monday-js 0.2.0 → 0.3.1

package/CHANGELOG.md

@@ -7,6 +7,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/monday-js` now accepts a RANGE of `@particle-academy/monday-ui`, not one exact version.**
+
+It peer-depended on `@particle-academy/monday-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/monday-ui` with a fixed help string and every consumer on the
+previous `@particle-academy/monday-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/monday-php` and `fancy-monday` 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
@@ -101,3 +160,5 @@ is better than implying a guarantee the API cannot give.
 
 [0.1.0]: https://github.com/Fancy-Friends/monday/releases/tag/v0.1.0
 [0.2.0]: https://github.com/Fancy-Friends/monday/releases/tag/v0.2.0
+[0.3.0]: https://github.com/Fancy-Friends/monday/releases/tag/v0.3.0
+[0.3.1]: https://github.com/Fancy-Friends/monday/releases/tag/v0.3.1

package/README.md

@@ -27,6 +27,43 @@ 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 monday.com connection holds 1 value.
+
+Every value here is `account` scope: one per connected account, not one per installation.
+
+| Field | Scope | Secret | Where it comes from |
+|---|---|---|---|
+| **API token** | per connected account | **secret** | From monday.com: your avatar -> Developers -> My Access Tokens. It carries YOUR permissions and every board you can see, so a personal token grants an automation everything you have. |
+
+### The estate
+
+**monday.com has no test estate, and somebody checked.** Everything this connector does is real. Use the faker to build against it.
+
+> monday has no test estate. A developer plan is a real account with real boards, so anything an action creates is created for real. The faker is the only safe way to develop against this connector, which is why every action ships with one.
+
+## What it can do
+
+### Actions
+
+#### `item_create` — monday.com item
+
+Create an item on a monday.com board.
+
+`POST /v2` · **unsafe to replay** — a retried durable run does it TWICE
+
+| Input | Required | What it is |
+|---|---|---|
+| `boardId` | yes | The numeric id in the board URL: monday.com/boards/1234567890. |
+| `itemName` | yes | What the item is called on the board. |
+| `groupId` | no | Which group on the board to create it in. Left empty, monday uses the board's default group. |
+| `columnValues` | no | Column id to value, e.g. status -> Done. Which values a column accepts depends on its type. |
+
 ## Run it before you have credentials
 
 Every operation ships a **faker**, whether or not monday.com has a sandbox. Set a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@particle-academy/monday-js",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "monday.com 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/monday-ui": "0.2.0"
+    "@particle-academy/monday-ui": ">=0.3.0 <0.4.0"
   },
   "peerDependenciesMeta": {
     "@particle-academy/fancy-flow": {