[GOD13emad]

Scope and lineage

DRAFT / DO NOT MERGE / DO NOT TAG OR PUBLISH. Base is the exact PR #64 private source commit da2c81cacd2ffb72e198fcd3b56f9355fedb022a; new HEAD 20673417c3db93503fcb5c143eba9e6961bafa83, 36 source/metadata/test paths. Public Stable v1.5.4 and historic R535 v1.5.6 private rollback work remain immutable on their own original branches.

Problem and change

Existing private Windows clients use FileVersion 1.5.6.0; their strict latest <= current checks make same-version v1.5.6 ineffective for normal GitHub updater. Retain that monotonic check. This private candidate prepares strictly newer 1.5.7, pairs Linux protected Root/User v1.5.6 as an explicitly verified old baseline, preserves old approved 1.5.2/1.5.4 and 1.5.5-rc1 baselines, and keeps unknown/mixed/tampered versions fail-closed. Updated Windows GUI/Service/Inno metadata and the Linux package doc/digest pins. A separate original-repository-only GitHub-hosted Windows 2025 R846 job is provided for experimental v1.5.4→v1.5.7→v1.5.4 native install/rollback; historic R535 native job remains separately gated.

Current evidence — scope-limited

On connected owner Windows, self-contained v1.5.7 GUI and Service Publish generated version 1.5.7.0, Service console-selftest Exit 0, Windows Manifest regenerated with 681 entries and SHA256 B6D6B5F6A927D18BB0C25A843E1589F28D218E24F75327D39ACB85A509965CEE. Five relevant Windows audit tools PASS, including 122/122 windows_contract_audit checks; GitHub Actions YAML parsed with 17 jobs. On owner Linux, the earlier identical R845 isolated source patch built a deterministic v1.5.7 Linux archive (8,427,156 bytes, SHA256 16009B39037D77399B41BB89DE86B48F8E0841A2AA4A1BB16FDE481180FDD2CF), 4/4 fake-Root stage/apply/rollback/tamper/version tests PASS and 2 independent User transaction suites each 19+3+11 fixtures PASS. These are source/sandbox results, not native product acceptance. This R846 commit adds further branch-specific CI and package checks; their results must be read independently rather than inherited from R845.

Mandatory HOLD gates

• Exact-head new CI (Linux source/native root and Windows hosted native installer/rollback), fresh CodeQL and resulting artifact hashes.
• Test the actual private installed 1.5.6 → new candidate under legitimate interactive Windows UAC/Linux polkit and return-to-known-good; ensure user data/settings and a single uninstall registration.
• Positive intended-uplink YouTube/Google HTTPS/TLS and reliable Stop/Recovery without breaking third-party OpenConnect/Tailscale; MMZ physical uplink currently blocked by its VPN kill-switch policy.
• Independent human security/release approval of PR Security review needed: Direct Internet Method Linux update/rollback candidate (do not merge) #63, PR Draft: Direct Internet Method v1.5.6 — unified Windows/Linux in-place upgrade #64 and this delta. Do not self-approve as the developer/author.
• Only after all gates have evidence should a separate user-approved merged public release/tag and updater acceptance be contemplated.

Do not use successful source builds or a PR comment as evidence of installation or release.

---

R847 exact-head QA closeout (2026-10-31; STILL DRAFT / NO PUBLIC RELEASE)

Current PR head: 34ab45eca15b964f1dbccf31562d5f2070258d9f; original v1.5.4 public Stable and PR63/64 remain unmerged and unchanged. Original-repository CI: run 41197320454, 14 SUCCESS, 0 FAILURE, 3 expected SKIPPED (historic R535 Windows native, tag-only public-release job, and R782 branch-specific bootstrap). This includes real root/user Linux ephemeral stage/apply/rollback, synthetic Polkit rejection, watchdog and drift recovery, and Windows hosted disposable v1.5.4→private v1.5.7→v1.5.4 in-place/rollback acceptance. Windows hosted installer SHA256 4E5B9AE73A5905E766839A556DD41D4D83CB5FB547901C624EEF43137DE47941, native receipt SHA256 88B6C41E1AF71F53BAE5A58DEF7AEB3F2967B5C49769F6C745818DE5EA73ED00; GitHub artifact ID 13041750127. Linux exact private ZIP 8,427,156 bytes SHA256 F5506E1AE0092A20071B8D63E770ADBF6CDE3AA0701CC6A1B4F1E925C74CAFB6.

