fix(agent): honor global JSON output format - #954
Conversation
|
CI triage note: The PR-specific focused verification passed locally:
Current failing GitHub checks appear unrelated to this PR's touched files:
Base branch |
- apply global --format json/json-compact to guard/validate/suggest - preserve legacy subcommand --json compact one-line output - cover offline and server-mode fallback format contracts
db13a9b to
2db074c
Compare
|
Option A follow-up pushed in Added:
Verification after the follow-up:
Independent review |
Fix the local base-branch CI blockers shared by PR #953/#954: - apply rustfmt to pre-existing terraphim_rlm formatting drift - replace Rust 1.91-only str::floor_char_boundary with MSRV-safe UTF-8 boundary logic for Rust 1.80 - harden Firecracker VM create diagnostics and error handling - install cargo-nextest via the existing upstream installer pattern - run cargo nextest directly so filter expression quoting survives rch Verification: - cargo fmt -- --check - cargo test -p terraphim_rlm query_loop::tests::test_truncate -- --nocapture - cargo clippy -p terraphim_rlm -- -D warnings - Firecracker workflow YAML parsed and shell path simulated - independent reviews passed
Fix the local base-branch CI blockers shared by PR #953/#954: - apply rustfmt to terraphim_rlm files that failed cargo fmt --check - replace str::floor_char_boundary with MSRV-safe char-boundary logic - harden Firecracker VM creation diagnostics with HTTP status/body logging - keep cargo nextest filter expressions out of rch shell reconstruction - install cargo-nextest with the upstream tarball installer on Firecracker runners - isolate nextest failures with ephemeral server test ports and isolated direct-dispatch test state Leaves the Firecracker VM lifecycle 401/capacity issue tracked separately in Gitea #3173.
Fix the local base-branch CI blockers shared by PR #953/#954: - apply rustfmt to terraphim_rlm files that failed cargo fmt --check - replace str::floor_char_boundary with MSRV-safe char-boundary logic - harden Firecracker VM creation diagnostics with HTTP status/body logging - keep cargo nextest filter expressions out of rch shell reconstruction - install cargo-nextest with the upstream tarball installer on Firecracker runners - isolate nextest failures with ephemeral server test ports and isolated direct-dispatch test state - run cargo-spawning MCP autocomplete E2E tests in a dedicated serial nextest step Leaves the Firecracker VM lifecycle 401/capacity issue tracked separately in Gitea #3173.
Fix the local base-branch CI blockers shared by PR #953/#954: - apply rustfmt to terraphim_rlm files that failed cargo fmt --check - replace str::floor_char_boundary with MSRV-safe char-boundary logic - harden Firecracker VM creation diagnostics with HTTP status/body logging - keep cargo nextest filter expressions out of rch shell reconstruction - install cargo-nextest with the upstream tarball installer on Firecracker runners - isolate nextest failures with ephemeral server test ports and isolated direct-dispatch test state - run cargo-spawning MCP autocomplete E2E tests in a dedicated serial nextest step - give performance benchmarks enough time to finish Criterion after service benchmarks Leaves the Firecracker VM lifecycle 401/capacity issue tracked separately in Gitea #3173.
|
Base CI unblocker update: PR #955 now has the ownable/code gates green on head
Only remaining red check on #955 is Recommendation: merge/rebase the base CI unblocker (#955) before judging this PR's checks; this PR's older CI runs include stale base failures that #955 fixes. |
Summary
--format json/--format json-compactforterraphim-agent guard,validate, andsuggest.--jsoncompact one-line JSON output.effective_json_output_mode(...).Test Plan
cargo test -p terraphim_agent --test agent_format_contract_tests -- --nocapture— 10 passedcargo test -p terraphim_agent --test robot_search_output_regression_tests -- --nocapture— 5 passedcargo test -p terraphim_agent --test offline_mode_tests -- --nocapture— 24 passedcargo clippy -p terraphim_agent -- -D warnings— passedgit diff --cached --check— clean before amendReview
deleg_5c4d6898passed: no security concerns, no logic errors, no suggestions.CI note
GitHub CI failures on this base are unrelated to the touched
crates/terraphim_agent/*files: Firecracker VM creation fails, and workspace formatting failures are in pre-existingcrates/terraphim_rlm/*files.Refs terraphim/terraphim-ai#3172