feat: render RunContract status through existing supervisor surfaces

[devkade]

Status

Output-contract implementation issue. Start after #98-#100 define the generic RunContract view, criteria, and advisory hints.

Summary

Render compact RunContract status through existing Kapi supervisor surfaces so humans and Hermes/Ragna can inspect generic run evidence, completion, and quality hints without changing workflow ownership or making coding workflows mandatory.

Context

Kapi already exposes supervisor surfaces through CLI commands such as status, report, probe, events, and doctor. RunContract rendering should extend those surfaces additively after the generic core shapes exist.

Problem

Without rendering, RunContract remains an internal projection and supervisors still need to inspect raw workflow state, artifacts, and evidence manually. But adding output too early or too broadly can break JSON/text consumers and clutter human reports.

Scope

• Add a compact RunContract section to selected existing JSON/text supervisor surfaces.
• Prefer additive JSON fields; do not remove or rename existing output fields.
• Keep text output concise and useful for non-coding runs.
• Preserve existing mode-specific reports and quality-probe output.

Compatibility constraints

• JSON output must be additive and backward-compatible.
• Human-readable text output should remain compact; avoid dumping full contracts or long evidence lists by default.
• Existing snapshots/tests should change only where the new additive surface intentionally appears.
• Read-only supervisor commands must remain read-only.

Non-goals

• No separate GitHub issue/PR command surface.
• No Discord lane rendering.
• No dev merge, PR approval, or tracker reconciliation automation.
• No replacement of existing mode-specific reports wholesale.

Acceptance criteria

• Supervisor-readable JSON includes RunContract status when available.
• Human-readable output includes concise evidence/completion/quality hints without overwhelming status/report output.
• Existing status/report/probe behavior remains backward-compatible except for intentional additive fields/sections.
• Output wording remains generic and useful for non-coding runs.
• Tests/snapshots cover the additive output contract.

Verification

• Run targeted CLI/report/status tests.
• Manually inspect one sample JSON output and one text output.
• Confirm changed snapshots/fixtures contain only intentional additive RunContract output.

References

• Depends on: docs: define RunContract harness core-adapter boundary #97, feat: add generic RunContract projection without workflow-specific assumptions #98, feat: model EvidenceExpectation and CompletionCriteria for RunContract #99, feat: add soft quality scoring hints for RunContract status #100
• Follow-up: feat: map RunContract status into Hermes/Ragna GitHub workflow adapters #102
• Existing source anchors: src/cli/kapi-cli.ts, src/presentation/command-formatters.ts, test/status-command.test.ts, test/worker-output-format.test.ts, test/quality-report-format.test.ts