tewip-ai 0.70.5 → 0.70.7

package/dist/engine/quality/write-command.js

@@ -62,19 +62,52 @@ ${noModelHelp()}`);
         const fileName = framework.fileFor(scenario.id);
         const file = join(framework.testDir, fileName);
         if (existsSync(file) || (cmd.moveTo && existsSync(join(cmd.moveTo, fileName)))) {
-            results.push({ id: scenario.id, title: scenario.title, file, outcome: { kind: 'rejected', reason: `${fileName} already exists; left untouched`, repairs: 0, passedReliably: false } });
+            // Every file this command writes carries "tewip" in its name, so one already sitting here is
+            // one of its own - an unverified draft from a run that did not finish, not a test the team
+            // wrote. Calling that "left untouched" sounds like a decision and hides that the file is in
+            // the test folder, where the suite is running it.
+            //
+            // Matched case-insensitively on the whole name rather than as a prefix, because only the
+            // JavaScript frameworks produce `tewip-ls-002.spec.ts`: pytest gives `test_tewip_ls_002.py`
+            // and JUnit `TewipLs002Test.java`, and a prefix check would have handed Python and Java teams
+            // the misleading message this fix exists to remove.
+            const mine = /tewip/i.test(fileName);
+            results.push({
+                id: scenario.id,
+                title: scenario.title,
+                file,
+                outcome: {
+                    kind: 'rejected',
+                    reason: mine
+                        ? `${fileName} is already here from a run that did not finish, and was never verified. It is in your test folder, so your suite is running it: delete it, or move it to .tewip/drafts/, then ask again.`
+                        : `${fileName} already exists and was written by somebody else; left untouched`,
+                    repairs: 0,
+                    passedReliably: false,
+                },
+            });
             continue;
         }
         console.error(`  ${scenario.id} ${scenario.title}`);
-        // Stopped part-way (Ctrl+C), a draft that was never verified must not stay in the project.
+        // A draft that was never verified must not stay in the project, however the run ended.
+        //
+        // SIGINT and SIGTERM were covered; nothing else was. A run of this interrupted another way -
+        // a closed pipe, an uncaught throw, a kill - left the draft in the **test folder**, where the
+        // project's own suite then runs it. Seen for real: a two-scenario run was cut short by a broken
+        // shell command, the suite went from green to red, and the next `write` reported the leftover as
+        // "already exists; left untouched", which reads like a decision rather than a casualty.
+        //
+        // `renameSync` is synchronous, so an `exit` handler can still do it: that covers every way out.
+        const rescue = () => {
+            if (!existsSync(file))
+                return;
+            mkdirSync(drafts, { recursive: true });
+            renameSync(file, join(drafts, fileName));
+        };
         const leaveNothing = () => {
-            if (existsSync(file)) {
-                mkdirSync(drafts, { recursive: true });
-                renameSync(file, join(drafts, fileName));
-            }
+            rescue();
             process.exit(130);
         };
-        process.once('SIGINT', leaveNothing).once('SIGTERM', leaveNothing);
+        process.once('SIGINT', leaveNothing).once('SIGTERM', leaveNothing).once('exit', rescue);
         let outcome;
         try {
             ({ outcome } = await writeAndVerify(model, { framework, fileName, pages, feature: saved.feature, code, houseRules: guidanceFor(loadStandards(cmd.root), fileName) }, scenario, file, { runs: cmd.runs, repairs: cmd.repairs, mutateSource: cmd.mutateSource, log: (l) => console.error(l) }));
@@ -83,7 +116,7 @@ ${noModelHelp()}`);
             outcome = { kind: 'rejected', reason: `stopped: ${error.message}`, repairs: 0, passedReliably: false };
         }
         finally {
-            process.off('SIGINT', leaveNothing).off('SIGTERM', leaveNothing);
+            process.off('SIGINT', leaveNothing).off('SIGTERM', leaveNothing).off('exit', rescue);
         }
         // Some runners take minutes per run (Angular rebuilds the app for every `ng test`): say how long
         // the rest will take, so a slow run is not mistaken for a stuck one.

package/dist/engine/work/jira-command.js

@@ -54,6 +54,35 @@ export async function runJira(cmd) {
         return;
     }
     const config = jiraFromEnv();
+    // Without a tracker, show what would be filed anyway.
+    //
+    // This file's own comment says "It shows what it would create and creates nothing until asked",
+    // and the help text says "Shows what it would create; --create actually files them" - but the
+    // refusal below ran whatever was asked, so a person who only wanted to see the list had to go and
+    // get a Jira account first. `bugs`, which does the same job for failures, has always answered this
+    // case: "No tracker was contacted: this is what would be filed."
+    //
+    // What a dry run genuinely cannot do without a server is say which scenarios are **already**
+    // filed, because that answer lives in the tracker. So it says so rather than implying the whole
+    // list is new work.
+    if (!config?.token && !cmd.create) {
+        const planned = JSON.parse(readFileSync(cmd.planFile, 'utf8'));
+        const wanted = chosen(planned.plan, cmd.only);
+        if (wanted.length === 0)
+            throw new Error(cmd.only.length ? `none of ${cmd.only.join(', ')} is in ${cmd.planFile}` : 'every scenario in the plan is already covered by a test');
+        console.log([
+            `Plan: ${planned.plan.title}`,
+            `Project: ${cmd.projectKey || '(none given)'}`,
+            '',
+            'No tracker was contacted: this is what would be filed.',
+            ...wanted.map((scenario) => `  ${scenario.id}  would create: ${scenario.id} ${scenario.title}`),
+            '',
+            `${wanted.length} item(s). Tewip could not check which of these you have already filed - that answer is in the tracker, not in the plan - so read the list as everything, not as new work.`,
+            'To file them, set a tracker up and add --create:',
+            jiraHelp(),
+        ].join(String.fromCharCode(10)));
+        return;
+    }
     if (!config)
         throw new Error(jiraHelp());
     if (!config.token)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tewip-ai",
-  "version": "0.70.5",
+  "version": "0.70.7",
   "mcpName": "io.github.hmamut39/tewip",
   "description": "Tewip finds why each failing test failed - real bug, flaky test, environment, test data or changed selector - for any stack, from the command line, CI, or your editor.",
   "keywords": [