Skip to content

policy: Bun is tier 1, Deno is being removed — correct local CLAUDE.md - #57

Merged
hyperpolymath merged 2 commits into
mainfrom
policy/bun-first-deno-removal
Aug 27, 2026
Merged

policy: Bun is tier 1, Deno is being removed — correct local CLAUDE.md#57
hyperpolymath merged 2 commits into
mainfrom
policy/bun-first-deno-removal

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Owner ruling, 2026-08-26:

"deno is to go and bun is the way we are going, put it first everywhere unless not possible and explain why if not"

This repo's .claude/CLAUDE.md is what an agent reads first. Correcting hyperpolymath/standards (#655) fixes one copy of ~372 — agents read the local one.

What this PR actually changes

Every line below was verified present in this PR's own diff — nothing is claimed that isn't here.

change in this diff
ALLOWED: Deno row → Bun, tier 1
BANNED: | Bun | Deno | row removed
BANNED: Deno added, replacement Bun
BANNED: Node.js/npm/pnpm/yarn → Bun
rule: manifest now required (package.json + bun.lock)
rule: bun install --production replaces the node_modules rule
pkg mgmt: JS deps → Bun, bunx --no-install --bun
repaired blanking scar: Only where cannot → Only where AffineScript cannot

⚠ An earlier revision of this description listed blanking-scar repairs generically, including some this repo did not need. codacy-production correctly flagged that as a description/diff mismatch. The table above is now generated from the diff itself.

Review feedback addressed

  • No TypeScript at all (codacy raised the contradiction; the owner then ruled it outright). The Bun row advertised "Executes .ts directly" inside a file that bans TypeScript. Owner ruling: TypeScript should not exist at all — so every .ts reference is gone from the row, including JS/TS in its label. It now reads JS runtime, running compiled ESM/JS.
  • Deno missing from BANNED (codacy): added — the ruling was only half expressed without it.
  • Unpinned bunx (coderabbitai, Security & Privacy): a bare bunx <tool> can fetch a package outside bun.lock and can start Node via a shebang. Guidance now requires a declared devDependency plus bunx --no-install --bun.

Not taken: "a npm-compatible" (LanguageTool is wrong — "an" is correct before a vowel sound); "--frozen-lockfile is redundant" (correct, and no such flag was added); the Nix → Guix point (real, but a separate ruling — deliberately not folded into a Deno/Bun change).

Scope

Policy text only — no code, no workflows, no build files.

Related: #655 (governing document), #658 (Deno→Bun assessment: 18 repos blocked on @affinescript/* npm packages that do not exist), #659 (policy duplicated into ~372 copies).

Owner ruling 2026-08-26: "deno is to go and bun is the way we are going, put it
first everywhere unless not possible and explain why if not".

