@turri-dev/cli 0.1.4-next.ebd337a → 0.1.4-next.fa9223b

package/dist/loop-cli.js

@@ -85,6 +85,10 @@ async function runLoopReporting(options) {
             console.log(`${mark} ${job.id} ${pulseName(job)} - ${job.status}`);
             if (job.status !== "succeeded")
                 console.log(c.dim((job.announce ?? job.report ?? job.error ?? "").trim()));
+            // Its report is not printed when it succeeds, and nobody is asked here: the spec gaps its agents met are said.
+            else
+                for (const gap of job.details?.specGaps ?? [])
+                    console.log(c.yellow(`  spec gap: ${gap.question}`), c.dim(`Meanwhile: ${gap.assumption}`));
             report?.write();
         },
     });

package/dist/regenerate/loop.js

@@ -597,7 +597,14 @@ export function createWorkLoop(options) {
                 }
                 return {
                     report: released !== undefined ? `${report}\n\n${released}` : report,
-                    details: { passed: result.landed, landed: result.landed, ...(released !== undefined ? { released: true } : {}), ...(result.story !== undefined ? { story: result.story } : {}) },
+                    details: {
+                        passed: result.landed,
+                        landed: result.landed,
+                        ...(released !== undefined ? { released: true } : {}),
+                        ...(result.story !== undefined ? { story: result.story } : {}),
+                        // The spec gaps its agents met, for a headless run to say - in the chat the report puts them to the person.
+                        ...(result.specGaps !== undefined && result.specGaps.length > 0 ? { specGaps: result.specGaps } : {}),
+                    },
                 };
             },
         });
@@ -1565,7 +1572,7 @@ const defaultConformanceRunner = async (job, onDelta) => {
         writeTestsRecord(result.conformanceDir, job.planned.step.tree);
         recordHistory(job.buildDir, `conformance tests: ${job.planned.title}`);
     }
-    return { landed: result.passed, report: describeSpecDiffConformance(result) };
+    return { landed: result.passed, report: describeSpecDiffConformance(result), ...(result.specGaps !== undefined ? { specGaps: result.specGaps } : {}) };
 };
 /** A job as a spec diff render, landed on its unit tests: conformance is a track of its own. */
 const defaultRunner = async (job, onDelta) => {
@@ -1581,7 +1588,9 @@ const defaultRunner = async (job, onDelta) => {
         onDelta,
     });
     // Landed code can be tried.
