Run Loom's repository checks

Loom's maintained repository workflow builds the pinned development image, installs dependencies once, runs the critical app checks, and builds the CLI and MCP. It uses two Docker jobs. Each run writes state.jsonl and events.jsonl for inspection.

From a committed Loom checkout with a reachable Docker daemon:

loom run --local --workflow .loom/workflow.yml --stream

The workflow is maintained in .loom/workflow.yml. Its verification job is:

verify:
  stage: verify
  image: loom:nix-local
  needs:
    - build-nix-image
  variables:
    NODE_OPTIONS: "--max-old-space-size=4096"
    TERSER_PARALLEL: 2
  script:
    - pnpm run install:ci
    - pnpm test
    - pnpm nx run-many -t build --projects=loom-cli,loom-mcp
  artifacts:
    paths:
      - bin/loom
      - bin/loom-mcp
    required: true

The prerequisite build-nix-image job builds nix/Dockerfile from the checkout. Each verification run installs dependencies in its fresh workspace. pnpm test selects critical checks; the optional pnpm run test:all runs the broader Go suites when a change needs them. No tests invoke the scripts/ directory.

Inspect the workflow state and execution output using the run identifier printed by loom run:

loom logs <run-id> --state
loom logs <run-id>

Add --json for the underlying JSONL records. The MCP tools loom_read_run and loom_read_events read the same files, including after the server restarts. Declared binary artifacts are stored separately from the two logging files.

This workflow is useful for dogfooding repository changes. Required GitLab CI, review, and merge-train policy remain documented in the repository's contribution guide.