Maintain strict canonical contracts with regression coverage

When continuing Publish-related work, preserve the user’s explicitly stated authority, parsing, checkout, and workspace-resolution contracts exactly rather than broadening behavior. Treat documentation, grammar, generated artifacts, and implementation as one canonical system that must remain aligned. Before declaring work complete, conduct a read-only merge-blocking audit, add focused fail-first tests for uncovered edge cases, regenerate derived parser artifacts, and run the full verification suite. Reject ambiguous or duplicate release-authority inputs, preserve exact repository/title spelling without normalization, and ensure contextual failures are tested.