@snappedly-tools/shipyard 0.9.2-staging.36261752709 → 0.9.2-staging.36277429987

package/dist/main.js

@@ -2400,7 +2400,7 @@ var runnerCommand = Command.make(
     purgeRunnerCommand
   ])
 );
-var VERSION = "0.9.2-staging.36261752709" ;
+var VERSION = "0.9.2-staging.36277429987" ;
 var SHIPYARD_PACKAGE_NAME = "@snappedly-tools/shipyard";
 var isMissingPath = (error) => error !== null && typeof error === "object" && "code" in error && error.code === "ENOENT";
 var lstatIfPresent = async (path) => {

package/dist/templates/parallel-planner/triage-prompt.md

@@ -2,6 +2,6 @@ Triage GitHub issue #{{TASK_ID}} before Shipyard implementation.
 
 Follow `/triage` and the repository's triage label mapping. Read the full issue and comments. Verify the reported behavior against `origin/{{BASE_BRANCH}}`, the integration baseline. The checked-out task branch may contain unfinished changes from an earlier attempt. Do not close the issue as already complete based on the task branch or comments about that candidate.
 
-Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. If a decision requires maintainer judgment, use `needs-triage` and record the question. Do not implement the issue or start a PR in this phase.
+Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. Derive acceptance criteria from the stated outcome. For example, equal spacing between named header items is a testable visual goal without a pixel target. Choose a representative supported viewport if none is specified. An inaccessible attachment does not require `needs-info` when the text establishes the current and desired behavior; record the verification limit in the brief. Do not treat equal CSS gap values alone as proof that the rendered gaps are equal. Apply `needs-info` and ask one concrete question only when missing details change the intended result or prevent meaningful verification. Use `needs-triage` only when the available facts leave a product or policy decision for the maintainer, not for routine layout or implementation choices. Preserve the `shipyard` or `shipyard:pending` label. Do not implement the issue or start a PR in this phase.
 
-Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying both `shipyard` and the sole triage state `ready-for-agent`.
+Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying `shipyard` or `shipyard:pending` and the sole triage state `ready-for-agent`.

package/dist/templates/parallel-planner/verify-triage.sh

@@ -11,9 +11,18 @@ gh issue view "$issue" --repo "$repo" --json state,labels |
     const issue = JSON.parse(require("node:fs").readFileSync(0, "utf8"));
     const labels = new Set(issue.labels.map((label) => label.name));
     const states = ["needs-triage", "needs-info", "ready-for-agent", "ready-for-human", "wontfix"];
-    if (issue.state !== "OPEN" || !labels.has("shipyard") ||
-        states.filter((state) => labels.has(state)).join() !== "ready-for-agent") {
-      console.error("Issue cannot be implemented: requires an open issue with shipyard and only ready-for-agent as its triage state");
+    if (issue.state !== "OPEN" ||
+        !(labels.has("shipyard") || labels.has("shipyard:pending"))) {
+      console.error("Issue cannot be implemented: requires an open issue with shipyard or shipyard:pending");
+      process.exit(1);
+    }
+    const triageStates = states.filter((state) => labels.has(state));
+    if (triageStates.join() === "needs-info") {
+      console.error("Issue needs information from the reporter before implementation");
+      process.exit(1);
+    }
+    if (triageStates.join() !== "ready-for-agent") {
+      console.error(`Issue cannot be implemented: triage state is ${triageStates.join() || "missing"}; requires only ready-for-agent`);
       process.exit(1);
     }
   '

package/dist/templates/parallel-planner-with-review/triage-prompt.md

@@ -2,6 +2,6 @@ Triage GitHub issue #{{TASK_ID}} before Shipyard implementation.
 
 Follow `/triage` and the repository's triage label mapping. Read the full issue and comments. Verify the reported behavior against `origin/{{BASE_BRANCH}}`, the integration baseline. The checked-out task branch may contain unfinished changes from an earlier attempt. Do not close the issue as already complete based on the task branch or comments about that candidate.
 
-Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. If a decision requires maintainer judgment, use `needs-triage` and record the question. Do not implement the issue or start a PR in this phase.
+Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. Derive acceptance criteria from the stated outcome. For example, equal spacing between named header items is a testable visual goal without a pixel target. Choose a representative supported viewport if none is specified. An inaccessible attachment does not require `needs-info` when the text establishes the current and desired behavior; record the verification limit in the brief. Do not treat equal CSS gap values alone as proof that the rendered gaps are equal. Apply `needs-info` and ask one concrete question only when missing details change the intended result or prevent meaningful verification. Use `needs-triage` only when the available facts leave a product or policy decision for the maintainer, not for routine layout or implementation choices. Preserve the `shipyard` or `shipyard:pending` label. Do not implement the issue or start a PR in this phase.
 
-Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying both `shipyard` and the sole triage state `ready-for-agent`.
+Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying `shipyard` or `shipyard:pending` and the sole triage state `ready-for-agent`.

package/dist/templates/parallel-planner-with-review/verify-triage.sh

@@ -11,9 +11,18 @@ gh issue view "$issue" --repo "$repo" --json state,labels |
     const issue = JSON.parse(require("node:fs").readFileSync(0, "utf8"));
     const labels = new Set(issue.labels.map((label) => label.name));
     const states = ["needs-triage", "needs-info", "ready-for-agent", "ready-for-human", "wontfix"];
-    if (issue.state !== "OPEN" || !labels.has("shipyard") ||
-        states.filter((state) => labels.has(state)).join() !== "ready-for-agent") {
-      console.error("Issue cannot be implemented: requires an open issue with shipyard and only ready-for-agent as its triage state");
+    if (issue.state !== "OPEN" ||
+        !(labels.has("shipyard") || labels.has("shipyard:pending"))) {
+      console.error("Issue cannot be implemented: requires an open issue with shipyard or shipyard:pending");
+      process.exit(1);
+    }
+    const triageStates = states.filter((state) => labels.has(state));
+    if (triageStates.join() === "needs-info") {
+      console.error("Issue needs information from the reporter before implementation");
+      process.exit(1);
+    }
+    if (triageStates.join() !== "ready-for-agent") {
+      console.error(`Issue cannot be implemented: triage state is ${triageStates.join() || "missing"}; requires only ready-for-agent`);
       process.exit(1);
     }
   '

package/dist/templates/sequential-reviewer/triage-prompt.md

@@ -2,6 +2,6 @@ Triage GitHub issue #{{TASK_ID}} before Shipyard implementation.
 
 Follow `/triage` and the repository's triage label mapping. Read the full issue and comments. Verify the reported behavior against `origin/{{BASE_BRANCH}}`, the integration baseline. The checked-out task branch may contain unfinished changes from an earlier attempt. Do not close the issue as already complete based on the task branch or comments about that candidate.
 
-Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. If a decision requires maintainer judgment, use `needs-triage` and record the question. Do not implement the issue or start a PR in this phase.
+Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. Derive acceptance criteria from the stated outcome. For example, equal spacing between named header items is a testable visual goal without a pixel target. Choose a representative supported viewport if none is specified. An inaccessible attachment does not require `needs-info` when the text establishes the current and desired behavior; record the verification limit in the brief. Do not treat equal CSS gap values alone as proof that the rendered gaps are equal. Apply `needs-info` and ask one concrete question only when missing details change the intended result or prevent meaningful verification. Use `needs-triage` only when the available facts leave a product or policy decision for the maintainer, not for routine layout or implementation choices. Preserve the `shipyard` or `shipyard:pending` label. Do not implement the issue or start a PR in this phase.
 
-Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying both `shipyard` and the sole triage state `ready-for-agent`.
+Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying `shipyard` or `shipyard:pending` and the sole triage state `ready-for-agent`.

package/dist/templates/sequential-reviewer/verify-triage.sh

@@ -11,9 +11,18 @@ gh issue view "$issue" --repo "$repo" --json state,labels |
     const issue = JSON.parse(require("node:fs").readFileSync(0, "utf8"));
     const labels = new Set(issue.labels.map((label) => label.name));
     const states = ["needs-triage", "needs-info", "ready-for-agent", "ready-for-human", "wontfix"];
-    if (issue.state !== "OPEN" || !labels.has("shipyard") ||
-        states.filter((state) => labels.has(state)).join() !== "ready-for-agent") {
-      console.error("Issue cannot be implemented: requires an open issue with shipyard and only ready-for-agent as its triage state");
+    if (issue.state !== "OPEN" ||
+        !(labels.has("shipyard") || labels.has("shipyard:pending"))) {
+      console.error("Issue cannot be implemented: requires an open issue with shipyard or shipyard:pending");
+      process.exit(1);
+    }
+    const triageStates = states.filter((state) => labels.has(state));
+    if (triageStates.join() === "needs-info") {
+      console.error("Issue needs information from the reporter before implementation");
+      process.exit(1);
+    }
+    if (triageStates.join() !== "ready-for-agent") {
+      console.error(`Issue cannot be implemented: triage state is ${triageStates.join() || "missing"}; requires only ready-for-agent`);
       process.exit(1);
     }
   '

package/dist/templates/shared/triage-prompt.md

@@ -2,6 +2,6 @@ Triage GitHub issue #{{TASK_ID}} before Shipyard implementation.
 
 Follow `/triage` and the repository's triage label mapping. Read the full issue and comments. Verify the reported behavior against `origin/{{BASE_BRANCH}}`, the integration baseline. The checked-out task branch may contain unfinished changes from an earlier attempt. Do not close the issue as already complete based on the task branch or comments about that candidate.
 
-Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. If a decision requires maintainer judgment, use `needs-triage` and record the question. Do not implement the issue or start a PR in this phase.
+Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. Derive acceptance criteria from the stated outcome. For example, equal spacing between named header items is a testable visual goal without a pixel target. Choose a representative supported viewport if none is specified. An inaccessible attachment does not require `needs-info` when the text establishes the current and desired behavior; record the verification limit in the brief. Do not treat equal CSS gap values alone as proof that the rendered gaps are equal. Apply `needs-info` and ask one concrete question only when missing details change the intended result or prevent meaningful verification. Use `needs-triage` only when the available facts leave a product or policy decision for the maintainer, not for routine layout or implementation choices. Preserve the `shipyard` or `shipyard:pending` label. Do not implement the issue or start a PR in this phase.
 
-Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying both `shipyard` and the sole triage state `ready-for-agent`.
+Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying `shipyard` or `shipyard:pending` and the sole triage state `ready-for-agent`.

package/dist/templates/shared/verify-triage.sh

@@ -11,9 +11,18 @@ gh issue view "$issue" --repo "$repo" --json state,labels |
     const issue = JSON.parse(require("node:fs").readFileSync(0, "utf8"));
     const labels = new Set(issue.labels.map((label) => label.name));
     const states = ["needs-triage", "needs-info", "ready-for-agent", "ready-for-human", "wontfix"];
-    if (issue.state !== "OPEN" || !labels.has("shipyard") ||
-        states.filter((state) => labels.has(state)).join() !== "ready-for-agent") {
-      console.error("Issue cannot be implemented: requires an open issue with shipyard and only ready-for-agent as its triage state");
+    if (issue.state !== "OPEN" ||
+        !(labels.has("shipyard") || labels.has("shipyard:pending"))) {
+      console.error("Issue cannot be implemented: requires an open issue with shipyard or shipyard:pending");
+      process.exit(1);
+    }
+    const triageStates = states.filter((state) => labels.has(state));
+    if (triageStates.join() === "needs-info") {
+      console.error("Issue needs information from the reporter before implementation");
+      process.exit(1);
+    }
+    if (triageStates.join() !== "ready-for-agent") {
+      console.error(`Issue cannot be implemented: triage state is ${triageStates.join() || "missing"}; requires only ready-for-agent`);
       process.exit(1);
     }
   '

package/dist/templates/simple-loop/triage-prompt.md

@@ -2,6 +2,6 @@ Triage GitHub issue #{{TASK_ID}} before Shipyard implementation.
 
 Follow `/triage` and the repository's triage label mapping. Read the full issue and comments. Verify the reported behavior against `origin/{{BASE_BRANCH}}`, the integration baseline. The checked-out task branch may contain unfinished changes from an earlier attempt. Do not close the issue as already complete based on the task branch or comments about that candidate.
 
-Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. If a decision requires maintainer judgment, use `needs-triage` and record the question. Do not implement the issue or start a PR in this phase.
+Apply the appropriate category and state label and post the brief or triage notes required by the skill. The maintainer has authorized Shipyard to apply an evidence-based recommendation during this unattended intake. Derive acceptance criteria from the stated outcome. For example, equal spacing between named header items is a testable visual goal without a pixel target. Choose a representative supported viewport if none is specified. An inaccessible attachment does not require `needs-info` when the text establishes the current and desired behavior; record the verification limit in the brief. Do not treat equal CSS gap values alone as proof that the rendered gaps are equal. Apply `needs-info` and ask one concrete question only when missing details change the intended result or prevent meaningful verification. Use `needs-triage` only when the available facts leave a product or policy decision for the maintainer, not for routine layout or implementation choices. Preserve the `shipyard` or `shipyard:pending` label. Do not implement the issue or start a PR in this phase.
 
-Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying both `shipyard` and the sole triage state `ready-for-agent`.
+Report the applied state and evidence. Shipyard will independently re-read GitHub labels and implement only an open issue carrying `shipyard` or `shipyard:pending` and the sole triage state `ready-for-agent`.

package/dist/templates/simple-loop/verify-triage.sh

@@ -11,9 +11,18 @@ gh issue view "$issue" --repo "$repo" --json state,labels |
     const issue = JSON.parse(require("node:fs").readFileSync(0, "utf8"));
     const labels = new Set(issue.labels.map((label) => label.name));
     const states = ["needs-triage", "needs-info", "ready-for-agent", "ready-for-human", "wontfix"];
-    if (issue.state !== "OPEN" || !labels.has("shipyard") ||
-        states.filter((state) => labels.has(state)).join() !== "ready-for-agent") {
-      console.error("Issue cannot be implemented: requires an open issue with shipyard and only ready-for-agent as its triage state");
+    if (issue.state !== "OPEN" ||
+        !(labels.has("shipyard") || labels.has("shipyard:pending"))) {
+      console.error("Issue cannot be implemented: requires an open issue with shipyard or shipyard:pending");
+      process.exit(1);
+    }
+    const triageStates = states.filter((state) => labels.has(state));
+    if (triageStates.join() === "needs-info") {
+      console.error("Issue needs information from the reporter before implementation");
+      process.exit(1);
+    }
+    if (triageStates.join() !== "ready-for-agent") {
+      console.error(`Issue cannot be implemented: triage state is ${triageStates.join() || "missing"}; requires only ready-for-agent`);
       process.exit(1);
     }
   '

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@snappedly-tools/shipyard",
-  "version": "0.9.2-staging.36261752709",
+  "version": "0.9.2-staging.36277429987",
   "description": "Run AI coding agents in isolated sandboxes",
   "type": "module",
   "main": "./dist/index.js",