Repository navigation
VibeTags v1.3.3
[1.3.3] - 2026-09-10
Upgrading
One build outcome changes under you, and it changes in the safe direction. A compilation
that was shown only part of a module's sources now writes nothing at all, warns, and names
the sources it never read. The build that hits this most often is an ordinary incremental
Gradle compileJava after touching one annotated file: before this release that round
rewrote the module's guardrails from the one element it could see, deleting rule files for
every element it was not shown. If your workflow relied on an incremental compile to
regenerate guardrails, it no longer does; run a full compile (clean compileJava, or
gradle --rerun-tasks) when you want the files refreshed. Nothing is deleted either way.
Added
-
Four platforms from a sweep of the AI tool landscape on 2026-09-08, taking the totals to 41
platforms, 50 config files and 17 scoped-rule directories: Antigravity workspace rules
(.agents/rules/, which was half-supported before this, since.antigravityignorewas
already generated), JetBrains AI Assistant project rules (.aiassistant/rules/, a
separate product from the already-supported Junie), Augment Code workspace rules
(.augment/rules/) and goose (.goosehints). All three granular directories are
front-matter-free, each for a reason read from the vendor's own docs: Antigravity and
JetBrains set a rule's activation mode outside the file, and Augment defaults a
front-matter-free rule toalways_apply, which is the safe mode for a guardrail because its
alternative leaves loading to the model.PlatformSweep202609EndToEndTestalso pins
Antigravity's documented 12,000-character-per-rule cap, the one output constraint nothing
else in the codebase has had to respect. -
examples/basicnow opts into.gemini/rules, which it never had. Gemini's granular output
shipped in #320 and no example ever covered it, so for four releases it had no committed
fixture, no byte-for-byte drift gate, and no coverage of the dual-opt-in path where
GEMINI.mdcollapses to a scoped-rules index. Adding it moved that file from 274 lines to
93, with the safety buckets inline and 32 pointers into the scoped files, which is what
invariant 6 has always specified and nothing was checking.ExampleOptInCoverageTestnow
holds the example to every opt-in key, withroot_indexandlocks_reportexempted by name
and reason. -
Grok Build scoped rules: opting in
.grok/rules/writes one Markdown rule file per annotated
element there, bringing the count to 38 platforms and 14 scoped-rule directories. Grok reads
AGENTS.mdnatively and.claude/rules/for compatibility, so a project already opted into
either was reaching Grok before this; the new directory is for projects that keep Grok's rules
separate from another tool's. Three properties of Grok's discovery, taken from its own user
guide rather than from third-party guides, shape the output: it reads only*.md, it parses no
YAML front matter (so none is written, where Cursor and Windsurf get aglobs:block), and it
loads every file in the directory on every session rather than on demand by glob. That last one
is a cost to weigh before opting in on a large codebase. Grok has no VibeTags aggregate of its
own, so opting in never collapses another platform's file to a scoped-rules index.
Fixed
-
examples/basic/reset-ai-files.shnow clears.kiro/steering, which it had left behind since
v0.9.7. The script exists so a following clean compile proves the processor regenerates
everything, and it worked from two hand-maintained copies of aServiceRegistrysubset. A rule
file for a class whose annotation had since been removed survived the reset, the next compile
did not rewrite it, and the stale file read as current output, so the check proved less than it
appeared to.ExampleResetScriptCoverageTestnow derives both lists from the registry, in both
directions: every path the example opts into must be cleared, and every path the script names
must still be written by some service. It reported.kiro/steeringbefore the fix. -
A compilation shown only some of a module's sources no longer rewrites that module's guardrails
from what it happened to see. Reported from a Gradle single-module build: touching one annotated
file and running an ordinary incrementalcompileJavadeleted 22 checked-in rule files and cut
27 lines out ofCLAUDE.md, including a whole<security_elements>block, with exit code 0 and
nothing on the console. Gradle picks the files to recompile from the annotations it can see in
class files, and every VibeTags annotation isSOURCE-retention, so an edit to one file
recompiles that file alone; the processor was then handed one element where the last build had
twelve, and every element it was not shown read as an element whose annotation had been deleted.
PartialRoundDetectornow refuses such a round: nothing is written, nothing is swept, no
fingerprint is recorded, and aWARNINGnames the sources the round never read and how to get a
full compile. The refusal needs two independent facts, so that neither of its own failure modes
can happen — a sidecar for this source tree naming an element the round did not produce, and an
uncompiled.javafile under a source root the round did compile from that names the annotation
package. An annotation genuinely removed from a source the round did compile still loses its
rule file, and a source permanently excluded from compilation never blocks a write. -
The orphan sweep no longer reports files it did not touch. A hand-written
booking-flow.mdin
.claude/rules/was named inremoved=while sitting intact on disk, which inflated the
destructive-sweep count and sent the reader hunting for a deletion that never happened. A file
with no VibeTags markers is neither modified nor listed.
Changed
vibetags.logrecords the jar the running processor was loaded from alongside its version
(processor.origin version=… origin=…). A build reported a banner naming a release two versions
older than the only one its dependency block resolved, which reads as a hardcoded fallback
constant; there is none, so the answer is always "an older jar was on the processor path" and
the path itself says which one.