Kevin/add completions upload script, defaults, and tests

.circleci/config.yml

@@ -0,0 +1,55 @@
+version: 2.1
+
+jobs:
+  test:
+    parameters:
+      executor:
+        type: executor
+    executor: << parameters.executor >>
+    steps:
+      - checkout
+      - node/install:
+          node-version: '24'
+      - run:
+          name: Enable linger for current user (Linux only)
+          command: |
+            if [[ "$OSTYPE" == "linux"* ]]; then
+              loginctl enable-linger $(whoami)
+              sudo chown -R circleci:circleci /usr/local /opt /var/tmp
+            fi
+      - run:
+          name: Install dependencies
+          command: npm ci
+      - run:
+          name: Clean up pre-installed tools
+          command: npx tsx scripts/cleanup-circleci.ts
+          no_output_timeout: 10m
+      - run:
+          name: Run tests
+          command: npm run test -- ./test --no-file-parallelism --disable-console-intercept
+          no_output_timeout: 30m
+
+orbs:
+  node: circleci/node@6
+
+executors:
+  linux-x86:
+    machine:
+      image: ubuntu-2404:current
+    resource_class: medium
+  linux-arm:
+    machine:
+      image: ubuntu-2404:current
+    resource_class: arm.medium
+  macos:
+    macos:
+      xcode: '26.4.0'
+    resource_class: m4pro.medium
+
+#workflows:
+#  test-all:
+#    jobs:
+#      - test:
+#          matrix:
+#            parameters:
+#              executor: [linux-arm]

.claude/commands/add-examples.md

