@owlmeans/planning 0.1.18-rc.24 → 0.1.18-rc.25

package/README.md

@@ -9,7 +9,7 @@ the executor with `@owlmeans/server-planning` and reads remotely with `@owlmeans
 ## Installation
 
 ```sh
-bun add @owlmeans/planning@^0.1.18-rc.23 ajv ajv-formats
+bun add @owlmeans/planning@^0.1.18-rc.25 ajv ajv-formats
 ```
 
 ## Concepts

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/planning",
-  "version": "0.1.18-rc.24",
-  "generatedAt": "2026-10-09T13:40:06.950Z",
+  "version": "0.1.18-rc.25",
+  "generatedAt": "2026-10-09T17:24:50.733Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/planning/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/planning
 
 **Layer:** Cross-cutting domain
-**Install:** `"@owlmeans/planning": "^0.1.18-rc.24"` in `dependencies` (`ajv` and `ajv-formats` are peers)
+**Install:** `"@owlmeans/planning": "^0.1.18-rc.25"` in `dependencies` (`ajv` and `ajv-formats` are peers)
 
 The contracts of project planning: record shapes, schemas, refusals, the protocol tree, the pure
 fold and the models. No database, no fastify, no React. The executor, the plugin registry, the
@@ -76,8 +76,9 @@ forms generated code keeps writing are `server-planning` → Creating and readin
 - **`entityId` is the organization's stable record id** — never the wire `entitySlug`, never a body
   value. Every read is scoped by it; where a request's comes from is `server-planning` → Scope and
   security.
-- **Membership is `parent` + `parents`, never a relationship.** `parents` always contains `parent`
-  (first), so many-to-many membership needs no junction row. `within` queries `parents`.
+- **Card containment is `parent` + `parents`.** `parents` always contains `parent` (first), so
+  multiple direct parents need no junction row. `within` queries those direct parents. Team
+  membership and project-team assignment use canonical typed relationships instead.
 - **Specification is a workcard** (`kind: specification`) with `category`, `format`, `body`, `ref`,
   `revision`, `version`, `bodyChars`. The SLOT — category, format, `multiple`, `revisioned`,
   `keepRevisions`, a JSON body `schema` — is declared on the PARENT's type. One record per
@@ -85,8 +86,10 @@ forms generated code keeps writing are `server-planning` → Creating and readin
   same record, and earlier bodies come back from the transition log.
 - **`createdBy` is written once, from a create's draft, and never moves.** Named in `changes` or
   `unset` it is refused on every action (`planning:immutable:createdBy`), so an ownership check
-  (`card.createdBy === profileId`) can trust it. A card that changes hands keeps that in a field of
-  its own type (`fields.assignee`); who made each later write is the transition's `actor`.
+  (`card.createdBy === profileId`) can trust it. Responsibility uses the optional top-level
+  `assignee` planning ID; additional participant fields belong in the type's `fields` schema.
+  The optional `reporter` also references an assignee ID. Who made each later write is the
+  transition's `actor`.
 - **`seq` is the last folded transition, `head` the highest allocated.** `head > seq` means a write
   is in flight (`cardHelper.isPending`); optimistic concurrency (`expectSeq`) compares against the
   head.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/planning",
-  "version": "0.1.18-rc.24",
+  "version": "0.1.18-rc.25",
   "license": "MIT",
   "description": "Runtime-free project-planning contracts — the workcard super type, projects, specifications, typed relationships, status flows with three intrinsic states, the transition event and its pure fold, the schema registry, the models and the protocol tree.",
   "type": "module",