gtmesh status

Prints the state of the mesh: per-status counts, drift, the writer’s worklist, and (with --env) the renderable set for an environment.

gtmesh status [--env <env>] [--summary]

What it does

gtmesh status is the read-only dashboard for your registry. In one command it shows:

• Per-status counts — how many rows sit in each lifecycle state (planned/backlog, queued, writing, review, published, needs_update).
• Drift — rows whose inputs have changed since they were built, i.e. what the next plan/apply will act on.
• The writer worklist — the pages currently in writing that need a body.
• The render set — with --env, the slugs that would render for that environment (the same set render-manifest emits).

Pass --summary for counts only, when you don’t want the writing worklist.

It changes nothing — run it as often as you like.

Arguments & flags

The global options (--project, --json, --quiet) also apply.

Reads & writes

• Consumes: the committed registry (and, with --env, your environment’s render rules).
• Produces: a report to your terminal. Read-only.
• Commits: nothing.

Examples

gtmesh status                 # counts, drift, and the writer worklist
gtmesh status --summary       # just the counts
gtmesh status --env prod      # also show what would render in prod
gtmesh status --json          # machine-readable, for a script or CI

Related

• render-manifest — emit the renderable slug set to a file.
• Lifecycle & reconcile — the statuses and drift this report reflects.
• Reference — the version-exact flag list.