actualizar-documentacion-taimbox

Documentation drift happens when code changes alter features or Edge Functions without updating the corresponding docs/* files or the DOCUMENTACION.md index. This causes reader confusion as modular documentation no longer reflects the actual product behavior.

You should update modular markdown documentation when releasing or closing a product feature, touching Edge Functions or contract references, or when documentation is explicitly requested. Updates are enforced only for user-visible changes to avoid unnecessary noise.

You prevent documentation drift in a modular markdown workflow by enforcing synchronization between docs/* files and the DOCUMENTACION.md index. This ensures modular documentation accurately reflects code changes without generating unnecessary noise for non-user-visible updates.

No, documentation alignment does not trigger on every code change. It enforces updates to docs/* and DOCUMENTACION.md only when there is a user-visible change, such as releasing or closing a product feature, to avoid unnecessary documentation noise.

The best way to sync docs/* with a central documentation index is to align them after code changes by applying updates only for user-visible product changes. This complements existing product-change rules and prevents modular documentation desynchronization.