-    return { landed: result.passed, report: withTryItLine(describeSpecDiff(result), result.passed && result.restructured !== true), story: codeStory(result) };
+    return { landed: result.passed, report: withTryItLine(describeSpecDiff(result), result.passed && result.restructured !== true), story: codeStory(result),
+        ...(result.specGaps !== undefined ? { specGaps: result.specGaps } : {}),
+    };
 };
 /** How a code pulse went, for its line in the notes: the rounds it took, its test runs, what the debugger found. */
 export function codeStory(result) {

package/dist/regenerate/spec-map-view.js

@@ -323,20 +323,13 @@ function wrapped(text, width, colour = (line) => line) {
         .flatMap((line) => (line === "" ? [""] : wrapTextWithAnsi(line, Math.max(10, width - CONTINUED.length))))
         .map((line) => `${CONTINUED}${colour(line)}`);
 }
-/**
- * Whether a new item is drawn as an addition: only beside code already built - a spec diff that adds it - never when the
- * whole page is new, built for the first time or from scratch, where green would say nothing.
- */
-function addedToBuilt(item, page) {
-    return item.state === "new" && page.items.some((other) => other.state === "built" || other.state === "changed" || other.state === "removed");
-}
 /** All of an item, opened: the rest of its text against the code's, and its acceptance tests. Where it stands is beside its mark. */
-function detailLines(item, width, style, added) {
+function detailLines(item, width, style) {
     const lines = [];
     // The rest of its text - its first line is the row - against the record's, for a change.
     const rest = item.state === "changed" ? lineDiff(item.was ?? "", item.text).slice(1) : item.text.split("\n").slice(1).map((line) => ({ was: line, now: line }));
     for (const line of rest) {
-        const drawn = item.state === "removed" ? style.removed(strike(line.now ?? "")) : item.state === "changed" ? diffLine(line, style) : added ? style.added(line.now ?? "") : highlighted(line.now ?? "", style);
+        const drawn = item.state === "removed" ? style.removed(strike(line.now ?? "")) : item.state === "changed" ? diffLine(line, style) : highlighted(line.now ?? "", style);
         lines.push(...wrapped(drawn, width));
     }
     if (item.acceptance.length > 0) {
@@ -483,9 +476,7 @@ export function specMapLines(pages, state, width, style, _jobs = [], now = Date.
             ? style.removed(strike(first))
             : item.state === "changed" && wasFirst !== first
                 ? wordDiff(wasFirst, first, style)
-                : addedToBuilt(item, page)
-                    ? style.added(first)
-                    : highlighted(first, style);
+                : highlighted(first, style);
         // Wrapped, never cut short: what follows a `…` is what a person came to read. The lines after the first hang
         // under the item's text, past its bullet.
         const [head = "", ...rest] = hanging(drawn, first, room);
@@ -499,7 +490,7 @@ export function specMapLines(pages, state, width, style, _jobs = [], now = Date.
                 add(line, mark);
         }
         if (state.open.has(row.key)) {
-            for (const detail of detailLines(item, width, style, addedToBuilt(item, page)))
+            for (const detail of detailLines(item, width, style))
                 add(detail, mark);
             return;
         }

package/dist/run-report.js

@@ -181,6 +181,18 @@ export function startRunReport(options) {
             list,
         };
     };
+    /** The spec gaps the pulses' agents met, in the order the pulses started: questions a person would want to decide. */
+    const specGapsOf = (jobs) => jobs.flatMap((job) => {
+        const details = job.details;
+        return (details?.specGaps ?? []).map((gap) => ({
+            module: job.module ?? null,
+            pulse: job.pulse ?? null,
+            pulse_id: job.id,
+            landed: job.status === "succeeded" && details?.landed === true,
+            question: gap.question,
+            assumption: gap.assumption,
+        }));
+    });
     const functionalitiesOf = (counts) => {
         if (counts === undefined)
             return null;
@@ -245,6 +257,7 @@ export function startRunReport(options) {
             usage: usageOf(jobs),
             pulses: pulsesOf(jobs, now),
             functionalities: functionalitiesOf(attempt(sources.completion)),
+            spec_gaps: specGapsOf(jobs),
             ...(exitParts ?? {}),
             logs: {
                 jobs_dir: fromProject(join(projectRoot, ".turri", "jobs")),

package/docs/headless.md

@@ -104,7 +104,8 @@ Conformance tests follow `conformance-tests:` in `config.turri.yaml`, or `--conf
 The command exits `0` only when every module is complete: its code regenerated from the spec as it is
 now, and its conformance tests written for what is built when they are on - no pulse failed, nothing
 halted, nothing waiting for a start over. Anything else exits `1`, and the last lines say which
-module is not complete, and why. The log says, per functionality, what was built and whether its
+module is not complete, and why. A behaviour the spec leaves open that an agent had to decide is printed
+as a `spec gap` under its pulse, with what was decided meanwhile. The log says, per functionality, what was built and whether its
 tests passed.
 
 | | |
@@ -191,6 +192,11 @@ changes meaning or goes; new fields may appear in the same version. Paths in `pu
     ],
     "codebases": ["plain_modules/app/code"]
   },
+  "spec_gaps": [{                                       // [] when no agent met one
+    "module": "app", "pulse": 3, "pulse_id": "2a058729", "landed": true,
+    "question": "What happens to a contact archived in HubSpot after it was synced?",
+    "assumption": "An archived contact is left as synced - asserted in sync.test.ts, archived contacts"
+  }],
   "build_dir_export": { "exported": true, "dir": "/work/out", "module": "app", "commit": "8036b3b", "files": 23 },
   "logs": { "jobs_dir": ".turri/jobs", "debug_dir": ".turri/debug", "sessions_dir": ".turri/sessions" }
 }
@@ -209,6 +215,13 @@ calls; a role or model turri could not tell is `unknown`.
 stopped, or did not pass - and everything it wrote was undone. A pulse that failed is tried once more
 before it counts as failed; both tries are the one pulse.
 
+**Spec gaps.** A behaviour the spec leaves open that an agent met and decided on its own - reported with
+`report_spec_gap` (see [regenerating](regenerating.md)). In the chat they are put to you as the pulse ends; a
+headless run has no one to ask, so they are listed here, in the order the pulses started, and printed under the
+pulse that met them. `assumption` is what the agent decided meanwhile, also in the codebase's notes'
+assumptions while its pulse is `landed`; a pulse rolled back takes it out of the notes, but the question still
+stands. Settle the ones you care about in the spec and run again.
+
 **Completed functional specs** - the pass rate, the figure to compare runs by.
 A functional spec is completed when the code record of the codebase the run delivers - the
 furthest-built of the chain, the one `--build-dir` exports - as last committed, holds it as the spec has

package/docs/regenerating.md

@@ -1111,7 +1111,9 @@ are the next agent's, and a gap is yours. An agent reports one with `report_spec
 and the assumption it made meanwhile; turri writes that assumption into the notes' assumptions, so the code built on
 it is known for what it is. The gaps a pulse's agents report are said in its report - "Spec gaps its agents met ... Put
 each to the user", each with its assumption - so the conversation asks you, and writes the ones you decide into the
-spec; the pulse that builds the answer finds the assumption it replaces in the notes, and the tests it names. However many gaps a pulse's agents report, they
+spec; the pulse that builds the answer finds the assumption it replaces in the notes, and the tests it names.
+A headless run has no one to ask: it prints each gap under its pulse, and lists them in its run report's
+`spec_gaps` ([running unattended](headless.md#the-run-report)). However many gaps a pulse's agents report, they
 are put to you - never a reason to stop the pulse; the tool is guarded like any other. A notes
 file from before keeps no spec gaps section: its lines are dropped as it is read.
 

package/docs/using.md

@@ -174,9 +174,7 @@ come waits for a free slot, and says so.
   regenerates. Pulses are numbered as they start in a module, from 1 each session.
 
   A changed item shows what changed in it: its first line word by word - what is gone struck through in red,
-  what is new in green, what is kept highlighted as it reads now - and, under it, only the sub-bullets that changed. A new
-  item beside code already built - one a spec diff adds - is green, all of it, so a new functional spec stands apart
-  from one changed; where everything is new, built for the first time or from scratch, nothing is. A spec never built that is taken
+  what is new in green, what is kept highlighted as it reads now - and, under it, only the sub-bullets that changed. A spec never built that is taken
   out is simply gone. The top line has a strip of the module's functional specs - built, regenerating, planned,
   waiting - and how many are built, then what is happening: `pulse 3 of 8 regenerating`, or why nothing is -
   `not asked to build - regenerate plans it` (turri was just opened, or nothing has asked for the module: the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@turri-dev/cli",
-  "version": "0.1.4-next.ebd337a",
+  "version": "0.1.4-next.fa9223b",
   "license": "MIT",
   "type": "module",
   "repository": {