Commit Graph
6 Commits
Author SHA1 Message Date
Gaurav DubeyandClaude Opus 5.5 f45a75b5f7 fix(install): reject blank quoted Antigravity triggers in the YAML fallback
When strict YAML cannot load a rule (for example unquoted globs), the
line-based fallback treated trigger: '' as native and left the rule
without an activation trigger. Read the trigger value by hand, drop a
trailing comment and surrounding quotes, and only treat a nonblank value
as native.

Refs #3548

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 04:45:06 +00:00
Gaurav DubeyandClaude Opus 5.5 5a236c2071 fix(install): decide native Antigravity triggers from parsed YAML
Treat a rule as native only when its parsed `trigger` is a non-empty
string, so empty, comment-only, and blank-string triggers are adapted.
The line check is kept only as the fallback for native rules whose
unquoted globs cannot be parsed as YAML.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 03:59:14 +00:00
Gaurav DubeyandClaude Opus 5.5 74e9a17291 fix(install): require a value before treating an Antigravity trigger as native
An empty `trigger:` line is not a usable activation trigger, so adapt
the rule instead of passing it through unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 03:38:46 +00:00
Gaurav DubeyandClaude Opus 5.5 23ae02e144 fix(install): pass native Antigravity rules through before YAML parsing
A rule that already declares a trigger may carry unquoted
`globs: **/*.ts`, which js-yaml rejects as an alias. Detect an existing
trigger before parsing so native rules, and the adapter's own output,
pass through unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 03:17:16 +00:00
Gaurav DubeyandClaude Opus 5.5 9bb1309db6 fix(install): quote Antigravity rule globs as a YAML string
A plain YAML scalar cannot start with `*`, so `globs: **/*.py` is not
valid YAML for a strict parser. Emit the joined globs as a quoted string
and have the adapter tests parse the emitted frontmatter.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 03:04:10 +00:00
Gaurav DubeyandClaude Opus 5.5 ee7156c0f6 fix(install): give Antigravity rules an activation trigger
Antigravity only attaches a workspace rule when its frontmatter declares
a trigger. The antigravity target copied rules verbatim: common rules
have no frontmatter and language rules carry Claude's `paths:` list, so
every ECC rule landed in .agents/rules/ and was never loaded.

Add an antigravity-rule-frontmatter content transform and apply it to
rule pack files on both the manifest and legacy install paths. Rules
without frontmatter become `trigger: always_on`; `paths:` becomes
`trigger: glob` with matching `globs:`. A rule that already declares a
trigger is left alone, and rules/README.md stays inert. Canonical rule
sources are unchanged.

Fixes #3548

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 02:39:52 +00:00