fix(e2e): preserve Deep Agents TUI outcome by cv · Pull Request #5912 · NVIDIA/NemoClaw

cv · 2026-06-27T22:07:43Z

Summary

Preserves the real exit status from the Deep Agents Code Expect harness and emits a bounded, secret-screened sanitized capture excerpt when the harness fails. This removes a shell declaration-order bug that made timeout and EOF outcomes appear successful, while keeping the strict prompt and exit assertions intact.

Changes

Declare the Expect status variable before invoking the harness so local cannot reset $?.
Print the last 20,000 bytes of the sanitized capture after failures only when no secret-shaped value remains.
Add behavioral and image-contract coverage for nonzero Expect outcomes and safe diagnostics.

Type of Change

Code change (feature, bug fix, or refactor)
Code change with doc updates
Doc only (prose changes, no code sample modifications)
Doc only (includes code sample changes)

Quality Gates

Tests added or updated for changed behavior
Existing tests cover changed behavior — justification:
Tests not applicable — justification:
Docs updated for user-facing behavior changes
Docs not applicable — justification: release-gate harness diagnostics only; no user-facing behavior changed.
Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: self-review confirms diagnostic output is read only from the already-sanitized artifact, is suppressed if secret-shaped data remains, and raw/combined captures are still deleted.
Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Verification

PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
Targeted tests pass for changed behavior
Full npm test passes (broad runtime changes only)
Quality Gates section completed with required justifications or waivers
No secrets, API keys, or credentials committed
npm run docs builds without warnings (doc changes only)
Doc pages follow the style guide (doc changes only)
New doc pages include SPDX header and frontmatter (new pages only)

Targeted verification:

bash -n test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh
npm test -- --run test/deepagents-code-tui-startup-check.test.ts test/langchain-deepagents-code-image.test.ts
npm run typecheck:cli

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

Tests
- Expanded TUI startup-check coverage to explicitly preserve lifecycle markers and ensure the embedded harness exits cleanly after marker writes.
- Added a new failure-case test that verifies the helper returns the correct non-zero status and emits only the sanitized capture excerpt (including the EOF marker) for diagnostics.
- Updated end-to-end checks to confirm the generated startup-check script includes and positions expect_rc correctly and prints the sanitized capture excerpt on non-zero runs.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

coderabbitai · 2026-06-27T22:07:57Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9c122f46-c332-4427-8671-1b7d3f4914ef

📥 Commits

Reviewing files that changed from the base of the PR and between db9af54 and 7f9efbf.

📒 Files selected for processing (1)

test/deepagents-code-tui-startup-check.test.ts

📝 Walkthrough

Walkthrough

Adds a print_sanitized_capture_excerpt function to the TUI startup check shell script that prints the last bytes of the sanitized capture file to stderr on expect harness failure. The expect_rc variable declaration is moved before run_tui_expect. New and updated tests cover both the success path and a simulated exit-code-21 failure path.

Changes

TUI Startup Check: Sanitized Capture Excerpt on Failure

Layer / File(s)	Summary
Shell: `print_sanitized_capture_excerpt` function and call site `test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh`	Adds `print_sanitized_capture_excerpt` that prints the tail of the sanitized capture to stderr (skipped if file is missing or contains secret-shaped data), moves `local expect_rc` before `run_tui_expect`, and calls the new function when `expect` exits non-zero.
Unit tests for success and failure paths `test/deepagents-code-tui-startup-check.test.ts`	Adds `return 0` to the success-path embedded snippet and adds a new test asserting the failure path exits `1`, emits the expect harness exit code `21` on stderr, and includes the sanitized capture excerpt with the EOF marker.
Image test assertions for new script shape `test/langchain-deepagents-code-image.test.ts`	Adds assertions that `local expect_rc` precedes `run_tui_expect "$raw_capture_file"` and that `print_sanitized_capture_excerpt "$plain_capture_file"` is present in the generated script content.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

NVIDIA/NemoClaw#5839: Touches the same TUI startup check script and validation flow in the cloud experimental checks.
NVIDIA/NemoClaw#5887: Extends the same test/deepagents-code-tui-startup-check.test.ts area with additional boundary coverage.
NVIDIA/NemoClaw#5911: Modifies the same TUI startup check lifecycle-marker handling and capture preservation flow.

