Stage exactly the listed trace-relative paths and commit. Replaces the `add -A` sweep with an explicit declaration of what this commit contains. Calle

`git init` in `root`. Idempotent — re-init on an existing repo is a no-op.

* Log error - for failures that impact functionality * Use when: API calls fail, validation fails, unexpected states

Follow `$ref` references through the root's definitions to land on a concrete SchemaObject. Returns the input unchanged if no ref. Also handles schem

SHA of HEAD. Errors if the repo has no commits yet.

Open the repo that owns `root`. Walks up from `root` so a trace folder nested inside a parent repo resolves to that parent (single-repo layout). When

Classify a filesystem event path into an SSE event body. `scope_root` MUST be canonicalized (see AppState::new). `path` MUST be the absolute path prod

Entry point: render the schema rooted at `path` in the requested format.

Locate the trace that owns the given run id. Returns `(trace_id, trace_root)`. Backed by `AppState.run_index`: hot path is one HashMap lookup. Cold m

Read state.json, apply the mutation, write it back, then commit — all on a blocking task so the async runtime worker isn't parked on disk I/O. The cal

* Format log message with context

`<trace_root>/runs/<run_id>/replies/`

Prefix a trace-relative path with the subpath portion, if any. Used when looking up paths via libgit2 (commits_under, show_at) — git always wants repo

* Log warning - for recoverable issues or unexpected but handled situations * Use when: Fallbacks are used, deprecated features, validation warning

If `s` is an array, return its element schema; else `None`. Tuple-typed arrays (`items: [schema, schema, …]`) and boolean-schema items are not support

Apply `check_and_normalize` to a slice, surfacing the offending value together with its reason so the caller can build an appropriate error type.

Human-readable type label for one schema node: `string`, `integer`, `[]Evidence`, `map<string, StepState>`, `oneOf`, named-ref types, etc.

Invalidate the trace cache. Call after any trace.json mutation or scope change so the next read picks up the new state immediately. Also drops the run

Acquire `extra_scopes` lock, recovering from a poisoned mutex. Poisoning is harmless here: the protected `Vec<PathBuf>` is plain data with no broken i

If `s` is a "map type" (object with `additionalProperties` and no declared properties — what schemars emits for `BTreeMap<String, T>`), return the val

Find the scope root that contains the given path (if any).

The step id this reply is pinned to, if any.

For a `#[serde(tag = "...", rename_all = "snake_case")]` enum variant, schemars emits an object whose tag field is a `const` string. Return that const

Append a new reply file. Returns the assigned seq and timestamp. `step_id` on the persisted record is always derived from `payload.checkpoint.step_id

Combine validation + normalization into the single call used at write sites.

Build a [`StepFile`] from a directory entry, or `None` to skip it: not a regular file, hidden (dotfile), or — defensively — resolving outside `scope_r

Commits whose tree changed `rel_path` (file or directory), newest first. `rel_path` is trace-relative; resolves to repo-relative internally so single-

Collect every run-relative path cited by `evidence[]`, deduped, in order. Walks `figure.path`, `document.path`, `table.source_file`, `comparison.left.