modificacion-segura-taimbox

Safely modifying shared types requires scoping edits to known files, exploring usages in src/ and supabase/ directories, and consulting repository documentation like DOCUMENTACION.md before committing changes to minimize regressions.

The safest way to update AppContext and permissions is through guided, scoped changes rather than sweeping edits, ensuring you check relevant docs sections like docs/08 and docs/09 to validate the impact on Realtime and RLS policies.

You should always consult documentation like docs/08, docs/09, and DOCUMENTACION.md before changing capacity or date utilities, because these are shared contracts where unvalidated modifications can easily introduce frontend or backend regressions.

To check the impact of modifying Supabase RLS policies and Realtime contracts, use a Task explore approach to locate usages across src/, supabase/, and docs/ without loading the entire tree, then apply checklist-based governance before committing.

No, you should not make sweeping exploratory edits when the impact is uncertain. Instead, use a Task explore approach to safely locate usages in src/, supabase/, and docs/ first, applying changes only after confirming the impact.

The main limitation of making broad changes to shared contracts is the high risk of regressions. Changes touching shared types, AppContext, or RLS require documentation-driven governance and checklist validation to ensure alignment and prevent issues.