Skip to content

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

Merged
hyperpolymath merged 3 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#195
hyperpolymath merged 3 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. 2 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.
@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

This PR successfully updates the policy to establish Bun as the Tier 1 JS/TS runtime and replaces references to Node.js/npm. However, there is a mismatch between the PR description and the actual changes: the restoration of 'ReScript' labels is missing, with 'TypeScript' being used in some places instead. Additionally, while Deno is being phased out, it is not explicitly listed in the BANNED tables of the modified CLAUDE.md files. Explicitly banning Deno is recommended to prevent LLMs from generating Deno-specific code or configurations.

About this PR

  • The PR description explicitly claims to repair 'blanking scars from the ReScript purge' by restoring the 'ReScript' name. However, the changes either leave those lines unchanged or use the label 'TypeScript' instead. Please align the implementation with the stated intent or update the description to reflect the move to TypeScript.

Test suggestions

  • Found recommended test scenario: Verify Bun is listed as the Tier 1 runtime with manifest requirements
  • Found recommended test scenario: Verify banned tools list points to Bun for Node/npm/pnpm/yarn replacements
  • Found recommended test scenario: Verify enforcement rules require package.json and bun.lock instead of Deno config
  • Missing recommended test scenario: Verify restoration of 'ReScript' name in policy tables and enforcement rules per description
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Missing recommended test scenario: Verify restoration of 'ReScript' name in policy tables and enforcement rules per description
Low confidence findings
  • The 'was' states described for the JavaScript usage rule in the PR description (e.g., '| JavaScript | Only where cannot |') do not match the old hunk in the diff, which contained the word 'AffineScript'. This suggests the PR description may be based on an outdated version of the file.

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

| pnpm/yarn | Deno |
| Node.js | Bun |
| npm | Bun |
| pnpm/yarn | Bun |

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

Suggestion: Add Deno to the BANNED list to ensure consistency with the new Bun-first policy and prevent the use of Deno-specific patterns.

Suggested change
| pnpm/yarn | Bun |
pnpm/yarn | Bun |
Deno | Bun |

Comment thread .claude/CLAUDE.md
| pnpm/yarn | Deno |
| Node.js | Bun |
| npm | Bun |
| pnpm/yarn | Bun |

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

Suggestion: Since Deno is being replaced by Bun as the Tier 1 runtime, it should be explicitly listed in the BANNED table to prevent AI agents from suggesting Deno-specific tools or APIs.

Suggested change
| pnpm/yarn | Bun |
pnpm/yarn | Bun |
Deno | Bun |

@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d1091c04-94d3-4b28-8435-96f3a903c459

📥 Commits

Reviewing files that changed from the base of the PR and between 787ffc5 and c3cc38a.

📒 Files selected for processing (2)
  • .claude/CLAUDE.md
  • alkahest-shell-transmuter/.claude/CLAUDE.md

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated project development guidance to use Bun as the JavaScript runtime and package manager.
    • Added Bun-based dependency and production installation instructions.
    • Revised tooling recommendations and restrictions to reflect the new Bun workflow.

Walkthrough

The two CLAUDE.md files replace Deno guidance with Bun runtime, dependency, installation, lockfile, and tooling rules.

Changes

Bun policy migration

Layer / File(s) Summary
Runtime and tool policy
.claude/CLAUDE.md, alkahest-shell-transmuter/.claude/CLAUDE.md
Bun replaces Deno as the default JavaScript runtime and package manager. Banned-tool replacements now point to Bun.
Dependency and installation policy
.claude/CLAUDE.md, alkahest-shell-transmuter/.claude/CLAUDE.md
The guidance requires package.json and bun.lock, uses bun install for production dependencies, and runs tools through bunx --no-install --bun.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

A rabbit checks the Bun command,
With bun.lock close at paw.
Deno hops beyond the gate,
While pinned tools follow law.
The manifests now guide the way.


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.

@github-actions

Copy link
Copy Markdown

🔍 Hypatia Security Scan

Findings: 56 issues detected

Severity Count
🔴 Critical 9
🟠 High 29
🟡 Medium 18

⚠️ Action Required: Critical security issues found!

View findings
[
  {
    "reason": "Required file missing (condition: public_repo)",
    "type": "missing_requirement",
    "file": "SECURITY.md",
    "action": "create",
    "rule_module": "cicd_rules",
    "severity": "high"
  },
  {
    "reason": "Agda postulate assumes without proof -- potential soundness hole (1 occurrences, CWE-704)",
    "type": "agda_postulate",
    "file": "/home/runner/work/valence-shell/valence-shell/proofs/agda/FilesystemModel.agda",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "critical"
  },
  {
    "reason": "believe_me undermines formal verification (2 occurrences, CWE-704)",
    "type": "believe_me",
    "file": "/home/runner/work/valence-shell/valence-shell/proofs/idris2/src/Filesystem/Axioms.idr",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "critical"
  },
  {
    "reason": "unsafe block -- requires SAFETY comment (16 occurrences, CWE-676)",
    "type": "unsafe_block",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/commands.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "as_ptr exposes raw pointer that may dangle or alias unsafely (6 occurrences, CWE-676)",
    "type": "as_ptr",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/commands.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "expect() in hot path (4 occurrences, CWE-754)",
    "type": "expect_in_hot_path",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/parser.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "unsafe block -- requires SAFETY comment (2 occurrences, CWE-676)",
    "type": "unsafe_block",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/process_sub.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "as_ptr exposes raw pointer that may dangle or alias unsafely (2 occurrences, CWE-676)",
    "type": "as_ptr",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/process_sub.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "unwrap() without prior check -- DoS via panic (1 occurrences, CWE-754)",
    "type": "unwrap_without_check",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/test_command.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "high"
  },
  {
    "reason": "expect() in hot path (1 occurrences, CWE-754)",
    "type": "expect_in_hot_path",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/external.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  }
]

