Add a bounded local JSON artifact viewer#255
Merged
Merged
Conversation
abrichr
marked this pull request as ready for review
July 26, 2026 10:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a reusable local-only JSON/JSONL artifact viewer to the protected operator console. The API admits only explicit workflow/run artifact families through opaque IDs, preserves existing loopback bearer auth, refuses traversal/symlinks and bounded-parser violations, and performs no Cloud/network transport. The UI adds search, collapse/expand, syntax highlighting, RFC 6901 JSON Pointer deep links, exact copy/raw/download, and responsive rendering.
Verification: tests/test_console.py: 71 passed, 1 warning; focused viewer contract: 2 passed, 69 deselected; Ruff, mypy, node --check, git diff --check, wheel build, archive inspection, and headless Chromium smoke at 390x844 passed.
Audit: the existing console had no raw JSON/JSONL artifact links; only report-referenced PNG. Viewer entry points are limited to admitted local workflow/run artifact families and do not turn unrelated prose paths, CLI output, arbitrary files, or the skill library into links.