[G14] Implement status, logs and sanitized diagnostics

[jjangg96]

Goal

Give operators one accurate view of organizations, pools, capacity, jobs and failures with bounded redacted local logs and machine-readable output.

Create one active Codex goal from the statement above when this issue is dispatched. The Project Goal field is a work specification; it does not start an agent. Do not invent a token budget.

Execution contract

Field	Value
Goal key	G14
Stage	M3 - Reliability qualification
Initial status	Backlog
Primary agent	gpt-5.6-luna / max
Priority / risk	P1 / Medium
Test profiles	offline, trusted-runtime

Use one issue branch/worktree and one focused PR. Independent Luna max review is required for authentication, protocol, concurrency, resource ownership, cleanup or service identity boundaries; other changes need independent contract review. Model fields are routing instructions, not GitHub user assignments.

Dependencies

• G06 #6
• G13 #13

Dependencies must be Done before implementation begins. A new issue is not blocked simply because its future evidence has not been collected.

Scope

status/list/describe/logs/doctor/export and telemetry adapters; no new auth scopes unless justified by an approved feature.

TDD and failure evidence

1. Red: desired/reserved/creating/busy/draining/unknown counts reflect durable and stale observations separately.
2. Test concurrent tail/rotation, slow clients, missing provider and bounded diagnostic export.
3. Secret canaries in SDK errors, config and job data never appear in CLI/JSON/logs/metrics.

Capture a meaningful failing case before the implementation, then green evidence and relevant refactor checks. Tooling/prose-only work uses appropriate negative checks without artificial application tests. Live/runtime profiles require reviewed commits, a dedicated trusted test environment and explicit authorization for the concrete experiment. Public PR CI uses hosted environments without credentials. Planned or skipped tests never count as passed.

Acceptance criteria

• Logs survive worker cleanup with retention/disk limits.
• Metrics distinguish manager overhead, engine limits and job costs.
• Stale/offline state is visible rather than falsely healthy.
• Exit codes/JSON version and cancellation behavior are documented.
• Record exact validation commands, actual results, skipped/live-test gaps and applicable rollback notes in the PR.
• Independent review is resolved and the focused PR is merged under the repository execution policy.
• Update issue/Project accurately; mark the active goal complete only after all required evidence and work are complete.

Safety invariants

Preserve existing manual runners; no global Docker prune/context switching, broad process kill, implicit App enrollment, busy-job cancellation during ordinary scale-down or transparent workflow replay. Use only verifiably owned resources. Keep management credentials and raw secret-bearing SDK errors out of worker environments, logs, fixtures and commits; per-worker JIT transport follows G01. Native pools remain trusted-only.

Design references

• Architecture and gates
• Language decision
• Security design
• TDD strategy
• Goal/model execution policy
• Ordered backlog