@inkeep/agents-core 0.51.0 → 0.53.0

package/dist/db/manage/manage-schema.js

@@ -338,7 +338,7 @@ const subAgentSkills = pgTable("sub_agent_skills", {
 		],
 		name: "sub_agent_skills_skill_fk"
 	}).onDelete("cascade"),
-	unique("sub_agent_skills_sub_agent_skill_unique").on(table.subAgentId, table.skillId),
+	unique("sub_agent_skills_sub_agent_skill_unique").on(table.tenantId, table.projectId, table.agentId, table.subAgentId, table.skillId),
 	index("sub_agent_skills_skill_idx").on(table.skillId)
 ]);
 const subAgentRelations = pgTable("sub_agent_relations", {

package/dist/db/manage/scope-definitions.d.ts

@@ -0,0 +1,31 @@
+//#region src/db/manage/scope-definitions.d.ts
+/**
+ * Single source of truth for hierarchical scope column definitions.
+ *
+ * Everything else — TypeScript config types, WHERE clause helpers, and
+ * compile-time table constraints — is derived from these key arrays.
+ *
+ * The schema column helpers (tenantScoped, projectScoped, etc.) in
+ * manage-schema.ts define the Drizzle columns using the same key names.
+ * If a key is added or removed here, the schema columns and all
+ * downstream consumers (types, query helpers) must be updated together —
+ * but now they'll fail at compile time instead of silently drifting.
+ */
+declare const SCOPE_KEYS: {
+  readonly tenant: readonly ["tenantId"];
+  readonly project: readonly ["tenantId", "projectId"];
+  readonly agent: readonly ["tenantId", "projectId", "agentId"];
+  readonly subAgent: readonly ["tenantId", "projectId", "agentId", "subAgentId"];
+};
+type ScopeLevel = keyof typeof SCOPE_KEYS;
+type ScopeKeysOf<L extends ScopeLevel> = (typeof SCOPE_KEYS)[L][number];
+/** A table that has the columns required for a given scope level. */
+type ScopedTable<L extends ScopeLevel> = { [K in ScopeKeysOf<L>]: any };
+/** The parameter object shape required to filter by a given scope level. */
+type ScopeConfig<L extends ScopeLevel> = { [K in ScopeKeysOf<L>]: string };
+type TenantScopeConfig = ScopeConfig<'tenant'>;
+type ProjectScopeConfig = ScopeConfig<'project'>;
+type AgentScopeConfig = ScopeConfig<'agent'>;
+type SubAgentScopeConfig = ScopeConfig<'subAgent'>;
+//#endregion
+export { AgentScopeConfig, ProjectScopeConfig, SCOPE_KEYS, ScopeConfig, ScopeKeysOf, ScopeLevel, ScopedTable, SubAgentScopeConfig, TenantScopeConfig };

package/dist/db/manage/scope-definitions.js

@@ -0,0 +1,31 @@
+//#region src/db/manage/scope-definitions.ts
+/**
+* Single source of truth for hierarchical scope column definitions.
+*
+* Everything else — TypeScript config types, WHERE clause helpers, and
+* compile-time table constraints — is derived from these key arrays.
+*
+* The schema column helpers (tenantScoped, projectScoped, etc.) in
+* manage-schema.ts define the Drizzle columns using the same key names.
+* If a key is added or removed here, the schema columns and all
+* downstream consumers (types, query helpers) must be updated together —
+* but now they'll fail at compile time instead of silently drifting.
+*/
+const SCOPE_KEYS = {
+	tenant: ["tenantId"],
+	project: ["tenantId", "projectId"],
+	agent: [
+		"tenantId",
+		"projectId",
+		"agentId"
+	],
+	subAgent: [
+		"tenantId",
+		"projectId",
+		"agentId",
+		"subAgentId"
+	]
+};
+
+//#endregion
+export { SCOPE_KEYS };