docs: remove ksp

docs/.vitepress/config.mts

···
         items: [
           {text: 'Introduction', link: '/getting-started/introduction'},
           {text: 'Quickstart', link: '/getting-started/quickstart'},
-          {text: 'Applying KSP', link: '/getting-started/ksp'},
           {text: 'Examples', link: '/getting-started/examples'},
         ]
       },

docs/src/core-apis/commands.md

···
 ```kt
 val TestCommand = Command("test") {
   async()
-  
+
   executor {
     ctx.sendMesage(text("Hello, world!"))
   }
···
 ```kt
 val TestCommand = Command("test") {
   aliases("hello")
-  
+
   executor {
     ctx.sendMesage(text("Hello, world!"))
   }
···
 ```kt
 val TestCommand = Command("test") {
   aliases("hello")
-  
+
   executor {
     ctx.sendMesage(text("Hello, world!"))
-  }
-  
+}
+
   sub("bye") {
     executor {
       ctx.sendMessage(text("Bye, world!"))
···
 ```kt
 val TestCommand = Command("test") {
   aliases("hello")
-  
+
   val name by arg("name", stringParser()) // stringParser comes from Cloud's StringParser
-  
+
   executor {
     ctx.sendMesage(text("Hello, $name!"))
   }
···
 This will work for `/hello rad`: `Hello, rad!`. But when we
 try to do `/hello bye rad`
 or `/hello rad bye`, we will either get a syntax exception
-or this:
+or this cloud exception:
 
-```
+```txt
 There is no object in the registry identified by the key 'name'
 ```
 
···
 ```kt
 val TestCommand = Command("test") {
   aliases("hello")
-  
+ 
   val name by arg("name", stringParser())
 
   executor {
···
 
   sub("bye") {
     val name by arg("name", stringParser())
-    
+
     executor {
       ctx.sendMessage(text("Bye, $name!"))
     }
···
 ```kt
 val TestCommand = Command("test") {
   aliases("hello")
-  
+ 
   val name by arg("name", stringParser())
 
   permission("axi.testcommands.hello")
-  
+ 
   executor {
     ctx.sendMesage(text("Hello, $name!"))
   }
-  
+ 
   // ...
 }
 ```
···
 
 Well, there's two options:
 
-* Use the [KSP processor](/getting-started/ksp) to register
-  them automatically
-* Register them manually
+- Use the KSP processor to register them automatically
+- Register them manually
 
 ### Automatic Registration
 
-First, make sure you have set up
-the [KSP processor](/getting-started/ksp).
+First, make sure you are using the
+Axi gradle plugin, as specified in the
+[Quickstart](/getting-started/quickstart) page.
 
 Then, all you need to do is to add the `@AutoRegistered`
 annotation to your
···
 @AutoRegistered
 val MyCommand = Command("hello")
 ```
+
+::: warning
+If you are making an Axi module used
+by other people, this will not work
+due to library loading and classloaders.
+See the manual section below.
+:::
 
 ### Manual Registration
 

docs/src/getting-started/ksp.md

···
-# Applying KSP
-
-This guide will teach you how to set up KSP and Axi's KSP
-processor, for automatically registering commands and
-more to come.
-
-## Applying the plugin
-
-Apply the plugin to your buildscript:
-
-::: code-group
-
-```kts [build.gradle.kts]
-plugins {
-  id("com.google.devtools.ksp") version "2.1.20-1.0.31"
-}
-```
-
-```groovy [build.gradle]
-plugins {
-  id 'com.google.devtools.ksp' version '2.1.20-1.0.31'
-}
-```
-
-:::
-
-## Add the processor
-
-Add the processor to your dependencies:
-
-::: code-group
-
-```kts{2} [build.gradle.kts]
-dependencies {
-  ksp("net.radstevee.axi:axi-ksp")
-}
-```
-
-```groovy{2} [build.gradle]
-dependencies {
-  ksp 'net.radstevee.axi:axi-ksp'
-}
-```
-
-:::
-
-::: warning
-If you are using shadow, you may have to change
-your shaded archive classifier:
-
-::: code-group
-
-```kts{3} [build.gradle.kts]
-tasks {
-  shadowJar {
-    archiveClassifier = ""
-  }
-}
-```
-
-```groovy{3} [build.gradle]
-tasks {
-  shadowJar {
-    archiveClassifier = ''
-  }
-}
-```
-
-:::