provisioning for one remote development machine master
A laptop pushes configuration to a server; the server never fetches its own. Credentials only flow one way, which is why a script's directory is a claim about which machine can run it. Design and rationale live in flit-spec.md, daily use in README.md, and working notes for an agent in CLAUDE.md. The history starts here. Earlier commits carried values that tie the repository to one account, machine and deployment — the kind a public repository must never hold, and which a published history cannot be made to forget. The working tree they were removed from is what this commit records. .githooks/pre-commit scans staged content for those patterns and refuses the commit, so the rule is enforced rather than remembered.