TeXTech 3.0 RC 1

[ImgoodWK]

Summary

This pull request relaunches the project as TeXTech-GTNH and prepares the immutable v3.0.0-rc.1 release candidate.

It keeps the five signed implementation commits intact and covers:

• the TeXTech 3.0 mod feature set, integrations, manuals, language data, and compatibility contracts;
• the WebAE 3.0 console, production bundle, diagnostics, tests, and operator guidance;
• reproducible Java/WebAE/AstrBot/documentation CI, CodeQL, dependency review, tagged assets, checksums, and attestations;
• bilingual README/documentation portals, verified project history, branding, community files, Wiki navigation, and release notes;
• transparent provenance monitoring using TT-GTNH-PROVENANCE-2025-04-29-E04BDE7, without hidden telemetry or prompt injection.

Release and compatibility

• Candidate tag: v3.0.0-rc.1
• Minecraft: 1.7.10
• Forge: 10.13.4.1614
• Target line: GTNH 2.9.0-beta-2 and compatible 2.9.x builds
• v2.0.0 remains the Latest stable release during the RC observation period.
• Card Battle remains a separate project; this repository contains only its documented bridge boundary.

Local verification

• All five commits have valid local SSH signatures and appear Verified on GitHub.
• git diff --check
• Tracked-file secret scan
• JSON, YAML/CFF, Markdown/link, and generated WebAE validation
• Documentation consistency check: 0 warnings
• Public provenance monitor policy tests: 2 passed
• AstrBot: 153 tests passed
• WebAE: 31 test files / 130 tests passed
• TypeScript check passed
• Production WebAE build reproduced the committed assets
• Gradle spotlessCheck test build passed
• Java/JUnit aggregate: 356 tests, 0 failures, 0 errors, 3 skipped
• Main JAR logo/resource and WebAE ZIP layout verified

Merge policy

Please use a GitHub merge commit so the five signed commits remain intact. Do not squash, rebase, force-push, or move the eventual RC tag.

After all checks pass, the merge commit will be verified, the final master ruleset will be created using the observed check names, and the signed annotated RC tag will be built again from a clean worktree before publication.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.