@@ -82,6 +82,24 @@ Fabric and Quilt startup were confirmed by the maintainer on 20 October 2026; lo
 
 The sole product version is `launcherVersion` in [`gradle.properties`](gradle.properties), now `0.6.0`. Changing it to a higher **plain `X.Y.Z` version** (e.g. `0.6.0` → `0.7.0`) and pushing to `main` automatically publishes a normal GitHub Release `vX.Y.Z` after all Gradle/Python tests and Windows/Linux/macOS packaging succeed. **No GitHub pre-releases are published.** Ordinary code changes do not issue new releases. Matching plain-version manual tags remain supported. Each published release is eligible for the stable launcher updater; remaining gameplay and distribution acceptance limitations are recorded in the roadmap. See [publishing instructions](docs/UPDATING.md).
 
+## v0.7 — NeoForge (in development, not yet released)
+
+A processor-backed NeoForge installer adapter is now connected to the existing
+instance and launch pipeline. The desktop can discover compatible NeoForge Maven
+versions and save them in instance metadata. Before game launch, the common
+coordinator first prepares the official Vanilla client and Java runtime, then
+downloads the official SHA-256-verified NeoForge installer, stages processor
+dependencies and generates the required client libraries in a separate working
+directory. A generated runtime profile is merged back into the shared launch
+pipeline. Local mod inventory can recognize the first NeoForge mods.toml record,
+and the existing Modrinth loader filter follows the selected NeoForge instance.
+
+**Not a certified working NeoForge release:** official installer smoke, real
+Minecraft boot, cancellation/recovery checks, and native platform acceptance
+must pass before marking v0.7 complete. Do not use this stage with your only
+world save or assume filesystem staging is a security sandbox. See
+[the v0.7 acceptance checklist](docs/TESTING_V0.7.md).
+
 ## v0.6 — Browse and install popular Modrinth mods (development)
 
 Open **Instances → Mods → Discover on Modrinth** for a Fabric instance. The discover
 
@@ -523,16 +523,17 @@ Goal: add a second major loader and prove the loader architecture is genuinely r
 
 - [ ] 🚧 IN PROGRESS — Discover official NeoForge Maven versions; processor installation and actual launch remain unimplemented.
 - [ ] 🚧 IN PROGRESS — Inspect NeoForge installer V2 metadata and list client processors in read-only preflight; execution/generated artifacts remain open.
-- [ ] 🚧 IN PROGRESS — Fetch the official NeoForge installer SHA-256 sidecar, download the checksum-verified JAR to a dedicated cache and run read-only preflight. Implementation added; automated/hosted and live Maven verification pending. See [v0.7 tests](TESTING_V0.7.md).
-- [ ] Resolve required libraries.
-- [ ] Integrate generated/processed artifacts safely.
-- [ ] Store NeoForge loader state in instance metadata.
-- [ ] Launch through common launch pipeline.
+- [ ] 🚧 IN PROGRESS — Fetch official NeoForge installer and SHA-256, verify the cache and inspect V2 client steps. Synthetic tests pass; live Maven/processor acceptance required before completion. See [v0.7 tests](TESTING_V0.7.md).
+- [ ] 🚧 IN PROGRESS — Execute NeoForge V2 processors in a child Java process using a temporary workspace, check declared output files, stage generated libraries and merge runtime version metadata. Synthetic fixtures integrated; official installation/game startup and failure-recovery matrix are not yet accepted.
+- [ ] 🚧 IN PROGRESS — Download processor libraries through verified shared download infrastructure and resolve generated output paths. Official Maven dependency matrix not yet accepted.
+- [ ] 🚧 IN PROGRESS — Stage generated/processed artifacts with collision checks; interrupted/concurrent processor recovery and real versions still require verification.
+- [x] Store NeoForge loader id/version using the existing instance metadata schema and expose the compatible-version selector in desktop creation/editing.
+- [ ] 🚧 IN PROGRESS — Wire NeoForge processing after base client/Java preparation into common launch pipeline. Actual NeoForge game startup remains to be demonstrated.
 
 ## Compatibility
 
-- [ ] Filter Modrinth content for NeoForge.
-- [ ] Parse relevant NeoForge mod metadata in local manager.
+- [ ] 🚧 IN PROGRESS — Generic Modrinth adapter already filters by the instance loader; NeoForge profile/UI integration added. Live install acceptance pending.
+- [ ] 🚧 IN PROGRESS — Identify NeoForge mods from META-INF/neoforge.mods.toml; richer TOML dependency/version semantics remain open.
 - [ ] Detect common incompatible loader combinations.
 
 ## v0.7 quality gate
 
@@ -3,24 +3,24 @@
 ## Stage 1: official installer acquisition and read-only preflight
 
 - [ ] Official NeoForge Maven metadata and compatible-version mapping verified against currently published releases.
-- [ ] SHA-256 sidecar fetch, checksum parsing, verified JAR download and cache reuse validated in Gradle tests.
+- [x] Synthetic SHA-256 sidecar fetch, checksum parsing, verified JAR download and cache reuse validated in Gradle core tests.
 - [ ] Tampered archive, missing/bad checksum, unsupported installer layout and wrong Minecraft target rejected.
 - [ ] Windows/Linux/macOS cache paths and interrupted downloads verified.
 - [ ] Real official NeoForge installer checked in preflight (read-only, no processor execution).
 
 ## Stage 2: processors, libraries and generated outputs
 
-- [ ] Resolve installer library coordinates and metadata-defined trusted repositories, with file integrity checks.
+- [ ] 🚧 Processor library coordinate resolution and allow-listed Maven downloads implemented; official source and artifact matrix acceptance open.
 - [ ] Expand client-side installer data placeholders in a confined staging directory; reject unsafe paths.
