T6B.1 Independent Audit — Preflight¶
Audit date: 2026-08-17. Mode: server. Workspace: /home/scola/odoo.
Application identity verified independently:
| Side | Application commit | Application tree | Branch state |
|---|---|---|---|
| FE | 2f716594ee769fe3cd8338ae5bcebb3f2e470d46 |
8606e7bbe49db194c7bdc8f5ef2cde67674ef125bbd468ee5518285f17a80a85 |
develop clean; tip 905eafa9… is docs-only |
| BE | e78d06d1ff64477fb73f2017e85cab034b56f188 |
6d13752ccbe11c63044b96a34420975f86a104213b700c8b986ff0367802de7f |
main clean and aligned with origin |
environment_isolation_check.py --live passed. No Golden canonical, GBN, demo, or production mutation was performed. The served FE :5181/version.json reports application commit 2f716594…; the disposable backend overlay was bound with an explicit database filter. The initial validator 404 caused by an ambiguous database selector was corrected by restarting the overlay with an exact -d and --db-filter; the E1.2 validator then passed with --allow-docs-tip.
The historical T6B.1 W01/W02/W05 evidence was not sufficient: it recorded BE d23c2c6… and FE 4c9d76b0…, not the claimed T6B.1 application. I therefore reran all three suites on a fresh disposable clone and retained the current-tip evidence under execution/T6B-evidence/.
The clone inherited Golden's database UUID because it was created from a template. Database name, exact runtime endpoint, and source tree were recorded; the UUID collision remains evidence-lineage hygiene debt, not a production mutation.