This file is what an agent reads FIRST and it listed Bun as BANNED with Deno as
its replacement. Correcting hyperpolymath/standards (#655) fixes one copy of
~372 - agents read the local one. This is that local copy.

  ALLOWED  **Deno** "Replaces Node/npm/bun"  ->  **Bun** tier 1
  BANNED   | Bun | Deno |                    ->  row REMOVED
  BANNED   Node.js / npm / pnpm/yarn -> Deno ->  -> Bun
  rule     "No package.json for runtime deps - use deno.json imports"
           -> Use package.json + bun.lock; a manifest is REQUIRED
  rule     "No node_modules in production"
           -> bun install --production, pinned via bun.lock
  pkg      JS deps: Deno  ->  JS deps: Bun (package.json + bun.lock), bunx

WHY THE MANIFEST RULE MATTERS MOST. "No package.json for runtime deps" did not
express a preference - it told repos not to declare their dependencies at all.
hyperpolymath/ubicity imported zod and glob, shipped NO manifest of any kind,
and could not build under ANY toolchain. Fixed in ubicity#107; the rule that
caused it is fixed here.

ALSO REPAIRED - blanking scars from the ReScript purge, which substituted the
token with an EMPTY STRING rather than removing the text:

  |  | AffineScript |               ->  | ReScript | AffineScript |
  1. **No new  files** ...          ->  **No new ReScript files** ...
  | **JavaScript** | Only where  cannot |  ->  Only where AffineScript cannot

Restoring the NAME in a policy table does not reintroduce the language. Same
root cause as the rm -rf /lib found in wordpress-tools#62.

Policy text only - no code, no workflows, no build files. 1 file(s).

NOT FOLDED IN: "Fallback: Nix (flake.nix)" is stale (Guix superseded Nix per
ADR-2026-STACK-MIGRATION) but that is a separate ruling; flagged, not changed.
@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

Next included review available in 7 minutes.

View limit details

Limit 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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c88aa64c-5700-4c7d-8503-3fc3311fade7

📥 Commits

Reviewing files that changed from the base of the PR and between 2e3be02 and 17a2ca0.

📒 Files selected for processing (1)
  • .claude/CLAUDE.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gitar-bot

gitar-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

The PR successfully initiates the transition to Bun as a Tier 1 runtime and removes Deno references. However, the secondary objective of correcting the 'automated language purge' (renaming ReScript to AffineScript) is incomplete and inconsistent. Multiple references to ReScript remain in critical sections like the allowed languages table, banned list, and enforcement rules (specifically lines 22, 40, 45, 55, and 66), which will cause conflicting instructions for AI agents using this CLAUDE.md file.

Additionally, there is a discrepancy between the PR description and the actual changes in the diff. The 'repaired' version of Rule 1 described in the PR summary does not match the implementation, which still refers to TypeScript instead of the intended ReScript-to-AffineScript conversion rule. These inconsistencies should be resolved before merging to maintain the integrity of the project's policy documentation.

About this PR

  • The PR description mentions specific repairs to the banned tools table (e.g., '| ReScript | AffineScript |') and Rule 1 text that are not reflected in the provided changes. Please verify if all intended modifications from the 'Also repaired' section of your description have been included in the commit.

Test suggestions

  • Verify AI agent identifies Bun as the default and preferred Tier 1 runtime for JS/TS.
  • Verify AI agent follows the requirement to create and maintain package.json and bun.lock.
  • Verify consistency of the 'AffineScript' rename across all policy tables and rules.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify AI agent identifies Bun as the default and preferred Tier 1 runtime for JS/TS.
2. Verify AI agent follows the requirement to create and maintain package.json and bun.lock.
3. Verify consistency of the 'AffineScript' rename across all policy tables and rules.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Comment thread .claude/CLAUDE.md
| **Gleam** | Backend services | Runs on BEAM or compiles to JS |
| **Bash/POSIX Shell** | Scripts, automation | Keep minimal |
| **JavaScript** | Only where ReScript cannot | MCP protocol glue, Deno APIs |
| **JavaScript** | Only where AffineScript cannot | MCP protocol glue, Bun APIs |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 MEDIUM RISK

The documentation now uses 'AffineScript' and 'ReScript' interchangeably. To ensure the AI assistant follows a single consistent language policy, replace all remaining instances of 'ReScript' with 'AffineScript', particularly in the allowed languages table (line 22), the banned list (lines 40, 45), and Rule 5 (line 66).

Comment thread .claude/CLAUDE.md
1. **No new TypeScript files** - Convert existing TS to ReScript
2. **No package.json for runtime deps** - Use deno.json imports
3. **No node_modules in production** - Deno caches deps automatically
1. **No new TypeScript files** - Convert existing TS to AffineScript

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ LOW RISK

The implementation of this rule diverges from the PR description's specific 'repaired' example: 'No new ReScript files — convert .res to AffineScript (.affine)'. The current code keeps 'No new TypeScript files', which contradicts the stated goal of repairing the language purge.

Review feedback from codacy-production and coderabbitai on the policy wave.
Three substantive points, all accepted:

1. ".ts CONTRADICTION" (codacy, MEDIUM, raised on most of the wave). The Bun row
   said "Executes .ts directly, no build step" in a file whose BANNED table bans
   TypeScript. OWNER RULING: TypeScript "should not exist at all", so advertising
   Bun's TypeScript capability is wrong regardless of whether it is true. Every
   .ts reference is removed from the row, including "JS/TS" in its label.
2. "DENO MISSING FROM BANNED" (codacy, raised repeatedly). The wave removed Deno
   from ALLOWED but never added it to BANNED, so the ruling was only half
   expressed. Added | Deno | Bun |.

3. "UNPINNED bunx" (coderabbitai, Security & Privacy). A bare `bunx <tool>` can
   fetch a package outside package.json/bun.lock, and can start Node via a
   shebang - both contrary to estate SHA-pinning doctrine and the Node ban.
   Guidance now requires a declared devDependency plus
   `bunx --no-install --bun <tool>`.

NOT taken: "a npm-compatible" (LanguageTool is wrong, "an" is correct before a
vowel sound); "--frozen-lockfile is redundant" (correct - no change needed, and
none made); the Nix->Guix point (real, but a separate ruling, deliberately not
folded into a Deno/Bun change).
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit c293d69 into main Aug 27, 2026
18 of 33 checks passed
@hyperpolymath
hyperpolymath deleted the policy/bun-first-deno-removal branch August 27, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant