chore(Item 11 tail): resolve 10 stale .md (keep canonical .adoc) + 2 .md→.adoc conversions - #80
Merged
Merged
Conversation
….md→.adoc conversions Day 10 lossy-tail, Day-9-style hybrid resolution: - DELETE_MD: .md was broken/auto-gen scaffold cruft; coherent .adoc retained. - CONVERT: .md was the real doc; faithfully converted to AsciiDoc via pandoc 3.9 (union-merge: any legacy .adoc-only content preserved verbatim). Inbound links repointed .md→.adoc. No content lost. FLAG-class ambiguous pairs intentionally deferred. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
hyperpolymath
force-pushed
the
chore/item11-tail-md-adoc-resolve
branch
from
May 17, 2026 00:57
898c086 to
48ea9e1
Compare
hyperpolymath
added a commit
that referenced
this pull request
Sep 22, 2026
Owner ruling: "deno is over, we're prioritising bun, and using bunx."
Until now the estate contradicted itself: LANGUAGE-POLICY.adoc §1 and
docs/JS-RUNTIME-POLICY.adoc both ranked Deno second and called existing
Deno projects "grandfathered", while the pre-commit hook summoned a Deno
toolchain to lint them. This lands the policy half of the ruling plus the
ledger the CI gate will read.
.machine_readable/deno-allow.txt — a SHRINK-ONLY exemption ledger, seeded
from a COMPLETE census, not a sample: all 458 non-archived repositories of
both accounts, each probed on its DEFAULT BRANCH with
`gh api repos/<slug>/git/trees/<branch>?recursive=1` and matched against
`(^|/)deno\.jsonc?$` at any depth. 11 carry a Deno config, 446 do not, 1 has
no commits, 0 probe errors.
Two controls, because a census that cannot fail is not a measurement:
* per-repo denominator — each probe recorded its tree entry count, so a
failed probe reports ERR and can never be read as "no Deno". This caught
a TOTAL probe failure (458/458 ERR, an IFS bug) that would otherwise
have been published as "zero Deno estate-wide".
* truncation — GitHub silently truncates a recursive tree at ~100k
entries. hyperpolymath/julia-ecosystem returned "truncated": true, so
its result was discarded and re-measured with a blobless clone: 57611
blobs, zero matches. Every other tree reported "truncated": false.
The plan this implements cited 69 repositories. That figure is WITHDRAWN:
it came from tracked deno.json files in local checkouts, which are stale
(last fetch 2026-09-15) while the default branches had already removed
them — e.g. coq-jr carries deno.json on local main and not on origin/main,
removed by 44f956e "eradicate TypeScript and NPM/Deno configs (#80)".
scripts/check-exemption-ratchet.sh registers the ledger as a 6th entry, so
adding a slug needs a Ratchet-exception trailer naming this exact path.
.githooks/validate-lint-format.sh now REFUSES a commit that adds or
modifies a deno.json(c) instead of linting it. It deliberately asks a
NARROWER question than CI: it runs in a caller's checkout, cannot read the
central ledger, and must not fake an exemption. STAGED is --diff-filter=ACM,
so deletions never appear and migrating away is never blocked. Dropping the
Deno lint leaves staged .js with no pre-commit gate; that is declared in the
hook's skip ledger rather than left silent.
Verified: ratchet test 14/14, lock-gate test 11/11, ts-allowlist 18/18,
governance contract PASS; shellcheck clean; asciidoctor clean on both
policy documents; hook refusal exercised 6/6 including the deno.jsonc
spelling and a `config/mydeno.json` near-miss control.
Ratchet-exception: .machine_readable/deno-allow.txt — seeding the ledger for the first time. 0 -> 11 entries, every one a repository that ALREADY carries the debt on its default branch; the file records nothing new and licenses nothing new. Shrink-only from here.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
chore(Item 11 tail): resolve 10 stale .md (keep canonical .adoc) + 2 .md→.adoc conversions
Day 10 lossy-tail, Day-9-style hybrid resolution:
3.9 (union-merge: any legacy .adoc-only content preserved verbatim).
Inbound links repointed .md→.adoc. No content lost. FLAG-class ambiguous
pairs intentionally deferred.
Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com