They are pack.mjs output and .gitignore already says so, but the rename (7e75aed13c) force-added them at 0.8.0. Any reset of lith's checkout without a re-pack after it (a rollback, or a second deploy landing in the same minute) put that stale feed back: after e4208fb385 production advertised Aesel 0.8.0 beside a 0.8.18 tarball, and ac-deploy's check caught it. Untracked, a reset can only remove them, and the pack that follows every deploy writes them fresh.