@erclx/aitk 2.0.0 → 2.1.0

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aitk",
   "description": "Automated governance, versioning, and discovery tools for Claude Code.",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {

package/scripts/lib/sandbox-git.sh

@@ -15,8 +15,13 @@ require_sandbox_anchor_config() {
   fi
 }
 
+resolve_sandbox_anchor_repo() {
+  printf '%s\n' "${1:-${ANCHOR_REPO:-}}"
+}
+
 sandbox_anchor_url() {
-  local repo_name="${1:-${ANCHOR_REPO:-}}"
+  local repo_name
+  repo_name="$(resolve_sandbox_anchor_repo "$@")"
 
   if [ -z "$repo_name" ] || [ -z "${GITHUB_ORG:-}" ]; then
     log_error "sandbox_anchor_url needs GITHUB_ORG and a repository name. Call require_sandbox_anchor_config first."
@@ -52,7 +57,7 @@ configure_sandbox_git_identity() {
 
 # Every scenario that needs a remote points at the same throwaway repository, so
 # the name lives here rather than in each one.
-SANDBOX_ANCHOR_REPO="toolkit-sandbox"
+SANDBOX_ANCHOR_REPO="aitk-sandbox"
 
 # A scenario calls this from its own use_anchor hook rather than this file
 # defining the hook. manage-sandbox.sh keys off `type -t use_anchor`, so
@@ -62,11 +67,58 @@ use_sandbox_anchor() {
   export ANCHOR_REPO="${1:-$SANDBOX_ANCHOR_REPO}"
 }
 
+# gh answers an absent repository and an unreachable host with the same exit
+# status, so the 404 is the only thing separating them. Anything else is a
+# network or credential fault, where creating a repository would be the wrong
+# answer and would fail for the same reason the read did.
+ensure_sandbox_anchor_repo() {
+  local repo_name gh_error
+
+  repo_name="$(resolve_sandbox_anchor_repo "$@")"
+
+  if [ -z "$repo_name" ] || [ -z "${GITHUB_ORG:-}" ]; then
+    log_error "ensure_sandbox_anchor_repo needs GITHUB_ORG and a repository name. Call require_sandbox_anchor_config first."
+  fi
+
+  if gh_error="$(gh api "repos/${GITHUB_ORG}/${repo_name}" --silent 2>&1)"; then
+    return 0
+  fi
+
+  case "$gh_error" in
+  *"HTTP 404"*) ;;
+  *) log_error "Cannot reach ${GITHUB_ORG}/${repo_name}: ${gh_error}" ;;
+  esac
+
+  # An absent anchor is nearly always a wrong GITHUB_ORG or a rename nobody
+  # performed, and provisioning stages a fixture rather than cloning while every
+  # scenario force-pushes to main, so a repository created here would carry all
+  # nine to a pass against something that is not the anchor. Refusing is the safe
+  # default and creating is the opt-in, the shape `aitk tooling sync --write`
+  # already sets. `aitk records push` refuses outright for the reason
+  # `.claude/context/development/scratch.md` records, so the two still differ.
+  # The sibling SANDBOX_ flags are presence tests, so any non-empty value turns
+  # them on. This one allowlists instead, because a presence test would have
+  # SANDBOX_ANCHOR_CREATE=false provisioning a repository. Both spellings are
+  # accepted so the `true` those siblings are set to does not land on a refusal.
+  case "${SANDBOX_ANCHOR_CREATE:-}" in
+  1 | true) ;;
+  *) log_error "${GITHUB_ORG}/${repo_name} does not exist. Check GITHUB_ORG and whether a rename is pending, then create it with 'gh repo create ${GITHUB_ORG}/${repo_name} --private' or re-run with SANDBOX_ANCHOR_CREATE=true." ;;
+  esac
+
+  log_warn "${GITHUB_ORG}/${repo_name} does not exist and SANDBOX_ANCHOR_CREATE is set. Creating it as private."
+  if ! gh_error="$(gh repo create "${GITHUB_ORG}/${repo_name}" --private 2>&1)"; then
+    log_error "Could not create ${GITHUB_ORG}/${repo_name}: ${gh_error}"
+  fi
+  log_info "Created ${GITHUB_ORG}/${repo_name} as a private repository."
+}
+
 # A remote is useless without an author, so the scenarios that reach one always
 # configure both. configure_sandbox_git_identity stays callable on its own for
-# the scenarios that never push. The remove keeps this idempotent against a
-# sandbox tree that already carries an origin.
+# the scenarios that never push. The probe runs first so an absent remote is
+# reported before the scenario stages anything. The remove keeps this idempotent
+# against a sandbox tree that already carries an origin.
 configure_sandbox_anchor_remote() {
+  ensure_sandbox_anchor_repo "$@"
   configure_sandbox_git_identity
   git remote remove origin 2>/dev/null || true
   git remote add origin "$(sandbox_anchor_url "$@")"