@rudderhq/cli 0.2.10-canary.25 → 0.2.10-canary.27

package/dist/index.js

@@ -723,7 +723,7 @@ var init_organization_intelligence_profile = __esm({
 
 // ../packages/shared/dist/validators/resource.js
 import { z as z7 } from "zod";
-function isValidLibraryRelativePath(locator) {
+function isValidLibraryProjectPath(locator, kind) {
   const trimmed = locator.trim();
   if (!trimmed)
     return false;
@@ -736,7 +736,9 @@ function isValidLibraryRelativePath(locator) {
   const parts = trimmed.split("/");
   if (!parts.every((part) => part.length > 0 && part !== "." && part !== ".."))
     return false;
-  return !PROTECTED_LIBRARY_RESOURCE_ROOTS.has(parts[0] ?? "");
+  if (parts[0] !== "projects")
+    return false;
+  return kind === "directory" ? parts.length >= 2 : parts.length >= 3;
 }
 function validateLibraryResourceContract(value, ctx) {
   if (value.sourceType !== "library")
@@ -748,15 +750,15 @@ function validateLibraryResourceContract(value, ctx) {
       path: ["kind"]
     });
   }
-  if (value.locator !== void 0 && !isValidLibraryRelativePath(value.locator)) {
+  if (value.locator !== void 0 && !isValidLibraryProjectPath(value.locator, value.kind)) {
     ctx.addIssue({
       code: z7.ZodIssueCode.custom,
-      message: "Library resource locator must be a normalized relative path inside the organization Library.",
+      message: "Library resource locator must be a normalized project Library path.",
       path: ["locator"]
     });
   }
 }
-var organizationResourceKindSchema, organizationResourceSourceTypeSchema, projectResourceAttachmentRoleSchema, LIBRARY_PATH_SCHEME_RE, PROTECTED_LIBRARY_RESOURCE_ROOTS, createOrganizationResourceBaseSchema, createOrganizationResourceSchema, updateOrganizationResourceSchema, projectResourceAttachmentInputSchema, updateProjectResourceAttachmentSchema, createProjectInlineResourceSchema;
+var organizationResourceKindSchema, organizationResourceSourceTypeSchema, projectResourceAttachmentRoleSchema, LIBRARY_PATH_SCHEME_RE, createOrganizationResourceBaseSchema, createOrganizationResourceSchema, updateOrganizationResourceSchema, projectResourceAttachmentInputSchema, updateProjectResourceAttachmentSchema, createProjectInlineResourceSchema;
 var init_resource = __esm({
   "../packages/shared/dist/validators/resource.js"() {
     "use strict";
@@ -765,7 +767,6 @@ var init_resource = __esm({
     organizationResourceSourceTypeSchema = z7.enum(ORGANIZATION_RESOURCE_SOURCE_TYPES);
     projectResourceAttachmentRoleSchema = z7.enum(PROJECT_RESOURCE_ATTACHMENT_ROLES);
     LIBRARY_PATH_SCHEME_RE = /^[a-z][a-z0-9+.-]*:/i;
-    PROTECTED_LIBRARY_RESOURCE_ROOTS = /* @__PURE__ */ new Set(["agents", "artifacts", "plans", "skills"]);
     createOrganizationResourceBaseSchema = z7.object({
       name: z7.string().min(1),
       kind: organizationResourceKindSchema,
@@ -10597,7 +10598,7 @@ var AGENT_CLI_CAPABILITIES = [
     id: "issue.documents.put",
     command: "rudder issue documents put <issue> <key> --body-file <path>",
     category: "issue",
-    description: "Legacy create or update of a DB-backed issue document; prefer `rudder library file put` for new docs.",
+    description: "Legacy create or update of a DB-backed issue document; prefer `rudder library file put` for durable project files.",
     mutating: true,
     contract: "compat",
     requiresOrgId: false,
@@ -11607,15 +11608,11 @@ var RUDDER_AGENT_OPERATING_CONTRACT = [
   "- Personal skills live under `$AGENT_HOME/skills`.",
   "- Shared organization workspace root lives under `$RUDDER_ORG_WORKSPACE_ROOT`.",
   "- Shared organization skills live under `$RUDDER_ORG_SKILLS_DIR`.",
-  "- Shared organization plans live under `$RUDDER_ORG_PLANS_DIR`.",
-  "- Shared organization artifacts live under `$RUDDER_ORG_ARTIFACTS_DIR`.",
-  '- Library-backed project resources use `sourceType: "library"`; their `locator` is a safe path relative to `$RUDDER_ORG_WORKSPACE_ROOT`, usually under `docs/`, so read them from `$RUDDER_ORG_WORKSPACE_ROOT/<locator>` when that root is available. Rudder does not use protected system roots such as `agents/`, `artifacts/`, `plans/`, or `skills/` as project Library resources.',
-  "- Project Context is explicit operator-curated context, not the whole knowledge boundary. When it is insufficient, inspect broader Library docs and org workspace know-how before concluding context is missing.",
-  "- Durable generated Markdown documents, plans, design docs, and decision notes should be written under `$RUDDER_ORG_WORKSPACE_ROOT/docs/` when available, preferably through `rudder library file put docs/<file>.md --body-file <path> --json`.",
-  "- Durable generated assets such as screenshots, images, mockups, reports, CSVs, handoff logs, and other user-visible non-doc files should be written under `$RUDDER_ORG_ARTIFACTS_DIR` when available.",
-  "- Use `/tmp` only for transient scratch files and temporary verification artifacts; do not put durable work product there.",
+  '- Library-backed project resources use `sourceType: "library"`; their `locator` points into `library:projects/<project-name>/`.',
+  "- Project Context is explicit operator-curated context, not the whole knowledge boundary. When it is insufficient, inspect broader Library and org workspace know-how before concluding context is missing.",
+  "- Durable generated project work files should be written under `library:projects/<project-name>/`.",
+  "- Use `/tmp` only for transient scratch files and temporary verification files; do not put durable work product there.",
   "- Local trusted runtimes may expose the host operator home as `$RUDDER_OPERATOR_HOME`; use it only when a local skill or script intentionally needs operator-owned desktop app or CLI state. Do not replace `$HOME` with it.",
-  "- Durable shared work output should prefer these managed workspace paths instead of ad-hoc top-level `projects/` folders.",
   "",
   "When you create or copy a skill under `$AGENT_HOME/skills/<slug>/`, check the agent's Skills snapshot before claiming it will load in future runs. If it is installed but not enabled, say exactly that future runs will not load it until enabled, and offer to enable it with `rudder agent skills enable <agent-id> <selection-ref>` when you have permission.",
   "",
@@ -11625,9 +11622,9 @@ var RUDDER_AGENT_OPERATING_CONTRACT = [
   "",
   "When an issue comment, done comment, or blocker comment cites visual evidence from a local screenshot/image path, attach the image with the Rudder CLI `--image <path>` option instead of leaving only the filesystem path in the text.",
   "",
-  "## Memory and Planning",
+  "## Memory and Shared Work Notes",
   "",
-  "You MUST use the `para-memory-files` skill for all memory operations: storing facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, and managing plans. The skill defines your three-layer memory system (knowledge graph, daily notes, tacit knowledge), the PARA folder structure, atomic fact schemas, memory decay rules, and recall/planning conventions.",
+  "You MUST use the `para-memory-files` skill for all memory operations: storing facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, and managing shared work notes. The skill defines your three-layer memory system (knowledge graph, daily notes, tacit knowledge), the PARA folder structure, atomic fact schemas, memory decay rules, and recall conventions.",
   "",
   "Keep stable preferences and operating lessons in `$AGENT_HOME/instructions/MEMORY.md`. Use `$AGENT_HOME/memory/YYYY-MM-DD.md` for daily notes and `$AGENT_HOME/life/` for structured long-term memory; those files are not auto-loaded.",
   "",
@@ -12544,7 +12541,7 @@ function registerLibraryCommands(program) {
   const library = program.command("library").description("Library file operations");
   const file = library.command("file").description("Path-based Library file operations");
   addCommonClientOptions(
-    file.command("list").description(getAgentCliCapabilityById("library.file.list").description).argument("[directoryPath]", "Library directory path", "docs").action(async (directoryPath, opts) => {
+    file.command("list").description(getAgentCliCapabilityById("library.file.list").description).argument("[directoryPath]", "Library directory path", "projects").action(async (directoryPath, opts) => {
       try {
         const ctx = resolveCommandContext(opts, { requireCompany: true });
         const search = new URLSearchParams();