viviscape-mcp 2.0.2 → 2.2.0

package/dist/enums.d.ts

@@ -0,0 +1,48 @@
+/**
+ * Status and priority vocabularies as the platform actually defines them.
+ *
+ * Source of truth is the ViviScape Work UI, not guesswork:
+ *   ClockWyzWeb/Views/App/Tasks.cshtml     -- task status + priority selects
+ *   ClockWyzWeb/Views/App/Projects.cshtml  -- task editor and project status selects
+ * Cross-checked against live rows from account 1 (211 projects, 6 open tasks).
+ *
+ * Two traps worth knowing:
+ *  - Tasks complete as "completed"; projects complete as "complete".
+ *  - Priority is low/moderate/important/urgent/critical. It is NOT
+ *    low/medium/high, which is what this server's task_add used to claim.
+ */
+/** Task status values, in board order. */
+export declare const TASK_STATUSES: readonly ["backlog", "new", "research", "inprogress", "pendingreview", "inreview", "testing", "waitingcustomer", "waitingteammember", "onhold", "cancelled", "completed"];
+/** Task and project priority values, ascending. */
+export declare const PRIORITIES: readonly ["low", "moderate", "important", "urgent", "critical"];
+/**
+ * Project (group) status values. Narrower than task status, and note "complete"
+ * rather than "completed". An empty status reads as "Undetermined" in the UI.
+ */
+export declare const PROJECT_STATUSES: readonly ["new", "inprogress", "complete"];
+/** Prospect pipeline stages, from the CRM tools. */
+export declare const PROSPECT_STATUSES: readonly ["new", "firstcontact", "negotiation", "pending", "won", "lost", "spam"];
+/** Group type ids; 5 (PROJECT) is what project tools create and expect. */
+export declare const GROUP_TYPES: {
+    readonly GENERAL: 1;
+    readonly TEAM: 3;
+    readonly SUPPORT: 4;
+    readonly PROJECT: 5;
+};
+export type TaskStatus = (typeof TASK_STATUSES)[number];
+export type Priority = (typeof PRIORITIES)[number];
+export type ProjectStatus = (typeof PROJECT_STATUSES)[number];
+/** Payload for the enums tool, so callers can discover these without guessing. */
+export declare function enumReference(): {
+    task_status: readonly ["backlog", "new", "research", "inprogress", "pendingreview", "inreview", "testing", "waitingcustomer", "waitingteammember", "onhold", "cancelled", "completed"];
+    priority: readonly ["low", "moderate", "important", "urgent", "critical"];
+    project_status: readonly ["new", "inprogress", "complete"];
+    prospect_status: readonly ["new", "firstcontact", "negotiation", "pending", "won", "lost", "spam"];
+    group_types: {
+        readonly GENERAL: 1;
+        readonly TEAM: 3;
+        readonly SUPPORT: 4;
+        readonly PROJECT: 5;
+    };
+    notes: string[];
+};

package/dist/enums.js

@@ -0,0 +1,67 @@
+/**
+ * Status and priority vocabularies as the platform actually defines them.
+ *
+ * Source of truth is the ViviScape Work UI, not guesswork:
+ *   ClockWyzWeb/Views/App/Tasks.cshtml     -- task status + priority selects
+ *   ClockWyzWeb/Views/App/Projects.cshtml  -- task editor and project status selects
+ * Cross-checked against live rows from account 1 (211 projects, 6 open tasks).
+ *
+ * Two traps worth knowing:
+ *  - Tasks complete as "completed"; projects complete as "complete".
+ *  - Priority is low/moderate/important/urgent/critical. It is NOT
+ *    low/medium/high, which is what this server's task_add used to claim.
+ */
+/** Task status values, in board order. */
+export const TASK_STATUSES = [
+    'backlog',
+    'new',
+    'research',
+    'inprogress',
+    'pendingreview',
+    'inreview',
+    'testing',
+    'waitingcustomer',
+    'waitingteammember',
+    'onhold',
+    'cancelled',
+    'completed',
+];
+/** Task and project priority values, ascending. */
+export const PRIORITIES = ['low', 'moderate', 'important', 'urgent', 'critical'];
+/**
+ * Project (group) status values. Narrower than task status, and note "complete"
+ * rather than "completed". An empty status reads as "Undetermined" in the UI.
+ */
+export const PROJECT_STATUSES = ['new', 'inprogress', 'complete'];
+/** Prospect pipeline stages, from the CRM tools. */
+export const PROSPECT_STATUSES = [
+    'new',
+    'firstcontact',
+    'negotiation',
+    'pending',
+    'won',
+    'lost',
+    'spam',
+];
+/** Group type ids; 5 (PROJECT) is what project tools create and expect. */
+export const GROUP_TYPES = {
+    GENERAL: 1,
+    TEAM: 3,
+    SUPPORT: 4,
+    PROJECT: 5,
+};
+/** Payload for the enums tool, so callers can discover these without guessing. */
+export function enumReference() {
+    return {
+        task_status: TASK_STATUSES,
+        priority: PRIORITIES,
+        project_status: PROJECT_STATUSES,
+        prospect_status: PROSPECT_STATUSES,
+        group_types: GROUP_TYPES,
+        notes: [
+            'Tasks use "completed"; projects use "complete".',
+            'Priority is low/moderate/important/urgent/critical -- not low/medium/high.',
+            'An empty project status displays as "Undetermined".',
+        ],
+    };
+}