@synap-core/workspace-templates 0.30.0 → 0.32.0

package/README.md

@@ -25,7 +25,7 @@ How installs, reconciles and tiers work is in the `synap-market` skill
 | `skills/<slug>/` | `skill` | Either a manifest `<slug>.skill.json` (`creative-director`), or an Agent-Skills folder (`SKILL.md` plus references) with a header `skills/<slug>.catalog.json` beside it | The manifest: yes. A folder: only with its header, and only when it holds no reference files (a skill package carries no documents). Headers decided by the founder on 2026-11-05: `bookmark-enrichment` and `routing-to-channels` public, `mapping-the-server` unlisted (private to the official owner); `reading-client-progress` and the parked `stellar-scf-grants-advisor` stay **staged** |
 | `views/<slug>.view.json` | `view` | Manifest; `spec.views` in the canonical shape the CP stores (`{slug, displayName, type, config, scopeProfileSlugs}`) | Category `view`. Three today (`bookmark-views-pack`, `event-views-pack`, `task-views-pack`), moved from the old CP pack fragments on 2026-11-05. CI on every push to main |
 | `automations/<slug>.automation.json` | `automation` | bridge-setup `flowDefinition` form, plus a header `automations/<slug>.catalog.json` beside it | Only with its header, and only without apply-time placeholders. Headers decided by the founder on 2026-11-05: `bookmark-enrichment` public; `url-bookmark-capture`, `github-pr-events` and the five `ship-a-change-*` unlisted. `mail-feed` stays **staged**: it carries two placeholders bridge-setup fills |
