Run details

GhostWorkspace

CI Pipeline Executions
- Current executionSucceeded
  claude/zod-config-schema-5979a1
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Added descriptions to the config schema, and a step to keep adding them no ref z.toJSONSchema() carries .meta() descriptions and examples straight through, so the schema can generate a config reference for self-hosters later. That only works if the metadata is there, and writing it with the key costs a line while retrofitting it across every key is a sweep nobody will volunteer for. So it is now a step in the SCHEMA.md instructions, and the two keys that have schemas today carry their own descriptions rather than telling the next person to do something the existing examples do not. .meta() registers in zod's registry and does not affect parsing, so the round-trip test over the shipped env configs is unchanged.

nx run ghost-monorepo:lint:boundaries

Succeeded

4 CPU cores

read-write access token used

104b9b1930936

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

GhostWorkspace