ci: verify CICD setup end-to-end #1
Reference in New Issue
Block a user
Delete Branch "cicd/test"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Trigger CI to verify all Variables/Secrets are correctly set.
Every subproject now has README.md: - 3 runnable modules (:standalone, :agentik-cli, :agentik-tui): quickstart, env table, parameters, known limits - 11 library modules: what it is, which problem solves, how to wire it in, where versions live Root README.md is the navigation hub (Quickstart, Modules table, publish + CI/CD notes). Also: ci.yml prunes the :memory-vector -x excludes now that text-embedding-kmp artifacts are published to caffeine. 518 tests green. Verified publish pipeline: :proto:publish to caffeine produces pom.module + per-target klibs + sources for all 9 KMP targets. 🤖 Generated with [opencode]shadowJar produces `standalone-0.1.0-all.jar` (archiveBaseName + classifier.all), not `standalone-all.jar`. Use `*-all.jar` glob patterns in upload + attach steps; works regardless of version. 🤖 Generated with [opencode]Pull request closed