-- [ ] Execute required processors using managed Java with bounded resource/time limits and captured diagnostics.
+- [ ] 🚧 Execute client processors in a child JVM selected from the resolved runtime, bounded by a time limit; cancellation/log persistence and official process acceptance open.
 - [ ] Check declared outputs, reject incomplete/corrupt generated artifacts and publish only on success.
-- [ ] Merge generated NeoForge version metadata with Mojang version for common launch pipeline.
+- [ ] 🚧 Overlay generated NeoForge metadata on the base client and route through common launch pipeline; actual Minecraft bootstrap/launch acceptance open.
 - [ ] Reuse the shared instance activity lock and preserve every existing world/mod when preparation fails.
-- [ ] Add deterministic successful/error/rollback MockEngine and process fixtures.
+- [ ] 🚧 Added deterministic successful Java processor and mismatch fixtures; rollback, partial-publish and cancellation cases open.
 
 ## Stage 3: desktop and actual-game acceptance
 
-- [ ] Offer NeoForge only after its end-to-end installer/launch path is operational.
+- [ ] 🚧 NeoForge selector is visible; do not label this path production-ready until full official smoke and gameplay pass.
 - [ ] Select compatible versions in instance creation/editing, without breaking Vanilla/Fabric/Quilt.
 - [ ] Filter Modrinth by NeoForge, and recognize NeoForge mod metadata in local manager.
 - [ ] Test real Minecraft startup using NeoForge and at least one compatible client mod.
@@ -31,3 +31,10 @@
 It never executes downloaded installers and never exposes an unusable NeoForge
 selection in the UI. GitHub CI and real-world acceptance must be recorded before
 checking their respective boxes. Stage 2 and Stage 3 are not implemented.
+
+## Hosted verification record
+
+- The core has both synthetic processor tests and an opt-in official NeoForge 21.1.213 / Minecraft 1.21.1 Maven integration test.
+- GitHub Actions runs the real integration test on main before creating native packages. A passing test demonstrates installation, not a real graphical Minecraft startup.
+- Processor code is downloaded executable third-party Java; the staged filesystem provides data isolation, **not an operating-system sandbox**.
+- No stable v0.7 release is authorized solely by passing unit tests or package builds. Real game launch, compatible mods and supported platform matrix must still be accepted.
@@ -8,6 +8,46 @@ Every code/build/documentation/CI task must add an entry according to `AGENTS.md
 
 ---
 
+## 2026-10-21 — NeoForge V2 processor integration and hosted acceptance gate
+
+**Milestone:** v0.7 — NeoForge  
+**Author/Agent:** GPT-6  
+**Status:** Partial — implementation and CI submitted; release acceptance pending
+
+### Completed
+- Added a processor-driven NeoForge installer staging service, shared dependency downloader integration, verification of declared processor outputs, SHA-1-tracked generated runtime libraries and profile merge.
+- Added a distinct prepared-loader interface. The standard coordinator obtains base client and Java first for processor-backed loaders; Fabric/Quilt retain the original metadata-only path.
+- Exposed NeoForge version selection in instance settings, instance creation and advanced modded-game setup, plus home mode switch/Mods workspace reuse.
+- Added simple NeoForge mods.toml ID/name/version extraction to local mod inventory. Full TOML dependency resolution remains future work.
+- Added synthetic Java processor fixture and negative checksum/target tests. Added opt-in official NeoForge Maven integration test, run as a CI gate for main before platform packaging. Actual Minecraft client startup is not tested by this fixture.
+- Left launcherVersion at 0.6.0 pending real NeoForge installer and gameplay acceptance; **did not publish a GitHub Release**.
+
+### Changed files
+- `launcher-core/.../loader/NeoForgeInstallerEngine.kt`, `ModLoader.kt`, `InstallerLoaderDiscovery.kt` — processor-driven loader adapter.
+- `launcher-core/.../launch/MinecraftLaunchCoordinator.kt` and desktop `Main.kt` — correct runtime/preparation order and dependency injection.
+- Desktop game setup, instance settings/workspace, home navigation and local-mod parser — NeoForge selection and metadata.
+- Core NeoForge smoke/fixture tests and `.github/workflows/build.yml` — synthetic and official Maven acceptance coverage.
+- `docs/ROADMAP.md`, `docs/TESTING_V0.7.md`, `README.md`, `docs/WORKLOG.md` — status and release gates.
+
+### Verification
+- `./gradlew test` — synthetic suite submitted to GitHub CI; latest run result must be checked.
+- `./gradlew build` — submitted to hosted CI; this entry does not assume final success.
+- Official NeoForge 21.1.213 V2 processor smoke — submitted as a hosted main-branch gate; must be checked.
+- Real Minecraft startup/native user acceptance — NOT RUN.
+- GitHub stable release — NOT PUBLISHED; do not call this a completed milestone yet.
+
+### Roadmap updates
+- `[x] v0.7 / Persist loader selection in instance metadata`
+- `[ ] v0.7 / Processor installation, runtime launch, Modrinth and platform quality gates` — integration added but final acceptance missing.
+
+### Follow-ups / known issues
+- The external Java process is constrained to a staging working directory but not sandboxed by the operating system. Do not claim that it cannot write outside that directory.
+- The live smoke test verifies processor artifacts, not that Minecraft opens a window or runs a NeoForge mod.
+- Do not bump the single-source version to 0.7.0 until all release checks pass.
+
+---
+
+
 ## 2026-10-21 — Begin v0.7 NeoForge installer acquisition and verification
 
 **Milestone:** v0.7 — NeoForge