Reset roadmap for 0.2 development

This commit is contained in:
2026-05-21 10:07:53 +00:00
parent 4e17cede2d
commit 106b3bd01b
2 changed files with 85 additions and 15 deletions
+47 -12
View File
@@ -59,37 +59,46 @@ Design intent:
Primary development repository:
```text
git@github.com:pacificao/AgrarianGameBuild.git
http://192.168.5.21:3000/nathan/agrarian-game.git
```
Primary local Codex/server checkout:
Primary Unreal/Codex build checkout:
```text
/mnt/projects/AgrarianGameBulid
/home/nathan/UnrealProjects/AgrarianGame
```
Ubuntu-Codex host:
Primary Unreal build host:
```text
192.168.5.10
unreal-engine / 192.168.5.20
```
Unraid project share:
Primary engine install:
```text
\\DevBox\projects\AgrarianGameBulid
/opt/UnrealEngine-5.7
```
Windows build VM:
Current engine source tag:
```text
Windows-Builder / 192.168.5.12
5.7.4-release
```
Codex headless editor build command:
Headless Linux editor build command:
```text
UNRAID_PASSWORD=<set in environment> /home/nathan/bin/agrarian-build-editor
cd /opt/UnrealEngine-5.7
./Engine/Build/BatchFiles/Linux/Build.sh AgrarianGameEditor Linux Development -Project=/home/nathan/UnrealProjects/AgrarianGame/AgrarianGame.uproject
```
Historical/secondary locations:
```text
GitHub mirror/source before Gitea migration: git@github.com:pacificao/AgrarianGameBuild.git
Old network-share workflow: \\DevBox\projects\AgrarianGameBulid
Windows build/visual QA VM: Windows-Builder / 192.168.5.12
```
Important tracked project root files/folders:
@@ -138,7 +147,33 @@ Roadmap headings now use release-style milestone numbers. Subsections use letter
labels such as `0.1.A`, `0.1.B`, and `0.1.C` so they do not look like
separate versions.
## Active Milestone - Version 0.01 Foundation Baseline
## Active Milestone - Version 0.2.A Land And Claiming
Status: not started.
Current reset baseline as of 2026-05-21:
- [x] Active game repository moved to self-hosted Gitea.
- [x] Active Unreal build machine moved to Ubuntu VM `unreal-engine`.
- [x] Unreal Engine `5.7.4-release` source build completed on Linux.
- [x] Agrarian Linux editor target builds on the Ubuntu VM.
- [x] Headless project load succeeds with `NullRHI`.
- [x] Git working tree is clean at the reset point.
- [x] Git LFS fsck passes.
- [x] Generated Unreal folders remain ignored.
- [x] Version 0.1 implementation track is complete through `0.1.S`.
- [ ] Start the next milestone with only `0.2.A Land And Claiming`.
- [ ] After `0.2.A` is complete and verified, choose the next milestone deliberately rather than letting the roadmap sprawl drive work out of order.
Coding rule for the next phase:
- Work one roadmap item or one tightly scoped milestone at a time.
- Keep every gameplay change server-authoritative unless explicitly documented otherwise.
- Preserve the Ubuntu Unreal VM and Gitea workflow as the default development path.
- Build or run a focused verifier before each commit.
- Do not use the old mapped-network-drive workflow for primary Unreal editing.
## Previous Milestone - Version 0.01 Foundation Baseline
Status: completed.
+38 -3
View File
@@ -1,13 +1,38 @@
# Codebase Readiness Review
Date: 2026-05-19
Date: 2026-05-21
Scope: source code, build scripts, verification scripts, config files, and the
roadmap after completion of `0.1.R`.
roadmap after completion of `0.1.S` and migration to the Ubuntu Unreal build
VM.
## 2026-05-21 Restart Audit Summary
- Active game checkout is clean on `main` at
`/home/nathan/UnrealProjects/AgrarianGame`.
- Active remote is self-hosted Gitea:
`http://192.168.5.21:3000/nathan/agrarian-game.git`.
- Repository currently tracks 723 files, including 300 Git LFS assets.
- `git lfs fsck` passes.
- Ignored Unreal-generated folders exist locally from verification builds:
`Binaries/`, `Intermediate/`, `Saved/`, and `DerivedDataCache/`.
- Those generated folders are ignored by `.gitignore` and are not part of the
repository state.
- Unreal Engine `5.7.4-release` is built from source at
`/opt/UnrealEngine-5.7`.
- `AgrarianGameEditor Linux Development` builds successfully on the Ubuntu VM;
the latest incremental check reported `Target is up to date` and
`Result: Succeeded`.
- Headless project load through the Linux source-built editor succeeds in
`NullRHI` mode with `0 error(s)`.
- The old roadmap project-location block was stale and has been reset to the
Ubuntu Unreal VM plus Gitea workflow.
- The next coding phase should begin with exactly `0.2.A Land And Claiming`,
not scattered open items from later design sections.
## 0.1 Completion Check
All `0.1.A` through `0.1.R` roadmap checkboxes are complete. The remaining
All `0.1.A` through `0.1.S` roadmap checkboxes are complete. The remaining
unchecked roadmap items before `Version 0.2` are North Star and philosophy
statements, not incomplete `0.1` implementation tasks.
@@ -27,6 +52,9 @@ statements, not incomplete `0.1` implementation tasks.
moves into larger systems.
- The Windows build pipeline, package script, visual QA gate, and Linux server
target are established enough to keep milestone work shippable.
- The Ubuntu source-built Unreal lane now gives Codex a headless, local-disk
development path that is better suited to automated C++ work than the old
mapped-drive Windows workflow.
## Cleanup Findings
@@ -50,6 +78,11 @@ statements, not incomplete `0.1` implementation tasks.
audit boundary so tester tools do not become gameplay exploits.
- Verifier scripts are useful but numerous. 0.2 should add a grouped verifier
runner so milestone verification is one command with explicit categories.
- Some status docs predate the automated setup passes and should be treated as
historical unless their claims are repeated in the main roadmap or this
readiness review.
- `ripgrep` is not installed on the Ubuntu Unreal VM. This is not blocking, but
adding it would make future audits and code search faster.
## Low-Risk Cleanup Applied
@@ -58,6 +91,8 @@ statements, not incomplete `0.1` implementation tasks.
## 0.2 Engineering Priorities
- Start with `0.2.A Land And Claiming` and finish it before moving to farming,
domestication, storage, or economy work.
- Keep land claims, farming, storage, household tasks, and future economy state
server-authoritative from the first implementation pass.
- Add schema/version fields when introducing new persistent records.