datex-studio-cli 0.4.22__tar.gz → 0.4.24__tar.gz

datex_studio_cli-0.4.24/.dockerignore

@@ -0,0 +1,25 @@
+# Context for quartermaster/Dockerfile (built from the repo root).
+.git
+.venv
+**/__pycache__
+.pytest_cache
+.mypy_cache
+.ruff_cache
+.claude
+.serena
+node_modules
+**/node_modules
+src/dxs/web/frontend
+tests
+quartermaster/tests
+quartermaster/.env
+docs
+documentation
+exploration
+examples
+example-reports
+exclude
+skills
+otel
+dist
+*.analysis.md

datex_studio_cli-0.4.24/.github/actionlint.yaml

@@ -0,0 +1,4 @@
+self-hosted-runner:
+  # Repo-scoped ARC scale set on datex-apps-eus (spec §5; CI-only, no cluster access).
+  labels:
+    - arc-dxs

datex_studio_cli-0.4.24/.github/workflows/build-image.yml

@@ -0,0 +1,71 @@
+# Image build + staging digest bump (spec §5, §6). CI runs in-workflow: red
+# tests produce no image. The final step commits the pushed digest to
+# quartermaster/deploy/staging/values.yaml with GITHUB_TOKEN — which natively
+# triggers no further workflow runs, so the rebuild loop is impossible.
+name: Build image
+
+on:
+  push:
+    branches: [main]
+    paths-ignore:
+      - "docs/**"
+      - "**.md"
+  workflow_dispatch:
+
+concurrency:
+  group: build-image-main
+  cancel-in-progress: false
+
+permissions:
+  contents: write
+  packages: write
+
+jobs:
+  ci:
+    uses: ./.github/workflows/ci.yml
+
+  build:
+    needs: ci
+    runs-on: arc-dxs
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v4
+      - uses: docker/setup-buildx-action@v3
+      - uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - id: meta
+        run: echo "datetag=$(date -u +%Y%m%d).${{ github.run_number }}" >> "$GITHUB_OUTPUT"
+      - id: build
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          file: quartermaster/Dockerfile
+          platforms: linux/amd64
+          push: true
+          tags: |
+            ghcr.io/datex/quartermaster:${{ github.sha }}
+            ghcr.io/datex/quartermaster:latest
+            ghcr.io/datex/quartermaster:${{ steps.meta.outputs.datetag }}
+      - name: Commit the staging digest bump
+        run: |
+          digest='${{ steps.build.outputs.digest }}'
+          sed -i -E "s|^  digest:.*|  digest: \"${digest}\"|" quartermaster/deploy/staging/values.yaml
+          if git diff --quiet; then
+            echo "staging already runs ${digest}; nothing to commit"
+            exit 0
+          fi
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git add quartermaster/deploy/staging/values.yaml
+          git commit -m "chore(deploy): staging → ${digest}"
+          for attempt in 1 2 3; do
+            if git push origin HEAD:main; then
+              exit 0
+            fi
+            git pull --rebase origin main
+          done
+          echo "digest bump push failed after 3 attempts" >&2
+          exit 1

datex_studio_cli-0.4.24/.github/workflows/ci.yml

