fix(review): guard fix-handoff suggestion blocks against an embedded code fence

[ultrahighsuper]

What

buildFixHandoffBlock and fixHandoffAggregateItem in src/review/fix-handoff-render.ts splice a finding's suggestion text into a fenced code block without checking whether the suggestion itself contains a ``` sequence. A suggestion demonstrating a fenced code example would close the outer fence early and break the rendered markdown.

Resolves #6632.

Fix

Add the same guard the sibling renderer src/review/inline-suggestion-anchor.ts's safeSuggestionBlock already uses — skip the fenced block entirely when the suggestion contains ``` — to both call sites (buildFixHandoffBlock and fixHandoffAggregateItem). No third convention is invented.

The structured suggestedChange field (raw data consumed programmatically, not a fenced block) is unchanged; only the markdown rendering is guarded, matching the precedent.

Tests

test/unit/fix-handoff-render.test.ts gains a regression for each function: a suggestion containing a ``` fence renders no fenced block (no stray ``` leaks into the output), while the existing present/absent/whitespace-only cases keep their behavior. The new guard branch is covered.

Locally green: npx vitest run test/unit/fix-handoff-render.test.ts → 22/22; eslint clean; the new branch is covered on the diff.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-16 18:23:33 UTC}

2 files · 1 AI reviewer · no blockers · readiness 86/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
Adds a guard to both fixed-block and aggregate-item suggestion rendering in fix-handoff-render.ts that skips the fenced block entirely when a suggestion contains a ``` sequence, mirroring the existing safeSuggestionBlock precedent in inline-suggestion-anchor.ts. The fix is correct, minimal, and matches the description exactly — the structured suggestedChange field is untouched, only the markdown rendering is guarded. Tests cover the new branch for both call sites and confirm no stray ``` leaks into output.

Nits — 2 non-blocking

• The all-or-nothing skip discards the suggestion text entirely rather than escaping/neutralizing the fence (e.g. widening the fence with four backticks), so a contributor loses that suggestion's content in the rendered block — worth confirming this matches the sibling safeSuggestionBlock behavior exactly (src/review/fix-handoff-render.ts:64, :117).
• Consider whether a future enhancement could preserve suggestion content with embedded fences by widening the outer fence delimiter instead of dropping the block, if that's ever a common case.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#6632
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 120 registered-repo PR(s), 72 merged, 21 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	ultrahighsuper; Gittensor profile; 120 PR(s), 21 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: minor

Linked issue satisfaction

Addressed
The diff adds the exact `!suggestedChange.includes("```")` guard from safeSuggestionBlock to both buildFixHandoffBlock and fixHandoffAggregateItem, skipping the fenced block when a triple-backtick sequence is present, and adds regression tests for both call sites as required.

Review context

• Author: ultrahighsuper
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 120 PR(s), 21 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Add a concise scope and risk note.
• Then work through the remaining 1 step in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.65%. Comparing base (6ac8c1f) to head (c8fe833).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6668   +/-   ##
=======================================
  Coverage   93.65%   93.65%           
=======================================
  Files         681      681           
  Lines       68086    68094    +8     
  Branches    18688    18695    +7     
=======================================
+ Hits        63764    63772    +8     
  Misses       3347     3347           
  Partials      975      975           

Flag	Coverage Δ
shard-1	43.91% <100.00%> (-0.08%)	⬇️
shard-2	36.95% <0.00%> (+0.07%)	⬆️
shard-3	32.40% <50.00%> (-0.03%)	⬇️
shard-4	34.14% <0.00%> (-0.43%)	⬇️
shard-5	31.40% <0.00%> (+0.45%)	⬆️
shard-6	45.75% <0.00%> (+0.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/review/fix-handoff-render.ts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.