Suggested labels

area: e2e, integration: dcode, v0.0.69

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately reflects the main change: preserving Deep Agents TUI outcomes in E2E behavior.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch codex/fix-deepagents-tui-outcome

_{Comment @coderabbitai help to get the list of available commands.}

github-code-quality · 2026-06-27T22:08:24Z

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in the codex/fix-deepagents... branch is 96%. Coverage data for the main branch is not yet available.

Show a code coverage summary of the most covered files.

File	`main`	`codex/fix-deepagents...` 7f9efbf	+/-
`nemoclaw/src/se...cret-scanner.ts`	—	100%	—
`nemoclaw/src/commands/slash.ts`	—	100%	—
`nemoclaw/src/li...bprocess-env.ts`	—	100%	—
`nemoclaw/src/bl...eprint/state.ts`	—	98%	—
`nemoclaw/src/onboard/config.ts`	—	98%	—
`nemoclaw/src/bl...int/snapshot.ts`	—	97%	—
`nemoclaw/src/bl...print/runner.ts`	—	95%	—
`nemoclaw/src/co...ration-state.ts`	—	94%	—
`nemoclaw/src/bl...ate-networks.ts`	—	94%	—
`nemoclaw/src/index.ts`	—	94%	—

TypeScript / code-coverage/cli

The overall coverage in the codex/fix-deepagents... branch is 67%. Coverage data for the main branch is not yet available.

Show a code coverage summary of the most covered files.

File	`main`	`codex/fix-deepagents...` 7f9efbf	+/-
`src/lib/actions...all/run-plan.ts`	—	80%	—
`src/lib/state/o...oard-session.ts`	—	79%	—
`src/lib/actions...dbox/rebuild.ts`	—	74%	—
`src/lib/state/sandbox.ts`	—	72%	—
`src/lib/shields/index.ts`	—	70%	—
`src/lib/onboard/preflight.ts`	—	69%	—
`src/lib/actions...licy-channel.ts`	—	59%	—
`src/lib/onboard...er-gpu-patch.ts`	—	59%	—
`src/lib/policy/index.ts`	—	52%	—
`src/lib/onboard.ts`	—	20%	—

_{Updated June 27, 2026 22:21 UTC
Code Coverage is in Public Preview. Learn more and provide us with your feedback.}

github-actions · 2026-06-27T22:09:06Z

PR Review Advisor (Nemotron Ultra) — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: Consider PRA-1: Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?.
Open items: 0 required · 0 warnings · 2 suggestions · 0 test follow-ups
Since last review: 0 prior items resolved · 0 still apply · 0 new items found

Action checklist

PRA-1 In-scope improvement: Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $? in test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:175
PRA-2 In-scope improvement: Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs in test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:139

Findings index

ID	Severity	Category	Location	Required action
`PRA-1`	Improvement	correctness	`test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:175`	No action needed; fix is correct and covered by new unit test 'preserves a failed expect status and emits only the sanitized capture excerpt'.
`PRA-2`	Improvement	security	`test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:139`	No action needed; secret gating is correct and tested.

Review findings by urgency: 0 required fixes, 0 items to resolve/justify, 2 in-scope improvements

⚠️ Resolve or justify before merge

Investigate these in the current review; either fix them, explain why they are not applicable, or document the accepted risk.

None.

💡 In-scope improvements

These are lower-risk, not throwaway. Prefer fixing them in this PR when they are local to changed code; defer only with rationale or a linked follow-up.

`PRA-1` Improvement — Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?

