Repository navigation
VibeTags v1.3.6
[1.3.6] - 2026-09-21
Added
vibetags-ksp: VibeTags under KSP (#496). A Kotlin project that has moved fully to KSP could
not run VibeTags at all, because KSP cannot load a JSR 269 processor. It now depends on
ksp("se.deversity.vibetags:vibetags-ksp")in place of the processor. The new artifact is an
adapter, not a second implementation: it presents KSP's declarations to the unchanged
AIGuardrailProcessoras the elements kapt's stubs would have contained, so element paths, and
therefore.vibetags-locksentries, granular rule filenames and sidecars, do not change when a
project switches front ends.StubParityTestcompares 110 annotated elements and every generated
file of a fixture with a recorded kapt build, byte for byte, and CI buildsexamples/kotlin-ksp
(the kapt example's sources through KSP) and fails unless its output equals the kapt example's.
Differences from kapt:.vibetags-locksline ranges point at the.ktsource rather than a
generated stub, and a guardrail on a function kapt has no stub for (a value class in its signature) is reported as a build warning instead of being
lost silently. An incremental KSP build regenerates from the whole module: without that, KSP shows
a processor only the changed files, and the first test run of the adapter rewroteCLAUDE.mdfrom
one file and dropped the untouched file's guardrail.- Fixed: a module whose main and test sources are both annotated produced invalid YAML. Every
generated YAML document (.coderabbit.yaml,sweep.yaml,ellipsis.yaml,.plandex.yaml,
.roomodes,.interpreter/profiles/vibetags.yaml,.aider.conf.yml) carried its top-level key
once per compiled source set, because a module's two rounds each render the whole document and
the merge stacked them. A strict parser rejects such a file outright; a lenient one keeps the
last block, so the main source set's guardrails were silently dropped. Single-module projects
were affected as well as reactors. Plandex was the worse case: itslocked:andaudit:keys
repeated inside the block, and the bucket merge resolved that by keeping the last, losing the
main source set's entries rather than merely producing an ambiguous document. Nothing had to be
opted into for this: any project that annotated a test class and opted into one of those files
had it. Annotate nothing in a test source set and the output is unchanged. TESTING.md: guardrails on test code, out of the always-loaded files. Annotating fixtures,
test helpers and test classes used to put their guardrails inCLAUDE.md,.cursorrulesand
every other always-loaded instruction file, so each agent session paid for test-only rules
whether or not it touched a test. Create an emptyTESTING.mdbeside them and a round that
compiles test code (source settest,*Test,*TestsortestFixtures) writes its
guardrails there instead; each file that gave some up ends with one sentence pointing at it.
The six safety annotations (@AILocked,@AICore,@AIPrivacy,@AIIgnore,@AIAudit,
@AISecure) never move, whatever code they are on:TESTING.mdis read on demand, which is too
late for a locked fixture. Ignore files, JSON, TOML and YAML tool configuration and granular rule
files are not routed. WithoutTESTING.mdnothing changes, and deleting it loses nothing: a
routed round also records what it would have written without the file (sidecar key~tfull~),
and the merge reads that once the file is gone, so a main-only build puts the test guardrails
back.TESTING.mddoes not count as another AI config file for theAGENTS.mdsole-file rule.
Known limits: a round that compiles main and test sources together counts as main and is not
routed; a module whose main sources carry no annotation gets its test guardrails back on the
next test compile afterTESTING.mdis deleted, not on a main-only build; and removing the last
annotation from a test source set leaves its guardrail in place, as it already did inCLAUDE.md.
Those three are tracked as issues #780, #782 and #781.-Avibetags.exclude: an annotated element that is not a guardrail (#792). Some annotated
elements exist to prove an annotation compiles, not to instruct an agent. Annotation-definition
fixtures are the clear case: one element per@AItype carrying a placeholder reason. Published,
they tell an agent never to edit a class calledTestLockedClass, in a file it loads every
session. In this repository they were 6 638 bytes ofCLAUDE.md, a third of the file, and half
its scoped rule files. The new option takes comma-separated globs matched against an element's
path, the same string the generated files print in their ownpath="..."attributes, so a
pattern can be written by copying from the output it is meant to shrink;/reads as.and
**as*. A matched element is collected and not published, which is the whole point:
leaving the source out of the compilation instead makes the round look incomplete and invariant
17 correctly refuses to write anything at all. It applies to the aggregates, the scoped rule
files and the.vibetags-lockspositions, and is part of the fingerprint, so adding or removing
a pattern regenerates rather than short-circuiting on the write cache.vibetags.logrecords
exclude.active patterns=[...]on any build that has one. Read the warning in
docs/PROCESSOR.md: a pattern broader than intended silently drops real
guardrails, and nothing downstream can tell that from an element nobody annotated. One known
limit: a pattern that stops an element being published does not always delete the scoped rule
file a previous build wrote for it, because a reactor module round may not sweep the shared root
directory (#383), so check for leftovers the first time a pattern is added. This repository's own
always-loaded block went from 184 lines to 102, and.claude/rules/from 48 files to 24.
Fixed
-
write.updateloggedreason=size-differsin the streaming fast path when on-disk and new sizes were equal but bytes differed (#775). It now logsreason=bytes-differ. -
A check-mode failure that saw one source set now says so (#794). Check mode writes no
sidecar, deliberately, so on a clean checkout neither the main nor the test round can see the
other's guardrails and a project whose main and test sources are both annotated reports drift
against files that are perfectly correct. The verdict is unchanged and still wrong in that case,
which #794 tracks. What changes is the advice under it: it used to end with "Run a normal compile
and commit the regenerated files", and for this shape a normal compile reproduces exactly the
files already committed, so the reader regenerates a correct tree, sees no diff, and is left with
a red gate and no next step. When the comparison saw one source set and nothing on disk from
another, the error now says that, names the issue, and points at regenerating and diffing the
tree instead. -
vibetags doctorreported a KSP project as unwired, because it looked only for
vibetags-processorin the build file.vibetags-kspnow counts as the processor wiring. -
The consumer sweep no longer reports a repository as
ERRORbecause an earlier sweep of the
same version left its worktree under a differentTMPDIR(#736).git worktree prunekeeps a
worktree whose directory still exists, so the branch stayed checked out there andworktree add
failed before the build ran. The sweep now removes a worktree holding the branch when it follows
its ownwt-<repo>naming, and skips the repository, naming the path, when it does not. -
The consumer sweep no longer reports a JDK-pinned consumer as
FAILon a newer default JDK
(#737). A consumer entry can name the JDK it needs; the sweep builds it withJAVA_HOMEfrom
JDK<n>_HOME, builds on the default JDK when that variable is unset and the default is inside the entry's range
(21-25for codekarta, matching its enforcer's[21,26), #743), skips it by name otherwise, and
reports an enforcerRequireJavaVersionfailure asERRORwith a toolchain note. On 2026-09-15
codekarta reportedFAILon JDK 26 and passed on JDK 21. The skip test asserted nothing on JDK 21,
which is every Windows and macOS leg of CI, because it branched on the test JVM's version rather
than thejavathe script reads; it now pins thatjavaonPATHin both directions. -
The consumer-sweep tests no longer skip silently where
shis not onPATH(#744). Maven run
from PowerShell on Windows reported all six as skipped. They now fall back to Git for Windows'
bin/sh.exe, found throughgit --exec-path, and with no shell at all they fail underCI=true
instead of reporting a green skip. Measured on Windows from PowerShell: 6 skipped before, 14 run
and 0 skipped after, counting the newConsumerSweepShellTest.