Report runtime isolation posture in gateway and CLI diagnostics #122

New issue

Closed

opened 2026-05-06 11:57:45 -07:00 by jwilger · 0 comments

jwilger commented

2026-05-06 11:57:45 -07:00

Owner

Follow-up implementation slice from #115.

Decision context

auto-review gateway should make runtime isolation posture visible. Default startup uses embedded OCI isolation; explicit bare mode is allowed but must warn. Operators should see the same posture in startup logs, /info, and CLI diagnostics.

Scope

Add runtime isolation posture classification.
Report OCI-default, OCI-active, OCI-failed, explicit-bare, container/image, and systemd/deployment hints where reliably detectable.
Add startup warnings for explicit bare-process mode.
Expose non-secret posture details in /info.
Surface posture in the grouped diagnostic command, e.g. auto-review ops doctor.
Ensure unsupported-platform behavior is explicit.

Acceptance criteria

Startup logs state the effective isolation posture.
/info reports posture without leaking paths/secrets that should stay private.
The doctor/status command reports posture and warns about explicit bare mode.
Posture text does not imply bare mode is container-equivalent.

Required tests

Unit tests for posture classification.
API contract tests for /info posture fields.
CLI output tests for diagnostic warnings.
Secret-redaction regression tests for posture reporting.

Follow-up implementation slice from #115. ## Decision context `auto-review gateway` should make runtime isolation posture visible. Default startup uses embedded OCI isolation; explicit bare mode is allowed but must warn. Operators should see the same posture in startup logs, `/info`, and CLI diagnostics. ## Scope - Add runtime isolation posture classification. - Report OCI-default, OCI-active, OCI-failed, explicit-bare, container/image, and systemd/deployment hints where reliably detectable. - Add startup warnings for explicit bare-process mode. - Expose non-secret posture details in `/info`. - Surface posture in the grouped diagnostic command, e.g. `auto-review ops doctor`. - Ensure unsupported-platform behavior is explicit. ## Acceptance criteria - Startup logs state the effective isolation posture. - `/info` reports posture without leaking paths/secrets that should stay private. - The doctor/status command reports posture and warns about explicit bare mode. - Posture text does not imply bare mode is container-equivalent. ## Required tests - Unit tests for posture classification. - API contract tests for `/info` posture fields. - CLI output tests for diagnostic warnings. - Secret-redaction regression tests for posture reporting.

jwilger added a new dependency

2026-05-06 12:14:06 -07:00

#117 Implement embedded youki OCI gateway launcher

jwilger added a new dependency

2026-05-06 12:14:07 -07:00

#119 Run the Docker image through the unified auto-review binary

jwilger added this to the 1.0 milestone

2026-05-06 12:17:51 -07:00

jwilger referenced this issue from a pull request that will close it,

2026-05-07 07:18:10 -07:00

feat(ops): report runtime isolation posture #132

jwilger closed this issue