@@ -0,0 +1,61 @@
+# add-examples
+
+Add `defaultConfig` and `exampleConfigs` to a Codify resource.
+
+## Instructions
+
+The user will either pass a file path as an argument (`$ARGUMENTS`) or have a file open in the IDE. Read the resource file, then follow the rules below to add `defaultConfig` and `exampleConfigs`.
+
+If `$ARGUMENTS` is provided, use that file path. Otherwise use the file the user has open.
+
+### Step 1 — Read the resource
+
+Read the resource file. Identify:
+- The config interface/type (fields, which are required vs optional)
+- `operatingSystems` declared in `getSettings()` — determines whether to add `os` to examples
+- `dependencies` — used to decide whether to show a multi-resource example
+- Any existing `defaultConfig` or `exampleConfigs` (update rather than duplicate)
+
+If the schema is a separate JSON file, read it too.
+
+Also check for sibling resources that are commonly used together (e.g. if this resource `dependsOn` another type, read that type's file to understand its config shape).
+
+### Step 2 — Add `defaultConfig`
+
+Rules:
+- Type: `Partial<TheConfig>` (never include `os` — it's not on the typed config interface)
+- For required fields with no sensible default: use the placeholder string `'<Replace me here!'>`
+- For optional arrays that default to empty: set to `[]`
+- Omit fields that are purely user-specific (paths, names, credentials)
+- Use the tool's own documented defaults where applicable
+
+### Step 3 — Add `exampleConfigs`
+
+Rules:
+- Up to two examples: `example1` and `example2`
+- **No trivial examples** — every example must have meaningful configuration, not just `{ type: 'foo' }` with no parameters
+- `example1`: the most common real-world use case with substantive config values
+- `example2`: a more advanced variant OR a multi-resource example showing full end-to-end setup; multi-resource is preferred when the resource `dependsOn` another
+- Every example needs a `title` (short noun-phrase) and a `description` (one sentence)
+- Use realistic placeholder values for sensitive fields (`'<Replace me here!'>`), not real credentials
+- Do not add step-numbering in descriptions
+
+**`os` field in examples:**
+- The `os` field values come from the `ResourceOs` enum in `@codifycli/schemas` (`../codify-schemas/src/types/index.ts`): `'macOS'`, `'linux'`, `'windows'`
+- Add `os` to config entries inside examples only when `operatingSystems` is restricted to a single OS (e.g. Darwin-only → `os: ['macOS']`, Linux-only → `os: ['linux']`)
+- Skip `os` entirely when the resource supports both Darwin and Linux
+
+**Shared examples:**
+- When a multi-resource example is used across multiple related resources (e.g. asdf + asdf-plugin + asdf-install), define it once in a shared `examples.ts` file in the resource folder and spread it in with `...exampleSharedConfigs`
+
+### Step 4 — Import `ExampleConfig`
+
+Add `ExampleConfig` to the existing `@codifycli/plugin-core` import if not already present.
+
+### Step 5 — Register in `getSettings()`
+
+Add `defaultConfig` and `exampleConfigs` fields inside the object returned by `getSettings()`, before `operatingSystems`.
+
+## Output format
+
+Make all edits directly to the file. Do not summarise every line changed — just briefly confirm what was added.

.github/workflows/claude-fixer.yml

@@ -0,0 +1,30 @@
+name: Claude Test Fixer
+on:
+  workflow_run:
+    workflows: ["Test all cron (Linux)", "Test all cron (MacOS)"]
+    types: [completed]
+
+jobs:
+  fix-on-failure:
+    runs-on: ubuntu-latest
+    if: ${{ github.event.workflow_run.conclusion == 'failure' }}
+    permissions:
+      contents: write
+      pull-requests: write
+      actions: read # Allows Claude to read the logs of the failed run
+    steps:
+      - uses: actions/checkout@v4
+      - name: Claude Fix Failed Tests
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          prompt: |
+            The "CI Tests" workflow just failed. 
+            1. Analyze the logs from the last failed run.
+            2. Identify the root cause of the test failure.
+            3. Implement a fix and create a new pull request.
+
+
+
+          additional_permissions: |
+            actions: read

.github/workflows/run-all-tests-cron-linux.yaml

@@ -0,0 +1,46 @@
+# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs
+
+name: Test all cron (Linux)
+
+on:
+#  push:
+  pull_request:
+    branches:
+      - release
+  schedule:
+    - cron: '0 0 * * *'  # Every day at midnight UTC
+  workflow_dispatch:
+
+jobs:
+  build-and-test:
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest]
+#        os: [ubuntu-latest, ubuntu-24.04-arm, macos-latest]
+        shard: ["1/20", "2/20", "3/20", "4/20", "5/20", "6/20", "7/20", "8/20", "9/20", "10/20", "11/20", "12/20", "13/20", "14/20", "15/20", "16/20", "17/20", "18/20", "19/20", "20/20"]
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Use Node.js 24
+        uses: actions/setup-node@v4
+        with:
+          node-version: '24.x'
+          cache: 'npm'
+      - name: Enable linger for admin user (Linux only)
+        if: runner.os == 'Linux'
+        run: loginctl enable-linger $(whoami)
+
+      - run: npm ci
+      - run: npx tsx scripts/cleanup-github-actions.ts
+
+#      - name: Setup tmate session
+#        uses: mxschmitt/action-tmate@v3
+
+      - name: Run tests (Linux)
+        if: runner.os == 'Linux'
+        run: npm run test -- ./test --no-file-parallelism --disable-console-intercept  --shard ${{ matrix.shard }}
+

.github/workflows/run-all-tests-cron-macos.yaml

@@ -0,0 +1,55 @@
+# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs
+
+name: Test all cron (MacOS)
+
+on:
+#  push:
+  pull_request:
+    branches:
+      - release
+  schedule:
+    - cron: '0 0 * * *'  # Every day at midnight UTC
+  workflow_dispatch:
+
+jobs:
+  build-and-test:
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [macos-latest]
+#        os: [ubuntu-latest, ubuntu-24.04-arm, macos-latest]
+        shard: ["1/5", "2/5", "3/5", "4/5", "5/5"]
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Use Node.js 24
+        uses: actions/setup-node@v4
+        with:
+          node-version: '24.x'
+          cache: 'npm'
+
+      - run: npm ci
+      - run: npx tsx scripts/cleanup-github-actions.ts
+
+#      - name: Setup tmate session
+#        uses: mxschmitt/action-tmate@v3
+
+      - name: Run tests (macOS - zsh login shell)
+        if: runner.os == 'macOS'
+        shell: zsh {0}
+        run: |
+          sudo chsh -s $(which zsh) $USER
+          echo $0
+
+          echo $ZSH_NAME $ZSH_VERSION
+          export SHELL=/bin/zsh
+          touch ~/.zshrc
+          unset JAVA_HOME
+          export PATH=/Users/runner/.local/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/opt/curl/bin:/usr/local/bin:/usr/local/sbin:/Users/runner/bin:/usr/bin:/bin:/usr/sbin:/sbin
+          export CI=true
+
+          npm run test -- ./test --no-file-parallelism --disable-console-intercept --exclude ./test/homebrew --shard ${{ matrix.shard }}
+

.gitignore

@@ -10,3 +10,5 @@
 node_modules
 oclif.manifest.json
 .env
+.dev.vars
+*.vars

.run/test_integration_dev -- $FilePathRelativeToProjectRoot$.run.xml

@@ -1,5 +1,5 @@
 <component name="ProjectRunConfigurationManager">
-  <configuration default="false" name="test:integration:dev -- $FilePathRelativeToProjectRoot$" type="js.build_tools.npm" nameIsGenerated="true">
+  <configuration default="false" name="test:integration:dev -- $FilePathRelativeToProjectRoot$" type="js.build_tools.npm">
     <package-json value="$PROJECT_DIR$/package.json" />
     <command value="run" />
     <scripts>