@niscorp/moss 0.9.0 → 0.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # @niscorp/moss
2
2
 
3
+ ## 0.9.1
4
+
5
+ ### Patch Changes
6
+
7
+ - efd5d03: The docs say what a boot does with the tables since `nisc migrate`: it checks them and refuses to start while a migration is pending, and applies them only under `migrations: 'apply'`. The sessions table, the boot order, a feature's sequences and how an old database adopts the ledger now read that way.
8
+
9
+ **What to change:** nothing. Documentation only.
10
+
3
11
  ## 0.9.0
4
12
 
5
13
  ### Minor Changes
package/DESIGN.md CHANGED
@@ -320,7 +320,7 @@ that made the table:
320
320
 
321
321
  | Table | Whose | Where its statements are written | What is somewhere else, and why |
322
322
  |---|---|---|---|
323
- | `sessions` | `identity` | `identity/sessions.ts`: five statements straight to the pool, before anybody is signed in | Its table is made in `data`'s one migration run, from a sequence `identity` declares |
323
+ | `sessions` | `identity` | `identity/sessions.ts`: five statements straight to the pool, before anybody is signed in | Its table is made in `data`'s one migration run (`migrateTables`, or boot under `migrations: 'apply'`; otherwise boot only checks it), from a sequence `identity` declares |
324
324
  | `moss_generation` | `data` | `data/own-entries.ts`: two entries, one that reads and one that moves | `artifactory` decides when it moves (`artifactory/generation.ts`), through a function `data` hands over |
325
325
  | `artifact_saves`, `artifacts` | `artifactory` | `artifactory/saves.ts`: three vex entries and the row rule they run under, replayed through a function `data` hands over (`Data.artifactEntries`) | The two tables are made by the core's sequence (`data/tables.ts`, `nisc.moss/5`). Their rows are somebody's, unlike the pointer's: the entries are replayed with the caller's scope, and vex keeps every read and write to the rows whose `principal` is the caller's `userId`. What is published for everybody is the rows of the principal `*`, replayed with that as the `userId` by the server's own code and by no caller. Moss updates and deletes no row, so a stored body is not rewritten when a grammar moves: it is brought to the current grammars where it is read |
326
326
  | `integrations`, `integration_actions` | the `integrations` feature | `integrations/entries.ts`: vex entries, replayed through the seam the feature is handed | The two tables are made by the core's own sequence (`data/tables.ts`, `nisc.moss`): that is the history every database has run, and it is not edited. The documents stored in `integration_actions` are brought to the current grammars by `data`, which holds the pool, when the feature asks through its seam |
package/DOCS.md CHANGED
@@ -921,9 +921,9 @@ the row.
921
921
  this is for signing out somebody else (an owner removes a member).
922
922
  No exported call deletes one token and leaves the principal's others.
923
923
  - Who a token is, is asked of the server: `server.principalOf(token)`. The
924
- table is made by `createServer`, and by `migrateTables`, under
925
- `session: 'sessions'` and only then. Nothing else is exported of the stored
926
- credential.
924
+ table is made by `migrateTables` (`nisc migrate`), and by `createServer`
925
+ under `migrations: 'apply'`, under `session: 'sessions'` and only then.
926
+ Nothing else is exported of the stored credential.
927
927
  - **They are for a deployment whose `session` is `'sessions'`, and for no
928
928
  other.** The stored sessions are what that verifier reads, and nothing else
929
929
  reads them.
@@ -1036,7 +1036,8 @@ parsing them, stores them stamped current, and refuses a bundle built on newer
1036
1036
  grammars than the host (*the host must be updated first*). Reads upgrade too:
1037
1037
  a row another process wrote since boot is read current, and one it cannot read
1038
1038
  is left out with a logged sentence. Migration 1 of each sequence is the DDL
1039
- boots used to run, so a database from before the ledger adopts on its next boot.
1039
+ boots used to run, so a database from before the ledger adopts on its next
1040
+ `nisc migrate`.
1040
1041
 
