opencode-gitlab-dap 1.11.0 → 1.12.0

package/dist/index.cjs

@@ -3604,7 +3604,8 @@ var MEMORY_TYPES = [
   "architecture",
   "conventions",
   "troubleshooting",
-  "people-and-contexts"
+  "people-and-contexts",
+  "plans"
 ];
 var MEMORY_DIRS = {
   all: MEMORY_TYPES.map((t) => `${PREFIX}/memory/${t}`),
@@ -3618,7 +3619,8 @@ var RECORD_TYPES = [
   "architecture",
   "convention",
   "troubleshooting",
-  "people"
+  "people",
+  "plan"
 ];
 var RECORD_DIR = {
   fact: `${PREFIX}/memory/facts`,
@@ -3627,7 +3629,8 @@ var RECORD_DIR = {
   architecture: `${PREFIX}/memory/architecture`,
   convention: `${PREFIX}/memory/conventions`,
   troubleshooting: `${PREFIX}/memory/troubleshooting`,
-  people: `${PREFIX}/memory/people-and-contexts`
+  people: `${PREFIX}/memory/people-and-contexts`,
+  plan: `${PREFIX}/memory/plans`
 };
 var PROJECT_ID_DESC = 'FULL project path with namespace (e.g., "gitlab-org/gitlab"). Must contain a slash. Never use just the project name.';
 function today() {
@@ -3707,7 +3710,7 @@ ${entries}`
       }
     }),
     gitlab_memory_record: (0, import_plugin5.tool)({
-      description: "Record knowledge in project memory. Each record creates its own page \u2014 safe for parallel writes.\nTypes:\n  fact \u2014 stable truths (tech stack, dependencies, deploy targets, project metadata)\n  decision \u2014 architectural choices with reasoning (why X over Y)\n  pattern \u2014 recurring observations that may evolve into skills\n  architecture \u2014 system design, module structure, data flow, key abstractions\n  convention \u2014 coding standards, naming patterns, review process, commit conventions\n  troubleshooting \u2014 known issues, workarounds, debugging tips, common errors\n  people \u2014 team members, roles, ownership areas, contact context",
+      description: "Record knowledge in project memory. Each record creates its own page \u2014 safe for parallel writes.\nTypes:\n  fact \u2014 stable truths (tech stack, dependencies, deploy targets, project metadata)\n  decision \u2014 architectural choices with reasoning (why X over Y)\n  pattern \u2014 recurring observations that may evolve into skills\n  architecture \u2014 system design, module structure, data flow, key abstractions\n  convention \u2014 coding standards, naming patterns, review process, commit conventions\n  troubleshooting \u2014 known issues, workarounds, debugging tips, common errors\n  people \u2014 team members, roles, ownership areas, contact context\n  plan \u2014 implementation plans, feature designs, task breakdowns, roadmap items",
       args: {
         project_id: z5.string().describe(PROJECT_ID_DESC),
         type: z5.enum([...RECORD_TYPES]).describe("Type of knowledge to record"),