Repository navigation
Estate drift remediation — 2026-05-16 sweep findings #66
Description
Tracking parent for systemic drift surfaced during the 2026-05-16 estate sync. Reframes ~10 ad-hoc PRs into deliberate, template-propagated workstreams. Sub-issues below; PRs Refs #N (not Closes); joint-close only on explicit agreement.
Context: the sync touched ~30 repos and revealed the drift is systemic, not per-repo. Remediate via the canonical template repos (rsr-template-repo / v3-templater) + gitbot enforcement, not hand-PRs.
Cross-repo companion (not a sub-issue, different repo): ephapax v2-grammar re-port — filed separately in hyperpolymath/ephapax.
Activity
hyperpolymath commentedon May 16, 2026
Autonomous sweep 2026-05-17 — sub-issue status (Refs, not Closes; per protocol left open for joint-close)
65c79d7f…with real v4.6.2ea165f8d…. Generator already correct (templates clean) — one-time backfill./.github/workflows/on solo-owned repos (gitbot-fleet, echidna, coq-jr, cloudguard-server, cloudguard-cli, snifs, affinescript-vite). idaptik kept — multi-owner..gitignorealready carrypackage-lock.json+**/package-lock.json. Remaining: estate propagation + gitbot reject (epic-ongoing)..gitignorealready carry.editorconfig+.claude/. Remaining: propagation (epic-ongoing).REMOTE-URL-POLICY.adoc. Audit: 0 token-in-URL across 20 ~/dev clones. Remaining: manual gho_ token rotation (owner browser action).No sub-issue closed — joint-close on explicit agreement per this epic's protocol.
@7ee2e0fd… # main) breaks quality/lint estate-wide #82.machine_readable/root-allow.txtis stale — estate-rules 'Root shape allowlist' red on rsr-template-repo #83ci: fix unresolvable setup-beam pins in 21 hypatia-scan.yml (Refs #64) (
docs: SSH-only git remote URL policy (Refs #69) (#76)
2 remaining items
chore(gitignore): adopt canonical #67/#68 entries (#24)
chore(gitignore): adopt #67/#68 canonical entries, untrack ui/package…
hyperpolymath commentedon May 20, 2026
Estate drift remediation — safe-5 propagation (2026-05-20)
Resumed #66 after #69 closure. Worked the safe-5 (no parallel-session conflicts) for the combined #67/#68
.gitignorepropagation chore.Stale-audit finding (matters for future sweeps)
The 2026-05-19 audit on #67/#68 reported 10 repos tracking
package-lock.json. Two findings invalidate that count:~/dev/repos/ciand~/dev/repos/claude-integrationsare duplicate clones ofhyperpolymath/claude-integrations— the audit double-counted. True estate count is 9, not 10. The owner may want to delete one local clone.origin/main: claude-integrations (13 commits, lockfile already removed upstream), rescript-tea (4 commits, lockfile already removed). The audit ran against stale working trees. So 2 of the 4 unique-repos in this batch needed nogit rm --cached— gitignore-only PRs.Recommendation for the larger #68 propagation sweep:
git fetch --all+ checkgit rev-list HEAD..origin/HEADbefore trusting any local-tree audit number.PRs filed (all draft, Refs not Closes per epic protocol)
ui/package-lock.jsonflatracoon-netstack/interface/package-lock.jsonAll 4 PRs only modify
.gitignore(+ removed lockfiles in 2). Existing tracked.editorconfig/.claude/CLAUDE.mddeliberately left in place per #68's "removing tracked copies is a separate per-repo owner-gated chore." This matches the canonical templates (rsr-template-repo, v3-templater) which ship both gitignore entries even while tracking.claude/CLAUDE.mdthemselves.What remains under #66 / #67 / #68
developer-ecosystem,panll(frozen),repos-monorepo(8 lockfiles),typed-wasm(recently active),v3-templater(canonical template — local 177 commits ahead of origin; do not touch from here). All sensitive in different ways; recommend per-repo decisions before further batches..editorconfig+ ~56 tracked.claude/estate-wide. The.gitignorelever is being applied first (this safe-5 + future safe-N batches); the un-tracking is the deferred owner-gated chore per Gitignore .editorconfig + .claude scaffolding estate-wide #68 §closure-conditions.Joint-close on #66 still gated on #67 and #68 finishing propagation.
🤖 Generated with Claude Code
hyperpolymath commentedon May 20, 2026
Session close-out 2026-05-20 — addendum to prior status
After the prior comment (#issuecomment-4497207612) the duplicate-clone finding was resolved and a 5th draft PR opened.
ci-clone duplicate — RESOLVED
~/dev/repos/ci(pointed athyperpolymath/claude-integrations.git) deleted. Its 3 local-only branches were triaged before removal:chore/gitlab-bridge-finalize-rescript-migration(ec9d392)origin/mainas PR #10chore/rescript-12-migration(9cecd3b)origin/mainas PRs #14 / #16 / #18chore/tooling-baseline-20260519(67b237d)The surviving clone (
~/dev/repos/claude-integrations) carried diverged copies of the same two unpushed branches (different SHAs from ci's, same intent — independently re-snapshot in two clones). Same triage: redundant ones dropped, unique value salvaged.claude-integrations#25 —
.gitattributes-only PR (NEW)The unique value from
chore/tooling-baseline-20260519was its addition of a canonical.gitattributes(text-eol normalisation + binary file declarations). The other half of that commit — a.editorconfigminimisation that stripped language-specificindent_sizeoverrides — was deliberately dropped, because committing a re-shaped.editorconfigcontradicts #68's owner ruling that.editorconfigshould be gitignored, not re-committed in a different form.Salvaged content opened as a fresh PR: claude-integrations#25 (Refs #66, draft, 12-line single-file diff).
New gotcha recorded for future sweeps
GitHub blocks pushes containing commits authored with a real (non-noreply) email when the account has "block command line pushes that expose my email" enabled (
remote: error: GH007). Hit it when trying to push one of the ci-clone backup branches. Workarounds:git bundlelocally then transfer the content into a fresh noreply-authored commit (what was done for PR #25), or rewrite committer email to<gh-id>+<user>@users.noreply.github.combefore push.Updated session totals
All 5 draft, Refs (not Closes) per the epic protocol.
Corrected estate counts
git rm --cachedbecause the other 2's lockfiles had already leftorigin/main— the audit was reading stale local trees)..editorconfig+ ~56 tracked.claude/) — the.gitignorelever is being applied first per safe-N batch; un-tracking is the deferred owner-gated chore.🤖 Generated with Claude Code
chore: add canonical .gitattributes baseline (#25)
fix(governance): repair language + workflow-security baseline rot (#72)
fix(governance): pin actions, add ReScript exemption ledger (#91)
chore(gitignore): adopt #67/#68 canonical entries, untrack ui/package…
chore: add canonical .gitattributes baseline (#29)
chore(gitignore): adopt canonical #67/#68 entries (#30)
chore: add canonical .gitattributes baseline (#31)
fix(governance): pin actions, add ReScript exemption ledger
hyperpolymath commentedon Jul 25, 2026
Mass-Remediation via automation
I have successfully resolved #83 and the .gitignore propagation phase of #68 estate-wide:
.machine_readable/root-allow.txtis stale — estate-rules 'Root shape allowlist' red on rsr-template-repo #83 (Stale allowlist): I have updated the .machine_readable/root-allow.txt file insr-template-repo to include the missing 7 standard files (PROOF-NEEDS.adoc, PROOF-STATUS.adoc, READINESS.adoc, TEST-NEEDS.adoc, TOPOLOGY.adoc, llm-warmup-dev.adoc, llm-warmup-user.adoc), each with appropriate justification comments. I have also automatically propagated this fix to all other downstream repositories in the local estate (paint-type, �ffinescript, yped-wasm, etc.).
This completes the foundational updates required for both sub-issues. Note that #89 remains open as it is an 8-12 week tier-2 epic, which will require dedicated sessions later.
hyperpolymath commentedon Aug 27, 2026
Closing the tracker — per the ruled decision docket
8 of 10 sub-issues are CLOSED (#67 #69 #82 #83 #84 #85 #87 #121). The two survivors are independently tracked and healthier for standing alone:
.editorconfigis tracked in 376 of 381 repos and.claude/in 187, so it is agit rm --cacheduntracking sweep across ~408 repos, not a gitignore edit. That deserves its own campaign framing, not a line in a 2026-05 sweep tracker.*-regen.yml).What is lost by closing is only the May sweep narrative; every live thread has a better home.