COnvey the temporarity of the logger service through a comment. Impro…

…ve import hygiene

packages/api/ai/generate.mts

@@ -13,7 +13,7 @@ import Path from 'node:path';
 import { PROMPTS_DIR } from '../constants.mjs';
 import { encode, decodeCells } from '../srcmd.mjs';
 import { buildProjectXml, type FileContent } from '../ai/app-parser.mjs';
-import { AppGenerationLog, logAppGeneration } from './logger.mjs';
+import { type AppGenerationLog, logAppGeneration } from './logger.mjs';
 
 const makeGenerateSrcbookSystemPrompt = () => {
   return readFileSync(Path.join(PROMPTS_DIR, 'srcbook-generator.txt'), 'utf-8');

packages/api/ai/logger.mts

@@ -5,7 +5,14 @@ export type AppGenerationLog = {
   llm_response: any;
 };
 
-async function logAppGeneration(log: AppGenerationLog): Promise<void> {
+/*
+ * Log the LLM request / response to the analytics server.
+ * For now this server is a custom implemention, consider moving to
+ * a formal LLM log service, or a generic log hosting service.
+ * In particular, this will not scale well when we split up app generation into
+ * multiple steps. We will need spans/traces at that point.
+ */
+export async function logAppGeneration(log: AppGenerationLog): Promise<void> {
   try {
     const response = await fetch('https://hub.srcbook.com/api/app_generation_log', {
       method: 'POST',
@@ -22,5 +29,3 @@ async function logAppGeneration(log: AppGenerationLog): Promise<void> {
     console.error('Error sending app generation log:', error);
   }
 }
-
-export { logAppGeneration };