Remove unused Unreal starter variants

Docs/RequiredPlugins.md

@@ -6,30 +6,21 @@ limited to editor workflow.
 
 ## Current Enabled Plugins
 
-These are the only plugins intentionally enabled in `AgrarianGame.uproject`.
+This is the only plugin intentionally enabled in `AgrarianGame.uproject`.
 
 | Plugin | Required For | Runtime Needed | Notes |
 | --- | --- | --- | --- |
-| `StateTree` | Template AI code that still compiles under `Variant_Combat` and `Variant_SideScrolling` | Yes, until those template variants are removed or rewritten | Required by `StateTreeModule` includes and dependencies. |
-| `GameplayStateTree` | StateTree AI component support used by the template AI controllers | Yes, until those template variants are removed or rewritten | Required by `GameplayStateTreeModule` and `UStateTreeAIComponent`. |
 | `ModelingToolsEditorMode` | Editor-side terrain, mesh, and prototype world-building workflow | No | Keep enabled for developer/editor use. Revisit before shipping if it adds unnecessary packaging overhead. |
 
 ## Module Dependencies Tied To Plugins
 
-`Source/AgrarianGame/AgrarianGame.Build.cs` currently depends on:
+`Source/AgrarianGame/AgrarianGame.Build.cs` has no current plugin-specific
+module dependencies.
 
-- `StateTreeModule`
-- `GameplayStateTreeModule`
-
-Do not disable `StateTree` or `GameplayStateTree` until the template AI source
-under these folders is removed or refactored:
-
-- `Source/AgrarianGame/Variant_Combat/`
-- `Source/AgrarianGame/Variant_SideScrolling/`
-
-The template variant decision is captured in `Docs/TemplateVariantDecision.md`.
-When those variants are removed, revisit this document and remove the StateTree
-plugin/module dependencies if no Agrarian-specific AI code needs them.
+The template variant cleanup removed the unused Combat, Platforming, and
+SideScrolling starter source/content. That allowed `StateTree`,
+`GameplayStateTree`, `StateTreeModule`, and `GameplayStateTreeModule` to be
+removed from the baseline.
 
 ## Explicitly Not Enabled Yet
 
@@ -72,9 +63,7 @@ Before disabling a plugin:
 
 ## Current Decision
 
-Keep `StateTree`, `GameplayStateTree`, and `ModelingToolsEditorMode` enabled for
-version `0.01`.
+Keep `ModelingToolsEditorMode` enabled for version `0.01` as an editor workflow
+plugin.
 
-Do not add additional plugins until a roadmap item requires them. The next
-plugin review is the template-variant cleanup item, because that may allow the
-project to remove StateTree dependencies if the template AI code is deleted.
+Do not add additional plugins until a roadmap item requires them.

Docs/TemplateVariantDecision.md

@@ -1,21 +1,20 @@
 # Unreal Template Variant Decision
 
 Version `0.01` decision: remove unused Unreal starter variants from the
-long-term Agrarian project, but do the actual source/content cleanup as the
-next focused cleanup item instead of mixing it with this decision record.
+long-term Agrarian project.
 
 ## Decision
 
 Agrarian should not keep the unused starter gameplay variants as normal project
 surface area.
 
-Remove or quarantine:
+Removed:
 
 - `Variant_Combat`
 - `Variant_Platforming`
 - `Variant_SideScrolling`
-- Their maps, external actors, input assets, UI assets, VFX, and prototype
-  content when no Agrarian-specific map depends on them.
+- Their maps, external actors, external objects, input assets, UI assets, VFX,
+  and prototype content.
 
 Keep temporarily:
 
@@ -31,33 +30,28 @@ The extra starter variants increase compile time, plugin dependencies, content
 noise, and risk during packaging. They also make the project look like a
 generic Unreal template instead of an Agrarian-specific survival game.
 
-The current compiled variant source still pulls in `StateTree` and
-`GameplayStateTree` through Combat and SideScrolling template AI code. Once the
-unused variants are removed, those plugin dependencies should be rechecked and
-removed if no Agrarian-specific AI code needs them.
+The removed compiled variant source pulled in `StateTree` and
+`GameplayStateTree` through Combat and SideScrolling template AI code. After the
+variant source/content cleanup, those plugin dependencies were removed from the
+baseline.
 
 ## Cleanup Rules
 
-Perform the cleanup in the editor-aware content organization pass:
+Cleanup performed:
 
-1. Create a backup or ensure the current project backup timer has a fresh
-   snapshot before deleting content.
-2. Remove unused variant C++ folders and include paths.
-3. Remove matching content folders and external actor/object data.
-4. Remove `StateTreeModule` and `GameplayStateTreeModule` if no remaining code
-   needs them.
-5. Disable `StateTree` and `GameplayStateTree` in `AgrarianGame.uproject` if no
-   remaining content needs them.
-6. Keep the current `ThirdPerson` character path until the MVP landing page and
+1. Removed unused variant C++ folders and include paths.
+2. Removed matching content folders and external actor/object data.
+3. Removed `StateTreeModule` and `GameplayStateTreeModule`.
+4. Disabled `StateTree` and `GameplayStateTree` in `AgrarianGame.uproject`.
+5. Kept the current `ThirdPerson` character path until the MVP landing page and
    male/female character selection flow are implemented.
-7. Build `AgrarianGameEditor`.
-8. Open the Ground Zero map and run map check.
-9. Run the existing automation smoke checks that cover interaction, resources,
-   wildlife, and Ground Zero placement.
 
 ## Current State
 
-Decision is complete. Cleanup is intentionally deferred to the next roadmap
-item, `Organize Content/Agrarian/ folders and move starter/prototype assets into
-clearly named locations`, so deletions and redirects can be validated in one
-focused pass.
+Decision and cleanup are complete for the unused starter variants. Remaining
+starter/prototype dependencies are intentionally narrow:
+
+- `ThirdPerson` stays until Agrarian-specific player character assets and the
+  MVP character selection flow replace it.
+- `LevelPrototyping` stays because current Agrarian setup scripts and prototype
+  Blueprints still use its simple cube/cylinder meshes.