@brainervirus/workit-core 1.0.1 → 1.0.3

package/package.json

@@ -1,16 +1,22 @@
 {
   "name": "@brainervirus/workit-core",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "private": false,
-  "description": "Workit — workflow rails for agentic coding: specs, plans, YouTrack, CI-gated commits (shared core)",
+  "description": "Workit shared core — task, policy, evidence, review, decision, worker, and writer state for agentic coding workflows",
   "keywords": [
-    "agent",
+    "agentic-coding",
+    "ai-agents",
+    "codex",
     "cursor",
     "mcp",
     "opencode",
-    "workflow",
-    "youTrack"
+    "pi",
+    "policy-engine",
+    "task-management",
+    "typescript",
+    "workflow"
   ],
+  "homepage": "https://github.com/BrainerVirus/workit#readme",
   "bugs": {
     "url": "https://github.com/BrainerVirus/workit/issues"
   },

package/scripts/analyze-release-scope.ts

@@ -1,7 +1,9 @@
 #!/usr/bin/env bun
-// AR-16: path-gated releases. Replaces message-only commit analysis: a
-// releasable commit counts only when it touches a PRODUCT PATH (any of the
-// four package dirs). Tooling-only merges produce no release at all.
+// AR-16: path-gated releases. A releasable commit counts only when it touches
+// a PRODUCT PATH (any of the four package dirs). Tooling-only merges produce no
+// release at all. A payload change typed docs/chore still publishes as patch —
+// skills and metadata live in the tarball, so installed users must receive
+// them; merge-backs and the release's own manifest sync never do.
 import { execFileSync } from "node:child_process";
 import { resolve } from "node:path";
 
@@ -15,6 +17,9 @@ export const RELEASE_PACKAGES = [
   "workit-pi",
 ] as const;
 
+/** The release pipeline's own version-sync commit: never a release trigger. */
+const RELEASE_SYNC = /^chore\(release\): sync manifests\b/;
+
 const g = (root: string, args: string[]): string =>
   execFileSync("git", args, { cwd: root, encoding: "utf8" }).trim();
 
@@ -64,9 +69,10 @@ const commitsSince = (root: string, from: string): { message: string; files: str
   }));
 };
 
-export function analyzeReleaseScope(
-  root = process.cwd(),
-): { level: Level | null; productPkgs: string[] } {
+export function analyzeReleaseScope(root = process.cwd()): {
+  level: Level | null;
+  productPkgs: string[];
+} {
   const from = latestTag(root);
   if (from === null) {
     return { level: "minor", productPkgs: [...RELEASE_PACKAGES] };
@@ -74,18 +80,27 @@ export function analyzeReleaseScope(
   const commits = commitsSince(root, from);
   const levels: Level[] = [];
   const pkgs = new Set<string>();
+  let payloadOnly = false;
   for (const { message, files } of commits) {
-    const touched = files.filter((f) => RELEASE_PACKAGES.some((p) => f.startsWith(`packages/${p}/`)));
+    const subject = (message.split("\n")[0] ?? "").trim();
+    if (RELEASE_SYNC.test(subject)) continue;
+    const touched = files.filter((f) =>
+      RELEASE_PACKAGES.some((p) => f.startsWith(`packages/${p}/`)),
+    );
     if (touched.length === 0) continue;
     const lvl = subjectLevel(message);
     if (lvl) levels.push(lvl);
+    else if (!subject.startsWith("Merge ")) payloadOnly = true;
     for (const f of touched) {
       const pkg = RELEASE_PACKAGES.find((p) => f.startsWith(`packages/${p}/`));
       if (pkg) pkgs.add(pkg);
     }
   }
-  if (levels.length === 0) return { level: null, productPkgs: [...pkgs] };
-  const level = levels.reduce<Level>((best, l) => (LEVEL_RANK[l] > LEVEL_RANK[best] ? l : best), "patch");
+  if (levels.length === 0) return { level: payloadOnly ? "patch" : null, productPkgs: [...pkgs] };
+  const level = levels.reduce<Level>(
+    (best, l) => (LEVEL_RANK[l] > LEVEL_RANK[best] ? l : best),
+    "patch",
+  );
   return { level, productPkgs: [...pkgs] };
 }
 

package/skills/workit-babysit/SKILL.md

@@ -31,3 +31,8 @@ selects requirements; do not wait for a rule that can only exist after assess.
 
 PR merged per settings, or a status brief (frontier state, next action) when
 blocked on the human. Record evidence for fixes, findings for blockers.
+
+A squash merge creates a new commit on the base branch, so the pre-merge
+candidate identity changes: re-record verification and review evidence against
+the merged commit before `task.close`, or the close will report unsatisfied
+requirements.

package/skills/workit-steer/SKILL.md

@@ -20,11 +20,14 @@ selects requirements; do not wait for a rule that can only exist after assess.
    blockers. Never trust memory across an interruption.
 2. Classify the steering:
    - same-task: fold into scope (reassess if facts changed), continue.
-   - new-task: `task.start` + `policy.assess`; the parked task waits.
+   - new-task: `task.pause` the parked lead task, then `task.start` +
+     `policy.assess` for the new one. Keep exactly one active lead per
+     session: external actions bind to that single active task, and a second
+     active lead makes writer authority ambiguous.
    - quick-question: answer from the parked state, then resume.
 3. Handle it with the same rigor as the parked work (no drive-by edits).
 4. Re-anchor: one-line resume brief (where we were, what changed, what
-   is next) before touching the parked work again.
+   is next), then `task.resume` the parked task before touching it again.
 
 ## Completion