feat: rename project to code-foundry

Author: 0xPlayerOne

.github/CODEOWNERS

@@ -1,4 +1,4 @@
-# Repository owners and administrators are populated by the repo-foundry
+# Repository owners and administrators are populated by code-foundry
 # initializer. GitHub CODEOWNERS does not interpolate shell variables.
 # Run the initializer in the target repository to replace this default rule.
 * @OWNER

.github/scripts/init-repo.sh

@@ -1,7 +1,7 @@
 #!/usr/bin/env bash
 set -euo pipefail
 
-source="${REPO_FOUNDRY_SOURCE:-https://github.com/${GITHUB_REPOSITORY_OWNER:-OWNER}/repo-foundry.git}"
+source="${REPO_FOUNDRY_SOURCE:-https://github.com/${GITHUB_REPOSITORY_OWNER:-OWNER}/code-foundry.git}"
 ref="main"
 protection=false
 dry_run=false

.github/scripts/sync-codeowners.sh

@@ -59,11 +59,11 @@ fi
 
 tmp_file="$(mktemp)"
 {
-  printf '%s\n' '# Managed by repo-foundry. Repository owners/admins are discovered during initialization.'
+  printf '%s\n' '# Managed by code-foundry. Repository owners/admins are discovered during initialization.'
   printf '* %s\n' "$owner_line"
   if [ -n "$existing_file" ]; then
     awk '
-      /^# Managed by repo-foundry\./ { managed=1; next }
+      /^# Managed by code-foundry\./ { managed=1; next }
       managed && /^\* / { managed=0; next }
       managed { next }
       /^\* @(OWNER|[^[:space:]]+)/ { next }

.github/scripts/sync-template.sh

@@ -133,7 +133,7 @@ fi
 
 if [ -f "$template_root/package.json" ]; then
   template_version="$(awk -F'"' '/"version"[[:space:]]*:/ {print $4; exit}' "$template_root/package.json")"
-  [ -n "$template_version" ] && template_ref="repo-foundry@$template_version"
+  [ -n "$template_version" ] && template_ref="code-foundry@$template_version"
 fi
 
 files=(

.github/template.yml

@@ -1,5 +1,5 @@
 version: 1
-template: repo-foundry@latest
+template: code-foundry@latest
 languages: typescript
 features: all
 package_manager: bun

.github/template.yml.example

@@ -1,6 +1,6 @@
 # Repository-specific settings for the shared initializer and sync scripts.
 version: 1
-template: repo-foundry@latest
+template: code-foundry@latest
 languages: auto
 features: all
 package_manager: auto

README.md

@@ -1,27 +1,32 @@
-# Repo Foundry
+# Code Foundry
 
-`repo-foundry` is a repository factory for TypeScript, Rust, Python, Solidity,
+[![npm version](https://img.shields.io/npm/v/code-foundry?logo=npm&logoColor=white)](https://www.npmjs.com/package/code-foundry)
+[![npm downloads](https://img.shields.io/npm/dm/code-foundry?logo=npm&logoColor=white)](https://www.npmjs.com/package/code-foundry)
+[![CI](../../actions/workflows/ci.yml/badge.svg?branch=main)](../../actions/workflows/ci.yml)
+[![Latest GitHub release](https://img.shields.io/badge/GitHub%20release-latest-181717?logo=github)](../../releases/latest)
+
+`code-foundry` is a repository factory for TypeScript, Rust, Python, Solidity,
 and mixed-language projects. It installs agent-ready instructions, fast native
 testing, security automation, release workflows, hooks, and repository policy
 from one versioned package.
 
 ## Quick start
 
 ```bash
-npx repo-foundry init
+npx code-foundry init
 ```
 
 Or select the project profile explicitly:
 
 ```bash
-npx repo-foundry init \
+npx code-foundry init \
   --languages typescript,python \
   --features all \
   --package-manager bun
 ```
 
-Use `repo-foundry sync` to update an existing repository and
-`repo-foundry doctor` to validate it. Add `--dry-run` to preview changes.
+Use `code-foundry sync` to update an existing repository and
+`code-foundry doctor` to validate it. Add `--dry-run` to preview changes.
 
 ## Setup
 
@@ -83,7 +88,7 @@ For npm publication, set `npm_publish: true` and configure npm trusted publishin
 
 The release flow is: promote `staging` into `main`; let Release Please open or update the version/changelog PR; merge that PR to create the GitHub release and tag; then publish to npm only when `npm_publish: true`.
 
-For a repository that does not yet contain the scripts, the initializer can be invoked directly from the published template checkout or a downloaded copy of `init-repo.sh`; it fetches the matching sync helper automatically. The generated `.github/template.yml` is the stable configuration contract for a future npm/package wrapper around these same operations.
+For a repository that does not yet contain the scripts, the initializer can be invoked directly from the published package or a downloaded copy of `init-repo.sh`; it fetches the matching sync helper automatically. The generated `.github/template.yml` is the stable configuration contract used by the package and later syncs.
 
 CI formatting and linting use the preloaded `ubuntu-latest` runner by default because dependency setup is usually faster there. Set `REPO_FOUNDRY_FAST_RUNNER=ubuntu-slim` only after measuring a repository where the lean image is faster; use `ubuntu-latest` for dependency-heavy or native-toolchain projects.
 

package.json

@@ -1,12 +1,12 @@
 {
-  "name": "repo-foundry",
+  "name": "code-foundry",
   "version": "0.1.4",
   "description": "A fast, language-aware repository factory for agent-ready workflows, testing, security, and release automation.",
   "type": "module",
   "license": "AGPL-3.0-or-later",
   "packageManager": "bun@1.3.14",
   "bin": {
-    "repo-foundry": "src/cli.mjs"
+    "code-foundry": "src/cli.mjs"
   },
   "files": [
     "src",

src/cli.mjs

@@ -7,12 +7,12 @@ import { fileURLToPath } from 'node:url'
 
 const packageRoot = resolve(fileURLToPath(new URL('..', import.meta.url)))
 
-const usage = `repo-foundry — initialize and maintain agent-ready repositories
+const usage = `code-foundry — initialize and maintain agent-ready repositories
 
 Usage:
-  repo-foundry init [options]
-  repo-foundry sync [options]
-  repo-foundry doctor [--target PATH]
+  code-foundry init [options]
+  code-foundry sync [options]
+  code-foundry doctor [--target PATH]
 
 Init/sync options:
   --target PATH             Repository directory (default: current directory)
@@ -31,7 +31,7 @@ Init/sync options:
 `
 
 function fail(message) {
-  console.error(`repo-foundry: ${message}`)
+  console.error(`code-foundry: ${message}`)
   process.exit(2)
 }