@popoverai/dotrequirements 0.32.0 → 0.32.1

package/dist/convex.d.ts

@@ -22,8 +22,6 @@ export declare const api: {
             checkDocumentsExist: import("convex/server").FunctionReference<"query", "public", any, any, string | undefined>;
         };
         mutations: {
-            create: import("convex/server").FunctionReference<"mutation", "public", any, any, string | undefined>;
-            update: import("convex/server").FunctionReference<"mutation", "public", any, any, string | undefined>;
             deleteForCli: import("convex/server").FunctionReference<"mutation", "public", any, any, string | undefined>;
             setAttachmentsForSync: import("convex/server").FunctionReference<"mutation", "public", any, any, string | undefined>;
         };

package/dist/convex.js

@@ -26,8 +26,6 @@ export const api = {
             checkDocumentsExist: query("documents/queries:checkDocumentsExist"),
         },
         mutations: {
-            create: mutation("documents/mutations:create"),
-            update: mutation("documents/mutations:update"),
             // SYNC-MODE-3: delete a cloud document from the CLI (repo-wins)
             deleteForCli: mutation("documents/mutations:deleteForCli"),
             // ATTACH-10.2: attachment-only sync — a metadata patch, never a publish

package/dist/templates/example-requirements.js

@@ -26,8 +26,8 @@ HOWTO-1: How to use dotrequirements
     2.0. Nesting → You can keep nesting. Label references don't need to be nested: requirement('HOWTO-1.nesting').
     2.1. Several words → Reference multi-word labels using kebab-case. Label references are never case sensitive: requirement('HOWTO-1.several-words')
   3. → While you _can_ write your requirements longhand in this format, there are a number of better ways.
-    3.0. MCP → The dotrequirements MCP equips an AI assistant to develop requirements with you
-    3.1. Your current tools → Dotrequirements has a composer for Jira, Confluence, and Notion
+    3.0. Coding assistants → Run \`dotreq ai-setup\` and your coding assistant develops requirements with you
+    3.1. Chat → Connect Claude or ChatGPT to dot•requirements and write specs in the conversation
     3.2. Our composer → You can use our requirements composer at app.dotrequirements.io
   4. Have fun → Especially in the time you get back from having a more stable, transparent, and AI-friendly codebase
 \`\`\`

package/dist/templates/example-requirements.ts

@@ -29,8 +29,8 @@ HOWTO-1: How to use dotrequirements
     2.0. Nesting → You can keep nesting. Label references don't need to be nested: requirement('HOWTO-1.nesting').
     2.1. Several words → Reference multi-word labels using kebab-case. Label references are never case sensitive: requirement('HOWTO-1.several-words')
   3. → While you _can_ write your requirements longhand in this format, there are a number of better ways.
-    3.0. MCP → The dotrequirements MCP equips an AI assistant to develop requirements with you
-    3.1. Your current tools → Dotrequirements has a composer for Jira, Confluence, and Notion
+    3.0. Coding assistants → Run \`dotreq ai-setup\` and your coding assistant develops requirements with you
+    3.1. Chat → Connect Claude or ChatGPT to dot•requirements and write specs in the conversation
     3.2. Our composer → You can use our requirements composer at app.dotrequirements.io
   4. Have fun → Especially in the time you get back from having a more stable, transparent, and AI-friendly codebase
 \`\`\`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@popoverai/dotrequirements",
-  "version": "0.32.0",
+  "version": "0.32.1",
   "description": "Requirements as testable, human-readable data — CLI and test harness for spec-driven development with AI coding agents",
   "type": "module",
   "bin": {