Repository navigation
feat: jrag-annotations — brownfield annotations as a Maven Central artifact - #480
Merged
Merged
Conversation
… as a dependency)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The brownfield annotation definitions (
@CodebaseRole,@CodebaseCapability,@CodebaseHttpRoute,@CodebaseAsyncRoute,@CodebaseHttpClient,@CodebaseProducer+ enums) existed only as fenced Java blocks indocs/CONFIGURATION.md§4.3 and test fixtures. This ships them as a real dependency:io.github.humanbean17:jrag-annotationson Maven Central, independently versioned (initial1.0.0),SOURCE-retained so consumers declare itprovided/compileOnly— nothing reaches runtime bytecode. No parser changes: the indexer matches simple names and reads attributes at usage sites, so JAR-provided definitions are invisible to it.annotations/— canonical, compilable Maven module (16 sources + pom; Java 8, Central-complete metadata;releaseprofile = flatten + GPG + Central Portal publish). Plainmvn verifyneeds no credentials.tests/_meta/test_annotations_module_consistency.py— three-way drift tripwire: module ↔ parser vocabulary (ast_javafrozensets,java_ontologyVALID_*), module ↔ §4.3 docs blocks, module ↔ fixtures; plus a docs-mention tripwire. Vocabulary growth now fails tests instead of silently diverging..github/workflows/release-annotations.yml— manual-dispatch Maven Central release (version input, regex + Central-search idempotency guards,annotations-v*tags — disjoint from Pythonv*), with the one-time setup runbook in the header. 7 structural tests pin its invariants.test.yml— blockingannotations-buildjob (mvn verifyon every PR).CODEBASE_REQUIREMENTS.md§A.2.1 andAGENTS.mdPublishing updated (the artifact is a third channel, outside the dual-PyPI sync rule).Spec:
docs/superpowers/specs/active/2026-09-13-jrag-annotations-artifact-design.md· Plan:docs/superpowers/plans/active/2026-09-13-jrag-annotations-artifact.mdTest evidence
tests/_meta/…consistency,tests/package/…release_annotations_workflow);mvn -B -f annotations/pom.xml verify→ BUILD SUCCESS (jar + sources + javadoc).test_publish_skill_runbook— pre-existing on master (hardcoded.claude/skills/publish-pip/SKILL.md; tracked path is.agents/skills/...since the claude→agents rename). Fails identically on clean master; deserves a separate one-line fix.test_release_sh— assert a clean tree; failed only because the shared dev worktree carried another session's uncommitted edits. Pass on clean checkouts.After merge
First
1.0.0release needs the one-time setup from the workflow header runbook: Central Portal namespace verification (io.github.humanbean17), GPG signing key, and the four secrets in thereleaseenvironment — then dispatchrelease-annotations.ymlwithversion=1.0.0.