@polycode-projects/the-mechanical-code-talker 0.9.0 → 0.9.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polycode-projects/the-mechanical-code-talker",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "private": false,
   "type": "module",
   "description": "The Mechanical Code Talker (tmct) — a tolerant, offline, $0 chat surface that guides you toward precision queries about a software repository. ELIZA/PARRY-style but domain-obsessed with code. No model calls; no codebase index of its own.",

package/src/ask.mjs

@@ -821,15 +821,19 @@ function parseRelationalOrQualified(w, lc, nlp, depth) {
   while (i < lc.length && QUALIFIERS[lc[i]]) { quals.push(lc[i]); i += 1; }
   const noun = i < lc.length ? entityNoun(lc[i]) : null;
   if (!noun) {
-    // an unknown adjective sitting in the qualifier slot, right before a known
-    // entity noun ("which shiny methods", "static frobnicated functions") — an
-    // honest miss that NAMES the supported qualifiers, never a guess (PLAN P3).
-    // STOPWORDS are excluded so a normal question auxiliary in that position ("what
-    // DID commit X touch", "what WAS in <sha>") is left for the existing parser, not
-    // mistaken for an unknown qualifier.
-    if ((framed || quals.length) && i + 1 < lc.length && /^[a-z]+$/.test(lc[i])
-      && !VERB_TO_KIND[lc[i]] && !STOPWORDS.has(lc[i]) && entityNoun(lc[i + 1])) {
-      return { node: "miss", reason: `unknown qualifier "${lc[i]}" — supported: ${Object.keys(QUALIFIERS).join(", ")}` };
+    // An unknown adjective sitting in the qualifier slot, right before a known entity
+    // noun ("list payment modules", "which shiny methods") — try it as a predicate-find
+    // fuzzy term FIRST ("payment" filtering Module labels/attributes) before declaring
+    // it an unrecognized qualifier: a real, honest answer beats an error message, and a
+    // genuine zero-hit still renders find's own honest "no <noun> found matching <term>"
+    // miss (never a confident-wrong guess either way — same discipline as everywhere
+    // else this AST node is produced). STOPWORDS are excluded so a normal question
+    // auxiliary in that position ("what DID commit X touch") is left for the existing
+    // parser, not mistaken for a term.
+    const nextNoun = i + 1 < lc.length ? entityNoun(lc[i + 1]) : null;
+    if ((framed || quals.length) && nextNoun && /^[a-z]+$/.test(lc[i])
+      && !VERB_TO_KIND[lc[i]] && !STOPWORDS.has(lc[i])) {
+      return { node: "find", entityType: nextNoun.entityType, term: w[i] };
     }
     return null;                                   // no subject entity → not this shape
   }
@@ -2286,11 +2290,16 @@ function renderCore(parsed, result) {
   }
   if (result.ambiguous) {
     // the candidates say what KIND of thing is ambiguous — a shared commit-sha
-    // prefix must read "more than one commit", not "module".
+    // prefix must read "more than one commit", not "module". Name the actual
+    // candidates in the prose (not just the structured `candidates` field) —
+    // "narrow the term" is not itself actionable if the reader can't see what
+    // it's ambiguous between; mirrors the mentionsShape branch's listing above.
     const pool = [result.objMatch, ...(result.candidates || [])].filter(Boolean);
     const noun = pool.length && pool.every((i) => i.class === "Commit") ? "commit" : "module";
+    const shown = pool.slice(0, OVERFLOW_CAP).map((i) => i.label);
+    const extra = pool.length > OVERFLOW_CAP ? `, …and ${pool.length - OVERFLOW_CAP} more` : "";
     return {
-      content: `"${parsed.object}" matches more than one ${noun} ambiguously — please narrow the term.`,
+      content: `"${parsed.object}" matches more than one ${noun} ambiguously — did you mean ${listJoin(shown)}${extra}? Try one of those.`,
       miss: false, ambiguous: true, candidates: pool.map((i) => i.label),
     };
   }

package/src/chat.mjs

@@ -2987,6 +2987,12 @@ export async function runChat({
   gitRoot = gitToplevel,
   ephemeral = false,
 } = {}) {
+  // createSession's first-run seed (~2-3s, corpus/seon + ConceptNet) produces ZERO
+  // output until it fully resolves — found live: an operator reported `npm run chat`
+  // appearing to hang with total silence. This one line is cheap on every run (a
+  // fast subsequent run just flashes it briefly) and removes the "is this even
+  // running" uncertainty during the one case that's genuinely slow.
+  output.write("tmct — starting…\n");
   const session = await createSession({ repoPath, source, env, cwd, gitRoot, ephemeral });
 
   const dim = (s) => (env.NO_COLOR || !output.isTTY ? s : `\x1b[2m${s}\x1b[0m`);

package/src/tui/app.mjs

@@ -231,6 +231,12 @@ export function App({ session }) {
  *  which also triggers the memory fold — stream flush). Returns
  *  { logFile, sidecarFile, turns } exactly like runChat. */
 export async function runTui({ repoPath, stdout = process.stdout, stdin = process.stdin, ...sessionOpts } = {}) {
+  // Same reasoning as runChat's equivalent line (src/chat.mjs): createSession's
+  // first-run seed is silent for ~2-3s, and nothing is written to the terminal
+  // (not even the alternate-screen switch below) until it resolves — this was
+  // reported live as an apparent hang. One cheap line on the PRIMARY screen,
+  // before the alt-screen switch, so there's visible proof of life immediately.
+  stdout.write("tmct — starting…\n");
   const session = await createSession({ repoPath, ...sessionOpts });
   stdout.write("\x1b[?1049h\x1b[H"); // alternate screen buffer + home — a clean full-screen canvas
   const app = render(h(App, { session }), { stdout, stdin, exitOnCtrlC: true });