Skip to content

feat(#1018): :agents-kt-ksp Gradle module skeleton + Maven Central pu…#44

Merged
Skobeltsyn merged 3 commits intomainfrom
feat/1018-agents-kt-ksp-module
May 5, 2026
Merged

feat(#1018): :agents-kt-ksp Gradle module skeleton + Maven Central pu…#44
Skobeltsyn merged 3 commits intomainfrom
feat/1018-agents-kt-ksp-module

Conversation

@Skobeltsyn
Copy link
Copy Markdown
Contributor

…blication

Stand up the KSP processor module as a sibling Gradle subproject. Empty SymbolProcessorProvider — consumers can wire it via the KSP plugin and ksp("ai.deep-code:agents-kt-ksp:VERSION") but it does no work yet. The validation pass (#1019) and schema codegen (#1020) plug into the processor's process() in subsequent issues.

What landed:

  • settings.gradle.kts — include(":agents-kt-ksp")
  • agents-kt-ksp/build.gradle.kts — kotlin("jvm"), KSP API dependency (com.google.devtools.ksp:symbol-processing-api:2.3.7), runtime library as compileOnly so it never reaches consumer's runtime classpath, full Maven Central publication block mirroring root, signed with the same in-memory PGP key
  • AgentsKtSymbolProcessor — empty no-op skeleton with TODO comments for #1019 + #1020 attachment points
  • AgentsKtSymbolProcessorProvider — wraps the processor for KSP service discovery
  • META-INF/services/com.google.devtools.ksp.processing.SymbolProcessorProvider — service-loader file pointing at the provider
  • gradle/verification-metadata.xml regenerated with KSP API SHA-256s
  • agents-kt-ksp/gradle.lockfile generated for dependency locking

Verified:

  • :agents-kt-ksp:build succeeds
  • :agents-kt-ksp:publishMavenCentralPublicationToMavenLocal produces signed jar + sources + javadoc + module + pom + .asc signatures
  • Root :build still succeeds — runtime artifact unchanged

Skobeltsyn and others added 3 commits May 5, 2026 12:52
…ate string overload

Migrate ~35 test files and 4 user-facing demos (swarmdemo agents +
InteractiveLiveShowDemo) from `tools("name")` string form to typed
`tools(handle)` form using `lateinit var` declarations inside the
`agent { }` block. Updates docs/model-and-tools.md examples to lead
with the typed form.

Add `@Deprecated(level = WARNING, ReplaceWith)` to `Skill.tools(vararg names: String)`.

New overload: `Skill.tools()` (no-arg) marks a skill agentic with no
allowlisted tools — disambiguates from the deprecated string-vararg
form so existing `tools()` empty calls don't fire the warning.

Files explicitly NOT migrated (legitimate string-form use):
- UnknownToolNameValidationTest, SkillFreezeTest, AgenticSkillTest —
  test the string API directly or test missing-tool detection. File-level
  @Suppress("DEPRECATION").
- ReservedMemoryToolNamesTest — references reserved built-in names that
  can't have a user `Tool` handle. File-level suppression.
- Mixed user+built-in tests (EscalateToolTest, ThrowExceptionIntegrationTest,
  JsonParseEscalationIntegrationTest, AgentMemoryTest) — per-method
  suppression where built-in tools (escalate, throwException, memory_*)
  appear; user-only methods migrated to typed form.
- AgentFibonacciMcpTest, AgentMcpToolUseTest — MCP tool names discovered
  at runtime; per-call suppression with reasoning.
- TypedToolRefsTest — single string-form test method retained for the
  side-by-side comparison with the typed test.

Verified: zero deprecation warnings from project code, full test suite
green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…at note

README "What's in the Box" calls out the typed `tools(handle)` form and
the soft-deprecation of the string overload.

CHANGELOG Unreleased section retargeted at 0.3.0 with an explicit
"Binary compatibility" subsection: source-compatible (existing code
compiles unchanged), binary-incompatible (`tool(...)` builders return
`Tool<...>` instead of `Unit` — consumers must recompile).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…blication

Stand up the KSP processor module as a sibling Gradle subproject. Empty
SymbolProcessorProvider — consumers can wire it via the KSP plugin and
ksp("ai.deep-code:agents-kt-ksp:VERSION") but it does no work yet. The
validation pass (#1019) and schema codegen (#1020) plug into the
processor's process() in subsequent issues.

What landed:
- settings.gradle.kts — include(":agents-kt-ksp")
- agents-kt-ksp/build.gradle.kts — kotlin("jvm"), KSP API dependency
  (com.google.devtools.ksp:symbol-processing-api:2.3.7), runtime library
  as compileOnly so it never reaches consumer's runtime classpath, full
  Maven Central publication block mirroring root, signed with the same
  in-memory PGP key
- AgentsKtSymbolProcessor — empty no-op skeleton with TODO comments for
  #1019 + #1020 attachment points
- AgentsKtSymbolProcessorProvider — wraps the processor for KSP service
  discovery
- META-INF/services/com.google.devtools.ksp.processing.SymbolProcessorProvider
  — service-loader file pointing at the provider
- gradle/verification-metadata.xml regenerated with KSP API SHA-256s
- agents-kt-ksp/gradle.lockfile generated for dependency locking

Verified:
- :agents-kt-ksp:build succeeds
- :agents-kt-ksp:publishMavenCentralPublicationToMavenLocal produces signed
  jar + sources + javadoc + module + pom + .asc signatures
- Root :build still succeeds — runtime artifact unchanged

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Skobeltsyn Skobeltsyn force-pushed the feat/1018-agents-kt-ksp-module branch from c238aa5 to 295c5e4 Compare May 5, 2026 09:55
@Skobeltsyn Skobeltsyn merged commit 0f247f2 into main May 5, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant