update docs

AGENTS.md

@@ -1,6 +1,6 @@
 # FDS/OS implementation scope
 
-Read `docs/master-plan.md` and `docs/build-host.md` before changing the build.
+Read `docs/developer/master-plan.md` and `docs/developer/build-host.md` before changing the build.
 The user has explicitly authorized implementation through M12. Proceed through
 the remaining milestones in order, keeping the repository buildable and recording
 actual acceptance evidence. Defer tests that require the physical Raspberry Pi
@@ -34,10 +34,12 @@ claim Pi boot or physical power-cycle recovery is verified.
 # Workstation software and emulator follow-up
 
 Read `docs/workstation.md`, `docs/software-format.md` and
-`docs/workstation-tooling-plan.md` for this extension. Software builds and new
+`docs/developer/workstation-tooling-plan.md` for this extension. Software builds and new
 PROGRAM cartridge creation run on generic Linux workstations. The public native
 Clap tools are `fds-cartridge` and `fds-emulator`. Software images have GPT
-metadata partition 1 plus m EROFS payload partitions holding xz tarballs. Keep
+metadata partition 1 plus m EROFS payload partitions containing installed Void
+package trees. Build source templates with xbps-src on the workstation; do not
+create new xz software bundles or extract programs at guest launch. Keep
 legacy reading and base Dasung integration. Do not mutate the frozen 0.1.0 release
 or treat its historical acceptance as evidence for changed sources. Validate
 with `make workstation-test` and `make emulator-test` plus relevant guest checks.