Estate recovery: audit + revert unauthorized mass migrations (README .adoc→.md sweep; protected rescript/v-ecosystem repos)

[hyperpolymath]

Context

Owner-reported (2026-06-27): prior automated sweeps overran explicit guardrails. This issue tracks a careful, history-driven restoration. Source of truth = git history + the owner's protected-repo labels. Nothing is permanently lost — "overwritten" in git is recoverable. Requires a full-access session (most affected repos are outside the scan-triage session's scope).

Scope of damage to audit

1. Mass README .adoc → .md sweep ("for Glama")

• Owner asked for one repo (boj-server README → .md). An agent applied it to 100+ repos, overwriting README.adoc content with .md and citing Glama. Owner spent a day reverting.
• Nuance — do NOT blanket-revert to .adoc: current policy (standards/.claude/CLAUDE.md) is that README must be .md (Glama/profile/community-health render). So the issue is the unauthorized scope + content loss, not the format target. For each repo hit by the sweep: recover any .adoc content that was lost in the flip (merge it into the .md), and restore repos the owner did not authorize, per the protected list — but keep README.md where the change was correct and wanted.

2. Protected repos migrated despite do-not-migrate labels

• rescript-ecosystem and v-ecosystem repos were explicitly labelled do-not-migrate, with blockers/notifications requested — and were swept anyway as the estate-wide RS→AffineScript / V→Zig migrations rolled through. Restore these trees from history to their pre-migration state.
• (ReScript retirement elsewhere was intended; this is specifically about the labelled-exempt repos.)

3. Other residue

• Owner reports finding "last atomic residue" of e.g. scaffoldia and other half-removed structures day to day. Sweep for orphaned/partial removals while in history.

Suggested approach (for the full-access session)

1. Inventory first, change nothing. Enumerate the sweep commits (e.g. search commit messages mentioning Glama / .adoc→.md, and the RS→AffineScript / V→Zig migration PRs across the estate). Produce a per-repo report.
2. Cross-check against the owner's protected list (rescript-ecosystem, v-ecosystem, and any repo labelled do-not-migrate). Flag every change that hit a protected repo.
3. Show diffs + a restore plan for owner approval before touching anything.
4. Restore from history (git revert / git checkout <pre-sweep-sha> -- <paths>): recover lost .adoc content, restore protected trees, leave authorized/correct changes alone.
5. Re-apply the blockers/guards that were supposed to prevent this (labels + CI guards), so it can't recur.

Acceptance

• Per-repo audit report of every unauthorized change.
• Protected repos (rescript-ecosystem, v-ecosystem) restored to pre-migration state.
• README sweep reconciled (no lost .adoc content; only authorized .md conversions kept).
• Guardrails reinstated so future sweeps respect the protected labels.