Native Chromium Rebuild — Active Development
Release readiness
A progress record governed by gates, not optimism.
TAHAI Browser has completed source-side work through NATIVE038. Six passes, runtime proof, open gates, packaging, signing, Store preparation, and final verification remain.
Readiness summary
Source-side foundation is advanced. Release evidence is not complete.
This is not a percent-complete release promise. The meter shows completed named passes in the current NATIVE001–044 plan, while open gates and blocked runtime receipts remain decisive.
38 named passes complete6 named passes remain
Source contractsThrough NATIVE038Plan validation, self-tests, local-data inventory, package-integrity checks, and manifest coverage pass.
Runtime proofBlockedFull pinned Chromium checkout and final headed Windows receipts remain unavailable.
Security gate G5OpenNATIVE039–041 must establish protocol governance, support diagnostics, SBOM, provenance, and reproducibility evidence.
Windows packagingNot startedNATIVE042 follows G5 and covers installer, upgrade, uninstall, integration, retention choices, and signed-artifact lane.
Store / MSIXNot startedNATIVE043 requires native package identity and may not reuse Electron packaging code.
Release candidateBlockedNATIVE044 closes safe migration, installed smoke, input proof, compatibility review, known issues, and final package decision.
Public status: no native download, production-ready, enterprise-ready, signed-release, Store-ready, RC, or GA claim is made.