From be82a06d48aa132f45d0fd90dfe5b175b19fbcfb Mon Sep 17 00:00:00 2001 From: "Arena Agent (triage patches)" Date: Thu, 17 Sep 2026 18:14:06 +0000 Subject: [PATCH] =?UTF-8?q?fix(policy):=20complete=20#655=20=E2=80=94=20De?= =?UTF-8?q?no=20rows=20in=20both=20runtime=20tables=20still=20say=20'grand?= =?UTF-8?q?fathered'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- LANGUAGE-POLICY.adoc | 6 ++++-- docs/JS-RUNTIME-POLICY.adoc | 6 ++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/LANGUAGE-POLICY.adoc b/LANGUAGE-POLICY.adoc index 6f4c4b6ae..19524f3f9 100644 --- a/LANGUAGE-POLICY.adoc +++ b/LANGUAGE-POLICY.adoc @@ -27,8 +27,10 @@ Ordered preference. Reach for the first one that can do the job. built-in test runner and bundler. | 2 | *Deno* -| Second position. Existing Deno projects are *grandfathered* and need not - migrate; prefer it over pnpm/npm when Bun genuinely cannot be used. +| *BEING REMOVED* (owner ruling 2026-08-26, #655): existing Deno projects + must migrate to Bun; where Bun genuinely cannot be used, the reason must + be documented. Ranked second only while the estate migration is in + flight — not a safe harbour. | 3 | *pnpm* | Third. Only where an upstream toolchain requires a node_modules layout. diff --git a/docs/JS-RUNTIME-POLICY.adoc b/docs/JS-RUNTIME-POLICY.adoc index 701790f00..84ae4b2b1 100644 --- a/docs/JS-RUNTIME-POLICY.adoc +++ b/docs/JS-RUNTIME-POLICY.adoc @@ -42,8 +42,10 @@ built-in test runner and bundler. | 2 | *Deno* -| Second position. Existing Deno projects are *grandfathered* and need not -migrate; prefer it over pnpm/npm where Bun genuinely cannot be used. +| *BEING REMOVED* (owner ruling 2026-08-26, #655): existing Deno projects +must migrate to Bun; where Bun genuinely cannot be used, the reason must be +documented. Ranked second only while the estate migration is in flight — +not a safe harbour. | 3 | *pnpm*