@mastra/factory 0.17.3-alpha.1 → 0.17.3-alpha.2

package/factory-skills/factory-rereview/SKILL.md

@@ -147,6 +147,8 @@ First, compose the **re-review handoff** — don't send it to the conversation y
 
 End the handoff with `Review runtime: <model>, reasoning setting: <reasoning>.`, copying both values verbatim from the current `factory-phase` signal.
 
+**The head must not have moved.** Immediately before publishing, run `gh pr view <number> --json headRefOid --jq .headRefOid` and compare it with the SHA your verification ran on (`git rev-parse HEAD`). A push can land while you verify or wait on bots, and a verdict on a superseded head misleads the author. If the head moved, do not publish: refresh the checkout to the new head, review the new commits and re-run the verification they affect, revise the handoff, then check again. Name the reviewed head SHA in the handoff.
+
 Next, publish the re-review on the PR itself — this is part of every pass, not something to wait to be asked for. Write the handoff body to `.artifacts/factory-rereview/pr-<number>.md` and submit a PR review matching the verdict:
 
 - approve → `gh pr review <number> --approve --body-file <file>`

package/factory-skills/factory-review/SKILL.md

@@ -139,6 +139,8 @@ First, compose the **review handoff** — don't send it to the conversation yet;
 
 End the handoff with `Review runtime: <model>, reasoning setting: <reasoning>.`, copying both values verbatim from the current `factory-phase` signal.
 
+**The head must not have moved.** Immediately before publishing, run `gh pr view <number> --json headRefOid --jq .headRefOid` and compare it with the SHA your verification ran on (`git rev-parse HEAD`). A push can land while you verify or wait on bots, and a verdict on a superseded head misleads the author. If the head moved, do not publish: refresh the checkout to the new head, review the new commits and re-run the verification they affect, revise the handoff, then check again. Name the reviewed head SHA in the handoff.
+
 Next, publish the review on the PR itself — this is part of every pass, not something to wait to be asked for. Write the handoff body to `.artifacts/factory-review/pr-<number>.md` and submit a PR review matching the verdict:
 
 - approve → `gh pr review <number> --approve --body-file <file>`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/factory",
-  "version": "0.17.3-alpha.1",
+  "version": "0.17.3-alpha.2",
   "description": "Mastra Software Factory module: the server core behind the Mastra Software Factory — storage domains, integrations, and surfaces for agent-powered software delivery",
   "type": "module",
   "publishConfig": {
@@ -59,9 +59,9 @@
     "zod": "^4.6.4",
     "@mastra/auth-studio": "1.3.7",
     "@mastra/auth-workos": "1.6.5",
-    "@mastra/code-sdk": "1.8.4-alpha.1",
-    "@mastra/core": "1.72.0-alpha.1",
-    "@mastra/slack": "1.6.4"
+    "@mastra/core": "1.72.0-alpha.2",
+    "@mastra/slack": "1.7.0-alpha.0",
+    "@mastra/code-sdk": "1.8.4-alpha.2"
   },
   "devDependencies": {
     "@types/node": "22.20.1",
@@ -70,11 +70,11 @@
     "typescript": "^6.0.3",
     "typescript-eslint": "^8.57.0",
     "vitest": "4.1.11",
+    "@mastra/libsql": "1.23.4-alpha.0",
+    "@mastra/pg": "1.27.2-alpha.1",
     "@internal/lint": "0.0.137",
-    "@mastra/libsql": "1.23.3",
     "@internal/types-builder": "0.0.112",
-    "@internal/workspace": "0.0.9",
-    "@mastra/pg": "1.27.2-alpha.0"
+    "@internal/workspace": "0.0.9"
   },
   "engines": {
     "node": ">=22.19.0"