vibetags AGENTS.md

VibeTags — Agent Instructions

Start with llms.txt for a map of this repo's docs and layout.

The primary agent briefing is CLAUDE.md — build commands, build order, architecture invariants, and the <project_guardrails> block (locked files, contract-frozen signatures, hot-path constraints). It is tool-neutral despite the name: read and follow it whichever agent you are.

Ground rules for any agent working here:

• Respect the guardrails in CLAUDE.md: never edit files/elements listed as locked, never change contract-frozen signatures.
• Never hand-edit content between VIBETAGS-START/VIBETAGS-END markers in any file — it is generated by this project's own annotation processor.
• Build order matters: vibetags-annotations → vibetags → vibetags-bom → example. Always build from the subproject's own directory.
• Reference docs load on demand: docs/ANNOTATIONS.md (annotation reference), docs/PLATFORMS.md (output-file table), docs/TESTS.md (test coverage map), docs/ARCHITECTURE.md (deep dive), docs/DEPENDENCIES.md (third-party artifacts).

Note: this file is intentionally not VibeTags-managed — other AI config files exist at the root, so the processor's AGENTS.md sole-file fallback leaves it untouched.

AUTO-GENERATED AI RULES

Generated by VibeTags | https://github.com/PIsberg/vibetags

Do not edit manually.

LOCKED FILES (DO NOT EDIT)

• se.deversity.vibetags.processor.AIGuardrailProcessor.generateFiles(): Step order is load-bearing: fingerprint check → sidecar write → sidecar read → merge → file write → cache flush; reordering steps silently skips regeneration or corrupts multi-module output
• se.deversity.vibetags.processor.internal.TransitiveManifest.RESOURCE_PACKAGE: Must stay a valid Java package name. javac's CLASS_PATH location skips archive directories that are not package identifiers, so moving these manifests under META-INF/ leaves Filer.getResource listing zero entries and transitive discovery fails silently while the conventional location looks correct. TransitiveManifestPathTest pins the working path.
• se.deversity.vibetags.processor.model.GuardrailAnnotations.ALL: Append only. This order fixes the insertion order of every LinkedHashSet downstream, so reordering or removing an entry rewrites generated files in every consuming build, with nothing failing to name the cause. BuildFingerprint hashes in its own separately pinned order; the two are not the same list and must not be aligned.