Why publication updates documentation
A dashboard-only publish should not require a separate manual documentation edit. The coordinator verifies that no application or infrastructure code changed, confirms the existing documentation matches the previous release, then generates the catalog and records the new fingerprint before activation.
Reviewed catalog
- Backend resources · My dashboard — 8 panels
Ownership and rollback
Public definitions use new identities, leaving editable owner copies untouched. Git review controls publication. Ordinary source changes cannot use this narrow synchronization exception, and a failed documentation build prevents activation.