Asignado a: Juan Miguel Revisado por: Luis Pallares Cliente: TLC (Eduardo Galvan) Estimado: ~10 horas
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Starlark Migration</title> | |
| <style> | |
| * { margin: 0; padding: 0; box-sizing: border-box; } | |
| body { | |
| background: #0a0a0a; |
| #!/usr/bin/env python3 | |
| """ | |
| Profile the rename-validate pipeline to find which analyzer step is slow. | |
| Usage: | |
| cd src/backend && python ../../scripts/profile_rename_validate.py \ | |
| --org-cuid cmf7c8pup000o0faz59yxbc62 \ | |
| --resource-type model \ | |
| --field-key associatedcrid |
Agenda para alinearnos antes de la asamblea del 28.
- Leer el orden del día juntos. ¿Incluye admin definitivo, comisión de recibo, peritaje?
- Si faltan puntos: decidir si los proponemos en la asamblea o si activamos plan B (convocatoria propia con 45 firmas)
When Workflow A calls Workflow B via a run_workflow node, both workflows must share the same entity_name_type (finding type). This is validated at save time and at every WorkflowManager instantiation. However, entity_name_type lives on the mutable Workflow record — not in the versioned snapshot — so it can be changed at any time via PUT /workflows/<cuid>, breaking running executions.
Two separate API paths update a workflow:
Ticket: SC-14561 — 25 - Final SA2 verification: zero legacy patterns + docs update
77 SA1 legacy patterns remain across src/backend/ (76) and tests/ (1). The CI gate already blocks new patterns on every PR. We need to reach zero to close the SA2 migration epic.
Deleting an Artifact Field (finding custom field) skips dependency checking entirely. A user can delete a field that is actively referenced in workflow nodes, breaking running executions. Model Fields have full dependency protection; Artifact Fields have none.
| Metric | Count |
|---|
| Category | Current State | Projected State | Impact |
|---|---|---|---|
| Core Service Coverage | 22.4% | >95% | Critical: Fixes blind spots in Cost/Price engine. |
| Isolation Coverage | ~0% | 100% | Critical: Proves cross-tenant data leaks are impossible. |
| Soft-Delete Coverage | <10% | 100% | High: Ensures deleted data is hidden from all UIs. |
| Action Redundancy | High | Low | Medium: Leaner, faster, more maintainable test suite. |