@ikunin/sprintpilot 2.2.31 → 2.3.1

package/_Sprintpilot/scripts/log-timing.js

@@ -47,10 +47,8 @@ const META_MAX_BYTES = 2048;
 const LINE_MAX_BYTES = 4096; // POSIX PIPE_BUF floor — single write() is atomic
 const VALID_ACTIONS = ['start', 'end', 'once', 'mark'];
 // Marker filenames are `.mark.<story>.json` — built by `markerPath()`.
-// Pre-2.0.5 used a single global `.mark.json`, which corrupted timing
-// data under parallel dispatch (concurrent sub-agents racing on one
-// rename target). The constant is gone; runtime always uses per-story
-// paths.
+// Per-story paths so parallel dispatch (concurrent sub-agents) can't
+// race on a shared rename target.
 //
 // Sanity ceiling for a single duration record. Phase durations longer
 // than this are treated as overflow (likely a stale marker from an
@@ -304,12 +302,10 @@ function clearMarker(projectRoot, story) {
  * for a given story emits no duration record — there's no "previous
  * phase" yet for that story.
  *
- * Pre-2.0.5 used a single global marker file shared across stories,
- * which under parallel dispatch (sub-agents marking different stories
- * concurrently against the same project root) raced on a single file —
- * one rename clobbered the other and durations were attributed to the
- * wrong (story, phase). Per-story markers eliminate the race entirely:
- * each story has its own marker file `.mark.<story>.json`.
+ * Per-story marker files (`.mark.<story>.json`) ensure parallel
+ * dispatch is race-free — sub-agents marking different stories
+ * concurrently never share a rename target, so durations are always
+ * attributed to the correct (story, phase) pair.
  *
  * Use phase = "_end" to close THIS story's last open phase without
  * starting a new one (e.g. at sprint-complete time, or per-story

package/_Sprintpilot/scripts/merge-shards.js

@@ -76,17 +76,17 @@ function implArtifactsDir(projectRoot) {
 // Cross-process merge lock
 // ──────────────────────────────────────────────────────────────────
 //
-// Pre-2.0.8 two concurrent merge invocations would each compute the
-// merge in-memory then both rename their tmp file over autopilot-state
-// .yaml. Tmp filenames are unique, so the renames never collided on
-// the source — but the LAST rename wins on the destination, and the
-// earlier merge (potentially with newer shard data) was clobbered.
-// Combined with the archive race below, the loser's archived shards
-// were also gone — silent state rewind.
+// Two concurrent merge invocations would each compute the merge in
+// memory then both rename their tmp file over autopilot-state.yaml.
+// Tmp filenames are unique so renames don't collide on the source,
+// but the LAST rename wins on the destination — the earlier merge
+// (potentially with newer shard data) would be clobbered. Combined
+// with archive races below, the loser's archived shards would also
+// vanish — a silent state rewind.
 //
-// The fix: a sibling lock file. If another invocation holds the lock,
-// either wait briefly + retry, or fail with a clear message naming
-// the holder's pid and start time so the operator can diagnose.
+// A sibling lock file serializes merges. If another invocation holds
+// the lock, callers wait briefly + retry, or fail with a clear message
+// naming the holder's pid and start time so the operator can diagnose.
 
 const MERGE_LOCK_FILE = '.merge-shards.lock';
 const STALE_LOCK_AGE_MS = 5 * 60 * 1000; // 5 minutes — merges are fast
@@ -186,10 +186,10 @@ function compareStamps(a, b) {
 }
 
 // Snapshot file stat at read time so we can verify it's unchanged
-// before archiving. Pre-2.0.8: a worker writing a fresh shard between
-// merge-read and archive-rename would have its shard moved into
-// .archive/ without ever being folded into the merged YAML — silent
-// data loss under parallel dispatch.
+// before archiving. Without the guard, a worker writing a fresh shard
+// between merge-read and archive-rename would have its shard moved
+// into .archive/ without being folded into the merged YAML —
+// silent data loss under parallel dispatch.
 function snapshotShard(file) {
   try {
     const st = fs.statSync(file);
@@ -242,10 +242,8 @@ function mergeStateShards(projectRoot) {
 }
 
 // Parse a timestamp string defensively: malformed `ts` returns 0
-// rather than NaN (which Array.sort treats unpredictably). Pre-2.0.8
-// `Date.parse('not-a-date')` returned NaN, NaN comparisons returned
-// 0, and entries clustered in undefined order — the documented
-// "sort by ts ascending" claim was silently violated.
+// rather than NaN (which Array.sort treats unpredictably; NaN
+// comparisons always return 0 and entries cluster in undefined order).
 function tsToMs(ts) {
   if (!ts) return 0;
   const v = Date.parse(ts);
@@ -281,11 +279,11 @@ function mergeDecisionShards(projectRoot) {
     }
     snapshots[story] = snap;
   }
-  // Deterministic dedup: sort by (id asc, ts DESC) first, then keep the
-  // first entry for each id — that's the latest-by-ts. Pre-2.0.8 the
-  // dedup was iteration-order-dependent (filesystem readdir order is
-  // unspecified), so identical inputs produced different outputs across
-  // OSes. Idempotency claim was filesystem-dependent.
+  // Deterministic dedup: sort by (id asc, ts DESC) first, then keep
+  // the first entry for each id — that's the latest-by-ts. The
+  // explicit sort avoids depending on filesystem readdir order, which
+  // is unspecified and varies by OS, so identical inputs always
+  // produce identical outputs.
   entries.sort((a, b) => {
     const ai = a.id !== undefined && a.id !== null ? String(a.id) : '';
     const bi = b.id !== undefined && b.id !== null ? String(b.id) : '';

package/_Sprintpilot/scripts/post-green-gates.js

@@ -20,7 +20,9 @@
 //     --output-limit:  max lines of lint output per gate (forwarded to
 //                      lint-changed.js as --limit). Honors
 //                      `git.lint.output_limit` from config when called
-//                      from the orchestrator (v2.2.28+).
+//                      from the orchestrator.
+//     --linters-json:  per-language linter map (forwarded to
+//                      lint-changed.js). See git.lint.linters.
 //
 // Each gate runs in a child process via execFileSync. Argv-only — no shell.