docs: add Intelligence Over Scripts to system prompt and PR issue-linkage guidance

[marcusquinn]

Summary

• Adds "Intelligence Over Scripts" as a core principle in build.txt (the system prompt loaded by every worker) so it's in the active reasoning chain — not buried in architecture.md where headless workers may never read it
• Adds mandatory issue-linkage guidance to full-loop.md Step 4 (PR Create): workers must search for ALL related issues before composing the PR body and include Closes #NNN for each match

Problem

PRs weren't connecting to the issues they resolved (observed on #2421, #2341):

1. Duplicate issues under different title formats — CodeRabbit creates coderabbit: Fix X, then claim-task-id.sh creates t1234: Fix X for the same task. The deterministic title-prefix dedup (startswith("t1234:")) misses the CodeRabbit-format issue entirely.
2. Workers closing duplicates with comments — A worker posted "Resolved by PR t1344: Fix ShellCheck SC1091 noise from sourced files #2427" as a comment on t1344: Add local dev / .local domains / LocalWP to build-plus.md Domain Expertise Check #2421, but comments don't create GitHub PR-issue links. Only Closes/Fixes/Resolves #NNN in the PR body does.
3. Stale labels on manually closed issues — Supervisor: duplicate workers dispatched for issue #2300 (t1337) #2341 was closed manually but kept needs-review label.

Fix approach

Intelligence over scripts: instead of adding more regex/heuristic dedup logic to bash scripts, tell the worker (an LLM that can reason about semantic similarity) to search for all related issues and link them properly. Two guidance-doc edits, zero new scripts.

Also cleaned up labels on #2421 and #2341 directly.

[coderabbitai]

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 7 minutes and 10 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d39739e and 8372f29.

📒 Files selected for processing (2)

• .agents/prompts/build.txt
• .agents/scripts/commands/full-loop.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/intelligence-over-scripts-build-txt

---

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.}

[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!

[github-actions]

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 36 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Fri Feb 27 03:18:31 UTC 2026: Code review monitoring started
Fri Feb 27 03:18:31 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 36

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 36
• VULNERABILITIES: 0

Generated on: Fri Feb 27 03:18:34 UTC 2026

---

Generated by AI DevOps Framework Code Review Monitoring

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud