@snappedly-tools/shipyard 0.5.0-staging.36002974657 → 0.5.0-staging.36005755873

package/README.md

@@ -85,10 +85,16 @@ wake-ups, and stops when it makes no progress. Restarting it recovers work
 labelled while the host was offline.
 GitHub-backed `shipyard init` provisions `shipyard`, `shipyard:blocked`,
 `shipyard:pending`, `shipyard:complete`, and `shipyard:outstanding-tasks` in the repository.
+It also provisions the `bug`, `enhancement`, and five triage state labels.
 For a connected repository, init reports an error if any label cannot be created.
 
 The bundled issue workflows install Snappedly skills and the candidate's
-dependencies in Docker. A standalone issue runs through `/implement`. Activating
+dependencies in Docker. When Shipyard takes an activated ticket, it runs
+`/triage` first and checks the current GitHub labels. Implementation requires
+both `shipyard` and `ready-for-agent`, with no conflicting triage state. Other
+triage outcomes follow the normal blocked flow: Shipyard adds
+`shipyard:blocked`, removes `shipyard`, and records the reason on the ticket.
+A standalone ready issue then runs through `/implement`. Activating
 a planning spec or a linked executable child resolves the parent and only
 linked tickets labelled `shipyard` into one `/implement-spec` scope. The sequential
 templates deliver selected tickets on one branch; the parallel templates assign

package/dist/main.js

@@ -2259,7 +2259,7 @@ var runnerCommand = Command.make(
     purgeRunnerCommand
   ])
 );
-var VERSION = "0.5.0-staging.36002974657" ;
+var VERSION = "0.5.0-staging.36005755873" ;
 
 // src/cli.ts
 var imageNameOption = Options.text("image-name").pipe(
@@ -2731,6 +2731,13 @@ var initCommand = Command.make(
       const failedLabels = [];
       for (const [name, description, color] of [
         [ACTIVATION_LABEL, `Issues for ${PRODUCT_NAME} to work on`, "F9A825"],
+        ["bug", "Something is broken", "D73A4A"],
+        ["enhancement", "New feature or improvement", "A2EEEF"],
+        ["needs-triage", "Maintainer evaluation needed", "FBCA04"],
+        ["needs-info", "Waiting for reporter information", "D4C5F9"],
+        ["ready-for-agent", "Ready for agent implementation", "0E8A16"],
+        ["ready-for-human", "Requires human implementation", "1D76DB"],
+        ["wontfix", "Will not be actioned", "FFFFFF"],
         ["shipyard:blocked", "Shipyard work needs intervention", "B60205"],
         ["shipyard:pending", "Shipyard is working on this ticket", "1D76DB"],
         [