fix(policy): complete #655 — Deno rows in both runtime tables still say 'grandfathered' - #816
Merged
Merged
Conversation
…ay 'grandfathered'
The 2026-08-26 owner ruling ('deno is to go and bun is the way we are
going, put it first everywhere unless not possible and explain why if
not') was closed as #655 after correcting .claude/CLAUDE.md — the file
agents read first. But the two published policy tables were never
updated and still teach the repudiated rule verbatim:
LANGUAGE-POLICY.adoc:29-31 'Existing Deno projects are
*grandfathered* and need not migrate'
docs/JS-RUNTIME-POLICY.adoc:43 same row, same wording
Downstream drift is already observable: rsr-template-repo's CLAUDE.md
carried 'Deno (grandfathered)' until today while its own
runtime-policy.yml enforced 'BEING REMOVED, not grandfathered (canon
standards#655)' — the contradiction filed as rsr-template-repo#70.
A canon that disagrees with itself re-seeds that contradiction into
every repo that copies either side.
New wording mirrors the correction table recorded in #655 itself:
BEING REMOVED; existing projects must migrate to Bun; where Bun
genuinely cannot be used, the reason must be documented. The rank-2
listing is kept (the estate migration is in flight and
runtime-policy.yml emits a warning, not an error, until it completes)
but explicitly marked as not a safe harbour.
Not touched, flagged for owner ruling instead:
- rhodium-standard-repositories/spec/LANGUAGE-POLICY.adoc (v1.5.0,
revdate 2026-08-31 — AFTER the ruling) still inverts the policy:
lists Deno as ALLOWED 'Replaces Node/npm/Bun' and bans
'npm/Bun/pnpm/yarn' with replacement 'Deno'. Correcting a versioned
spec needs a revnumber bump + Amendments entry: owner call.
- ai-instruction/{opus,sonnet}.adoc briefing-template examples still
say 'Deno first' / 'no npm/bun/yarn' — templates, not gates;
owner call on the example text.
Contributor
|
Warning Review limit reachedNext included review available in 15 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Completes the 2026-08-26 owner ruling recorded in #655 ("deno is to go and bun is the way we are going, put it first everywhere unless not possible and explain why if not").
#655 was closed after correcting
.claude/CLAUDE.md— the file agents read first. But the two published policy tables were never updated and still teach the repudiated rule verbatim:LANGUAGE-POLICY.adocdocs/JS-RUNTIME-POLICY.adocDownstream drift is already observable:
rsr-template-repo'sCLAUDE.mdcarried "Deno (grandfathered)" while its ownruntime-policy.ymlenforced "BEING REMOVED, not grandfathered (canon standards#655)" — the contradiction filed as rsr-template-repo#70 (companion PR there fixes the template side; merge together).New wording mirrors #655's own correction table: BEING REMOVED; existing projects must migrate to Bun; where Bun genuinely cannot be used, the reason must be documented. The rank-2 listing is kept (the estate migration is in flight and
runtime-policy.ymlemits a warning, not an error, until it completes) but explicitly marked not a safe harbour.Escalated in the companion PR, deliberately NOT touched here (owner calls)
rhodium-standard-repositories/spec/LANGUAGE-POLICY.adoc— the RSR spec, v1.5.0, revdate 2026-08-31, five days AFTER the ruling — still encodes the inverse policy: Deno ALLOWED "Replaces Node/npm/Bun" (:70–72); Node.js banned → replacement Deno (:193–194); "npm/Bun/pnpm/yarn" banned → replacement Deno (:227–228). Correcting a versioned spec needs a revnumber bump + Amendments entry.ai-instruction/opus.adoc:92,170,sonnet.adoc:85–86,118— briefing-template examples still teach "Deno first" / "no npm/bun/yarn".Refs rsr-template-repo#70.