ikigai-script 0.3.5

Scripts (Lisp; SPARQL queries with typed parameters and authority derived from the graphs they name; or plans, validated before they are stored, with authority derived from their steps) as resources in any ikigai host: `urn:script:{name}` is an atom with content-addressed versions, a compiled form, a result you read and runs you record, run under the least of what the script declares, what its publisher held at publish time, the host's ceiling and the runner's own capability. A host library: no binary, no elevation.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

name: ci
on:
  push: { branches: [main] }
  pull_request:
concurrency:
  group: ci-${{ github.ref }}
  cancel-in-progress: ${{ github.event_name == 'pull_request' }}   # never cancel main
jobs:
  ci:
    uses: ikigai-rs/.github/.github/workflows/rust.yml@main
    # `features:` — the test-only `http-client-probe` (ledger #1085), which compiles oxigraph's
    # HTTP client into the test build the way rudof does in ikigai-cli, so
    # `tests/sparql_service_egress.rs` proves a SERVICE or LOAD script reaches no network, and
    # its controls prove the client is live. Without this job those tests run only half.
    with:
      features: http-client-probe
    # The other absences are decisions:
    #
    # `wasm-lib:` — not claimed. The library itself is plain Rust, but `DirBackend` is
    # `std::fs`, and a gate that has never run is not evidence. When a browser host wants
    # scripts, the line goes in with the work that makes it true.
    #
    # msrv — automatic: `rust-version` in Cargo.toml makes the shared workflow run clippy
    # and test on it.