publish: reproducible standalone mod repo via git-filter-repo

The mod is 63 files; the tree it lives in is 1838 files of a commercial game
and 296 MB of history. Publishing therefore means stripping, and stripping by
hand is exactly the sort of thing that quietly leaks a build of the game.

accessibility/publish/publish.sh rebuilds the standalone repository from this
tree with git-filter-repo, then asserts that no path outside accessibility/ and
the docs survived, and aborts rather than pushing if one did.

The publish-only files live in accessibility/publish/ rather than at the root
so that the game-file footprint check stays a clean "main.lua | 1 +", and the
filter renames them to the root where a visitor to the mod repo expects them.
The script then drops the publish machinery itself, which means nothing to
someone installing the mod.

README.md is the install guide: copy accessibility/ into an extracted game
folder and add the one line to main.lua, which install.patch also applies.

CLAUDE.md now states which of the two repos the reader is in, since half of it
(running the game, the footprint check) is meaningless without the game present.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Accessibility Mod

2026-08-02 01:21:16 +02:00

co-authored by

Claude Opus 5

parent 18e6473dd3

commit 86c71fc001

3 changed files with 186 additions and 6 deletions

									
										install.patch
									
		+12
		
												View File
												
				@@ -0,0 +1,12 @@

				diff --git a/main.lua b/main.lua

				index 35d3b50..5a83f76 100644

				--- a/main.lua

				+++ b/main.lua

				@@ -95,6 +95,7 @@ function love.load()

				 	user.initialize()

				 	states.setup()

				 	console.prepare()

				+	require("accessibility").initialize() --ACCESSIBILITY MOD: sole entry point

				 	local messages = require("models.messages")

				 	if keybindingsConflicts then

				 		states.switch("menu_message",