fix: explain pause-point truncation flags filtered by captured-variable names

[hatayama]

Summary

• Pause-point hit responses now explain when CapturedVariablesTruncated stays true after --captured-variable-names drops every clipped variable.
• Listed captured values in that case are complete; the truncation flag is left unchanged so the clip is not hidden.

User Impact

• Before: --captured-variable-names could return CapturedVariablesTruncated: true with TruncatedVariableCount: 0 and TruncatedVariableNames: [] even though every remaining variable was complete, so agents could not tell whether the values they asked for were clipped.
• After: the CLI adds CapturedVariablesTruncatedNote in that case: the truncation flag refers to a variable excluded by the name filter, and every listed variable is complete.

Changes

• After the captured-variable name filter, detect CapturedVariablesTruncated == true, TruncatedVariableCount == 0, and no remaining truncated variables, then set CapturedVariablesTruncatedNote (omitempty).
• Do not rewrite CapturedVariablesTruncated.
• Document that Unity-side truncation also covers preview element-count and depth caps, and that the name filter can leave the top-level flag pointing at an excluded variable.
• Shared pause_point_status_response_contract.json is unchanged (omitempty keeps the CLI-only note off Unity payloads).

Verification

• scripts/check-go-cli.sh passed (format, vet, lint, tests, rebuild), including:
  • TestFilterPausePointCapturedVariablesByNameSetsTruncatedNote (note set / omitted / no filter / count-cap)
  • TestUnityPausePointStatusContractTruncationInvariant
  • TestPausePointStatusResponseMatchesSharedContract
• git diff -- tests/contracts/pause_point_status_response_contract.json is empty

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 54e8580f-3ae4-46d0-9ca0-c6a8f5e3d240

📥 Commits

Reviewing files that changed from the base of the PR and between 61bfe96 and fa01b3d.

📒 Files selected for processing (1)

• cli/project-runner/internal/projectrunner/pause_point_captured_variable_names_filter_test.go

---

📝 Walkthrough

Walkthrough

The pause-point response now includes an optional CapturedVariablesTruncatedNote. Name filtering preserves capture-time truncation and adds the note when it excludes all truncated variables. Tests and skill documentation describe the updated semantics.

Changes

Pause-point capture truncation

Layer / File(s)	Summary
Truncation response contract cli/project-runner/internal/projectrunner/pause_point_types.go, cli/project-runner/internal/projectrunner/pause_point_status_response_contract_test.go	The response adds an optional CapturedVariablesTruncatedNote. Contract tests verify that Unity-originated truncation responses omit this CLI-only note.
Filtered truncation reporting and documentation cli/project-runner/internal/projectrunner/pause_point_captured_variable_names_filter.go, cli/project-runner/internal/projectrunner/pause_point_captured_variable_names_filter_test.go, .agents/skills/uloop-pause-point/*, .claude/skills/uloop-pause-point/*, Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/*	Name filtering checks current and historical variables, preserves CapturedVariablesTruncated, and adds a note when all truncated variables are excluded. Tests cover filtering, history variables, and JSON serialization. Documentation includes preview-depth clipping and the filtering note semantics.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

• hatayama/unity-cli-loop#2017: Modifies the same captured-variable name-filtering path and its tests.
• hatayama/unity-cli-loop#2052: Extends related captured-variable truncation and filtering behavior.
• hatayama/unity-cli-loop#1944: Covers related preview-cap truncation semantics.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change to pause-point truncation flags after captured-variable name filtering.
Description check	✅ Passed	The description accurately explains the new truncation note, preserved flag behavior, documentation updates, and verification results.
Docstring Coverage	✅ Passed	Docstring coverage is 84.62% which is sufficient. The required threshold is 80.00%.
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 fix/pause-point-truncated-flag-name-filter

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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