Location: test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:175
Category: correctness
Problem: The PR moves `local expect_rc` before the `run_tui_expect` invocation. Previously, `local expect_rc` was declared after the call, which reset `$?` to 0 (the exit status of `local` itself), causing timeout (exit 20), EOF before ready (exit 21), exit timeout (exit 22), and EOF before exit (exit 23) to be misreported as success.
Impact: Release-gate harness would incorrectly pass when the Expect harness failed due to timeout or EOF, masking real TUI startup failures in CI.
Suggested action: No action needed; fix is correct and covered by new unit test 'preserves a failed expect status and emits only the sanitized capture excerpt'.
Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
Verification: Read test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh lines 173-178: verify `local expect_rc` precedes `run_tui_expect` call and `expect_rc=$?` captures the result.
Missing regression test: Already covered: test/deepagents-code-tui-startup-check.test.ts 'preserves a failed expect status and emits only the sanitized capture excerpt' asserts result.status === 1 and stderr contains 'finite expect harness exited 21'.
Done when: The local improvement is applied, or the PR notes why it should be deferred.
Evidence: Diff shows `local expect_rc` moved from after to before `run_tui_expect`; new test exercises exit code 21 path.

`PRA-2` Improvement — Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs

Location: test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:139
Category: security
Problem: New `print_sanitized_capture_excerpt` function prints the last 20KB of the sanitized capture on Expect failure, but only after confirming `contains_secret` returns false on the plain capture. If secrets remain, it emits only 'sanitized TUI capture omitted because secret-shaped data remains' and suppresses the excerpt entirely.
Impact: Prevents accidental credential exposure in CI logs when TUI startup fails, while still providing actionable diagnostics for non-secret failures.
Suggested action: No action needed; secret gating is correct and tested.
Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
Verification: Read test/deepagents-code-tui-startup-check.test.ts 'suppresses the capture excerpt when secret-shaped data remains' — it writes a secret to the capture file, calls the helper, and asserts stdout contains the omission message and neither stdout nor stderr contains the secret or 'sanitized capture excerpt'.
Missing regression test: Already covered: the same test verifies secret suppression behavior end-to-end.
Done when: The local improvement is applied, or the PR notes why it should be deferred.
Evidence: print_sanitized_capture_excerpt function at lines 139-156; test at deepagents-code-tui-startup-check.test.ts lines 139-170.

Since last review details

Current findings, using the urgency labels above:

`PRA-1` Improvement — Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?

Location: test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:175
Category: correctness
Problem: The PR moves `local expect_rc` before the `run_tui_expect` invocation. Previously, `local expect_rc` was declared after the call, which reset `$?` to 0 (the exit status of `local` itself), causing timeout (exit 20), EOF before ready (exit 21), exit timeout (exit 22), and EOF before exit (exit 23) to be misreported as success.
Impact: Release-gate harness would incorrectly pass when the Expect harness failed due to timeout or EOF, masking real TUI startup failures in CI.
Suggested action: No action needed; fix is correct and covered by new unit test 'preserves a failed expect status and emits only the sanitized capture excerpt'.
Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
Verification: Read test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh lines 173-178: verify `local expect_rc` precedes `run_tui_expect` call and `expect_rc=$?` captures the result.
Missing regression test: Already covered: test/deepagents-code-tui-startup-check.test.ts 'preserves a failed expect status and emits only the sanitized capture excerpt' asserts result.status === 1 and stderr contains 'finite expect harness exited 21'.
Done when: The local improvement is applied, or the PR notes why it should be deferred.
Evidence: Diff shows `local expect_rc` moved from after to before `run_tui_expect`; new test exercises exit code 21 path.

`PRA-2` Improvement — Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs

Location: test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh:139
Category: security
Problem: New `print_sanitized_capture_excerpt` function prints the last 20KB of the sanitized capture on Expect failure, but only after confirming `contains_secret` returns false on the plain capture. If secrets remain, it emits only 'sanitized TUI capture omitted because secret-shaped data remains' and suppresses the excerpt entirely.
Impact: Prevents accidental credential exposure in CI logs when TUI startup fails, while still providing actionable diagnostics for non-secret failures.
Suggested action: No action needed; secret gating is correct and tested.
Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
Verification: Read test/deepagents-code-tui-startup-check.test.ts 'suppresses the capture excerpt when secret-shaped data remains' — it writes a secret to the capture file, calls the helper, and asserts stdout contains the omission message and neither stdout nor stderr contains the secret or 'sanitized capture excerpt'.
Missing regression test: Already covered: the same test verifies secret suppression behavior end-to-end.
Done when: The local improvement is applied, or the PR notes why it should be deferred.
Evidence: print_sanitized_capture_excerpt function at lines 139-156; test at deepagents-code-tui-startup-check.test.ts lines 139-170.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

