onetaskgraph 0.2.23

One interface over the ticketing systems your work lives in.
{
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "name": "onetaskgraph",
  "projectType": "application",
  "tags": ["lang:rust", "layer:binary"],
  "//": "implicitDependencies mirror this crate's Cargo dependencies; scripts/check-nx-graph.sh fails when the two disagree. llmlint: ignore-file[expensive_tests_stay_behind_their_own_edge,external_service_suite_stays_out_of_the_affected_tier] JSON has no comment to scope either to `test`, where tests/live.rs reads the public registries; affected selection is the edge, and AGENTS.md records why. The second name is here on the same terms the two plugin crates carry it on, and for the same reason stated one level up: a registry read is a check the merge waits on or it is not a check at all. This repository had the arrangement that rule describes -- the suite outside the required tier, advisory -- and a query GitHub refuses outright reached the default branch through it, because auto-merge waits only on required checks and nobody read the red advisory one. So tests/live.rs is an ordinary test of this crate, and affected selection is what keeps it off every other change.",
  "implicitDependencies": [
    "onetaskgraph-core",
    "onetaskgraph-github-projects",
    "onetaskgraph-linear",
    "onetaskgraph-plugin-api"
  ],
  "targets": {
    "bootstrap": {
      "executor": "nx:run-commands",
      "options": {
        "command": "cargo fetch --locked"
      },
      "//": "Uncached: it reaches the network and writes to the shared cargo registry outside the workspace, so no input in the tree describes its result."
    },
    "check": {
      "executor": "nx:noop"
    },
    "build": {
      "executor": "nx:run-commands",
      "options": {
        "command": "cargo build --quiet -p onetaskgraph --bin onetaskgraph --locked"
      },
      "//": "Integration tests and both SDK generators execute this binary. Making it an Nx target lets every consumer depend on one completed build instead of racing independent Cargo commands that replace the executable on macOS."
    },
    "format": {
      "executor": "nx:run-commands",
      "options": {
        "command": "cargo fmt -p onetaskgraph"
      },
      "cache": false,
      "//": "Uncached: it rewrites the tree in place, so replaying a cached result would be a no-op that silently leaves the tree unformatted."
    },
    "format-check": {
      "executor": "nx:run-commands",
      "options": {
        "command": "cargo fmt -p onetaskgraph -- --check"
      }
    },
    "lint": {
      "executor": "nx:run-commands",
      "options": {
        "command": "cargo clippy --quiet -p onetaskgraph --all-targets --all-features --locked -- -D warnings"
      }
    },
    "typecheck": {
      "executor": "nx:run-commands",
      "options": {
        "command": "cargo check --quiet -p onetaskgraph --all-targets --all-features --locked"
      }
    },
    "test": {
      "executor": "nx:run-commands",
      "dependsOn": ["build"],
      "options": {
        "command": "cargo test --quiet -p onetaskgraph --all-features --locked --target-dir target/tests/onetaskgraph"
      },
      "//": "Cargo builds CARGO_BIN_EXE_onetaskgraph once in this target's private directory before starting any integration-test executable. Gate targets run concurrently, so sharing target/debug lets another Cargo invocation replace the binary between a test resolving and spawning it on macOS."
    },
    "coverage": {
      "executor": "nx:run-commands",
      "options": {
        "command": "bash scripts/rust-coverage.sh onetaskgraph"
      }
    }
  }
}