feat(settings): add read-only Registry tab - #304
Merged
Conversation
Adds a Registry tab to Settings showing the persisted job registry (registry.json) in a read-only viewer, so the on-disk state can be inspected without leaving the app. Backed by a new read-only GET /api/registry endpoint. Closes #303
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
1 participant
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.
Summary
registry.json) in a read-only, monospace viewer with a Refresh button — no need to leave the app or dig through the filesystem to check what's actually persisted on disk.GET /api/registryendpoint returns the raw registry file content.jobs_dir / "registry.json"path construction into aregistry_path()helper inapp/core/registry.py, reused bypersist(),restore(), and the new endpoint.Closes #303
Test plan
ruff check/ruff format --checkcleanpytest tests/test_registry_persistence.pypasses (7/7) — confirms theregistry_path()refactor didn't change persist/restore behaviorGET /api/registryreturns valid JSON from a running server