fix: address CI lint failures in chat routes and grok MCP schema server

This commit is contained in:
gsxdsm
2026-07-11 23:05:11 -07:00
parent 6267a762a4
commit de8d00a475
2 changed files with 10 additions and 3 deletions

View File

@@ -4,14 +4,19 @@ import { mkdir, rm, writeFile } from "node:fs/promises";
import { basename, join, resolve } from "node:path";
import { THINKING_LEVELS, type EnrichedChatSession, type ChatAttachment } from "@fusion/core";
import { ApiError, badRequest, notFound } from "../api-error.js";
import { resolveProjectChatContext } from "../chat-project-services.js";
/*
FNXC:GrokAcp 2026-07-11-18:30:
List/create and ChatManager share resolveProjectChatContext (not getOrCreateProjectStore /
getOrCreateScopedChatStore at this layer). Direct imports of those helpers were leftover after
the store-alignment fix and failed lint as unused; keep manager construction on the resolved
store/chatStore pair only.
*/
import { getOrCreateScopedChatManager, resolveProjectChatContext } from "../chat-project-services.js";
import { CHAT_ALLOWED_MIME_TYPES, CHAT_MAX_ATTACHMENT_SIZE } from "./chat-attachment-config.js";
import { rateLimit, RATE_LIMITS } from "../rate-limit.js";
import { writeSSEEvent, type SessionBufferedEvent } from "../sse-buffer.js";
import { TASK_PLANNER_CHAT_AGENT_ID_PREFIX } from "../chat.js";
import type { ApiRoutesContext } from "./types.js";
import { getOrCreateScopedChatManager, getOrCreateScopedChatStore } from "../chat-project-services.js";
import { getOrCreateProjectStore } from "../project-store-resolver.js";
interface ChatRouteDeps {
parseLastEventId: (req: import("express").Request) => number | undefined;

View File

@@ -12,6 +12,8 @@ Grok actually invokes MCP tools/call itself.
const fs = require("fs");
const http = require("http");
const readline = require("readline");
// FNXC:GrokAcp 2026-07-11-18:30: CJS has no global URL under eslint no-undef; use node:url.
const { URL } = require("node:url");
const schemaPath = process.argv[2];
const bridgeUrl = process.env.FUSION_GROK_TOOL_BRIDGE_URL;