Operator surface

jackin❯ join & Debug Export

Status: Open

Current state: local telemetry artifacts and their reveal/open surfaces have been removed; project join and a non-telemetry redacted debug bundle remain unimplemented

Shipped facts

jackin exports production telemetry directly over OTLP and keeps only bounded current-invocation state in memory for operator UI. The configured backend owns history; Debug info uses cli.invocation.id as the correlation handle and exposes no local telemetry artifact or reveal/open action. A future shareable debug bundle therefore covers redacted product/configuration state while telemetry retention and queries remain the operator's backend responsibility.

Remaining work

1. Redacted debug bundle

Add a diagnostic export command, name still open (jackin debug export or similar), that packages a local .tar.zst bundle containing redacted workspace config, redacted role manifest, redacted env/auth summary, jackin and Capsule versions, OS info, container/runtime state, and sanitized static exporter configuration. Live exporter health is not persisted. An optional cli.invocation.id may be recorded as a backend correlation reference, but the bundle never queries the backend or contains logs, traces, metrics, OTLP payloads, or another telemetry serialization.

Redaction must hide token/API-key values and 1Password vault/item/field specifics while preserving enough structure to debug resolution failures. Bundles stay local; no upload service and no import/replay command in this item.

2. Project onboarding

Implement project-level onboarding separately from debug export. jackin join <org>/<project> should let a repository publish jackin workspace setup information, then guide a new contributor through trust, workspace choice, credentials, clone/setup, and first launch. Before implementation, decide the config shape, private-repository auth, trust model, multi-workspace monorepo behavior, and whether prerequisites are installed or only diagnosed.

Non-goals

  • Do not implement jackin join before the project-config trust model is designed.
  • Do not reintroduce diagnostics JSONL, create an OTLP file export, or query a configured backend as part of the bundle.
  • Do not store bundles remotely.

Cross-references

On this page