Repository navigation
fix(tui): classify Native outcomes from presentation metadata - #340
Merged
Merged
Conversation
This was referenced Oct 20, 2026
# Conflicts: # docs/CHANGELOG.md
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.
Closes #339
What was wrong
The TUI activity observer only understood JSON text envelopes, but Native file tools and Native
ops_resultintentionally render compact model-facing prose. The sidebar counted returns while leaving successful reads, previews, refusals and operation errors business-unconfirmed. The optional real-host fixture also needed the explicit user-message source required by DSH 0.2.1.The change
output.presentationMeta/ committedmeta.opsOutcomepath. Model text and tool input/output schemas are unchanged.Validation
The complete gate uses the host's real Landlock backend (bwrap probe deliberately unavailable on PATH) because main's unrelated private-
/tmpreference-cache defect is fixed independently in #338. No unconfined substitute or permission relaxation is used. The targeted real-host Native suites also pass with the machine's ordinary bwrap-enabled PATH.PR-triggered CI: https://github.com/T-Auto/dsh-ops/actions/runs/39477813622 —
pull_request, aggregateCI required: SUCCESS (Windows x64, Linux x64, macOS arm64 and required supporting jobs passed). The first macOS job was abandoned before allocation (runner_id: 0, no steps). A targeted rerun of only that unexecuted job and its dependent aggregate succeeded on attempt 2; no failed code-test assertion was retried.Environment
Arch Linux x64; Node 24.21.0; Rust 1.97.1; dsh-TUI 0.16.1; base main
a9ff940. Local source checkout with rebuilt native worker.Combined local validation
The submitted heads of #338, #340, #341, #342, #343, #344 and #345 were applied together in an isolated local verification worktree, including their combined changelog entries. With ordinary PATH selecting real bwrap 0.13.0 and real dsh-TUI 0.16.1 host/worker/renderer suites enabled,
node scripts/verify-gate.mjs --skip-installpassed all 11 release-gate steps: 129 suites passed, 0 skipped; 46 Rust unit tests passed; manifest 73/59. This Linux combined-tree evidence is separate from each PR's own cross-platform CI; no upstream merge or host installation was performed.