fix(review): avoid post-harness action claims

[khaliqgant]

Summary

• Tighten the pr-reviewer prompt so harness output does not claim fixes were pushed, a GitHub review was submitted, or CI was verified.
• Leaves those post-harness actions for cloud to report after they actually happen.

Verification

• npm run typecheck

Notes

• This pairs with the cloud checkout/push fix so the PR comment no longer over-claims actions that happen after harness stdout is generated.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fda1405c-180e-4c99-8f47-a97c1bf7b1c8

📥 Commits

Reviewing files that changed from the base of the PR and between 4e55c27 and bd258f2.

📒 Files selected for processing (1)

• review/agent.ts

---

📝 Walkthrough

Walkthrough

The agent's review harness prompt is clarified to prevent the agent from claiming external actions (pushing fixes, submitting GitHub reviews, verifying CI) that are performed outside the harness, while preserving the READY sentinel requirement.

Changes

Agent Review Harness Prompt Update

Layer / File(s)	Summary
Harness prompt constraints review/agent.ts	The agent prompt instructions are expanded to explicitly prohibit claims about pushing fixes, posting GitHub reviews, or verifying CI status. The READY sentinel requirement is retained for readiness signaling.

🎯 1 (Trivial) | ⏱️ ~5 minutes

🐰 A whisker-twitching prompt we adjust,
No false claims the agent must thrust!
READY stands tall, a beacon so bright,
While fixes and reviews stay out of sight. 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: tightening the pr-reviewer prompt to prevent claiming post-harness actions, which directly aligns with the changeset.
Description check	✅ Passed	The description is directly related to the changeset, providing clear context about why the prompt was tightened and how it coordinates with cloud-side changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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/pr-reviewer-avoid-action-claims

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

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 and usage tips.}

[agent-relay-code]

Blocked: every shell command fails before execution with:

bwrap: setting up uid map: Permission denied

This happens even for pwd and ls in /tmp, so I can’t read .workforce/pr.diff, inspect changed files, run tests, or edit safely. MCP resources are also empty, and approval escalation is disabled in this environment.

I’m not marking this PR ready because I could not perform the review or fixes.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}