-
-
Notifications
You must be signed in to change notification settings - Fork 0
Remove committed Idris2 build artifacts under src/interface/build/ttc/ #51
Copy link
Copy link
Open
Labels
enhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourfeeds:valence-shellFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes thereFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes therepriority:p2Normal - queue itNormal - queue itscope:repoConfined to this repositoryConfined to this repositorystatus:readyFully specified and ready to be picked upFully specified and ready to be picked up
Description
Activity
Metadata
Metadata
Assignees
Labels
enhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourfeeds:valence-shellFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes thereFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes therepriority:p2Normal - queue itNormal - queue itscope:repoConfined to this repositoryConfined to this repositorystatus:readyFully specified and ready to be picked upFully specified and ready to be picked up
What
src/interface/build/ttc/2025081600/*.ttc/*.ttm(compiled Idris2 TTC/TTM build artifacts) are committed to the repo. They are matched by the/build/gitignore rule but were committed before/around it, so they persist as tracked cruft.Why it matters
Build artifacts shouldn't be version-controlled (churn, stale binaries, repo bloat).
Action
git rm -r --cached src/interface/build/(or delete the dir) and confirm/build/ignore coverage.Caveat:
src/interface/is the contested RSR proof scaffold under OQ-001 (#32 — docs-only monorepo vs proof repo). If OQ-001 resolves to "docs-only, drop the scaffold", this directory goes away wholesale and this issue is subsumed. So either fold this into the OQ-001 cleanup, or do the artifact removal now as an independent safe step.Found during the 2026-06-14 deep-checkpoint (not in scope for the safe-hygiene PR #50).