-| `agents/<slug>.agent.yaml` | `agent` | Manifest. `spec` (`schema/agent.ts`) is what the pod reads as `definition.agent`: `harness` (the `agent_type` join key), `aliases`, `worker`, `tried`, `detect`, `wake` (data: `program` + `args` + `params`, never a shell line; required for a worker only), `practices.skills`, `mcp` (where its program reads MCP servers: `config` under ~/, `format` yaml/json, `key` dot path, `entry`; the CLI writes the pod's server there on `synap agents add`, the pod ignores it). One per program of the backend harness registry, plus `hermes`. CP category `agent`, official vendor only, left out of browse lists (the catalog installs every official agent on every pod, founder decision D8) | Yes, on every push to main, like every other kind (the first publish was the founder's, by hand, on 2026-11-07; `FIRST_PUBLISH_BY_HAND` is empty since) |
+| `agents/<slug>.agent.yaml` | `agent` | Manifest. `spec` (`schema/agent.ts`) is what the pod reads as `definition.agent`: `harness` (the `agent_type` join key), `aliases`, `worker`, `tried`, `detect`, `wake` (data: `program` + `args` + `params`, never a shell line; required for a worker only), `practices.skills`, `mcp` (where its program reads MCP servers: `config` under ~/, `format` yaml/json, `key` dot path, `entry`; the CLI writes the pod's server there on `synap agents add`, the pod ignores it), `toolProfile` (`entry` / `builder`) + `toolGroups` (only with `entry`): the MCP tools an agent's first key lists, read by the pod (backend#900). One per program of the backend harness registry, plus `hermes`. CP category `agent`, official vendor only, left out of browse lists (the catalog installs every official agent on every pod, founder decision D8) | Yes, on every push to main, like every other kind (the first publish was the founder's, by hand, on 2026-11-07; `FIRST_PUBLISH_BY_HAND` is empty since) |
 | `schema/` | | Zod manifest schema: `header.ts`, plus one body per kind (`workspace`, `capability`, `skill`, `automation`, `view`, `agent`, `playbook`) | |
 | `standards/*.standard.yaml` | | Quality standard per workspace (`pnpm eval`) | |
 | `scripts/catalog-lib.mjs` | | **The ONE lib**: `loadCatalog` → `validateCatalog` → `diffCatalog` → `publishCatalog` | |
@@ -270,23 +270,26 @@ proposal; the review is the catalog commit.
 | Field | Where | Rule |
 |---|---|---|
 | `subjectProfile.profileSlug` | playbook | The kind or role the process works. |
-| `subjectProfile.statusProperty` | playbook | Omit it: the pod follows the profile's declared lifecycle. If you name it, name that same property. A status worker on a role with no declared lifecycle is refused. |
+| (no status field) | playbook | The process FOLLOWS the kind's declared lifecycle: every `subjectStatus` and worker `status` is an option of it. `statusProperty`, `onEnd` and `humanOnlyStatuses` are retired (One model decision 4, `playbook-field-retired`): a person-only option is `humanOnly` on the lifecycle, a status no stage owns is derived by the pod, and a session that ends early moves nothing. |
 | `stages[].subjectStatus` | stage | Entering the stage moves the subject to this option, through the door. Must be an **existing option** of the lifecycle — never invent one. |
 | `stages[].gate` | stage | `{kind: human}` at every commitment: send to a client, sign, pay, publish, won/lost, anything irreversible. `{kind: check}` only where the stage's own criteria can be verified. A gated stage writes its status only when the gate passes. A check gate judges the stage being LEFT, so never use it to guard an irreversible status. |
 | `stages[].onFail` | stage | `{toStage: <key>}` — where a rejected gate sends the run (rework loop). |
 | `stages[].criteria` | stage | 2–5 binary statements; `check.kind` evidence (cheapest) · capability · judge · human. |
 | `expectedOutputs[]` | stage or playbook | What the step must produce: `kind` + `label` + `relationToSubject` (an existing relation slug, or `none`). The UI shows what was produced from this. |
 | `activators[]` (workers) | playbook | `on`: `created` · `enters_status` (+ `status`) · `count` (+ `status`, `min` ≥ 2) · `schedule` (+ `cron`, UTC) · `manual`. `size`: `per_thing` (default) · `per_moment` (count and schedule always are). `mode`: `propose` (default) · `run` only when cheap and safe. `maxPendingApprovals` (default 20) throttles. Compiled to a governed rule the owner can pause; it fires once per thing per transition. |
-| `humanOnlyStatuses` | playbook | Legacy: the options no stage owns. Mark a person-only option `humanOnly` on the lifecycle instead; while `statusProperty` is set, `synap catalog validate` still checks that stages and this list cover every option. |
 | `goalTemplate` | playbook | Placeholders are `{paramName}`. Never `@{arg:…}` (read-only legacy). |
 | `params` | playbook | The subject is a `type: entity` param. A required param left unanswered becomes a question owed by the person, not an empty string. |
 
 Human moments use an `ask` on an owed slot: `confirm` / `choose` (one `recommended`) / `form` / `act` / `provide`
 (connection, file or secret through the vault). Never ask for a secret in a form.
 
-Validation: `synap catalog validate` (process contract, goal grammar, lifecycle coverage ratchet — the count of
+Validation: `synap catalog validate` (process contract, goal grammar, lifecycle ratchet — the count of
 lifecycle kinds with no process may only go down).
 
+**Boards.** A kanban names its columns in `config.groupByField` (the one key the board reads); grouped on the
+kind's lifecycle property it is the flow board, where a drag is the governed status move. A `groupBy` (top-level
+or in `config`) is never read and is refused (`view-kanban-group-*`).
+
 ## Intent: what a space produces
 
 A space is named by its PURPOSE first ("Product · Dev", "Sales · CRM") and is read through the THINGS it makes.
@@ -296,6 +299,7 @@ The template that owns the space says both, in `meta.intent`:
 meta:
   intent:
     label: Product            # the purpose word, ≤ 24 characters
+    primary: devplane_feature # the ONE output the main flow produces; one of produces
     produces:                 # ordered; kinds or roles
       - profile: devplane_feature
       - profile: devplane_story
@@ -304,8 +308,12 @@ meta:
 
 - **Several kinds, never one only.** List what a person would come to the space to see move, in the order a home
   shows them.
+- **One `primary` output** (One model decision 3): the kind or role the space's main flow produces, the one its
+  home leads with. Required when the space produces anything, and one of `produces`; the rest are its operational
+  kinds (`intent-primary-missing`, `intent-primary-not-produced`). `meta.start.profile` defaults to it: omit it
+  unless the start is about another kind (`start-profile-redundant`).
 - **No `produces` (or `[]`) = a library.** Brand, Strategy, Ecosystem, Knowledge… are read, not moved: they carry
-  a label only.
+  a label only, and no `primary` (`intent-primary-library`).
 - **Each produced profile declares a lifecycle** — a home counts things by lifecycle category, so a kind without
   one cannot be counted (`intent-no-lifecycle`, naming it). Declare the lifecycle first (see "Writing a process").
 - **Each produced profile is the template's own or one it depends on** (`require`/`compose` closure), e.g. CRM

package/agents/hermes.agent.yaml

@@ -24,5 +24,8 @@ spec:
     format: yaml
     key: mcp_servers
     entry: url-headers
+  # Its first key lists the essential tools plus the read group (backend#900).
+  toolProfile: entry
+  toolGroups: [read]
   practices:
     skills: [synap]

package/dist/{define-DqoItRiR.d.ts → define-DHDi8C33.d.ts}

@@ -459,12 +459,11 @@ interface TemplatePlaybook {
      * `playbooks.matchForEntity` (filters `subject_profile->>'profileSlug'`), so a
      * captured entity of this kind can auto-launch the playbook as a session.
      *
-     * `statusProperty` names the subject kind's SELECT property that holds its
-     * lifecycle (e.g. `post-status`). It is what ties `stages[].subjectStatus`
-     * to the subject: advancing into a stage writes that value (governed), and
-     * the subject entering the value advances an open run to the stage.
-     * `validate.ts` checks it is a select property of the kind, and that every
-     * `subjectStatus` / activator `status` is one of its enum values.
+     * The process FOLLOWS the kind's declared lifecycle (`profiles[].lifecycle`):
+     * that property is what `stages[].subjectStatus` and activator `status` are
+     * values of (`validate.ts`). A playbook never names it again — the
+     * `statusProperty`, `onEnd` and `humanOnlyStatuses` fields are retired from
+     * the catalog (One model decision 4; rule `playbook-field-retired`).
      */
     subjectProfile?: {
         profileSlug: string;
@@ -476,7 +475,6 @@ interface TemplatePlaybook {
          * fan-out is refused, so the schedule would silently never be created.
          */
         filter?: string;
-        statusProperty?: string;
     };
     /**
      * Playbook-level slots: what a run of this process is expected to produce.
@@ -497,14 +495,6 @@ interface TemplatePlaybook {
      * `automations:`. Public templates default to `mode: propose`.
      */
     activators?: TemplatePlaybookActivator[];
-    /**
-     * TEMPLATE-AUTHORING ONLY. Values of `subjectProfile.statusProperty` that no
-     * stage owns because a PERSON sets them (e.g. Idea, Archived). The lifecycle
-     * coverage ratchet (`lifecycle-coverage.test.ts`) requires every enum value
-     * of the status property to be either a stage's `subjectStatus` or listed
-     * here, so a lifecycle state can never be silently orphaned by a process.
-     */
-    humanOnlyStatuses?: string[];
     status?: "draft" | "active" | "paused";
     /**
      * `project` = a TRACK template (a method a project runs over its `stages`);
@@ -546,7 +536,7 @@ interface TemplatePlaybookStage {
         proposalType?: "playbook.stage_gate";
     };
     /**
-     * The value of the playbook's `subjectProfile.statusProperty` this stage
+     * The value of the subject kind's lifecycle property this stage
      * corresponds to. Advancing INTO the stage writes it to the subject
      * (governed); the subject ENTERING it advances an open run to the stage.
      */
@@ -829,8 +819,12 @@ interface TemplateStart {
     promise: string;
     /** Identity ids this start is suggested for; each id belongs to one start. */
     suggestFor: string[];
-    /** The produced kind the views and the first session are about. */
-    profile: string;
+    /**
+     * The kind the views and the first session are about. Omit it: it defaults
+     * to `meta.intent.primary` (one source; `define.ts` fills it on the wire).
+     * Name it only when the start is about another kind than the primary.
+     */
+    profile?: string;
     /** 1-3 slugs of THIS template's views, scoped to `profile`; first = default. */
     views: string[];
     /** Preview rows, never written. `values` keys are properties of `profile`. */
@@ -851,6 +845,13 @@ declare const INTENT_LABEL_MAX = 24;
 interface TemplateIntent {
     /** ≤ {@link INTENT_LABEL_MAX} chars. */
     label: string;
+    /**
+     * The space's ONE primary output (One model decision 3): the kind or role
+     * its main flow produces, the one its home leads with. Required when the
+     * space produces anything, and one of `produces` (the rest of `produces` are
+     * its operational kinds). A library (no `produces`) names none.
+     */
+    primary?: string;
     produces?: Array<{
         profile: string;
     }>;

package/dist/index.d.ts

@@ -1,5 +1,5 @@
-import { W as WorkspaceYaml, T as TemplateDependency, a as TemplateLifecycleOption, b as TemplateLifecycleOptionWaits } from './define-DqoItRiR.js';
-export { B as BentoViewBlockWire, c as BentoWidgetBlockWire, d as BuiltSpacePackage, e as BuiltSpacePackageCell, I as INTENT_LABEL_MAX, P as PACKAGE_DEPENDENCY_KINDS, f as PackageAutomationWire, g as PackageDefinitionOutput, h as PackageDependencyKind, S as START_EXAMPLE_RANGE, i as START_STARTERS_RANGE, j as START_VIEWS_MAX, k as SpacePackageCellWire, l as SplitBentoBlocks, m as TemplateActionPlacement, n as TemplateAppKind, o as TemplateAppRef, p as TemplateAutomation, q as TemplateBentoBlock, r as TemplateDefaultSource, s as TemplateDisplayTemplate, t as TemplateEntityLink, u as TemplateExtendsRef, v as TemplateIntegration, w as TemplateIntent, x as TemplateLayoutConfig, y as TemplateMeta, z as TemplateOnboarding, A as TemplateOnboardingCollectTarget, C as TemplatePlaybook, D as TemplatePlaybookParam, E as TemplatePrimarySurface, F as TemplateProfile, G as TemplateProfileEntityBentoTemplates, H as TemplateProperty, J as TemplateSeedEntity, K as TemplateSidebarItem, L as TemplateSidebarSurface, M as TemplateSourceRole, N as TemplateSpacePackage, O as TemplateSpacePackageCell, Q as TemplateStart, R as TemplateSuggestedRelation, U as TemplateView, V as ToDefinitionResult, X as WorkspaceDefinitionInput, Y as WorkspaceJsonValue, Z as WorkspacePrimarySurface, _ as WorkspacePrimarySurfaceViewReference, $ as normalizeTemplateLayout, a0 as spacePackageCells, a1 as splitBentoBlocks, a2 as toAutomationWire, a3 as toPackageDefinition, a4 as toWorkspaceDefinition } from './define-DqoItRiR.js';
+import { W as WorkspaceYaml, T as TemplateDependency, a as TemplateLifecycleOption, b as TemplateLifecycleOptionWaits } from './define-DHDi8C33.js';
+export { B as BentoViewBlockWire, c as BentoWidgetBlockWire, d as BuiltSpacePackage, e as BuiltSpacePackageCell, I as INTENT_LABEL_MAX, P as PACKAGE_DEPENDENCY_KINDS, f as PackageAutomationWire, g as PackageDefinitionOutput, h as PackageDependencyKind, S as START_EXAMPLE_RANGE, i as START_STARTERS_RANGE, j as START_VIEWS_MAX, k as SpacePackageCellWire, l as SplitBentoBlocks, m as TemplateActionPlacement, n as TemplateAppKind, o as TemplateAppRef, p as TemplateAutomation, q as TemplateBentoBlock, r as TemplateDefaultSource, s as TemplateDisplayTemplate, t as TemplateEntityLink, u as TemplateExtendsRef, v as TemplateIntegration, w as TemplateIntent, x as TemplateLayoutConfig, y as TemplateMeta, z as TemplateOnboarding, A as TemplateOnboardingCollectTarget, C as TemplatePlaybook, D as TemplatePlaybookParam, E as TemplatePrimarySurface, F as TemplateProfile, G as TemplateProfileEntityBentoTemplates, H as TemplateProperty, J as TemplateSeedEntity, K as TemplateSidebarItem, L as TemplateSidebarSurface, M as TemplateSourceRole, N as TemplateSpacePackage, O as TemplateSpacePackageCell, Q as TemplateStart, R as TemplateSuggestedRelation, U as TemplateView, V as ToDefinitionResult, X as WorkspaceDefinitionInput, Y as WorkspaceJsonValue, Z as WorkspacePrimarySurface, _ as WorkspacePrimarySurfaceViewReference, $ as normalizeTemplateLayout, a0 as spacePackageCells, a1 as splitBentoBlocks, a2 as toAutomationWire, a3 as toPackageDefinition, a4 as toWorkspaceDefinition } from './define-DHDi8C33.js';
 import '@synap-core/types/presentation';
 import '@synap-core/types/space-brief';
 import '@synap-core/types/capability-intents';