@cosmicdrift/kumiko-types 0.176.2 → 0.178.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmicdrift/kumiko-types",
-  "version": "0.176.2",
+  "version": "0.178.1",
   "description": "Framework-Type-Definitions für Kumiko — FeatureDefinition, BootCheck-Types und die reinen Engine-Types. Erlaubt Downstream-Konsumenten, gegen die Type-Contracts zu bauen, ohne das ganze Framework-Package zu importieren. Enthaelt keine identitaets-sensitiven Runtime-Werte mehr (Error-Klassen leben seit #1629 in kumiko-framework, Brand-Symbole nutzen Symbol.for) und ist deshalb eine plain dependency, keine peerDependency.",
   "license": "BUSL-1.1",
   "author": "Marc Frost <marc@cosmicdriftgamestudio.com>",

package/src/feature.ts

@@ -64,7 +64,7 @@ import type {
   ValidationHookFn,
 } from "./hooks";
 import type { HttpRouteDefinition } from "./http-route";
-import type { NavDefinition } from "./nav";
+import type { ContentCollectionDefinition, NavDefinition } from "./nav";
 import type {
   EntityProjectionExtension,
   MultiStreamProjectionDefinition,
@@ -356,6 +356,11 @@ export type FeatureDefinition = {
   // feature exports via setup-return — buildTarget consumes the handle,
   // not this slot. See visual-tree.md A5 + A7.
   readonly treeActions?: Readonly<Record<string, TreeActionDef>>;
+  // Content collections declared via r.contentCollection(). Keyed by the
+  // feature-local short id. Each one also produced a nav entry under the
+  // same id — this slot carries the `kind` the client needs to build the
+  // matching tree provider, which a NavDefinition has no place for.
+  readonly contentCollections?: Readonly<Record<string, ContentCollectionDefinition>>;
   // HTTP-Routes declared via r.httpRoute(). Index is "METHOD path"
   // (z.B. "GET /feed.xml") — eindeutig pro Feature. Die App-Server-
   // Boot-Stage iteriert getAllHttpRoutes() und mountet jede Route auf
@@ -764,6 +769,17 @@ export type FeatureRegistrar<TFeature extends string = string> = {
   // that parent chains don't contain cycles.
   nav(definition: NavDefinition): void;
 
+  // Register a content collection — a set of template-resources of one kind,
+  // navigable where it fachlich belongs (mail templates under Mail, not under
+  // a central "Content" section). Sugar over r.nav(): registers the nav entry
+  // with `provider: true` under the same id and records the kind so the client
+  // can wire the tree provider without repeating navId + kind.
+  //
+  // Returns the qualified nav name ("<feature>:nav:<id>") — apps that pass the
+  // collection to a client feature explicitly take it from here instead of
+  // re-typing the QN.
+  contentCollection(definition: ContentCollectionDefinition): string;
+
   // Register a workspace — a persona-/role-scoped UI surface. Pure UI
   // composition; the registry qualifies the short id to
   // "<feature>:workspace:<id>". Boot-validation checks that any nav refs

package/src/nav.ts

@@ -65,3 +65,54 @@ export type NavDefinition = {
   // → entry belongs to no workspace).
   readonly workspaces?: readonly string[];
 };
+
+// A feature's content collection — a set of template-resources of one `kind`,
+// mounted in the nav next to the feature it belongs to rather than under a
+// central "Content" section. Declared via r.contentCollection(), which
+// registers the nav entry (always `provider: true`, the tree children arrive
+// at runtime) and records the `kind` so the client can build the matching tree
+// provider without the app repeating it.
+//
+// `parent` may point at another feature's nav QN; the boot validator rejects
+// dangling refs, so a collection mounted under a feature that isn't mounted
+// fails boot instead of silently disappearing from the sidebar.
+export type ContentCollectionDefinition = {
+  // Feature-local short id, kebab-case. Also becomes the nav entry's id, so
+  // it must not collide with an r.nav()/r.screen() id in the same feature.
+  // Handlers take this id, not a kind — a payload can therefore only ever
+  // address a declared collection, with the rules that were declared for it.
+  readonly id: string;
+  // Which template-resource kind this collection lists ("mail-html",
+  // "document-pdf", "text-block", ...). The engine keeps it opaque —
+  // bundled-features owns the kind vocabulary. Two collections may share a
+  // kind and still differ in access and ownership.
+  readonly kind: string;
+  // Who may read and write this collection's entries. Declared at mount time
+  // by the app, because a bundled feature cannot know the host's role
+  // vocabulary — same reasoning as the `access` option on tags/folders/ledger.
+  // Omitted means the mounting app didn't decide; the feature's own default
+  // applies.
+  readonly access?: AccessRule;
+  // "tenant": one set of entries shared by everyone in the tenant (reply
+  // snippets an admin curates). "user": every user keeps their own (mail
+  // signatures). Defaults to "tenant".
+  readonly ownership?: "tenant" | "user";
+  readonly nav: {
+    readonly label: string;
+    readonly icon?: string;
+    readonly parent?: string;
+    readonly order?: number;
+    // Visibility of the nav node. Leave unset — it then follows the
+    // collection's `access`, so the sidebar never offers a node whose
+    // contents the handler will refuse. Set it only to hide the node from
+    // someone who may still reach the data another way.
+    readonly access?: AccessRule;
+    readonly workspaces?: readonly string[];
+    // "+" affordance on the node and hover actions on the row — same meaning
+    // as on NavDefinition. Without a createAction a collection can only list
+    // what already exists; the target is usually the owning feature's
+    // r.treeActions create.
+    readonly createAction?: TreeAction;
+    readonly actions?: readonly TreeAction[];
+  };
+};