Independent fork scanner-only CodeQL: run 41197374646 actions/csharp/python 3/3 SUCCESS; GitHub CodeQL check "No new alerts in code changed by this pull request", with NO assertion about complete historic alert inventory or human APPROVE. Separate scanner fork Source Contracts failed intentionally at the R527 exact-original-repository privileged-root guard; original-repo CI above is the production source result.

Physical canaries (STAGING ONLY): Exact installer privately staged under Emad Windows user-local cache, not installed (active Service stays private 1.5.6.0), and exact Linux ZIP privately staged on MMZ Linux, not installed. Source-temp directories were cleaned; original user dirty trees and external OpenConnect/Tailscale state preserved. Independent human reviewer mohammadmohammadzadeh19960-code requested but not yet APPROVED. Remaining release gates: native owner-approved Windows UAC 1.5.6→1.5.7 install/rollback, MMZ native Polkit and direct physical uplink acceptance with third-party VPN managed legitimately, independent human security/release approvals for PR63/64/66, and a separately controlled public merge/tag/updater round-trip. DO NOT MERGE/TAG/PUBLISH based solely on these CI receipts. Canonical Windows PROJECT_BRAIN.md R847 and evidence/DIM_R847_V157_EXACT_CI_CODEQL_AND_CANARY_STAGING_20261031.json SHA256 C173CDEC612C793524225DA2DE8AE64FA4E8BE44EA756F17EE5A5BA1E8ED3ACC.

---

R848 exact-head original private 1.5.6 → new private 1.5.7 → old private 1.5.6 native hosted gate (2026-10-31)

Original CI: run #41200329723, commit 1ab328f899a4b9e350cd1e8063489a542b377c79: 15 SUCCESS, 0 FAILURE, 3 intentional SKIPPED (18 total). Additional one-time GitHub-hosted Windows 2025 windows-private-r848-v156-forward-one-time PASS; not a personal machine. Actual old original PR64 private v1.5.6 unsigned Installer fetched from exact CI run 41038434425, artifact 12969796101 (original setup SHA256 5BDE9DFFC3B866A7754DABEF9EDC853CFE519A08944163C39D812B2C8E9F3620) and new candidate v1.5.7 Installer verified SHA256 4E5B9AE73A5905E766839A556DD41D4D83CB5FB547901C624EEF43137DE47941. 66/66 native checks PASS: one AppId/Uninstaller, no HKCU duplicate, provider/custom configuration and unknown evidence retained, exact old private GUI+Service hashes restored on rollback, DNS/routes unchanged. Native receipt SHA256 DE979E151B7545FC1DFC535E1CE53B98D937154A7F9081F0649F35BC90C2EFA0; GitHub receipt artifact 13042127623, independently retrieved ZIP CRC PASS.

Independent exact-head CodeQL: run #41200395368, actions/C#/Python 3/3 SUCCESS; check: No new alerts in code changed by this pull request. This does not establish that all historical alerts are absent or that any independent human has approved. Historical fork Source Contracts intentionally fail their upstream-only R527 Root-authority guard.

Release/physical HOLD maintained: Emad Windows currently installed private 1.5.6.0 Service SHA256 237FDF518783194295072B6C1C14C744BB83E260005BDA4117DBB30FD8909130 differs from the old hosted v1.5.6 Service SHA256 32AA6E88F57097D669D395999ED23A8AA85C2A330C41C542D1CB44A744C031FB. Hosted PASS therefore cannot replace native owner-consented in-place/rollback on Emad Windows. MMZ Linux Root setup remains absent; owner native Polkit read-only request timed out with exit 124 and no privileges, vendor VPN vpn0 untouched; v1.5.7 ZIP only staged. Requested independent human PR63/PR64/PR66 reviews remain without APPROVE. No merger, tag, public release, or physical direct-network TLS acceptance. Canonical PROJECT_BRAIN.md R848 evidence evidence/DIM_R848_PRIVATE156_TO157_HOSTED_NATIVE_20261031.json SHA256 257AD01B5D046D2E1392168606666A726C4E09C9EB244D76DD71E6AFB99D71C8.

