@mestreyoda/fabrica 0.2.6 → 0.2.7

package/defaults/fabrica/prompts/reviewer.md

@@ -73,8 +73,7 @@ Do **not** treat the task envelope (`Repo:`, `Project:`, `Channel:`, branch hint
 
 - Read the PR diff carefully
 - Check the code against the review checklist
-- Call `review_submit` with your review findings so the artifact is written to the PR itself
-- Then call `work_finish`
+- Submit your review using **one of the two methods below** (prefer `review_submit` if available)
 
 ## Conventions
 
@@ -92,22 +91,50 @@ If you discover unrelated bugs or needed improvements, call `task_create`:
 
 ## Completing Your Task
 
-When you are done, submit the review artifact first, then **call `work_finish` yourself** — do not just announce in text.
+When you are done, submit your review using **Method A** if the tools are available, or **Method B** otherwise.
 
-- **Approve review artifact:** `review_submit({ channelId: "<project slug from 'Project:' field in task message>", issueId: <issue number>, result: "approve", body: "<what you checked>" })`
-- **Reject review artifact:** `review_submit({ channelId: "<project slug from 'Project:' field in task message>", issueId: <issue number>, result: "reject", body: "<specific issues>" })`
-- Capture the returned `artifactId` and `artifactType` from `review_submit`.
+### Method A — Fabrica tools (preferred)
 
-**Never call `task_comment` for review findings.** The orchestrator may mirror your result to the issue separately, but your authoritative feedback must live on the PR via `review_submit`.
-
-- **Approve:** `work_finish({ role: "reviewer", result: "approve", channelId: "<project slug from 'Project:' field in task message>", summary: "<what you checked>", reviewArtifactId: <artifactId>, reviewArtifactType: "<artifactType>" })`
-- **Reject:** `work_finish({ role: "reviewer", result: "reject", channelId: "<project slug from 'Project:' field in task message>", summary: "<specific issues>", reviewArtifactId: <artifactId>, reviewArtifactType: "<artifactType>" })`
-- **Blocked:** `work_finish({ role: "reviewer", result: "blocked", channelId: "<project slug from 'Project:' field in task message>", summary: "<what you need>" })`
+1. Call `review_submit` to write the review artifact to the PR:
+   - **Approve:** `review_submit({ channelId: "<project slug>", issueId: <issue number>, result: "approve", body: "<what you checked>" })`
+   - **Reject:** `review_submit({ channelId: "<project slug>", issueId: <issue number>, result: "reject", body: "<specific issues>" })`
+   - Capture the returned `artifactId` and `artifactType`.
+2. Then call `work_finish`:
+   - **Approve:** `work_finish({ role: "reviewer", result: "approve", channelId: "<project slug>", summary: "<what you checked>", reviewArtifactId: <artifactId>, reviewArtifactType: "<artifactType>" })`
+   - **Reject:** `work_finish({ role: "reviewer", result: "reject", channelId: "<project slug>", summary: "<specific issues>", reviewArtifactId: <artifactId>, reviewArtifactType: "<artifactType>" })`
+   - **Blocked:** `work_finish({ role: "reviewer", result: "blocked", channelId: "<project slug>", summary: "<what you need>" })`
 
 > **IMPORTANT:** The `channelId` parameter accepts the project slug (e.g., "gestao-notas").
 > Extract it from the "Project: <name>" line in your task message. Do NOT use the numeric
 > channel ID — use the project slug to avoid resolution errors when channels are shared.
 
+### Method B — GitHub CLI fallback (use only if `review_submit` / `work_finish` are unavailable)
+
+Extract from your task message:
+- `OWNER/REPO` from the `Repo:` line
+- `PR_NUMBER` from the PR URL in the diff header or the `Branch:` line
+- `ISSUE_NUMBER` from the `Issue:` field
+
+**Approve:**
+```bash
+gh pr review PR_NUMBER --repo OWNER/REPO --approve -b "$(cat <<'EOF'
+<your full review body here>
+EOF
+)"
+```
+
+**Reject (request changes):**
+```bash
+gh pr review PR_NUMBER --repo OWNER/REPO --request-changes -b "$(cat <<'EOF'
+<specific issues and how to fix them>
+EOF
+)"
+```
+
+After submitting via `gh pr review`, the Fabrica heartbeat will detect the PR review state and advance the pipeline automatically. **Do NOT manually edit issue labels.**
+
+**Never call `task_comment` for review findings.** Your review must be posted on the PR itself.
+
 ## Tools You Should NOT Use
 
 These are orchestrator-only tools. Do not call them:

package/dist/index.js

@@ -111330,8 +111330,8 @@ import fsSync from "node:fs";
 import path5 from "node:path";
 import { fileURLToPath as fileURLToPath3 } from "node:url";
 function getCurrentVersion() {
-  if ("0.2.6") {
-    return "0.2.6";
+  if ("0.2.7") {
+    return "0.2.7";
   }
   try {
     const pkgPath = path5.join(THIS_DIR, "..", "..", "package.json");
@@ -130791,7 +130791,7 @@ async function reviewPass(opts) {
     const issues = await provider.listIssuesByLabel(state.label);
     for (const issue2 of issues) {
       const routing = detectStepRouting(issue2.labels, "review");
-      if (routing !== "human") continue;
+      if (routing !== "human" && routing !== "agent") continue;
       const isManaged = await provider.issueHasReaction(issue2.iid, "eyes");
       if (!isManaged) continue;
       const status = await provider.getPrStatus(issue2.iid);