Powered by Hypatia Neurosymbolic CI/CD Intelligence

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).
@github-actions

Copy link
Copy Markdown

🔍 Hypatia Security Scan

Findings: 56 issues detected

Severity Count
🔴 Critical 9
🟠 High 29
🟡 Medium 18

⚠️ Action Required: Critical security issues found!

View findings
[
  {
    "reason": "Required file missing (condition: public_repo)",
    "type": "missing_requirement",
    "file": "SECURITY.md",
    "action": "create",
    "rule_module": "cicd_rules",
    "severity": "high"
  },
  {
    "reason": "Agda postulate assumes without proof -- potential soundness hole (1 occurrences, CWE-704)",
    "type": "agda_postulate",
    "file": "/home/runner/work/valence-shell/valence-shell/proofs/agda/FilesystemModel.agda",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "critical"
  },
  {
    "reason": "believe_me undermines formal verification (2 occurrences, CWE-704)",
    "type": "believe_me",
    "file": "/home/runner/work/valence-shell/valence-shell/proofs/idris2/src/Filesystem/Axioms.idr",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "critical"
  },
  {
    "reason": "unsafe block -- requires SAFETY comment (16 occurrences, CWE-676)",
    "type": "unsafe_block",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/commands.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "as_ptr exposes raw pointer that may dangle or alias unsafely (6 occurrences, CWE-676)",
    "type": "as_ptr",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/commands.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "expect() in hot path (4 occurrences, CWE-754)",
    "type": "expect_in_hot_path",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/parser.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "unsafe block -- requires SAFETY comment (2 occurrences, CWE-676)",
    "type": "unsafe_block",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/process_sub.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "as_ptr exposes raw pointer that may dangle or alias unsafely (2 occurrences, CWE-676)",
    "type": "as_ptr",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/process_sub.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "unwrap() without prior check -- DoS via panic (1 occurrences, CWE-754)",
    "type": "unwrap_without_check",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/test_command.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "high"
  },
  {
    "reason": "expect() in hot path (1 occurrences, CWE-754)",
    "type": "expect_in_hot_path",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/external.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  }
]

Powered by Hypatia Neurosymbolic CI/CD Intelligence

Addresses the two live static-analysis findings on this PR.

ReScript was absent from the BANNED table although canon bans it (destination
AffineScript), so the table read as permitting it.

Enforcement Rule 3 said `bun install --production` with no `--frozen-lockfile`,
so a lockfile mismatch silently re-resolved instead of failing, which defeats
the point of committing `bun.lock`.

Enforcement Rule 1 is deliberately untouched: standards#655 records that
collision as not resolvable unilaterally.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@hyperpolymath
hyperpolymath merged commit 2ec67b1 into main Aug 27, 2026
15 of 16 checks passed
@hyperpolymath
hyperpolymath deleted the policy/bun-first-deno-removal branch August 27, 2026 03:50
@github-actions

Copy link
Copy Markdown

🔍 Hypatia Security Scan

Findings: 56 issues detected

Severity Count
🔴 Critical 9
🟠 High 29
🟡 Medium 18

⚠️ Action Required: Critical security issues found!

View findings
[
  {
    "reason": "Required file missing (condition: public_repo)",
    "type": "missing_requirement",
    "file": "SECURITY.md",
    "action": "create",
    "rule_module": "cicd_rules",
    "severity": "high"
  },
  {
    "reason": "Agda postulate assumes without proof -- potential soundness hole (1 occurrences, CWE-704)",
    "type": "agda_postulate",
    "file": "/home/runner/work/valence-shell/valence-shell/proofs/agda/FilesystemModel.agda",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "critical"
  },
  {
    "reason": "believe_me undermines formal verification (2 occurrences, CWE-704)",
    "type": "believe_me",
    "file": "/home/runner/work/valence-shell/valence-shell/proofs/idris2/src/Filesystem/Axioms.idr",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "critical"
  },
  {
    "reason": "unsafe block -- requires SAFETY comment (16 occurrences, CWE-676)",
    "type": "unsafe_block",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/commands.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "as_ptr exposes raw pointer that may dangle or alias unsafely (6 occurrences, CWE-676)",
    "type": "as_ptr",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/commands.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "expect() in hot path (4 occurrences, CWE-754)",
    "type": "expect_in_hot_path",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/parser.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "unsafe block -- requires SAFETY comment (2 occurrences, CWE-676)",
    "type": "unsafe_block",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/process_sub.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "as_ptr exposes raw pointer that may dangle or alias unsafely (2 occurrences, CWE-676)",
    "type": "as_ptr",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/process_sub.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  },
  {
    "reason": "unwrap() without prior check -- DoS via panic (1 occurrences, CWE-754)",
    "type": "unwrap_without_check",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/test_command.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "high"
  },
  {
    "reason": "expect() in hot path (1 occurrences, CWE-754)",
    "type": "expect_in_hot_path",
    "file": "/home/runner/work/valence-shell/valence-shell/impl/rust-cli/src/external.rs",
    "action": "flag",
    "rule_module": "code_safety",
    "severity": "medium"
  }
]

Powered by Hypatia Neurosymbolic CI/CD Intelligence

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