---

R849 physical native preinstall read-only gates (2026-10-31)

Owner Windows actual installed private 1.5.6.0: All 681/681 version-managed installed files (674 privileged, 7 user; 481,274,140 bytes) match the currently installed manifest byte-for-byte by SHA256; no missing/modified managed file. One owned HKLM AppId registration, zero owner HKCU duplicates, one matched Inno unins001.exe/.dat pair. Actual installed Service SHA256 237FDF518783194295072B6C1C14C744BB83E260005BDA4117DBB30FD8909130 and GUI SHA256 1EAD4A7212E0ADE871CCE9864088891A7A96E0E5D890A5D5A7E361AFDA4436D2; Service console-selftest exit 0 and background Service/Tailscale remain Running. Important: physical old Service SHA does not match historical hosted private-v1.5.6 old Service SHA 32AA6E88..., so the hosted R848 native 66-PASS result is not evidence of direct in-place native acceptance on this physically installed binary. v1.5.7 exact CI Installer still staged only, not executed.

Owner MMZ Linux: private v1.5.7 archive SHA256 F5506E1AE0092A20071B8D63E770ADBF6CDE3AA0701CC6A1B4F1E925C74CAFB6 checked ZIP CRC and 28/28 Manifest item hashes locally. No conflicting existing managed launcher/desktop files or Root/User receipt; GTK4/Adwaita available. Root-owned trusted bootstrap exists with owner 0:0, mode 0500; contents remain protected and NOT verified since interactive native Polkit permission not granted. Existing VPN default remains vpn0, untouched. NO privileged install, network switch, or physical HTTPS functional acceptance occurred.

This is a physical source-integrity readiness PASS only, not an installation, reviewer approval, merge or release. Canonical single Brain evidence evidence/DIM_R849_PHYSICAL_PREINSTALL_WINDOWS_MMZ_READONLY_20261031.json SHA256 734D018A9EC7C9DDED82217F2C86752C6F9348A8EE09F030F7F5A82F776E3039. Remaining gates: legitimate native UAC/Polkit installations and rollback, positive direct-uplink HTTPS/TLS with third-party VPN safety, and independent human security/release approval PR63/64/66. No new public release.

---

R850 — actual installed-file SHA-256 acceptance in both hosted upgrade routes (2026-10-31)

Current private PR66 head: 7d587587349d011e6aa4df0c1b339b2d16813dfd. Original GitHub CI #41204189407: 15 SUCCESS, 0 FAILURE, 3 intentional SKIPPED across 18 jobs. The new read-only, fail-closed tests/r850_windows_privileged_manifest_attestation.ps1 validates all 674/674 protected files, their exact size and SHA-256, against the newly built actually installed manifest.json during both Windows 2025 GitHub-hosted native paths: (1) public v1.5.4→private v1.5.7→v1.5.4, R846 receipt SHA256 177DC44C262697E2BD588E63572A8796471281F437329BBA5BCAB89DB0AD3CA7; (2) original pinned private v1.5.6→v1.5.7→v1.5.6, R848 receipt SHA256 D10C889564B28BCEE931F466CF16106430FDE25EC5C671F32EBDF1786689C1B3. Both are PASS and preserve single AppId/Uninstaller, user settings and known+unknown data, with network routes and DNS unchanged. Verified unsigned private setup SHA256 stays 4E5B9AE73A5905E766839A556DD41D4D83CB5FB547901C624EEF43137DE47941.

Independent exact-head CodeQL #41204225192: Python, C# and Actions all SUCCESS; check output: No new alerts in code changed by this pull request. Not an assertion of no historical alerts or a human approval. Fork Source Contracts deliberately reject privileged Root CI via the original-repository-only R527 guard.

