zinkee 0.1.40 → 0.1.42

package/.github/workflows/npm-publish.yml

@@ -0,0 +1,77 @@
+name: Publish to npm
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  publish:
+    name: Publish package
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          registry-url: https://registry.npmjs.org
+          package-manager-cache: false
+
+      - name: Check package version
+        id: version
+        shell: bash
+        run: |
+          package_name="$(node -p "require('./package.json').name")"
+          package_version="$(node -p "require('./package.json').version")"
+
+          set +e
+          lookup_output="$(npm view "${package_name}@${package_version}" version 2>&1)"
+          lookup_status=$?
+          set -e
+
+          if [ "$lookup_status" -eq 0 ]; then
+            echo "${package_name}@${package_version} is already published; skipping."
+            echo "already-published=true" >> "$GITHUB_OUTPUT"
+          elif echo "$lookup_output" | grep -q "E404"; then
+            echo "${package_name}@${package_version} is not published yet."
+            echo "already-published=false" >> "$GITHUB_OUTPUT"
+          else
+            echo "$lookup_output" >&2
+            exit "$lookup_status"
+          fi
+
+      - name: Set up trusted publishing
+        if: steps.version.outputs.already-published == 'false'
+        run: npm install --global npm@11.5.1
+
+      - name: Install dependencies
+        if: steps.version.outputs.already-published == 'false'
+        run: npm ci
+
+      - name: Run tests
+        if: steps.version.outputs.already-published == 'false'
+        run: npm test
+
+      - name: Run typecheck
+        if: steps.version.outputs.already-published == 'false'
+        run: npm run typecheck
+
+      - name: Build project
+        if: steps.version.outputs.already-published == 'false'
+        run: npm run build
+
+      - name: Inspect package contents
+        if: steps.version.outputs.already-published == 'false'
+        run: npm pack --dry-run
+
+      - name: Publish package
+        if: steps.version.outputs.already-published == 'false'
+        run: npm publish --access public

package/.github/workflows/pr-checks.yml

@@ -0,0 +1,36 @@
+name: PR Checks
+
+on:
+  pull_request:
+    branches:
+      - main
+
+permissions:
+  contents: read
+
+jobs:
+  validate:
+    name: Test, Typecheck, and Build
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests
+        run: npm test
+
+      - name: Run typecheck
+        run: npm run typecheck
+
+      - name: Build project
+        run: npm run build

package/AGENTS.md

@@ -37,6 +37,7 @@ Use this order when reasoning about behavior:
 - `displays`
 - `automations`
 - `document-templates`
+- `formulas`
 
 ## Implementation Shape
 
@@ -101,8 +102,9 @@ Prefer focused command tests and parser/client unit tests.
 
 - Versioning is patch-only today (`0.1.x`). Bump the patch number unless the
   team decides to move to a different scheme.
-- Every PR that ships user-visible changes (new commands, fixed examples,
-  behaviour changes) bumps `package.json` version in the same PR — not in a
-  separate "release" PR.
+- If an agent determines that a PR requires a new published version, it must
+  bump the version in `package.json` in that same PR and keep
+  `package-lock.json` in sync. User-visible changes (new commands, fixed
+  examples, behaviour changes) always require this.
 - Before bumping, fetch `origin/main` to make sure the version you pick isn't
   already taken by another PR that merged ahead of yours.

package/README.md

@@ -18,6 +18,7 @@ Implemented command groups:
 - `displays`
 - `automations`
 - `document-templates`
+- `formulas`
 
 ## Requirements
 
@@ -815,6 +816,27 @@ zinkee document-templates assets download <template-uuid> <asset-uuid> > contrac
 
 ---
 
+## Formula recalculation
+
+Queue a full recalculation without changing the formula text. Acceptance means
+the work was queued; it does not mean calculation has completed.
+
+```bash
+zinkee formulas recompute field <schema> <field>
+zinkee formulas recompute schema <schema> --yes
+zinkee formulas recompute workspace --yes
+```
+
+`schema` and `field` accept UUIDs or slugs. Prefer the smallest useful scope.
+Schema and workspace recalculations require `--yes` because they can enqueue
+substantial work and trigger dependent formula cascades. All three commands are
+blocked by global `--read-only` mode.
+
+Use `--json --example formulas recompute <scope>` for canonical payloads and
+responses.
+
+---
+
 ## Discovery
 
 ```bash
@@ -825,5 +847,6 @@ zinkee --json automations list
 zinkee --json automations plugins list
 zinkee --json automations connections list
 zinkee --json document-templates list
+zinkee --json formulas recompute field <schema> <field>
 zinkee --example <command path>
 ```