@nxgt/janus 0.2.1 → 0.2.2

package/docs/guide/adapters.md

@@ -299,3 +299,5 @@ Types: `ConformanceHarness`, `OpenedStores`, `StoreFaults`, `ConformanceCase`,
 - [Errors](errors.md) — `StoreFailure`, `StoreConflict` and the rule behind them
 - [Vocabulary](vocabulary.md) — ids, cursors and `invalidCursor`
 - `@nxgt/janus-mongo` — an adapter that passes both suites against a real mongod, outages included
+- `@nxgt/janus-drizzle` — both suites on PostgreSQL 17 and PGlite
+- `@nxgt/janus-redis` — the sessions and one-time tokens cases on Redis 7.4

package/docs/guide/vocabulary.md

@@ -78,7 +78,7 @@ either finds this row.
 | --- | --- | --- |
 | **store** | Where a side keeps its data, behind a port. The **identity stores** are `users`, `sessions` and `tokens`; the **relation store** holds the tuples | "database", "repository" |
 | **port** | The interface a store implements: `JanusStores` for the identity stores — named after the package, not the side — and `RelationStore` | "driver" |
-| **adapter** | A package implementing the ports for one database: `@nxgt/janus-mongo`. What its `create…Adapter(db)` answers is its stores, keyed as `janus()` takes them — `{ store, relations }` | "plugin", "connector" |
+| **adapter** | A package implementing the ports for one database: `@nxgt/janus-mongo`, `@nxgt/janus-drizzle`, `@nxgt/janus-redis`. What its `create…Adapter(db)` answers is its stores, keyed as `janus()` takes them — `{ store, relations }` | "plugin", "connector" |
 | **integration** | A package fitting Janus into one web framework or one observability library: `@nxgt/janus-hono`, `@nxgt/janus-telemetry`. It implements no port | "plugin", "adapter" |
 | **kit** | A package that opens the connections and wires adapters and integrations into one object for an application: `@nxgt/janus-kit`'s `connectKit` answers `{ auth, access, db, redis, ping, close }`. It implements no port, and `janus()` and `permissions()` are still written by the application | "framework", "starter" |
 

package/docs/roadmap.md

@@ -5,17 +5,7 @@ dates here, and the version something shipped in is the only number.
 
 ## Now
 
-- **A PostgreSQL adapter** — in a package of its own, `@nxgt/janus-drizzle`,
-  on Drizzle: both sides over one database, the tables in your own drizzle-kit
-  migrations. Built, not yet published.
-- **Tracing and an audit trail** — in a package of its own,
-  `@nxgt/janus-telemetry`: a span per flow and per permission check, and the
-  security events worth keeping, never a login, a password, a session token
-  or a one-time token. Built, not yet published.
-- **A Redis adapter for sessions and one-time tokens** — in a package of its
-  own, `@nxgt/janus-redis`: both are read on every request and ephemeral, so
-  they live in Redis, expired by Redis itself, while users stay in another
-  store. Built, not yet published.
+Nothing yet.
 
 ## Next
 
@@ -92,7 +82,19 @@ dates here, and the version something shipped in is the only number.
 
 ## Shipped
 
-The first public release, v0.1.
+Each entry names the version it came in.
+
+- **The adapters and the kit, each at its first release, v0.1.0, beside
+  `@nxgt/janus` 0.2.2** —
+  [`@nxgt/janus-drizzle`](https://www.npmjs.com/package/@nxgt/janus-drizzle),
+  both sides over one PostgreSQL database on Drizzle;
+  [`@nxgt/janus-redis`](https://www.npmjs.com/package/@nxgt/janus-redis),
+  sessions and one-time tokens in Redis, expired by Redis itself;
+  [`@nxgt/janus-telemetry`](https://www.npmjs.com/package/@nxgt/janus-telemetry),
+  a span per flow and per permission check, and the security events worth an
+  audit trail, never a login, a password, a session token or a one-time token;
+  and [`@nxgt/janus-kit`](https://www.npmjs.com/package/@nxgt/janus-kit), all
+  of it wired in one call.
 
 - **The model's keys read `related` and `permits`** — Keto's OPL words: an
   object type declares `related: { members: ['staff', 'team#members'] }` and
@@ -100,17 +102,17 @@ The first public release, v0.1.
   `relations` and `permissions` as keys are refused, by the compiler and by
   `defineModel`, with a message naming the new key —
   `types.team.relations is now related: rename the key`. The `permissions()`
-  function and `janus({ relations })` keep their names. — next minor
+  function and `janus({ relations })` keep their names. — v0.2.0
 - **`LOGIN_TAKEN` no longer quotes the login in its message**, in the memory
   store and in both adapters; `error.login` still names it, and the
-  conformance suite checks it. — next patch
+  conformance suite checks it. — v0.2.0
 - **The conformance suite accepts a store with its own expiry** — a store
   that drops a lapsed session at once, as a Redis TTL does, passes
-  `sessions.deleteUser`; one that still holds it must count it. — next patch
+  `sessions.deleteUser`; one that still holds it must count it. — v0.2.0
 - **A NUL character or a lone surrogate never reaches a store** — refused in
   fields with `USER_INVALID` on every adapter, rather than `STORE_FAILED` on
   PostgreSQL alone; a login holding one is nobody's. The conformance suite
-  holds every adapter to round-tripping every other character. — next patch
+  holds every adapter to round-tripping every other character. — v0.2.1
 
 - **A Hono integration** — [`@nxgt/janus-hono`](https://www.npmjs.com/package/@nxgt/janus-hono):
   the session middleware, the cookie, a route guarded by a permission,

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@nxgt/janus",
-	"version": "0.2.1",
+	"version": "0.2.2",
 	"description": "Embeddable, type-safe identities and permissions: bring your own database",
 	"license": "MIT",
 	"type": "module",