@databutton/firebase-types 1.176.0 → 1.177.1

package/lib/types/published/persisted.d.ts

@@ -1223,11 +1223,9 @@ export interface ProjectMigrationRecord {
 }
 export type ProjectVariant = "beyond-streamlit" | "riff";
 /**
- * Known agent type tags the platform gates specific behavior on (e.g. the
- * orchestrator selecting per-agent-type tool variants for
- * "order-confirmation-agent"). Not a closed set — projects may carry other
- * ad-hoc values (e.g. per-customer agents identified only via agentSpecUrl),
- * so this stays open with a string fallback rather than a strict union.
+ * The agent's SKU, as named in the agent catalogue — one level more specific
+ * than {@link SpecialProjectType}, which gives the shape: several SKUs are all
+ * operational agents. Open on purpose; not every SKU is listed.
  */
 export type ProjectAgentType = "order-confirmation-agent" | "supplier-communications-agent" | (string & {});
 export interface IntegrationPackages {
@@ -1625,7 +1623,7 @@ export interface Project {
     githubUrl?: string;
     /** URL to the agent type spec document (e.g. riff-agent-docs/agents/supplier-communications-agent.md). */
     agentSpecUrl?: string;
-    /** Agent type tag identifying which kind of agent this project implements (e.g. "supplier-communications-agent"). */
+    /** The agent's SKU — see {@link ProjectAgentType}. */
     agentType?: ProjectAgentType;
     isShowcase?: boolean;
     last_deployed?: Timestamp;
@@ -1805,6 +1803,15 @@ export interface ProjectTemplate {
     build: ProjectTemplateBuildSnapshot;
     targetPoolSize?: number;
     variant: ProjectVariant;
+    /**
+     * The project kind and SKU inherited by projects created from this template.
+     * Snapshotted from the project the template was built from, so a new agent
+     * starts out as the same kind of agent, with the same SKU, as the one it was
+     * modelled on. Unset means the created project gets no kind or SKU either.
+     */
+    specialType?: SpecialProjectType;
+    /** See {@link ProjectAgentType}. Snapshotted alongside {@link specialType}. */
+    agentType?: ProjectAgentType;
     initialPromptInstructions?: string;
     secretNames?: string[];
     secretRefs?: {
@@ -2747,8 +2754,19 @@ export interface AgentSkillBase {
     content: string;
     availability: "draft" | "preview" | "active";
     /**
-     * Restricts which kind of project can see this skill, mirroring
-     * SpecialProjectType on the project doc.
+     * Restricts which kinds of project can see this skill, mirroring
+     * SpecialProjectType on the project doc. More than one kind may be listed:
+     * a skill that reads the same for an operational agent and for a strategic
+     * agent (a copilot) is tagged with both rather than duplicated per kind,
+     * while one that does not — configuring a trigger, say — names only the kind
+     * it applies to.
+     *
+     * Set this on new and edited skills. Unset or empty falls back to `type`.
+     */
+    types?: SpecialProjectType[] | null;
+    /**
+     * Superseded by `types`, which can carry more than one kind. Still read when
+     * `types` is unset, so skills written before it keep resolving.
      * - null: defaults to SpecialProjectType.APP (backwards compatible)
      */
     type?: SpecialProjectType | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@databutton/firebase-types",
-  "version": "1.176.0",
+  "version": "1.177.1",
   "main": "lib/types/published/index.js",
   "type": "module",
   "engines": {