github-actions · 2026-06-27T22:09:08Z

E2E Advisor Recommendation

Required E2E: None
Optional E2E: ubuntu-repo-cloud-langchain-deepagents-code

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

None. No merge-blocking E2E is required because this PR is tests-only and changes E2E harness diagnostics/assertions, not runtime code or user-facing installer, onboarding, sandbox, credential, network-policy, inference, deployment, or assistant-flow behavior.

Optional E2E

ubuntu-repo-cloud-langchain-deepagents-code (high): Optional confidence only: this live Vitest scenario onboards the LangChain Deep Agents Code sandbox and runs the e2e-cloud-experimental Deep Agents checks, including the modified 10-deepagents-code-tui-startup.sh script.

New E2E recommendations

None.

github-actions · 2026-06-27T22:09:09Z

Vitest E2E Scenario Recommendation

Required Vitest E2E scenarios: ubuntu-repo-cloud-langchain-deepagents-code
Optional Vitest E2E scenarios: None

Dispatch required Vitest E2E scenarios:

gh workflow run e2e-vitest-scenarios.yaml --ref <pr-head-ref> --field scenarios=ubuntu-repo-cloud-langchain-deepagents-code

Workflow run

Full Vitest E2E advisor summary

Vitest E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required Vitest E2E scenarios

ubuntu-repo-cloud-langchain-deepagents-code: The changed Deep Agents Code TUI startup cloud-experimental check is executed by the live Vitest registry scenario for cloud-langchain-deepagents-code onboarding, so the targeted Ubuntu repo Deep Agents Code scenario is the smallest live-supported dispatch that exercises it.
- Dispatch: gh workflow run e2e-vitest-scenarios.yaml --ref <pr-head-ref> --field scenarios=ubuntu-repo-cloud-langchain-deepagents-code

Optional Vitest E2E scenarios

None.

Relevant changed files

test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh

cv · 2026-06-27T22:11:48Z

CodeRabbit’s only pre-merge warning is the generic docstring-coverage heuristic. This PR adds a Bash E2E helper, where Python/TypeScript-style docstrings do not apply; its behavior and safety boundary are explicit in the function name, control flow, PR description, and behavioral tests. Treating this warning as non-blocking. CodeRabbit generated no actionable inline findings, and the PR Review Advisor reports 0 required items and 0 warnings.

github-actions · 2026-06-27T22:13:55Z

PR Review Advisor — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: No advisor follow-up required beyond maintainer review.
Open items: 0 required · 0 warnings · 0 suggestions · 0 test follow-ups
Since last review: 2 prior items resolved · 0 still apply · 0 new items found

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

cv · 2026-06-27T22:17:03Z

Addressed PRA-2, PRA-T1, and PRA-T2 in 7f9efbf9e: the helper test now writes a representative fake sk- token, calls the diagnostic function, and proves the omission message is emitted while the token, excerpt header, and body are absent from stderr.

PRA-1 source-of-truth review:

Invalid state: a nonzero Expect timeout/EOF result was reported as success because local expect_rc reset $? after run_tui_expect.
Source boundary: the shell call site immediately capturing run_tui_expect status.
Source fix constraint: declare the variable before the command and capture $? immediately; do not synthesize readiness or exit markers.
Regression tests: exit 21 is preserved through main, safe diagnostics are emitted, and secret-shaped residual data suppresses the excerpt.
Removal condition: the bounded diagnostic can be removed if the live workflow uploads the sanitized capture directly or upstream dcode exposes a stable machine-readable ready/exit protocol. It is observability for real failures, not a substitute for the strict prompt/exit assertions.

