Run the rebrand self-test in the CI checks
The self-test generates two identities on a scratch copy of the tree and
checks that --clean restores it, so a Forkgram release that moves the
strings, icons or account-type literals the generator patches fails the
sync's compile check instead of breaking the next rebrand.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019mVy1fu8zBn38wHgJqmLNz
commit0f073e893bfabedca468b33c1ae7210b9f933e41
authorClaude <noreply@anthropic.com>
dateSun 27 Sep 2026, 05:53 (2 weeks ago)
parent6fc5793
multigram/tools/check.sh+6
@@ -23,6 +23,12 @@ if [ -f multigram/tools/style_knobs_check.py ]; then
2323 python3 multigram/tools/style_knobs_check.py
2424fi
2525
26+if [ -f multigram/rebrand/selftest.py ]; then
27+ # Rebrand toolkit: generate two identities on a scratch copy, check the output, then --clean back to the commit.
28+ echo "== rebrand toolkit: self-test"
29+ python3 multigram/rebrand/selftest.py
30+fi
31+
2632echo "== style table: format and readability on the current theme sources"
2733python3 multigram/tools/check_style_table.py
2834