@@ -0,0 +1,55 @@
+# CI (spec §5): two jobs, both always run — the uv workspace couples the CLI
+# and the service. Callable from build-image.yml and release.yml so a red
+# suite produces no image and no release (the pipeline is the gate, not the
+# merge — GitHub Free has no required checks).
+name: CI
+
+on:
+  pull_request:
+    paths-ignore:
+      - "docs/**"
+      - "**.md"
+  workflow_call:
+
+concurrency:
+  group: ci-${{ github.head_ref || github.run_id }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  cli:
+    runs-on: arc-dxs
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv python install 3.13
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+      - name: Build the report renderer bundle (snapshot tests shell out to it)
+        working-directory: src/dxs/web/frontend
+        run: |
+          npm ci
+          npm run build:render-cli
+      - run: uv sync --all-packages --extra dev
+      - run: uv run ruff check .
+      - name: mypy (non-blocking — 21 pre-existing errors, see #171)
+        run: uv run mypy src/dxs
+        continue-on-error: true
+      - run: uv run pytest -q
+
+  service:
+    runs-on: arc-dxs
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv python install 3.13
+      - run: uv sync --all-packages --extra dev
+      - run: uv run ruff check quartermaster
+      - run: uv run --package quartermaster mypy quartermaster/src/quartermaster
+      - run: uv run --package quartermaster pytest quartermaster/tests -q

datex_studio_cli-0.4.24/.github/workflows/promote-prod.yml

@@ -0,0 +1,104 @@
+# Prod promotion by git commit (spec §6): dispatch-only, typed confirmation,
+# moving-ref rejection, GHCR existence preflight, staging-parity assert
+# (promote-what-you-tested). Rollback = re-dispatch the previous digest with
+# the parity override. Actor and inputs are recorded in the run and commit.
+# NOTE: no `environment:` on jobs — the pre-existing `production` environment
+# carries a protected_branches policy no branch can satisfy on this plan.
+name: Promote prod
+
+on:
+  workflow_dispatch:
+    inputs:
+      ref:
+        description: "Immutable image digest (sha256:…) or the git SHA of a staging bump commit"
+        required: true
+      confirm:
+        description: 'Type "promote-to-prod" to confirm'
+        required: true
+      override_parity:
+        description: "Promote even though staging is not currently running this digest (rollbacks)"
+        type: boolean
+        default: false
+
+concurrency:
+  group: promote-prod
+  cancel-in-progress: false
+
+permissions:
+  contents: write
+  packages: read
+
+jobs:
+  promote:
+    runs-on: arc-dxs
+    timeout-minutes: 15
+    steps:
+      - name: Typed confirmation
+        run: |
+          if [ "${{ inputs.confirm }}" != "promote-to-prod" ]; then
+            echo "confirmation mismatch: expected the literal string promote-to-prod" >&2
+            exit 1
+          fi
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - id: resolve
+        name: Resolve digest (moving refs rejected)
+        run: |
+          ref='${{ inputs.ref }}'
+          if echo "$ref" | grep -qE '^sha256:[0-9a-f]{64}$'; then
+            digest="$ref"
+          elif echo "$ref" | grep -qE '^[0-9a-f]{7,40}$'; then
+            digest=$(git show "${ref}:quartermaster/deploy/staging/values.yaml" | awk -F'"' '/^  digest:/ {print $2}')
+            if ! echo "$digest" | grep -qE '^sha256:[0-9a-f]{64}$'; then
+              echo "commit ${ref} carries no staging digest" >&2
+              exit 1
+            fi
+          else
+            echo "ref must be an immutable digest or a git SHA — tags like 'latest' are rejected" >&2
+            exit 1
+          fi
+          echo "digest=${digest}" >> "$GITHUB_OUTPUT"
+      - name: GHCR existence preflight
+        run: |
+          token=$(curl -sf -u "x:${{ secrets.GITHUB_TOKEN }}" \
+            "https://ghcr.io/token?scope=repository:datex/quartermaster:pull" | \
+            sed -E 's/.*"token":"([^"]+)".*/\1/')
+          curl -sf -o /dev/null \
+            -H "Authorization: Bearer ${token}" \
+            -H "Accept: application/vnd.oci.image.index.v1+json, application/vnd.docker.distribution.manifest.v2+json, application/vnd.oci.image.manifest.v1+json" \
+            "https://ghcr.io/v2/datex/quartermaster/manifests/${{ steps.resolve.outputs.digest }}" \
+            || { echo "digest not found in GHCR — nothing to promote" >&2; exit 1; }
+      - name: Staging-parity assert (promote-what-you-tested)
+        run: |
+          staging=$(awk -F'"' '/^  digest:/ {print $2}' quartermaster/deploy/staging/values.yaml)
+          if [ "$staging" != "${{ steps.resolve.outputs.digest }}" ]; then
+            if [ "${{ inputs.override_parity }}" = "true" ]; then
+              echo "parity override: staging runs ${staging}, promoting ${{ steps.resolve.outputs.digest }} anyway"
+            else
+              echo "staging currently runs ${staging}, not the requested digest — pass override_parity for rollbacks" >&2
+              exit 1
+            fi
+          fi
+      - name: Commit the prod digest bump
+        run: |
+          digest='${{ steps.resolve.outputs.digest }}'
+          sed -i -E "s|^  digest:.*|  digest: \"${digest}\"|" quartermaster/deploy/prod/values.yaml
+          if git diff --quiet; then
+            echo "prod already runs ${digest}; nothing to commit"
+            exit 0
+          fi
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git add quartermaster/deploy/prod/values.yaml
+          git commit \
+            -m "chore(deploy): prod → ${digest}" \
+            -m "Promoted by @${{ github.actor }} via promote-prod (ref input: ${{ inputs.ref }})"
+          for attempt in 1 2 3; do
+            if git push origin HEAD:main; then
+              exit 0
+            fi
+            git pull --rebase origin main
+          done
+          echo "prod bump push failed after 3 attempts" >&2
+          exit 1

datex_studio_cli-0.4.24/.github/workflows/release.yml

@@ -0,0 +1,54 @@
+# The CLI's PyPI release lane (spec §5), retiring publish.sh and ~/.pypirc.
+# Tag vX.Y.Z → full CI → version-agreement assert (the uv.lock entry is the
+# one nothing else updates) → frontend build with a hard existence check (the
+# gitignored web/static/ ships via hatch `artifacts`, which silently includes
+# nothing when absent) → uv build + publish via PyPI trusted publishing.
+# Prerequisite: a trusted publisher for this repo/workflow configured on PyPI.
+name: Release to PyPI
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  ci:
+    uses: ./.github/workflows/ci.yml
+
+  publish:
+    needs: ci
+    runs-on: arc-dxs
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v4
+      - name: Assert tag == pyproject == __init__ == uv.lock
+        run: |
+          tag="${GITHUB_REF#refs/tags/v}"
+          pyproject=$(grep -m1 '^version = ' pyproject.toml | cut -d'"' -f2)
+          init=$(grep -m1 '__version__' src/dxs/__init__.py | cut -d'"' -f2)
+          lock=$(awk '/^name = "datex-studio-cli"$/ {found=1} found && /^version = / {print; exit}' uv.lock | cut -d'"' -f2)
+          echo "tag=${tag} pyproject=${pyproject} __init__=${init} uv.lock=${lock}"
+          if [ "$tag" != "$pyproject" ] || [ "$pyproject" != "$init" ] || [ "$pyproject" != "$lock" ]; then
+            echo "version sources disagree — run 'uv lock' and align all three before tagging" >&2
+            exit 1
+          fi
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv python install 3.13
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+      - name: Build the web UI (shipped via hatch artifacts)
+        working-directory: src/dxs/web/frontend
+        run: |
+          npm ci
+          npm run build
+      - name: Assert the frontend build actually produced the static export
+        run: test -f src/dxs/web/static/index.html
+      - run: uv build
+      - name: Publish via trusted publishing
+        run: uv publish

{datex_studio_cli-0.4.22 → datex_studio_cli-0.4.24}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: datex-studio-cli
-Version: 0.4.22
+Version: 0.4.24
 Summary: CLI for Datex Studio low-code platform, designed for LLM-based AI agents
 Project-URL: Homepage, https://github.com/datex/datex-studio-cli
 Project-URL: Documentation, https://github.com/datex/datex-studio-cli
@@ -179,13 +179,13 @@ Configuration values are resolved in order:
 
 ```bash
 # View current configuration
-dxs config list
+dxs settings list
 
 # Set a default
-dxs config set default_repo 10
+dxs settings set default_repo 10
 
 # Get a specific value
-dxs config get default_repo
+dxs settings get default_repo
 ```
 
 Configuration stored in `~/.datex/config.yaml`. Credentials stored separately in `~/.datex/credentials.yaml`.
@@ -225,7 +225,7 @@ dxs auth list
 dxs auth switch other-org
 ```
 
-### Configuration (`dxs config`)
+### CLI Settings (`dxs settings`)
 
 | Command | Description |
 |---------|-------------|

{datex_studio_cli-0.4.22 → datex_studio_cli-0.4.24}/README.md

@@ -126,13 +126,13 @@ Configuration values are resolved in order:
 
 ```bash
 # View current configuration
-dxs config list
+dxs settings list
 
 # Set a default
-dxs config set default_repo 10
+dxs settings set default_repo 10
 
 # Get a specific value
-dxs config get default_repo
+dxs settings get default_repo
 ```
 
 Configuration stored in `~/.datex/config.yaml`. Credentials stored separately in `~/.datex/credentials.yaml`.
@@ -172,7 +172,7 @@ dxs auth list
 dxs auth switch other-org
 ```
 
-### Configuration (`dxs config`)
+### CLI Settings (`dxs settings`)
 
 | Command | Description |
 |---------|-------------|

datex_studio_cli-0.4.24/inspections.md

@@ -0,0 +1,147 @@
+# Marketing Brief: Footprint Inspections Module
+
+## Executive Summary
+
+**Product**: Footprint Inspections Module
+**Platform**: Footprint Warehouse Management System (Datex Studio)
+**Category**: Quality Control & Compliance Management
+**Target Market**: 3PL providers, distribution centers, manufacturing warehouses, regulated industries
+
+---
+
+## Product Overview
+
+The Footprint Inspections module delivers enterprise-grade quality control and compliance verification capabilities embedded directly within warehouse operations. It transforms ad-hoc quality checks into systematic, auditable workflows that drive accountability and regulatory compliance.
+
+---
+
+## Target Audience
+
+### Primary Users
+- **Quality Control Personnel** — Execute daily inspection tasks and complete quality surveys
+- **Warehouse Supervisors** — Create and assign inspection work, monitor completion rates
+- **Compliance Officers** — Configure inspection protocols, audit survey results, ensure regulatory adherence
+
+### Decision Makers
+- VP of Operations / Chief Operations Officer
+- Quality Assurance Directors
+- Warehouse General Managers
+- Compliance & Regulatory Affairs Leaders
+
+---
+
+## Key Value Propositions
+
+### 1. Unified Quality Workflow
+Inspections are first-class warehouse tasks—not separate systems. They share the same task lifecycle (Created → Released → Started → Completed) as picking, putaway, and other operations. This means one training model, one labor pool, and one visibility dashboard.
+
+### 2. Granular Targeting
+Create inspection tasks at any level of specificity:
+- **Location-level** — Inspect a rack, zone, or staging area
+- **License plate-level** — Target specific pallets or containers
+- **Material & lot-level** — Focus on SKUs, batches, or vendor lots
+
+### 3. Built-In Survey Integration
+Link structured quality surveys to inspection tasks. Surveys capture standardized data points—temperature readings, damage assessments, packaging integrity—providing auditable evidence trails for regulators and customers.
+
+### 4. Bulk Operations for Scale
+Process inspections at scale with bulk status changes. Supervisors can advance 50, 100, or 500 tasks simultaneously—critical during receiving surges, pre-ship audits, or periodic compliance sweeps.
+
+### 5. Configurable Operation Codes
+Define custom inspection types (e.g., "Receiving QC", "Pre-Ship Audit", "Temperature Verification", "Lot Trace Inspection") to match your operational vocabulary and reporting requirements.
+
+---
+
+## Feature Highlights
+
+| Capability | Benefit |
+|------------|---------|
+| **Task Creation Wizard** | Guided form ensures all required fields captured—no missing data |
+| **Multi-Status Filtering** | Instantly view open inspections, completed today, or overdue tasks |
+| **Date Range Queries** | Filter by created, released, started, or completed timestamps |
+| **Full-Text Search** | Find tasks by material name, lot number, or notes |
+| **Labor Management Integration** | Inspection tasks flow into workforce assignment for labor-tracked environments |
+| **Role-Based Access Control** | Granular permissions—restrict hub access or default warehouse scope |
+
+---
+
+## Integration Points
+
+### Survey System
+Inspections link directly to the Surveys module. Quality personnel complete standardized checklists, and results attach permanently to inspection records—providing audit-ready documentation.
+
+### Labor Management
+Inspection operation codes can be flagged as "Eligible for Labor Management," enabling supervisors to assign QC work alongside picks and puts through a unified workforce planning interface.
+
+### Inventory Context
+Every inspection carries full inventory lineage: warehouse, location, license plate, material, lot, and vendor lot. This context powers traceability reports and root-cause analysis.
+
+---
+
+## Compliance & Audit Benefits
+
+- **Immutable Timestamps** — Created, released, started, and completed times auto-captured
+- **Operation Code Categorization** — Classify inspections for regulatory reporting (FDA, USDA, customer audits)
+- **Survey Evidence** — Attach photos, temperature readings, and structured responses
+- **Deletion Controls** — Operation codes with linked tasks cannot be deleted, preserving audit integrity
+
+---
+
+## Competitive Differentiators
+
+| Traditional QC Systems | Footprint Inspections |
+|------------------------|----------------------|
+| Separate application requiring integration | Native module within WMS—zero integration cost |
+| Paper-based or standalone mobile app | Web-based hub + mobile-ready for handheld devices |
+| Quality data siloed from inventory | Inspections linked to real-time inventory records |
+| Manual labor tracking | Automatic labor capture when integrated with Labor Management |
+| Limited configurability | Fully customizable operation codes, surveys, and access controls |
+
+---
+
+## Use Cases
+
+### Receiving Quality Control
+Create inspection tasks automatically upon ASN receipt. QC personnel inspect materials before putaway, completing surveys that capture damage photos, quantity counts, and lot verification.
+
+### Pre-Ship Audits
+Before orders release to shipping, generate inspection tasks for high-value or regulated products. Confirm packaging integrity, label accuracy, and temperature compliance.
+
+### Periodic Compliance Sweeps
+Schedule weekly or monthly inspection batches across storage zones. Track completion rates and escalate overdue tasks to supervisors.
+
+### Customer-Mandated QC
+Configure customer-specific operation codes (e.g., "Customer ABC 100% Inspect") with linked surveys matching SLA requirements. Provide customers with survey exports as proof of compliance.
+
+---
+
+## Technical Specifications
+
+| Attribute | Value |
+|-----------|-------|
+| Platform | Datex Studio Low-Code |
+| Deployment | Cloud-hosted SaaS |
+| API | REST/OData for inspection task queries |
+| Data Export | Native Excel export from task grids |
+| Permissions Model | Operation-based access control |
+| Audit Trail | Full timestamp capture on all status transitions |
+
+---
+
+## Pricing Position
+
+The Inspections module is included in the Footprint Planning tier. Customers with base Footprint WMS licenses may require a Planning add-on to access Inspections and Labor Management capabilities.
+
+---
+
+## Call to Action
+
+**For Sales Teams**: Position Inspections as a compliance accelerator for FDA-regulated, food-grade, and high-value inventory operations. Lead with audit trail capabilities and survey integration.
+
+**For Marketing Campaigns**: Highlight the unified task model—"One system for picks, puts, and QC"—to differentiate against point solutions.
+
+**For Customer Success**: Offer inspection workflow design sessions as part of onboarding to ensure operation codes and surveys match customer processes from day one.
+
+---
+
+*For detailed technical documentation, refer to the Footprint Planning section documentation.*