INTENT-2 v2: .prompt {{name}} substitution + .dialog dual-brace, drop comment exception#71
Conversation
|
Warning Review limit reached
More reviews will be available in 39 minutes and 9 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
…rop comment exception
feat!: breaking reinterpretation of brace handling.
- §4.4 (.prompt): substitution variable is now {{name}} (double-brace) ONLY.
A single {name}, a lone { or }, and literal JSON/markup pass through
unchanged — which is why prompts (full of literal single braces) require
double braces. The author-comment exception is removed entirely: a .prompt
has no comment handling and <!-- --> is literal text. {{name}} substitution
is the only special handling a .prompt receives.
- §4.2 (.dialog): now recognizes BOTH {name} and {{name}} per INTENT-1 §3.4,
treating them identically.
Bumps OVOS-INTENT-2 to Version 2 (header, CHANGELOG ### 2, README class).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
9182345 to
384a426
Compare
What
Breaking reinterpretation of brace handling in
.promptand.dialog. The implementation already landed in ovos-spec-tools #38; this PR is the matching spec text.Sections changed (
intent-2.md).dialog) — flips the old "single-brace{name}only; no{{ }}form" restriction:.dialognow recognizes both{name}and{{name}}per OVOS-INTENT-1 §3.4, treating them identically..prompt):{{name}}(double-brace only). A single{name}, a lone{/}, and literal JSON/markup ({},{ },{"key": 1}) pass through unchanged. This is why prompts require double-brace — they routinely contain literal single braces..prompthas no comment handling;<!-- … -->is literal text. The only special handling a.promptreceives is{{name}}substitution.{name}is already literal everywhere, so the carve-out is moot).{{query}}is substituted; the<!-- … -->line and single-brace{response}survive verbatim.{name}to{{name}}.### 2section describing the breaking.prompt/.dialogbrace changes.1→2.Version (triple-match)
Breaking (reinterprets previously-literal
{{ }}; drops comment-stripping) → bump to Version 2:**Version:** 2### 2under OVOS-INTENT-22Dangling-reference check
Removing the comment exception left no dangling references inside
.promptcontent. The only stale mention — the See-also "verbatim text with optional{name}substitution only" — was updated to{{name}}. The §3 common-reader#-comment rule is unrelated (it governs line-oriented files;.promptis read whole and is explicitly exempt).