jig formatted status

[dulaj-me]

Eg:

App:
  Name    : sprocket-test-dulaj ┃ ID: f1ae8348-7379-4c34-9004-6cd273d6d644
  Image   : registry.together.xyz/proj_csvnq3lka36nwbncbkkva/sprocket-test-dulaj:v0.0.3
  Status  : Ready
  Created : 2026-02-03 18:51:11 ┃ Updated : 2026-02-06 14:00:53

  Autoscaling: QueueBacklogPerWorker 1.05(target)

  Replicas:
    Min/Max         : 1/10
    Ready/Desired   : 1/1

Configuration:
  Port: 8000
  Command: []
  Args: []
  Health Check Path: /health
  Resources: 4.0 core CPU ┃ 32.0GB Memory ┃ 100GB Storage
  GPU: 1x h100-80gb

  Volumes:
    NAME                         MOUNT_PATH
    my-test-volume-2             /app/my-volume

  Secrets: ['TOGETHER_API_KEY']

  Environment Variables:
    NAME                                     VALUE
    TOGETHER_DEPLOYMENT_REVISION_ID          a6dccc34-ba86-46ba-a597-4605cbdfc551
    TOGETHER_API_BASE_URL                    https://api.together.xyz
    FOO                                      bar

Replica Events:
v0.0.4:
  5c589f4f76-2zm8k: Running, ready since 2026-02-09 17:53:37
v0.0.2:
  6974755b98-hdt4d: Terminated

---

Note

Low Risk
Primarily changes CLI output formatting and switches jig status to use the typed SDK response; low blast radius but could affect scripts that depended on the previous default JSON output.

Overview
jig status now defaults to a human-readable, sectioned status display (app metadata, autoscaling, replica counts, configuration, volumes/env/secrets, and replica events) instead of always printing raw JSON.

Adds a --json flag to preserve the prior machine-readable output, and introduces beta/jig/_utils.py to centralize timestamp/image tag formatting and deployment status rendering.

^{Written by Cursor Bugbot for commit 43a3b05. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Missing f-string prefix on tip string literals

Medium Severity

The tip assignments in the non-pyproject else branch are plain strings, not f-strings. "update \name` in {path}"and"rename your folder or add `name` to {path}"will include the literal text{path}instead of the actual file path. Compare with the pyproject branch which correctly hardcodes the path. This surfaces in the user-facing error message"Deployment name must be unique. Tip: ..."`.