Repository navigation
feat(wikibrowser): show workflow titles and fold management metadata - #152
Merged
Merged
Conversation
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.
Changes
Kinic Superpowers workflows previously exposed UUID folder names and raw management JSON in the Web Wiki. Folders containing only a manifest provided no convenient route to their documents.
For workflows with validated project registration and v1/v2 manifests, the tree and breadcrumbs now display workflow titles. Workflow folders show their current state and links to canonical documents. Management JSON is collapsed in directory listings and search results, and formatted when opened directly. Users can switch to actual filenames or refresh the display. Document reference links do not expose move or delete actions.
Storage paths, UUIDs, manifests, the CLI, and canister APIs remain unchanged. Additional reads fetch management metadata only, with at most four concurrent requests per reader. Caches are isolated by canister, database, and principal. Saving management metadata invalidates only the affected path, while explicit refreshes retain the same request queue. Invalid metadata or failed reads fall back to the ordinary file view.
Validation
Limitations
Browser validation used a local fixture populated with real data. Authenticated browsing in the production Web UI and deployment were not performed. iOS presentation is outside this change. Existing storage layouts are preserved.
Follow-up review fixes
Fixed an issue where navigation recreated the reader, allowing old and new requests to exceed the four-request limit in aggregate. The reader and request queue now persist within the connection/principal scope, and saves invalidate only the affected metadata. Responses from before invalidation cannot update the display, and invalidated requests that have not started are skipped. Regression tests cover repeated navigation and refreshes, targeted refetching, and delayed stale responses.
Display language
All added UI labels are English, including Workflows, Design, Plan, Progress, Review, Results, Management metadata, and the display controls. User-authored workflow titles and state text remain unchanged. After this copy update, 26 focused tests, type checking, and lint passed.