Historial change-history panel on edit-bearing routes (prácticas first)

Elazar fleet directive via Mars relay: every route holding trackable data needs a 'Historial' change-history panel. Reference = Mars live /practicas/[id] Historial (audited-table + archive-trigger + Historial-render template; pull shape from mars-coder/audit, do NOT re-derive). VENUS PRIORITY: venus now allows práctica edits (editarPractica) with no audit-visible history = the exact gap. Start prácticas/[id], then any other edit-bearing route. SCOPE FIRST (read-only): venus already sets archive-trigger context (setArchiveContext) on practicas + practicaParticipations writes -> archive rows likely exist; if a render panel can be built on existing archive/appEvents data = render-only (solo). If it needs a NEW audit-history table or archive trigger (DDL) = Class-A tripwire to team/db-venus, do NOT self-approve. Economize tokens: mirror Mars, don't reinvent.