The article has "Copy check contraints" set to False. This ALTER would certainly add a constraint to default new values to 0. It seems to me that the Log Reader should just end up picking up the ALTER and applying the change on subscribers, resulting in a new constraint on the downstream DBs. Just thinking out loud about the possibility of a conflict between the article properties and what the subscribed servers would end up doing.