Lewati ke isi

T0-E1 independent preflight

Mode: server, read-only application audit. Workspace: /home/scola/odoo.

Independent baseline

Item Observed
FE branch / HEAD / origin develop / 7bf75bbe59a978ef276c2063266e8d0c0c405d73 / same
FE application certification faefe33cc44bb45f32dabeea5831b6c6b5cd7583
BE branch / HEAD / origin main / 039e95b587cb40ca7db12fdfeb2320deeff2c8cc / same
BE application certification 508400c7effa272f49e3c111b4a2f6f6360b5cd1 (configuration affecting native reset); security application fix is ancestor f0272c3
Working tree FE has implementation evidence files plus pre-existing recon XLSX; BE clean
Served FE 127.0.0.1:5181 and :5174, version.json = faefe33cc44b45f32dabeea5831b6c6b5cd7583, build fe-build-faefe33cc44b-mslesrv8
Served BE 127.0.0.1:8090, source identity = 039e95b587cb40ca7db12fdfeb2320deeff2c8cc via environment identity
Golden DB scola_golden, fixture gt-core-b1.1, UUID 2bf5fd27-9390-11f1-9617-28e8d4be73f5
Installed Scola modules Core 13 plus scola_hr, scola_leadership_hub, attendance, identity, portal, timetable, news, observability and platform support; scola_hr is installed while entitlement is false
Entitlement profile auth_signup.reset_password=False; optional flags default/false; mixed install remains
Current hashes FE application tree 0483accf2d113546e87f90d6da235cf66514579b8419525ce5b38af9788f7bd8; BE application tree dbb9c29b4fe8d73f290826afa89269cbd1354326c70d305072715ec62410901d; served dist checksum b1ab296aac58a2da4d0d70c56e5dd215144b2c9dbf43b86081f34264133ec0d8
Route snapshot 1,715 extracted; 1,678 protected; 34 public; 3 internal; 0 unknown/ambiguous; registry 429; checksum 90129c47e18581761629ceac4396e78b9f16c686e8c07801ea34e8f981e4e739

Diff classification

FE faefe33..7bf75 contains only documentation/evidence additions. BE 508400c..039e95 contains only scripts/golden evidence/harness changes; the application tree is unchanged. The application commits are therefore exact ancestors for the files they certify. This does not establish runtime identity: no T0-E1-runtime-manifest.json exists, and the default E1 validator fails with FileNotFoundError before validating any identity.

Independent preflight result

The implementation labels were ignored. The served FE/BE pair is identifiable, but the E1 evidence chain is incomplete because the claimed runtime manifest is absent and the validator does not query the served BE identity or validate evidence-case completeness.