@owlmeans/server-planning 0.1.18-rc.29 → 0.1.18-rc.30

package/README.md

@@ -2,7 +2,7 @@
 
 The server half of `@owlmeans/planning`: the planning service and its plugin registry, the
 transition executor every write goes through, the in-memory reference store, the commit hub and the
-protocol handlers. A backend appends the service once, binds the handlers to the shared protocol
+protocol handlers, versioned auxiliary resource commands and schema-governed hierarchy. A backend appends the service once, binds the handlers to the shared protocol
 tree, and reads and writes through a scoped facade. A browser or Node client uses
 `@owlmeans/client-planning` against the same tree; a durable store implements the ports and reuses
 the `@owlmeans/server-planning/store` subpath.
@@ -10,7 +10,7 @@ the `@owlmeans/server-planning/store` subpath.
 ## Installation
 
 ```sh
-bun add @owlmeans/server-planning@^0.1.18-rc.29 @owlmeans/planning@^0.1.18-rc.25 ajv
+bun add @owlmeans/server-planning@^0.1.18-rc.30 @owlmeans/planning@^0.1.18-rc.26 ajv
 ```
 
 ## Concepts
@@ -29,6 +29,8 @@ bun add @owlmeans/server-planning@^0.1.18-rc.29 @owlmeans/planning@^0.1.18-rc.25
   `after` chain exactly once and publishes a commit event.
 - **Store** — `makeMemoryPlanningStore()` for tests and single-process tools; a durable store in
   anything with more than one process.
+- **Resource facade** — `assignees`, `teams`, `comments` and `mentions` use native versioned ports.
+  Organization units serialize dependent writes, schema changes and derived relationships.
 
 ## Usage
 
@@ -40,6 +42,8 @@ import { makePlanningProtocols } from '@owlmeans/planning'
 export const planningProtocols = makePlanningProtocols({
   base: { alias: 'app:planning', path: '/planning' },
   guards: DEFAULT_GUARD,
+  resources: true,
+  definitions: true,
 })
 ```
 
@@ -100,6 +104,36 @@ appendPlanningService(testContext, { store: makeMemoryPlanningStore({ sync: fals
 const cards = await planningHandlerOf(ctx).planningFor(req, { channel: 'web' }).cards.list({ parent: projectId })
 ```
 
+## Native planning resources
+
+Register assignee type schemas through `schemas.assigneeTypes` or the facade's definitions.
+The scoped facade exposes versioned `assignees.create/update/retire`, `teams.create/update/remove`,
+`comments.create/update/remove` and derived `mentions` reads/rebuilds. Resource updates and
+removals require `{ version: record.version }`; they do not allocate card transitions.
+
+Supply a verified `assigneeId` in the trusted scope for comment authors. Hosts may also supply
+`defaultAssigneeId`; `@owlmeans/planning-auth` resolves verified authentication subjects and groups
+to planning ids and can attribute missing card reporters. Never accept author or organization
+claims from an untrusted resource request. Human authentication requirements come from assignee
+type schemas, while nicknames identify participants only within an organization entity.
+
+Use `teams.addMember/removeMember`, `teams.attach/detach`, `teams.members`, `teams.projects` and
+`teams.assignees`. They reuse the relationship store and preserve reusable organization teams.
+Schema reference fields maintain their canonical edges and named inverse views in the same
+organization unit. Explicit relationship writes cannot contradict a field-authoritative edge.
+
+`parent`, `parents` and derived `parentType` are the hierarchy. Schema parent/child rules validate
+creates and reparenting; recursive project scope is checked before paging, including comments,
+history, specifications and relationships. Project `mode` is access-policy metadata, separate
+from status. Deleting a card removes its comments and mention cache. Project purge follows
+current ancestry and retains unrelated organization assignees, reusable teams and reparented
+survivors, even when an older log or edge caches the deleted project id.
+
+Mount `resources: true` and `definitions: true` in the shared protocol tree, then bind stock
+`servePlanningEntrypoints`. Its access resolver authorizes resource commands and conceals records
+outside scope. Stock replies remove native `entityId` metadata from known record/envelope
+positions, while application fields, schema definitions and transition changes remain opaque.
+
 ## API
 
 - Service: `appendPlanningService`, `ensurePlanningService`, `makePlanningService`,
@@ -145,6 +179,7 @@ const cards = await planningHandlerOf(ctx).planningFor(req, { channel: 'web' }).
 
 - `after` hooks run where the transition is FOLDED, once per commit — register the same plugins in
   every folding process, and never run hooks from a commit-bus subscription.
+- Organization locks are released before `after` hooks, so a hook may write into the same scope.
 - The memory store is per-process heap: wrong for multiple processes or restarts.
 - `actor` comes from the scope; a wire `actor` or `createdBy` is ignored.
 - A create's `createdBy` defaults to the scope's subject (`profileId`, else `userId`, else the
@@ -160,6 +195,9 @@ const cards = await planningHandlerOf(ctx).planningFor(req, { channel: 'web' }).
 - `opts.access` makes the resolver the only source of the organization; a `grants` object refuses
   every flag it leaves out.
 - A durable store is not done until it passes `@owlmeans/server-planning/conformance`.
+- Resource writes require their current `version`; assignee/team `fields` replace the previous
+  object, while card `changes.fields` merge. A field-backed relationship is changed through its
+  field, not by writing an independent link.
 
 ## Related packages
 

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/server-planning",
-  "version": "0.1.18-rc.29",
-  "generatedAt": "2026-10-09T17:24:50.729Z",
+  "version": "0.1.18-rc.30",
+  "generatedAt": "2026-10-09T20:19:04.321Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

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

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/server-planning
 
 **Layer:** Server
-**Install:** `"@owlmeans/server-planning": "^0.1.18-rc.29"` in `dependencies` (`ajv` is a peer)
+**Install:** `"@owlmeans/server-planning": "^0.1.18-rc.30"` in `dependencies` (`ajv` is a peer)
 
 The general implementation of `@owlmeans/planning`: the planning service (a plugin host), the
 scoped facade, the executor every write goes through, the in-memory reference store, the commit

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/server-planning",
-  "version": "0.1.18-rc.29",
+  "version": "0.1.18-rc.30",
   "license": "MIT",
   "description": "The general planning implementation — the planning service and its plugin/middleware registry, the transition executor, the in-memory store, the protocol handlers and the commit feed.",
   "type": "module",
@@ -50,7 +50,7 @@
     "@owlmeans/context": "^0.1.18-rc.34",
     "@owlmeans/entrypoint": "^0.1.18-rc.41",
     "@owlmeans/error": "^0.1.18-rc.38",
-    "@owlmeans/planning": "^0.1.18-rc.25",
+    "@owlmeans/planning": "^0.1.18-rc.26",
     "@owlmeans/queue": "^0.1.18-rc.44",
     "@owlmeans/resource": "^0.1.18-rc.40",
     "@owlmeans/log": "^0.1.18-rc.3",