Gemmein

Returns what changed in each Gemmein release newer than `since` (a Gemmein version, e.g. "0.22.1"), or the last three when `since` is left out: each change as was → now, with the error codes it added or removed. Useful when knowledge of Gemmein may be older than the installed release (training data, or a guide read weeks ago). The feed is bundled with this server, offline; every release in full is at https://docs.gemmein.com/changes.txt. Where the feed and older knowledge differ, the feed is current.

Runs the reaffirm boundary checks live against the caller's own app; returns structured pass/fail (structuredContent: checks, notes, failedCount, passed). Useful once the app is wired to Gemmein, when confirming it is done, and before go-live. Tier A (public pk_ key only): the collection name is valid, anonymous reads and writes of a private collection are refused, an optional public collection reads as its rule intends — safe against any environment, live included. Tier B (with the sk_dev secret key): proves one user cannot read another's private records, using two throwaway test sessions in the dev environment. sk_live is refused by design — a live secret is never needed here; dev and live enforce the same rules, so isolation proven in dev holds in live. Tier A writes nothing while the boundaries hold — but if a private collection is open to strangers, its anonymous test write succeeds and the record stays, in whatever environment the key names (live included), and the check fails, naming the collection. Tier B writes only in the caller's dev environment: it signs in two test people (created on first use and kept; any earlier sessions of theirs are signed out), creates one probe record as the first and deletes it at the end of the check. Signing a person in signs them out of their earlier sessions, so testUsers suits throwaway addresses: real development people named there are signed out. A failed check means the app's assumptions drifted from its rules.

Explains a GemmeinError code (err.code: conflict, forbidden, unknown_collection, invalid_shape, html_not_allowed, …): what the code means and the exact next step — including whether the refusal is final (a forbidden repeats on retry; the approach changes, not the request). Parsed from the installed API reference, so codes match the SDK version the app runs. With no code it lists every stable code.

Validates a relay definition — the contents of gemmein/relays/<name>.json — offline, before `gemmein sync` carries it to the cloud. A relay is one trigger (receiver: a provider's webhook; schedule: a clock; data_change: a record changing) and up to ten actions in Gemmein's own verbs (write_record, grant_access, revoke_access, grant_credits, email_person, call_url, fulfil_product, refund_product, grant_plan, revoke_plan) — Gemmein runs it: receives the event, maps the fields, authorises, carries out the action. Takes the definition JSON; returns the English sentence the dashboard shows ("When gocardless-paid receives an event where event_type is confirmed → grant Pro, email the person, call https://…") or the one refusal sentence the cloud would answer, naming the field and the fix. Offline and read-only: nothing is created. Two checks run only in the cloud and are stated in the answer (the API's own hosts; the address's resolved network at call time).

Explains one of the seven collection safety rules (private, shared, admin_write, public_read, community, addressed, direct): its exact access contract, what it is right for, and the mistakes that leak data. Useful when choosing a collection's rule, or when a rule refuses something at runtime. With no rule it returns the all-seven cheat-sheet plus the cross-cutting law, including what no rule supports (team/group/workspace scope, per-user visibility inside a rule) — an app that needs those shapes has a fit gap, and client-side filtering does not close it.

Returns the Gemmein build guide (llms.txt): the packaged contract — what code calls, matching the installed SDK. Useful before building an app on Gemmein, moving an existing app onto it, or deciding whether an app fits. The guide opens with two doors — starting from an idea with nothing built yet, or already holding an app — and both lead to the same fit assessment: the in-scope map, what Gemmein does not support, and the three possible outcomes (fits; fits except named gaps; doesn't fit). After that it is the full build contract: auth flow, the seven collection safety rules, record shapes, links/expand, uploads, contention patterns, payments (g.payments.products / g.subscriptions.plans to list what the app sells, which is not a collection; g.subscriptions.checkout / g.payments.buy), drafts, error philosophy, pricing, the keys (server · CLI · sync), `gemmein sync` and `sync --live`, go-live and promotion, relays, AI tools defined on the server and run with `g.ai.run`, and credits. The dashboard section (connecting Stripe, the dashboard's rooms, health checks) is appended live from docs.gemmein.com, because it changes with the dashboard; offline, a link to it takes its place. With `topic` ("refund a payment", "free trial") it returns only the docs-site sections that answer it, each a direct markdown link with its anchor (https://docs.gemmein.com/<page>.md#<section>); with no topic the guide ends with every docs page's markdown link, one page per topic.

Returns reaffirm.mjs, the ready-to-edit harness that re-proves the app's boundaries against live Gemmein on every deploy (also shipped inside the @gemmein/sdk package): copied next to the app with its CONFIG block set, it runs in CI. Useful when wiring up the app's CI or handing over the finished app. check_integration runs the same checks once, with no file to install.

Returns the @gemmein/sdk API reference (REFERENCE.md): every method, exact signature, return shape, and the stable error-code table. Useful while writing code against the SDK. With `topic` (a module or method: "g.collection", "checkout") it returns only the matching sections — the packaged text plus each section's direct link, https://docs.gemmein.com/reference.md#<section>. `guide` covers how the model works and whether an app fits; `search_docs` finds one fact in either document.

Searches the Gemmein docs for one term or phrase ('keyed create', 'ifVersion', 'addressed', 'expand') without reading a whole document. Returns the docs site's matching sections first, best first — each a direct markdown link with its anchor (https://docs.gemmein.com/<page>.md#<section>) and its opening words, so one section is read, not a page — then the matching passages of the packaged guide and API reference with 3 lines of context either side, at most 6 match blocks per document. Offline: the section index ships with this server. Search finds what the docs say, not what Gemmein does not support; the fit assessment is in `guide`.

Checks a collection name against the naming law: lowercase letters, numbers, underscores; starts with a letter; 2-63 characters. Useful while planning collections, before any g.collection(name) call is written: a bad name throws from g.collection(name) before any network call — at module load that blanks the whole app with no console error. An invalid name comes back with a suggested fix.