## Summary Preserves the real exit status from the Deep Agents Code Expect harness and emits a bounded, secret-screened sanitized capture excerpt when the harness fails. This removes a shell declaration-order bug that made timeout and EOF outcomes appear successful, while keeping the strict prompt and exit assertions intact. ## Changes - Declare the Expect status variable before invoking the harness so `local` cannot reset `$?`. - Print the last 20,000 bytes of the sanitized capture after failures only when no secret-shaped value remains. - Add behavioral and image-contract coverage for nonzero Expect outcomes and safe diagnostics. ## Type of Change - [x] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [x] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [ ] Tests not applicable — justification: - [ ] Docs updated for user-facing behavior changes - [x] Docs not applicable — justification: release-gate harness diagnostics only; no user-facing behavior changed. - [x] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [x] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: self-review confirms diagnostic output is read only from the already-sanitized artifact, is suppressed if secret-shaped data remains, and raw/combined captures are still deleted. - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Verification - [x] PR description includes the DCO sign-off declaration and every commit appears as `Verified` in GitHub - [x] Git hooks passed during commit and push, or `npx prek run --from-ref main --to-ref HEAD` passes - [x] Targeted tests pass for changed behavior - [ ] Full `npm test` passes (broad runtime changes only) - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) - [ ] Doc pages follow the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md) (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) Targeted verification: ```bash bash -n test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh npm test -- --run test/deepagents-code-tui-startup-check.test.ts test/langchain-deepagents-code-image.test.ts npm run typecheck:cli ``` --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit * **Tests** * Expanded TUI startup-check coverage to explicitly preserve lifecycle markers and ensure the embedded harness exits cleanly after marker writes. * Added a new failure-case test that verifies the helper returns the correct non-zero status and emits only the sanitized capture excerpt (including the EOF marker) for diagnostics. * Updated end-to-end checks to confirm the generated startup-check script includes and positions `expect_rc` correctly and prints the sanitized capture excerpt on non-zero runs.  --------- Signed-off-by: Carlos Villela <cvillela@nvidia.com>

fix(e2e): preserve Deep Agents TUI outcome

db9af54

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

cv self-assigned this Jun 27, 2026

test(e2e): cover TUI diagnostic suppression

7f9efbf

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

cv enabled auto-merge (squash) June 27, 2026 22:22

cv disabled auto-merge June 27, 2026 22:28

cv merged commit 5d95247 into main Jun 27, 2026
45 checks passed

cv deleted the codex/fix-deepagents-tui-outcome branch June 27, 2026 22:28

wscurran added area: ci CI workflows, checks, release automation, or GitHub Actions area: e2e End-to-end tests, nightly failures, or validation infrastructure bug-fix PR fixes a bug or regression integration: dcode LangChain Deep Code integration behavior labels Aug 1, 2026

Uh oh!

Conversation

cv commented Jun 27, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Type of Change

Quality Gates

Verification

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

❌ Failed checks (1 warning)

Uh oh!

github-code-quality Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Coverage Overview

TypeScript / code-coverage/plugin

TypeScript / code-coverage/cli

Uh oh!

github-actions Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Advisor (Nemotron Ultra) — No blocking findings

Action checklist

Findings index

⚠️ Resolve or justify before merge

💡 In-scope improvements

PRA-1 Improvement — Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?

PRA-2 Improvement — Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs

PRA-1 Improvement — Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?

PRA-2 Improvement — Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs

Uh oh!

github-actions Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

E2E Advisor Recommendation

E2E Recommendation Advisor

Required E2E

Optional E2E

New E2E recommendations

Uh oh!

github-actions Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Vitest E2E Scenario Recommendation

Vitest E2E Scenario Advisor

Required Vitest E2E scenarios

Optional Vitest E2E scenarios

Relevant changed files

Uh oh!

cv commented Jun 27, 2026

Uh oh!

github-actions Bot commented Jun 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Advisor — No blocking findings

Uh oh!

cv commented Jun 27, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

cv commented Jun 27, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jun 27, 2026 •

edited

Loading

github-code-quality Bot commented Jun 27, 2026 •

edited

Loading

github-actions Bot commented Jun 27, 2026 •

edited

Loading

`PRA-1` Improvement — Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?

`PRA-2` Improvement — Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs

`PRA-1` Improvement — Shell declaration-order bug fixed: expect_rc now captured before local declaration resets $?

`PRA-2` Improvement — Diagnostic excerpt gated by secret scan prevents credential leakage in failure logs

github-actions Bot commented Jun 27, 2026 •

edited

Loading

github-actions Bot commented Jun 27, 2026 •

edited

Loading

github-actions Bot commented Jun 27, 2026 •

edited

Loading