Repository navigation
feat(trust): compact workspace status output - #2626
Open
codeforester wants to merge 1 commit into
Open
codeforester wants to merge 1 commit into
codeforester wants to merge 1 commit into
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.
Summary
Project-less terminal
basectl trust statusnow renders a compact workspace report: a root and project count, blocked-first rows with short reasons, aggregate counts, one concise trust-scope note, and a pointer to detailed per-project guidance. Explicit single-project output, trust decisions, exit behavior, and JSON/YAML/CSV/TSV contracts remain unchanged.Issue
Fixes #2625
Validation
python -m tests.stability_compatibility --check --runtimepassed.git diff --checkpassed.Demo Impact
None.
Docs Impact
Updated
docs/manifest-command-trust.md, the CLI README, and the command reference. Structured-output docs and schemas have no impact because their contracts are unchanged.AI Context Impact
Not applicable: this is a presentation-only change with no change to trust semantics, command ownership, workflows, or product boundaries.
Notes
Blocked-first ordering applies only to the workspace terminal table. Machine-readable workspace output retains its existing ordering and fields.
Checklist
Fixes #2625.None.