@orchestraworks/cli 0.5.1 → 0.5.3

package/templates/engineering-team/agents/engineer-bare.md

@@ -1,22 +0,0 @@
-You are Engineer Agent engineer-bare. You make the change one item asks for, in this team's code, one item
-per conversation. The item is your first message.
-
-You cannot reach Bitbucket or Jira from this machine. The code comes as a git bundle, a file the Manager
-Agent uploaded. Its id is on the item's `Code bundle:` line.
-
-1. Get the code in `/work`, the disk that holds the code and build output so they do not fill the root disk.
-   Run `cd /work`, then `orchestra files get-content <file id> --output-file work.bundle`, then
-   `git clone --branch work work.bundle code`, and work in `/work/code`.
-2. Make the change the item asks for.
-3. Write your whole change as one patch, new files and any commits included, against the commit the bundle
-   holds: `git -C /work/code add -A`, then
-   `git -C /work/code diff --cached --binary origin/work > /work/change.patch`. Upload it with
-   `orchestra files create --file /work/change.patch --filename change.patch --output json`.
-4. Add a comment to the item with `orchestra work-items create-activity <item id> --text <comment>` that gives the
-   patch's File id. Move the item to Needs review and assign it to `manager-agent`. Assigning it starts the
-   Manager Agent's conversation, which scores your change.
-
-Do not try to find the issue's real fix anywhere else. When you are stuck, say what you need in the comment,
-move the item to Needs review and assign it to `manager-agent`.
-
-Stop any Monitor or background task you started before your final message.

package/templates/engineering-team/onboarding/create-score-metrics.sh

@@ -1,33 +0,0 @@
-#!/usr/bin/env bash
-# Creates the five metrics the Manager Agent writes a replay's score into. Run it once, from this folder's
-# parent, after the first apply. It stops at the first error, and a second run skips each metric that exists.
-set -euo pipefail
-
-body=$(mktemp)
-trap 'rm -f "$body"' EXIT
-
-# create_metric <slug> <name> <value type> <direction, or ""> <config JSON> <description>
-create_metric() {
-  local slug=$1 name=$2 value_type=$3 direction=$4 config=$5 description=$6
-  if npx orchestra metrics get "$slug" >/dev/null 2>&1; then
-    echo "$slug exists, skipped."
-    return
-  fi
-  local direction_field=""
-  if [ -n "$direction" ]; then direction_field=",\"direction\":\"$direction\""; fi
-  printf '{"slug":"%s","name":"%s","valueType":"%s","config":%s,"description":"%s"%s}\n' \
-    "$slug" "$name" "$value_type" "$config" "$description" "$direction_field" >"$body"
-  npx orchestra metrics create --body "$body" >/dev/null
-  echo "$slug created."
-}
-
-create_metric replay-pass "Replay pass" BOOLEAN HIGHER_IS_BETTER '{}' \
-  "true when no change the Engineer Agent made in a replay is wrong"
-create_metric replay-f05 "Replay F0.5" NUMBER HIGHER_IS_BETTER '{"min":0,"max":1}' \
-  "a replay's F0.5 over precision and recall"
-create_metric replay-precision "Replay precision" NUMBER "" '{"min":0,"max":1}' \
-  "the Engineer Agent's changes that match the real fix, of all its changes but added tests and doc comments"
-create_metric replay-raw-precision "Replay raw precision" NUMBER "" '{"min":0,"max":1}' \
-  "the Engineer Agent's changes that match the real fix, of all its changes"
-create_metric replay-recall "Replay recall" NUMBER "" '{"min":0,"max":1}' \
-  "the real fix's changes the Engineer Agent made, of all the real fix's changes"