3 Commits

Include renames

Author	SHA1	Message	Date
Sergey Matyunin	50099acc75	fix: allow stable promotion of published beta history ... Issue: #130 User-Visible: no	2026-08-13 22:59:23 +03:00
Sergey Matyunin	22e98c5555	ci: mark the pre-push hook executable ... Git skips a hook without the bit and says nothing about it, so the gate would have reported success by being absent. The API cannot set the mode: a file pushed that way arrives as 100644. Issue: #121 User-Visible: no	2026-08-13 15:11:20 +03:00
Matysh	42335bc16d	ci: add the pre-push gate and stop lying about it in the canon ... Section 10.1 promised pre-push as the blocking gate that replaces pull requests. The hook did not exist, so the document promised a check that was not there — worse than saying nothing, because a promise like that gets relied on. Until now process-gate ran only as the catch-up job in CI, which reports after the code is already in dev. The hook skips branch deletions and tags, and for a branch the remote has not seen it measures from the merge-base with dev rather than from the root, or every violation committed before the gate existed would make it impossible to pass. A missing script does not block a push: old checkouts and worktrees have to stay usable. gh is optional on purpose. Reading issue status needs the network, and a hook that cannot work on a train is a hook people switch off; offline it runs what it can and CI does the strict pass. The executable bit is the quiet part. Git skips a hook without +x and says nothing — the gate reports success by being absent. Measured on a real push: mode 644 produces zero lines from the gate and the push goes through, 755 stops it. The API cannot set the bit, so install-hooks restores it on every install. Issue: #121 User-Visible: no	2026-08-13 14:58:57 +03:00