1041
1042
  `shellFrameDelta` and `socketCompression` are the two wire-size knobs. They are
1042
1043
  environment settings, not manifest ones — an operational decision about a
@@ -1076,7 +1077,8 @@ does nothing. Returns a Hono app extended with the `MossServer` members below.
1076
1077
  `createServer` wires, and answers no question of its own (`src/server/`). In
1077
1078
  order: the manifest is read and frozen; who a token is is resolved
1078
1079
  (`runtime.session`; unset, the boot is refused here, before a table exists);
1079
- the tables are migrated and the data module stands; the running manifest is
1080
+ the tables are checked (migrated under `migrations: 'apply'`) and the data
1081
+ module stands; the running manifest is
1080
1082
  created, which is the boot check, and the data module is told to ask it for an
1081
1083
  entry (it compiles the ones it holds, and one vex cannot run refuses the boot);
1082
1084
  identity; the server's own routes (the
@@ -1785,8 +1787,9 @@ app share a name. What a feature routes, keeps and serves is documented under
1785
1787
  its entry point.
1786
1788
 
1787
1789
  A feature names the tables that are its own and the strata sequences that make
1788
- them. The sequences are migrated in the one ledgered run, before the feature
1789
- starts, and `migrateTables` runs them too. A feature reads and writes those
1790
+ them. The sequences are checked in the one ledgered run, before the feature
1791
+ starts (migrated there under `migrations: 'apply'`), and `migrateTables`
1792
+ applies them. A feature reads and writes those
1790
1793
  tables through vex, as an app does, with entries of its own: they are seeded into a
1791
1794
  cache of their own, held by an engine no route is handed, so `/api/vex`
1792
1795
  answers `cache_miss` for one of them whatever the charter grants whoever asks,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@niscorp/moss",
3
- "version": "0.9.0",
3
+ "version": "0.9.1",
4
4
  "description": "moss — the nisc app server: serves existence (catalog, scoped vex, the socket), derived from artifacts",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -212,12 +212,12 @@
212
212
  "zod": "^4.2.0",
213
213
  "vue": "^3.5.0",
214
214
  "vite": ">=6",
215
- "@niscorp/nova": "^0.5.1",
216
- "@niscorp/prism": "^0.3.2",
217
- "@niscorp/charter": "^0.1.4",
218
- "@niscorp/strata": "^0.1.8",
219
- "@niscorp/tide": "^0.1.9",
220
- "@niscorp/vex": "^0.4.3"
215
+ "@niscorp/nova": "^0.5.2",
216
+ "@niscorp/prism": "^0.3.3",
217
+ "@niscorp/charter": "^0.1.5",
218
+ "@niscorp/tide": "^0.1.10",
219
+ "@niscorp/strata": "^0.1.9",
220
+ "@niscorp/vex": "^0.4.4"
221
221
  },
222
222
  "peerDependenciesMeta": {
223
223
  "@niscorp/tide": {
@@ -255,12 +255,12 @@
255
255
  "vitest": "^4.1.2",
256
256
  "vue": "^3.5.43",
257
257
  "zod": "^4.6.5",
258
- "@niscorp/charter": "^0.1.4",
259
- "@niscorp/prism": "^0.3.2",
260
- "@niscorp/nova": "^0.5.1",
261
- "@niscorp/tide": "^0.1.9",
262
- "@niscorp/strata": "^0.1.8",
263
- "@niscorp/vex": "^0.4.3"
258
+ "@niscorp/charter": "^0.1.5",
259
+ "@niscorp/prism": "^0.3.3",
260
+ "@niscorp/tide": "^0.1.10",
261
+ "@niscorp/nova": "^0.5.2",
262
+ "@niscorp/strata": "^0.1.9",
263
+ "@niscorp/vex": "^0.4.4"
264
264
  },
265
265
  "scripts": {
266
266
  "build": "node -e \"fs.rmSync('dist',{recursive:true,force:true})\" && tsup",