Physical Windows read-only preflight: Existing private v1.5.6.0 681/681 managed file SHA verified; the same R850 script confirms 674/674 protected SHA, with local tamper, traversal, duplicate, and manifest-digest negative tests rejecting bad inputs. Actual installed Start-Direct.ps1 is byte-identical to current PR64/PR66 source (SHA256 E03AA828A89F8BEA34051C58EEE250685F440CE65B923C4B2CD6EAE8ABE3FE95). Do not confuse checked-in, precompiled Windows manifest hashes with the freshly regenerated hosted build manifest; only the on-disk installed 674/674 test closes actual package-integrity scope. A local hash-only baseline of 19 user data files across 3 scopes was recorded; no data contents copied or published. Original physical private 1.5.6 Service SHA remains 237FDF518783194295072B6C1C14C744BB83E260005BDA4117DBB30FD8909130, different from historical hosted private v1.5.6; physical UAC 1.5.7 upgrade remains UNTESTED.

Release HOLD: No real user-machine in-place upgrade or MMZ Linux Polkit approval; VPN vpn0 must not be changed without legitimate owner-directed acceptance; independent security/release reviewers of PR #63/#64/#66 have not submitted APPROVE. Original public Stable remains v1.5.4; do not merge/tag/publish on CI alone. Canonical Windows PROJECT_BRAIN.md R850 source and evidence evidence/DIM_R850_EXACT_NATIVE_PRIVILEGED_MANIFEST_CI_20261031.json SHA256 892DBC00032C84CE35D5DD034F7BF141B96824517DC1AB6F069CC5306A60B32A; local data baseline evidence/DIM_R850_PHYSICAL_MUTABLE_DATA_PREUPGRADE_BASELINE_20261031.json SHA256 6394F8B02FDA4A8187F355FFF3FAEF82B38D3C66EF4BF2E9FD48BDF98319B85A.

---

R851 critical native rollback-provenance HOLD — actual physical private v1.5.6 is not the CI old v1.5.6

The 2026-10-24 actual Emad Windows native R809 installation receipt validation-sandboxes/R809_PRIVATE_WINDOWS_CANARY/R809_PHYSICAL_RESULT.json, SHA256 A3EF6AD2439872BA628BA6B3DA00953422A3655D82325150A79EC977BA408552, proves that the physically installed private v1.5.6.0 originated from Setup SHA256 13E7B8ACB0392D0CB5C2CB64CFCBB4FC4B5F0E69B10E391803BF899CECBF16DA (154,320,361 bytes). Current physical Service SHA256 237FDF518783194295072B6C1C14C744BB83E260005BDA4117DBB30FD8909130 and complete local installed manifest 681/681 PASS; original R809 setup's documented exact keeper and intentionally retired duplicate are no longer present. Searches in bounded relevant Windows/Linux source/caches did not recover that exact setup. The original repository currently lists 69 Actions artifacts without an R809-named exact physical Installer; this is not a global proof no backup exists.

The available different old private 1.5.6 CI setup SHA256 5BDE9DFFC3B866A7754DABEF9EDC853CFE519A08944163C39D812B2C8E9F3620 and CI's R848 66-PASS rollback are valid only for that alternative old build; they do not prove restoration of the actually installed R809 Build. Official public v1.5.4 setup SHA256 FFB9A2AE19C2E89338EE12EE8DA133F5A16DBF4DCF961678C33D77D0C3843133 is verified via public v1.5.4 release and the v1.5.4 hosted rollback path PASS, but it is an older public downgrade, not equivalent to same-private-build rollback and must not be silently substituted.

Safety decision: Physical Windows upgrade to private v1.5.7 stays FAIL-CLOSED pending a cryptographically verified copy of the exact R809 original Installer, or an explicit owner decision accepting the public-v1.5.4 downgrade as fallback, plus native owner UAC and the other outstanding reviews. No UAC installer was launched, the current Service/Tailscale/VPN remained unchanged, no product was merged/tagged/released. PR #63/#64/#66 still require independent human review; MMZ Linux native Polkit and direct uplink HTTPS/TLS positive acceptance remain separate blockers. Upstream canonical evidence evidence/DIM_R851_PHYSICAL_EXACT_V156_ROLLBACK_ASSET_RECOVERY_20261031.json SHA256 E908B3FB82CA89B293A083DB588D36799BAE1C278E48C485E6A8788D5F75FE83. Existing CI #41204189407 15/18 PASS and CodeQL #41204225192 3/3 PASS are retained in their original scope.