ttsc 0.18.3 → 0.18.4

package/cmd/ttscgraph/main.go

@@ -1,9 +1,7 @@
-// Command ttscgraph builds the checker-resolved code graph for a project and
-// prints it as JSON (`ttscgraph dump`). It is the native data provider for
-// @ttsc/graph: the JavaScript launcher runs `ttscgraph dump` once, then serves
-// the Model Context Protocol from the in-memory graph itself. The MCP server,
-// its tools, and their schemas live in @ttsc/graph (TypeScript); nothing here
-// answers tool calls.
+// Command ttscgraph builds the checker-resolved code graph for a project. The
+// one-shot `dump` command prints JSON; the internal `serve` command keeps an
+// incremental compiler session resident for @ttsc/graph. MCP tools and schemas
+// remain in the TypeScript package.
 package main
 
 import (
@@ -35,9 +33,9 @@ func main() {
   os.Exit(run(os.Args[1:]))
 }
 
-// run dispatches the top-level command and returns an exit code. ttscgraph is
-// dump-only; anything that is not help/version/dump prints usage and exits 2,
-// since serving MCP is the launcher's job.
+// run dispatches the top-level command and returns an exit code. Anything that
+// is not help, version, dump, or the internal serve protocol prints usage and
+// exits 2; serving MCP itself remains the launcher's job.
 func run(args []string) int {
   if len(args) > 0 {
     switch args[0] {
@@ -49,6 +47,8 @@ func run(args []string) int {
       return 0
     case "dump":
       return runDump(args[1:])
+    case "serve":
+      return runServe(args[1:])
     }
   }
   printHelp(stderr)
@@ -72,12 +72,12 @@ func printHelp(w io.Writer) {
   fmt.Fprintln(w, strings.TrimSpace(`
 ttscgraph — checker-resolved code graph for ttsc.
 
-Builds the project's code graph and prints it as JSON. The @ttsc/graph launcher
-runs this and serves the Model Context Protocol from the result; the MCP tools
-live in @ttsc/graph, not here.
+Builds the project's code graph as JSON or keeps an incremental compiler session
+for the @ttsc/graph launcher. The MCP tools live in @ttsc/graph, not here.
 
 Usage:
   ttscgraph dump [--cwd <dir>] [--tsconfig <path>] [--pretty] > graph.json
+  ttscgraph serve [--cwd <dir>] [--tsconfig <path>]
   ttscgraph --version
   ttscgraph --help
 
@@ -87,5 +87,11 @@ Dump:
   --cwd <dir>          Project root (defaults to the process working directory).
   --tsconfig <path>    Project tsconfig path (default: tsconfig.json).
   --pretty             Indent the JSON output.
+
+Serve:
+  serve                Internal newline-delimited snapshot protocol used by
+                       @ttsc/graph. Keeps the compiler Program resident, applies
+                       source edits incrementally, and reloads on structural
+                       project changes.
 `))
 }

package/cmd/ttscgraph/run_help_version_and_bad_flags_exit_codes_test.go

@@ -8,9 +8,10 @@ import (
 )
 
 // TestRunHelpVersionAndBadFlagsExitCodes verifies the top-level run dispatcher
-// returns the documented exit codes for the dump-only command surface: help and
-// version short-circuit to 0, an unknown command prints usage and exits 2, and a
-// dump that cannot resolve its working directory exits 2 with an explanation.
+// returns the documented exit codes for the command surface: help and version
+// short-circuit to 0, an unknown command prints usage and exits 2, and dump or
+// serve invocations that cannot parse flags or resolve their working directory
+// exit 2 with an explanation.
 //
 // These are the non-load paths a user hits with a typo or `--help`; each must
 // resolve to a code without building a Program. The getwd seam stands in for an
@@ -19,8 +20,8 @@ import (
 //
 //  1. run --help and run --version exit 0, printing the command name / version.
 //  2. run --bogus (unknown command) exits 2 and prints usage.
-//  3. run dump --nope exits 2 (dump flag parse failure).
-//  4. With getwd forced to fail, run dump exits 2 and explains why.
+//  3. run dump --nope and run serve --nope exit 2 (flag parse failure).
+//  4. With getwd forced to fail, run dump and run serve exit 2 and explain why.
 func TestRunHelpVersionAndBadFlagsExitCodes(t *testing.T) {
   oldStdout, oldStderr, oldGetwd := stdout, stderr, getwd
   defer func() { stdout, stderr, getwd = oldStdout, oldStderr, oldGetwd }()
@@ -62,6 +63,13 @@ func TestRunHelpVersionAndBadFlagsExitCodes(t *testing.T) {
     t.Fatalf("run dump --nope exit = %d, want 2", code)
   }
 
+  // An unknown serve flag is an invalid invocation: serve's flag.Parse fails -> 2.
+  var serveFlagErr bytes.Buffer
+  stderr = &serveFlagErr
+  if code := run([]string{"serve", "--nope"}); code != 2 {
+    t.Fatalf("run serve --nope exit = %d, want 2", code)
+  }
+
   // A getwd failure (no --cwd given) is an invalid invocation -> 2, explained.
   var wdErr bytes.Buffer
   stderr = &wdErr
@@ -72,4 +80,14 @@ func TestRunHelpVersionAndBadFlagsExitCodes(t *testing.T) {
   if !strings.Contains(wdErr.String(), "could not resolve working directory") {
     t.Fatalf("getwd failure did not explain itself:\n%s", wdErr.String())
   }
+
+  // serve resolves the working directory the same way before touching stdin.
+  var serveWdErr bytes.Buffer
+  stderr = &serveWdErr
+  if code := run([]string{"serve"}); code != 2 {
+    t.Fatalf("run serve with getwd failure exit = %d, want 2", code)
+  }
+  if !strings.Contains(serveWdErr.String(), "could not resolve working directory") {
+    t.Fatalf("serve getwd failure did not explain itself:\n%s", serveWdErr.String())
+  }
 }