@niscorp/nisc 0.2.1 → 0.2.3

package/AGENTS.md

@@ -2,6 +2,8 @@
 
 > **Reading this from `node_modules/@niscorp/nisc/`?** It is the rulebook for the nisc version installed beside it, shipped with it. Where it names a path in the nisc repository, look here instead: `packages/<name>/README.md` and `DESIGN.md` are `node_modules/@niscorp/<name>/`; `/STYLE_GUIDE.md` is beside this file; the lab apps it holds up as examples (`apps/lab/atrium`, `mythos`, …) and `docs/` are at [github.com/moccadroid/niscorp](https://github.com/moccadroid/niscorp). An app made by `npm create nisc` points its own `AGENTS.md` here.
 
+> **Changing nisc itself — a package, not an app built on it?** The `@niscorp` packages are live on npm and may be in use by third parties. No change may break an app that works today, and a breaking change is never yours to decide: it is a last resort that needs the maintainer's explicit approval *before* it is written. Read `/STYLE_GUIDE.md`, "The packages are live", first.
+
 For agents generating or reviewing a nisc application. This file states the application-level rules, and it presumes no app that came before it — but it is not the whole specification. The **grammars** live in the package docs, and they are required reading, not background: a layout node, an `ActionDefinition`, a Prism config, a charter document and a Vex DSL are each defined in their own package's `README.md` and `DESIGN.md`. Read the doc for a package before authoring that package's artifact. This file governs how they compose into an application.
 
 ## The thesis

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # @niscorp/nisc
 
+## 0.2.3
+
+### Patch Changes
+
+- 80e1ee8: Documentation: the packages are live, and releases are compatible. `STYLE_GUIDE.md` gains "The packages are live" — a release does not break an app that works on the one before it; what should go is deprecated and stays; a breaking change is a last resort that needs the maintainer's approval before it is written — and `AGENTS.md` points every agent changing nisc itself to it. The status lines that said "pre-1.0, breaking changes expected" (nova), "API is pre-1.0 and moves" (moss) and "everything else may move" (tide) now say the same. moss's deprecated `installedIntegrations` is no longer described as scheduled for removal: it stays on the type. The style guide's Node floor is corrected to 22.12, what every package's `engines` already says. No code changes.
+- Updated dependencies [48da7db]
+- Updated dependencies [8a04243]
+- Updated dependencies [8a04243]
+- Updated dependencies [80e1ee8]
+  - @niscorp/moss@0.2.3
+  - @niscorp/cli@0.2.2
+  - @niscorp/nova@0.1.3
+  - @niscorp/tide@0.1.2
+
+## 0.2.2
+
+### Patch Changes
+
+- Updated dependencies [b67a125]
+- Updated dependencies [633d0d1]
+- Updated dependencies [45d6731]
+- Updated dependencies [633d0d1]
+- Updated dependencies [45d6731]
+- Updated dependencies [45d6731]
+- Updated dependencies [45d6731]
+  - @niscorp/charter@0.1.1
+  - @niscorp/cli@0.2.1
+  - @niscorp/cortex@0.1.1
+  - @niscorp/loom@0.1.1
+  - @niscorp/prism@0.1.2
+  - @niscorp/signal@0.1.1
+  - @niscorp/strata@0.1.1
+  - @niscorp/moss@0.2.2
+  - @niscorp/nova@0.1.2
+  - @niscorp/tide@0.1.1
+  - @niscorp/vex@0.1.1
+
 ## 0.2.1
 
 ### Patch Changes

package/README.md

@@ -14,8 +14,12 @@ was released with, so installing `@niscorp/nisc@0.4.0` installs the set that
 was tested as nisc 0.4.0. Import from the packages themselves
 (`@niscorp/nova`, `@niscorp/moss`, …).
 
-Its version moves whenever any member's does, and it breaks whenever any member
-breaks — `pnpm check:changesets` refuses a release plan that forgets.
+Its version moves whenever any member's does. The packages are live, and a
+release is compatible with the one before it: installing a newer
+`@niscorp/nisc` does not break an app that worked on the older one. A breaking
+release is a last resort that needs the maintainer's approval; if one ever
+ships in a member, this package breaks with it — `pnpm check:changesets`
+refuses a plan that is missing either the approval or this.
 
 ## The rulebook
 

package/STYLE_GUIDE.md

@@ -4,6 +4,22 @@ Rules for writing code in this codebase. Short, focused on what matters.
 
 ---
 
+## The packages are live
+
+The `@niscorp` packages are published on npm, and people we have never met may be building on them. That decides what a change may do.
+
+- **A release does not break an app that works on the release before it.** If an app would have to change anything to keep working — an import, a call, a type it relied on, a config field, an artifact, a command or a flag — the change is breaking.
+- **A breaking change is a failure of the design, not a kind of release.** Find the compatible shape first: add beside what is there, keep the old spelling working, make new behaviour something an app opts into. What should go is marked `@deprecated` and stays. A default may get better; where some setup would stop working under the new one, it gets a way to keep the old, and the changeset names that setup.
+- **Nobody breaks a package on their own judgment.** If you believe a break cannot be avoided: stop before writing it. Say so first — at the top of what you report, not in a summary of work done — with the compatible shapes you tried and why each one fails, and wait. It ships only with the maintainer's explicit approval, as the last resort.
+- **Not sure whether it breaks?** That is the same stop: say what would change for an app that exists today, and ask.
+- **Data never breaks; it migrates.** Tables and stored documents move through strata sequences (AGENTS.md 17–20).
+
+Mechanically: every package change carries a changeset, and its bump is `patch`. Below 1.0 a `minor` is the breaking bump, and `pnpm check:changesets` refuses one whose changeset does not carry its approval (`docs/releasing.md`).
+
+This binds the packages. An app is its own to change.
+
+---
+
 ## TypeScript Strictness
 
 - `strict: true` in tsconfig. Always.
@@ -226,5 +242,5 @@ export const createShell = (config: ShellConfig, bus: MessageBus, reg: Registry,
 ## Build
 
 - ESM source, dual ESM/CJS output via tsup.
-- Target ES2022, Node >= 18.18.
+- Target ES2022, Node >= 22.12 (what every package's `engines` says).
 - Minimal dependencies. Every dep must earn its place.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@niscorp/nisc",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "The nisc platform as one known-compatible set: every @niscorp package, each pinned to the exact version it was released with.",
   "license": "Apache-2.0",
   "repository": {
@@ -19,18 +19,18 @@
     "node": ">=22.12"
   },
   "dependencies": {
-    "@niscorp/charter": "0.1.0",
-    "@niscorp/cli": "0.2.0",
-    "@niscorp/loom": "0.1.0",
-    "@niscorp/moss": "0.2.1",
-    "@niscorp/cortex": "0.1.0",
-    "@niscorp/nova": "0.1.1",
-    "@niscorp/prism": "0.1.1",
+    "@niscorp/cli": "0.2.2",
+    "@niscorp/charter": "0.1.1",
+    "@niscorp/cortex": "0.1.1",
+    "@niscorp/moss": "0.2.3",
+    "@niscorp/loom": "0.1.1",
+    "@niscorp/nova": "0.1.3",
+    "@niscorp/prism": "0.1.2",
+    "@niscorp/signal": "0.1.1",
+    "@niscorp/strata": "0.1.1",
+    "@niscorp/vex": "0.1.1",
     "@niscorp/solid": "0.1.0",
-    "@niscorp/strata": "0.1.0",
-    "@niscorp/tide": "0.1.0",
-    "@niscorp/vex": "0.1.0",
-    "@niscorp/signal": "0.1.0"
+    "@niscorp/tide": "0.1.2"
   },
   "peerDependencies": {
     "zod": "^4.2.0"