@cat-factory/app 0.23.1 → 0.24.0

package/app/components/board/AddTaskModal.vue

@@ -42,6 +42,9 @@ const container = computed(() =>
 const title = ref('')
 const description = ref('')
 const saving = ref(false)
+// Whether the user marks this as a purely technical task up front (a refactor /
+// non-functional change). Left off ⇒ the engine infers it from the spec phase.
+const technical = ref(false)
 
 // The kind of task being created. `recurring` is special: it is created through the
 // recurring-pipeline schedule flow (a schedule on the service frame), so picking it
@@ -276,6 +279,7 @@ watch(open, (isOpen) => {
   description.value = ''
   saving.value = false
   taskType.value = 'feature'
+  technical.value = false
   severity.value = ''
   stepsToReproduce.value = ''
   timeboxHours.value = undefined
@@ -339,6 +343,7 @@ async function add() {
       ...(Object.keys(agentConfigValues.value).length
         ? { agentConfig: agentConfigValues.value }
         : {}),
+      ...(technical.value ? { technical: true } : {}),
     })
     if (block) {
       const failed = await linkPending(block.id, pendingContext.value)
@@ -448,6 +453,19 @@ async function add() {
             />
           </UFormField>
 
+          <UCheckbox v-model="technical" name="technical">
+            <template #label>
+              <span class="text-sm text-slate-200">Technical task</span>
+            </template>
+            <template #description>
+              <span class="text-[11px] text-slate-500">
+                A refactor / non-functional / internal change. The implementer treats the task
+                definition as primary and the spec as a regression reference; leave off to let the
+                spec phase decide.
+              </span>
+            </template>
+          </UCheckbox>
+
           <!-- Per-type fields. -->
           <div v-if="taskType === 'bug'" class="grid grid-cols-2 gap-3">
             <UFormField label="Severity">

package/app/components/panels/inspector/TaskRunSettings.vue

@@ -173,6 +173,31 @@ const commentOnPrOpenLabel = computed(() =>
 const resolveOnMergeLabel = computed(() =>
   writebackLabel(props.block.trackerResolveOnMerge, tracker.settings.writebackResolveOnMerge),
 )
+
+// ---- technical label (tri-state) -------------------------------------------
+// Whether this is a purely technical task (the implementer then treats the task
+// definition as primary and the spec as a regression reference). Tri-state: Unset lets
+// the engine infer it from the spec phase; Technical / Business are authoritative human
+// choices the engine never overrides. `null` clears back to Unset.
+function setTechnical(value: boolean | null) {
+  board.updateBlock(props.block.id, { technical: value })
+}
+const technicalMenu = [
+  [
+    {
+      label: 'Unset (auto-detect)',
+      icon: 'i-lucide-rotate-ccw',
+      onSelect: () => setTechnical(null),
+    },
+    { label: 'Technical', icon: 'i-lucide-wrench', onSelect: () => setTechnical(true) },
+    { label: 'Business', icon: 'i-lucide-briefcase', onSelect: () => setTechnical(false) },
+  ],
+]
+const technicalLabel = computed(() => {
+  if (props.block.technical === true) return 'Technical'
+  if (props.block.technical === false) return 'Business'
+  return 'Unset (auto-detect)'
+})
 </script>
 
 <template>
@@ -302,6 +327,38 @@ const resolveOnMergeLabel = computed(() =>
       </p>
     </div>
 
+    <!-- technical label (tri-state) -->
+    <div>
+      <div class="mb-1 flex items-center justify-between">
+        <span class="text-[11px] font-semibold uppercase tracking-wide text-slate-400">
+          Task kind
+        </span>
+        <UDropdownMenu :items="technicalMenu">
+          <UButton
+            size="xs"
+            variant="ghost"
+            color="neutral"
+            icon="i-lucide-wrench"
+            trailing-icon="i-lucide-chevron-down"
+          >
+            {{ technicalLabel }}
+          </UButton>
+        </UDropdownMenu>
+      </div>
+      <div class="text-[11px] text-slate-500">
+        <template v-if="block.technical === true">
+          Technical — the implementer treats the task definition as primary and the spec as a
+          regression reference; the spec-writer may produce no business specs.
+        </template>
+        <template v-else-if="block.technical === false">
+          Business — the specification leads, as usual.
+        </template>
+        <template v-else>
+          Auto-detect — inferred from the spec phase. Set it explicitly to override.
+        </template>
+      </div>
+    </div>
+
     <!-- issue-tracker writeback overrides -->
     <div>
       <div class="mb-1 flex items-center justify-between">

package/app/composables/api/board.ts

@@ -42,6 +42,7 @@ export function boardApi({ http, ws }: ApiContext) {
         modelPresetId?: string
         pipelineId?: string
         agentConfig?: Record<string, string>
+        technical?: boolean
       },
     ) => http<Block>(`${ws(workspaceId)}/blocks/${blockId}/tasks`, { method: 'POST', body }),
 

package/app/stores/board.ts

@@ -80,6 +80,7 @@ export const useBoardStore = defineStore('board', () => {
       modelPresetId?: string
       pipelineId?: string
       agentConfig?: Record<string, string>
+      technical?: boolean
     },
   ): Promise<Block | undefined> {
     if (!getBlock(containerId)) return
@@ -92,6 +93,7 @@ export const useBoardStore = defineStore('board', () => {
       ...(options?.modelPresetId ? { modelPresetId: options.modelPresetId } : {}),
       ...(options?.pipelineId ? { pipelineId: options.pipelineId } : {}),
       ...(options?.agentConfig ? { agentConfig: options.agentConfig } : {}),
+      ...(options?.technical ? { technical: true } : {}),
     })
     upsert(block)
     return block

package/app/types/domain.ts

@@ -132,6 +132,15 @@ export interface Block {
   taskType?: TaskType
   /** task-only: small per-type form fields (bug severity, spike timebox, …). */
   taskTypeFields?: TaskTypeFields | null
+  /**
+   * task-only: TECHNICAL label. `true` ⇒ a refactor / non-functional / internal change
+   * (the implementer treats the task definition as primary, specs as a regression
+   * reference; the spec-writer may produce no business specs). `false` ⇒ a business task.
+   * `null`/absent ⇒ not yet determined — the engine may infer it from the spec phase. A
+   * human-set value is authoritative and never overridden; the inspector toggle is
+   * tri-state (unset / technical / business) and sends `null` for "unset".
+   */
+  technical?: boolean | null
   /** ids of best-practice prompt fragments folded into this block's agent prompts. */
   fragmentIds?: string[]
   /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.23.1",
+  "version": "0.24.0",
   "description": "Reusable Nuxt layer for the Agent Architecture Board SPA (components, stores, composables, pages). Consume it from a thin deployment app via `extends: ['@cat-factory/app']` and point it at your backend with NUXT_PUBLIC_API_BASE. See deploy/frontend for an example.",
   "repository": {
     "type": "git",