MTA-7135: Agent Mode Compilation Guardrails AST Verification

[anarnold97]

---

JIRA

• MTA-7135

---

PREVIEW

• 1.5. Output verification and agent mode guardrails
  • 1.5.1. Agent mode code quality safeguards
  • 1.5.2. Agent mode validation checks
  • 1.5.3. Autocorrection on compilation failure

---

DESCRIPTION

Add documentation for Agent Mode guardrails and the build-tool validation loop introduced in MTA-7135.

New content:

• con_agent-mode-guardrails.adoc — explains how the extension passes each AI-generated code suggestion through a local build dry-run (mvn compile, gradle compileJava, npm run build, or yarn build) before applying it to the workspace, covering syntax verification, method signature and classpath resolution, import consistency checks, and the auto-correction retry loop on compilation failure

• proc_enabling-agent-mode.adoc — step-by-step procedure for enabling Agent Mode via the VS Code command palette or settings panel, with a verification example using the Lightspeed output panel
  The two new modules are included in assembly_understanding_dl.adoc after the existing Agent AI concept and before the benefits reference.

[coderabbitai]

Warning

Review limit reached

@anarnold97, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 72235d1e-6801-4ad4-ac49-b2de9ccb24bb

📥 Commits

Reviewing files that changed from the base of the PR and between a37205d and 827d05f.

📒 Files selected for processing (3)

• docs/topics/developer-lightspeed/assembly_understanding_dl.adoc
• docs/topics/developer-lightspeed/con_agent-mode-guardrails.adoc
• docs/topics/developer-lightspeed/proc_enabling-agent-mode.adoc

📝 Walkthrough

Walkthrough

Two new AsciiDoc documentation topics are added: one describing Agent Mode output verification and guardrails, and one describing procedures for enabling agent mode in the Lightspeed VS Code extension. The existing assembly page is updated to include both new topics.

Changes

Agent Mode Documentation

Layer / File(s)	Summary
Assembly page include wiring docs/topics/developer-lightspeed/assembly_understanding_dl.adoc	The include sequence and end-of-page attribute reset logic are updated to reference the two new topics.
Agent Mode guardrails topic docs/topics/developer-lightspeed/con_agent-mode-guardrails.adoc	New topic describing local dry-run verification, syntax/reference/import checks, and a two-pass auto-correction retry flow, limited to minor errors.
Enabling agent mode procedure docs/topics/developer-lightspeed/proc_enabling-agent-mode.adoc	New procedure topic with prerequisites, two enablement workflows, a language-server restart step, and a sample verification output.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: Pkylas007, djzager

Poem

A rabbit hops through docs anew,
Guardrails set for Agent's view,
Enable steps, a checklist neat,
Dry-runs done, then all complete,
Hop, hop, the manuals grew! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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.
Title check	✅ Passed	The title matches the PR’s main theme of agent mode guardrails and verification updates.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[Pkylas007]

Suggested minor clarification questions.

LGTM, thanks!

[rromannissen]

Overall LGTM, but the bit about refining the prompt needs to be changed.