forge-neoforge-sft-v2.0.1 (full)

Supervised fine-tuning corpus for Forge 1.20.1 -> NeoForge 1.21.1 mod migration. Every task is grounded in exact pinned upstream snapshots (branch + commit sha per record): the model is never asked about invisible code - all context files are serialized inline (inline-fenced-v2) and their presence is enforced by a blocking gate (G-CTX).

This is the full release of v2: 3615 records / 15 families / 447 repositories, expanded from v2 (1070) with pin-to-pin snapshot mining over 181 additional repository pairs, a widened GitHub issues/PR layer, and three new families (porting_diff_review, project_porting L2, multiturn_repair) plus test_generation.

Splits (repo-disjoint)

split	records	repos
train	3082	381
validation	201	27
eval	333	39

Repositories are disjoint across splits (no leakage). eval is slightly above the 300 target because split purity is preserved per repository.

Families

family	total	train / val / eval	description
api_version_lookup	150	138 / 6 / 6	symbol-level Forge->NeoForge replacement lookups validated literally in the repository own pre/post snapshots
code_generation	177	146 / 9 / 22	implement a new class from scratch consistent with attached conventions; the answer is the real upstream-added file
config_and_resources	416	343 / 24 / 49	lang/pack.mcmeta/toml/recipe/tag updates between pins, real diff notes only
context_verification	19	14 / 2 / 3	context adequacy checks (v2 family, extended)
grounded_qa	496	423 / 31 / 42	code comprehension Q&A grounded in pinned files (events, registrations, config, responsibilities)
insufficient_context	293	251 / 17 / 25	symmetric negative cases: missing internal dependencies, version-mismatch claims, unconfirmed third-party APIs - the correct behavior is to refuse and request exactly what is needed
issue_bugfix	151	127 / 3 / 21	real upstream bugfixes: prompt carries the exact pre-fix parent revision; the answer is the real fix commit result
issue_context_check	217	184 / 6 / 27	real issue triage: version-conflict reports and insufficient bug reports (no logs) -> request specifics, do not act
multiturn_repair	9	5 / 0 / 4	(new in v2.0.1) real fix -> follow-up commit sequences as 4-message dialogues
porting	826	708 / 55 / 63	L1 file migration: migrate an exact Forge 1.20.1 snapshot of one file to NeoForge 1.21.1; the answer is the upstream 1.21.1 state of that file (pinned sha256)
porting_diff_review	335	290 / 19 / 26	L1 (new in v2.0.1): review a proposed single-file migration diff that IS the real upstream change; verify hunks and state what a full port additionally requires
pr_review	136	113 / 5 / 18	file-by-file review of real merged PR diffs with verifiable observations
project_porting	84	72 / 4 / 8	L2 (new in v2.0.1): subsystem-level migration; multiple dependent files planned, migrated and cross-referenced
review	262	225 / 19 / 18	L1 review-and-verify: analyze real 1.20.1 code / real migration artifacts, grounded quotes only
test_generation	45	43 / 1 / 1	game-test skeletons grounded in real registrations + NeoForge 1.21.1 gametest API surface; honest static_checked status

Methodology (honesty core)

• Pins. Each record carries pins (branch + commit sha for Forge 1.20.1 and NeoForge 1.21.1) and upstream_truth (paths + sha256 of the exact source/target snapshots it was derived from).
• No fabricated builds. Statuses: static_checked (static verification against pinned snapshots). validation.method states exactly what was verified. No compile/run was performed in the producing environment for this release.
• Gates. G1 unique ids; G-CTX (every context file byte-present in a user turn - blocking); G3 context sha256; G5 secret scan; G9 base-v2 answers byte-identical (1070/1070); G10 upstream re-fetch sample (9/9 sha256 matches); exact-duplicate drop; repo-level split disjointness.
• Loader gate. Full-tree git grep at BOTH pins for all 190 candidate repos: 181 pass (120 of them multiloader with NeoForge subprojects; fabric/quilt subtrees excluded), 9 rejected as loader violations (fabric-only or forge-less targets).
• Multiloader policy (v2 precedent): repos like Serilum's Common/Forge/NeoForge trees are valid material; fabric/quilt subtrees are excluded from every selection.

Record schema (per record)

task_id, task_family, task_type, source_target, prompt, context_files[] (path, content, sha256, source_url), messages (self-contained inline-fenced-v2; for multiturn_repair a 4-message dialogue), expected_changes, evidence[] (claim, source_url, source_revision), build_environment, validation (honest status), repo, pins, split, serialization, upstream_truth (path/sha256/revision).

Limitations

• compile_verified statuses are absent: NeoForm decompile requires >=8 GB RAM (Vineflower -Xmx4G), unavailable in the producing environment; nothing was fabricated to hide this.
• multiturn_repair is small (9): real fix -> follow-up commit sequences with fetchable exact pre-states are rare in the pool; the family is seeded and the mining method is documented.
• test_generation records are grounded skeletons (API surface verified against NeoForge 1.21.1 tree), not compiled tests.
• Issue/PR texts are used as real user reports; issue-layer records are limited to repos with fetchable commit objects.

Source & provenance

• Base: ComerX/forge-neoforge-sft-v2 (1070 records, byte-identical answers).
• Expansion: 181 new repository pairs mined pin-to-pin (shallow git snapshots, no API quota), issues/PRs via GitHub search for 107 repos (12 from v2 + 95 new).
• Upstream licenses: per-repository (MIT/Apache-2.0/LGPL-2.1/BSD and similar); pins allow byte-exact verification of every derived answer.

Citation

@dataset{comerx_sft_v201_2026,
  title  = {forge-neoforge-sft-v2.0.1 (full): Forge 1.20.1 -> NeoForge 1.21.1 SFT corpus},
  author = {ComerX},
  year   = {2026},
  url    = {https://huggingface.co/datasets/ComerX/forge-neoforge-sft-v2.0.1}
}