Public-template privacy boundary

The public default is a clearly marked placeholder, not a real recipient. Personal input belongs in an ignored local directory or a deliberately private workflow. Public Issues, commits, PRs, CAD lettering, images, movies, downloadable archives and Pages can all expose their displayed text. Secret storage alone does not hide generated content.

What was cleaned

The prior individual distribution was withdrawn before generic regeneration. An owner-controlled private backup preserves the original gift and pending manufacturing notes; it is outside Git and is not a public artifact.

Only the authorized repository was inspected. The inventory found two public branches and no forks, pull requests, tags or releases. An isolated mirror and git-filter-repo 2.47.0 were used to remove identified recipient-bearing generated artifacts and generalize related text, paths and commit metadata. Both branches were updated atomically with exact --force-with-lease expectations; no blind mirror overwrite or repository deletion was used. Ordinary unrelated source and reusable brick meshes were retained.

The filtered reachable history was checked across both refs, commit messages, trees, blobs and retained archives. Identified old Actions artifacts and completed logs were removed. Detailed original values, withdrawn paths, old-SHA URLs and the private mapping are deliberately not reproduced in this public record.

What is not guaranteed erased

Rewriting reachable history does not guarantee removal of GitHub's unreachable objects or cached views, existing clones, prior downloads, or third-party caches. A bounded unauthenticated request still returned bytes from a known old rendered artifact, matching the corresponding privately preserved bytes. This residual server retention is not described as erased, and it is not evidence that the current generic distribution contains it.

An owner may choose to ask GitHub Support what assistance is available. Public account identifiers are not leaked credentials; do not misrepresent the request as a secret leak. Support may decline non-sensitive-data removal, and complete erasure is not promised. A specific private inquiry draft and private technical appendix are held outside this repository; no request has been sent on the owner's behalf.

See the official removing-sensitive-data guide.

Prevent reintroduction

Do not merge or push old local branches from before the privacy rewrite. Use a fresh clone of the cleaned repository, or deliberately migrate only reviewed clean changes. Do not restore old personalized binaries from private backups into public output folders. The new public build checks its generic defaults; personalization must use the explicit route in the customization guide, with human review of the intended publication scope.

Cleanup does not validate physical fit, printed strength, retention, durability or tip resistance.