feat(taxonomy): add writing_report to the trajectory component vocabulary (#1153)

Author: stateofkate

backend/api/services/blocks/analyzer/trajectory/trajectory_component_block.py

@@ -19,9 +19,10 @@ class ExploreTrajectoryBlockTaxonomy(str, enum.Enum):
 
 
 class ImplementTrajectoryBlockTaxonomy(str, enum.Enum):
-    # Ordered as the work happens: plan, replan, build, correct, test, debug.
-    # PLAN_CORRECTION sits beside WRITING_PLAN so the model reads the two as a
-    # pair; the flat vocabulary below preserves this order in the prompt.
+    # Ordered as the work happens: plan, replan, build, correct, test, debug,
+    # report. PLAN_CORRECTION sits beside WRITING_PLAN so the model reads the
+    # two as a pair; the flat vocabulary below preserves this order in the
+    # prompt. WRITING_REPORT is last because it is what a run ends with.
     WRITING_PLAN = "writing_plan"
     PLAN_CORRECTION = "plan_correction"
     IMPLEMENTING = "implementing"
@@ -31,6 +32,7 @@ class ImplementTrajectoryBlockTaxonomy(str, enum.Enum):
     TESTING_CUSTOM = "testing_custom"
     TESTING_EDGE_CASES = "testing_edge_cases"
     DEBUGGING = "debugging"
+    WRITING_REPORT = "writing_report"
 
 
 # One flat vocabulary built from the two sub-enums, so a component carries a

frontend/src/app/globals.css

@@ -237,6 +237,12 @@
     --tc-testing-custom: #c94592;
     --tc-testing-edge: #852c5e;
     --tc-debugging: #eb6834;
+    /* Dark, desaturated brown: writing_report is terminal bookkeeping, so it
+       recedes rather than competing. The warm half is already past the
+       categorical limit and every warm hue between implementing (43deg) and
+       debugging (17deg) is taken, so this separates on value and chroma
+       instead -- sat 0.30 against their 0.92/0.82, and much darker. */
+    --tc-writing-report: #5c4033;
   }
 
   .dark {
@@ -305,6 +311,7 @@
     --tc-testing-custom: #d55181;
     --tc-testing-edge: #9d3973;
     --tc-debugging: #d95926;
+    --tc-writing-report: #836b5c;
   }
 
   /*

frontend/src/lib/trajectory-metrics.ts

@@ -105,6 +105,7 @@ const COMPONENT_COLOR_VARS: Record<string, string> = {
   testing_custom: "var(--tc-testing-custom)",
   testing_edge_cases: "var(--tc-testing-edge)",
   debugging: "var(--tc-debugging)",
+  writing_report: "var(--tc-writing-report)",
   // Retired kinds, kept so stored summaries keep their fixed color rather than
   // falling through to appearance-order phase slots. Each shares the slot its
   // replacement took over; the two vocabularies never co-occur in one summary.

frontend/src/lib/trajectory-segments.ts

@@ -19,6 +19,7 @@ const COMPONENT_LABELS: Record<TrajectoryComponentKind, string> = {
   testing_custom: "Running custom tests",
   testing_edge_cases: "Testing edge cases",
   debugging: "Debugging",
+  writing_report: "Reporting",
   // Retired kinds, kept so stored summaries still render a real label.
   thinking_correction: "Correcting course",
   thinking_diagnose: "Diagnosing",

frontend/src/lib/types.ts

@@ -712,6 +712,7 @@ export type TrajectoryComponentKind =
   | "testing_custom"
   | "testing_edge_cases"
   | "debugging"
+  | "writing_report"
   // Retired from the backend enum, but stored summaries still carry them.
   | "thinking_correction"
   | "thinking_diagnose"