refactor!: rename tetra to flash

.claude/settings.json

@@ -4,16 +4,16 @@
   },
   "enableAllProjectMcpServers": true,
   "enabledMcpjsonServers": [
-    "tetra-code-intel"
+    "flash-code-intel"
   ],
   "permissions": {
     "allow": [
-      "mcp__tetra-code-intel__find_by_decorator",
-      "mcp__tetra-code-intel__find_symbol",
-      "mcp__tetra-code-intel__get_class_interface",
-      "mcp__tetra-code-intel__list_classes",
-      "mcp__tetra-code-intel__list_file_symbols",
-      "mcp__tetra-code-intel__parse_test_output",
+      "mcp__flash-code-intel__find_by_decorator",
+      "mcp__flash-code-intel__find_symbol",
+      "mcp__flash-code-intel__get_class_interface",
+      "mcp__flash-code-intel__list_classes",
+      "mcp__flash-code-intel__list_file_symbols",
+      "mcp__flash-code-intel__parse_test_output",
       "Bash(./scripts/validate-wheel.sh:*)",
       "Bash(git diff:*)",
       "Bash(git fetch:*)",

.claude/skills/tetra-explorer/SKILL.md → .claude/skills/flash-explorer/SKILL.md

@@ -1,9 +1,9 @@
-# Tetra-rp Framework Explorer Skill
+# Flash Framework Explorer Skill
 
 ## When to Use
 
 Use this skill when:
-- Exploring the tetra-rp framework codebase
+- Exploring the runpod-flash framework codebase
 - Understanding class hierarchies and relationships
 - Finding where methods or classes are defined
 - Checking what decorators are used in the codebase
@@ -74,7 +74,7 @@ After running tests (`make test-unit`, `make test`, `pytest`), **ALWAYS use `par
 3. Only read the full file if you need implementation details
 
 **Bad - Reading files directly:**
-1. Read entire `src/tetra_rp/core/resources/serverless.py` (500+ tokens)
+1. Read entire `src/runpod_flash/core/resources/serverless.py` (500+ tokens)
 2. Search manually for ServerlessEndpoint
 
 **Good - Parse test output:**

.github/workflows/release-please.yml

@@ -76,7 +76,7 @@ jobs:
 
     environment:
       name: pypi-production
-      url: https://pypi.org/project/tetra-rp/
+      url: https://pypi.org/project/runpod-flash/
 
     steps:
       - name: Checkout code

.mcp.json

@@ -1,6 +1,6 @@
 {
   "mcpServers": {
-    "tetra-code-intel": {
+    "flash-code-intel": {
       "command": "uv",
       "args": [
         "run",
@@ -11,3 +11,4 @@
     }
   }
 }
+

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.25.2"
+  ".": "0.25.1"
 }

CLAUDE.md

@@ -1,13 +1,13 @@
-# tetra-rp Project Configuration
+# runpod-flash Project Configuration
 
 ## Claude Code Configuration
 
-When using Claude Code on this project, always prefer the tetra-code-intel MCP tools for code exploration instead of using Explore agents or generic search:
+When using Claude Code on this project, always prefer the flash-code-intel MCP tools for code exploration instead of using Explore agents or generic search:
 
-- `mcp__tetra-code-intel__find_symbol` - Search for classes, functions, methods by name
-- `mcp__tetra-code-intel__get_class_interface` - Inspect class methods and properties
-- `mcp__tetra-code-intel__list_file_symbols` - View file structure without reading full content
-- `mcp__tetra-code-intel__list_classes` - Explore the class hierarchy
-- `mcp__tetra-code-intel__find_by_decorator` - Find decorated items (e.g., `@property`, `@remote`)
+- `mcp__flash-code-intel__find_symbol` - Search for classes, functions, methods by name
+- `mcp__flash-code-intel__get_class_interface` - Inspect class methods and properties
+- `mcp__flash-code-intel__list_file_symbols` - View file structure without reading full content
+- `mcp__flash-code-intel__list_classes` - Explore the class hierarchy
+- `mcp__flash-code-intel__find_by_decorator` - Find decorated items (e.g., `@property`, `@remote`)
 
 **Do NOT** use the Task tool with the "Explore" subagent for codebase exploration. Use the MCP tools directly instead.

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to tetra-rp
+# Contributing to runpod-flash
 
 ## Development Setup
 
@@ -12,8 +12,8 @@
 
 ```bash
 # Clone the repository
-git clone https://github.com/your-org/tetra-rp.git
-cd tetra-rp
+git clone https://github.com/your-org/runpod-flash.git
+cd runpod-flash
 
 # Install dependencies and package in editable mode
 make dev
@@ -278,7 +278,7 @@ make quality-check
 
 **Coverage threshold failures**
 - Use `--no-cov` flag: `uv run pytest tests/unit/test_file.py -v --no-cov`
-- Or test specific module: `uv run pytest --cov=src/tetra_rp/module`
+- Or test specific module: `uv run pytest --cov=src/runpod_flash/module`
 
 ## Release Process
 
@@ -310,7 +310,7 @@ When reviewing code, consider:
 
 ## Getting Help
 
-- Check existing [Issues](https://github.com/your-org/tetra-rp/issues)
+- Check existing [Issues](https://github.com/your-org/runpod-flash/issues)
 - Review [README.md](README.md) for usage examples
 - See [TESTING.md](TESTING.md) for testing details
 - See [RELEASE_SYSTEM.md](RELEASE_SYSTEM.md) for release process
@@ -354,7 +354,7 @@ uv run python scripts/code_intel.py interface LiveServerless
 **List symbols in a file:**
 
 ```bash
-uv run python scripts/code_intel.py file tetra_rp/decorators.py
+uv run python scripts/code_intel.py file runpod_flash/decorators.py
 ```
 
 **List all symbols:**
@@ -373,7 +373,7 @@ Claude Code automatically uses the MCP code intelligence server when exploring t
 - **85% token reduction**: No need to read full files for structure queries
 - **Instant results**: Direct database queries instead of file parsing
 
-The MCP server is configured in `.mcp.json` and automatically activated when you open this project in Claude Code. Use the `/tetra-explorer` skill to get guidance on best exploration practices.
+The MCP server is configured in `.mcp.json` and automatically activated when you open this project in Claude Code. Use the `/flash-explorer` skill to get guidance on best exploration practices.
 
 Available MCP tools:
 - `find_symbol` - Search for classes, functions, methods
@@ -405,7 +405,7 @@ uv run python scripts/code_intel.py interface <ClassName>
 ```bash
 # Instead of reading full file (500+ tokens):
 # Do this query first (50 tokens):
-uv run python scripts/code_intel.py file tetra_rp/decorators.py
+uv run python scripts/code_intel.py file runpod_flash/decorators.py
 
 # Then only read full file if implementation details needed
 ```

Makefile

@@ -73,11 +73,11 @@ test-integration-serial: # Run integration tests serially (for debugging)
 	uv run pytest tests/integration/ -v -m integration
 
 test-coverage: # Run tests with coverage report (parallel by default)
-	uv run pytest tests/ -v -n auto -m "not serial" --cov=tetra_rp --cov-report=xml
-	uv run pytest tests/ -v -m "serial" --cov=tetra_rp --cov-append --cov-report=term-missing
+	uv run pytest tests/ -v -n auto -m "not serial" --cov=runpod_flash --cov-report=xml
+	uv run pytest tests/ -v -m "serial" --cov=runpod_flash --cov-append --cov-report=term-missing
 
 test-coverage-serial: # Run tests with coverage report (serial execution)
-	uv run pytest tests/ -v --cov=tetra_rp --cov-report=term-missing
+	uv run pytest tests/ -v --cov=runpod_flash --cov-report=term-missing
 
 test-fast: # Run tests with fast-fail mode and parallel execution
 	uv run pytest tests/ -v -x --tb=short -n auto
@@ -116,8 +116,8 @@ ci-quality-github: # Quality checks with GitHub Actions formatting (parallel by
 	uv run ruff check . --output-format=github
 	@echo "::endgroup::"
 	@echo "::group::Test suite with coverage"
-	uv run pytest tests/ --junitxml=pytest-results.xml -v -n auto -m "not serial" --cov=tetra_rp --cov-report=xml --cov-fail-under=0
-	uv run pytest tests/ --junitxml=pytest-results.xml -v -m "serial" --cov=tetra_rp --cov-append --cov-report=term-missing
+	uv run pytest tests/ --junitxml=pytest-results.xml -v -n auto -m "not serial" --cov=runpod_flash --cov-report=xml --cov-fail-under=0
+	uv run pytest tests/ --junitxml=pytest-results.xml -v -m "serial" --cov=runpod_flash --cov-append --cov-report=term-missing
 	@echo "::endgroup::"
 
 ci-quality-github-serial: # Serial quality checks for GitHub Actions (for debugging)
@@ -128,5 +128,5 @@ ci-quality-github-serial: # Serial quality checks for GitHub Actions (for debugg
 	uv run ruff check . --output-format=github
 	@echo "::endgroup::"
 	@echo "::group::Test suite with coverage (serial)"
-	uv run pytest tests/ --junitxml=pytest-results.xml -v --cov=tetra_rp --cov-report=term-missing
+	uv run pytest tests/ --junitxml=pytest-results.xml -v --cov=runpod_flash --cov-report=term-missing
 	@echo "::endgroup::"

README.md

@@ -1,16 +1,3 @@
-# ⚠️ DEPRECATED: tetra-rp
-
-> **This package is deprecated.** The final release of `tetra-rp` is version 0.25.2. All future development and releases will be under the new package name `runpod-flash`.
->
-> **Migration Required:** To upgrade, install the new package and update your imports:
-> ```bash
-> pip uninstall tetra-rp
-> pip install runpod-flash
-> ```
-> Then update your imports from `from tetra_rp import ...` to `from runpod_flash import ...`
->
-> See [runpod/flash](https://github.com/runpod/flash) for the new repository.
-
 # Flash: Serverless computing for AI workloads
 
 Runpod Flash is a Python SDK that streamlines the development and deployment of AI workflows on Runpod's [Serverless infrastructure](http://docs.runpod.io/serverless/overview). Write Python functions locally, and Flash handles the infrastructure, provisioning GPUs and CPUs, managing dependencies, and transferring data, allowing you to focus on building AI applications.
@@ -56,14 +43,8 @@ Before you can use Flash, you'll need:
 
 ### Step 1: Install Flash
 
-> **Note:** This documentation describes the deprecated `tetra-rp` package. For new projects, use `runpod-flash`:
-> ```bash
-> pip install runpod-flash
-> ```
-
-For the legacy package:
 ```bash
-pip install tetra_rp
+pip install runpod-flash
 ```
 
 ### Step 2: Set your API key
@@ -86,7 +67,7 @@ Add the following code to a new Python file:
 
 ```python
 import asyncio
-from tetra_rp import remote, LiveServerless
+from runpod_flash import remote, LiveServerless
 from dotenv import load_dotenv
 
 # Uncomment if using a .env file
@@ -310,7 +291,7 @@ async def main():
 Flash provides fine-grained control over hardware allocation through configuration objects:
 
 ```python
-from tetra_rp import LiveServerless, GpuGroup, CpuInstanceType, PodTemplate
+from runpod_flash import LiveServerless, GpuGroup, CpuInstanceType, PodTemplate
 
 # GPU configuration
 gpu_config = LiveServerless(
@@ -364,7 +345,7 @@ results = await asyncio.gather(
 For API endpoints requiring low-latency HTTP access with direct routing, use load-balanced endpoints:
 
 ```python
-from tetra_rp import LiveLoadBalancer, remote
+from runpod_flash import LiveLoadBalancer, remote
 
 api = LiveLoadBalancer(name="api-service")
 
@@ -413,7 +394,7 @@ Flash orchestrates workflow execution through a sophisticated multi-step process
 `LiveServerless` resources use a fixed Docker image that's optimized for Flash runtime, and supports full remote code execution. For specialized environments that require a custom Docker image, use `ServerlessEndpoint` or `CpuServerlessEndpoint`:
 
 ```python
-from tetra_rp import ServerlessEndpoint
+from runpod_flash import ServerlessEndpoint
 
 custom_gpu = ServerlessEndpoint(
     name="custom-ml-env",
@@ -525,7 +506,7 @@ For information on load-balanced endpoints (required for Mothership and HTTP ser
 
 RunPod serverless has a **500MB deployment limit**. Exceeding this limit will cause deployment failures.
 
-Use `--exclude` to skip packages already in your worker-tetra Docker image:
+Use `--exclude` to skip packages already in your worker-flash Docker image:
 
 ```bash
 # For GPU deployments (PyTorch pre-installed)
@@ -539,7 +520,7 @@ flash build --exclude torch,torchvision,torchaudio
 - **CPU resources** → Python slim images have NO ML frameworks pre-installed
 - **Load-balanced** → Same as above, depends on GPU vs CPU variant
 
-See [worker-tetra](https://github.com/runpod-workers/worker-tetra) for base image details.
+See [worker-flash](https://github.com/runpod-workers/worker-flash) for base image details.
 
 ## Configuration
 
@@ -614,7 +595,7 @@ Some common GPU groups available through `GpuGroup`:
 
 ```python
 import asyncio
-from tetra_rp import remote, LiveServerless
+from runpod_flash import remote, LiveServerless
 
 # Simple GPU configuration
 gpu_config = LiveServerless(name="example-gpu-server")
@@ -653,7 +634,7 @@ if __name__ == "__main__":
 
 ```python
 import asyncio
-from tetra_rp import remote, LiveServerless, GpuGroup, PodTemplate
+from runpod_flash import remote, LiveServerless, GpuGroup, PodTemplate
 import base64
 
 # Advanced GPU configuration with consolidated template overrides
@@ -708,7 +689,7 @@ if __name__ == "__main__":
 
 ```python
 import asyncio
-from tetra_rp import remote, LiveServerless, CpuInstanceType
+from runpod_flash import remote, LiveServerless, CpuInstanceType
 
 # Simple CPU configuration
 cpu_config = LiveServerless(
@@ -756,7 +737,7 @@ if __name__ == "__main__":
 ```python
 import asyncio
 import base64
-from tetra_rp import remote, LiveServerless, CpuInstanceType, PodTemplate
+from runpod_flash import remote, LiveServerless, CpuInstanceType, PodTemplate
 
 # Advanced CPU configuration with template overrides
 data_processing_config = LiveServerless(
@@ -833,7 +814,7 @@ if __name__ == "__main__":
 
 ```python
 import asyncio
-from tetra_rp import remote, LiveServerless, GpuGroup, CpuInstanceType, PodTemplate
+from runpod_flash import remote, LiveServerless, GpuGroup, CpuInstanceType, PodTemplate
 
 # GPU configuration for model inference
 gpu_config = LiveServerless(
@@ -948,7 +929,7 @@ if __name__ == "__main__":
 ```python
 import os
 import asyncio
-from tetra_rp import remote, LiveServerless
+from runpod_flash import remote, LiveServerless
 
 # Configure Runpod resources
 runpod_config = LiveServerless(name="multi-stage-pipeline-server")
@@ -1107,6 +1088,6 @@ def fetch_data(url):
 This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
 
 <p align="center">
-  <a href="https://github.com/runpod/tetra-rp">Flash</a> •
+  <a href="https://github.com/runpod/runpod-flash">Flash</a> •
   <a href="https://runpod.io">Runpod</a>
 </p>

RELEASE_SYSTEM.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-The tetra-rp project uses a simple, reliable release automation system built on **Release Please v4** with quality gates and automated PyPI publishing via OIDC trusted publishing.
+The runpod-flash project uses a simple, reliable release automation system built on **Release Please v4** with quality gates and automated PyPI publishing via OIDC trusted publishing.
 
 ## Architecture
 

TESTING.md

@@ -8,7 +8,7 @@ uv pip install -e .
 
 # Development (complete - includes packaging validation)
 # Build wheel and install it to test CLI from anywhere
-cd /path/to/tetra-rp && uv build && pip install dist/tetra_rp-*.whl --force-reinstall
+cd /path/to/runpod_flash && uv build && pip install dist/runpod_flash-*.whl --force-reinstall
 cd /tmp && flash init test_project
 
 # Unit tests
@@ -38,11 +38,11 @@ make validate-wheel
 
 **Coverage threshold failures**
 - Use `--no-cov` flag for focused testing: `uv run pytest tests/unit/test_skeleton.py -v --no-cov`
-- Or test specific module: `uv run pytest --cov=src/tetra_rp/cli/utils/skeleton`
+- Or test specific module: `uv run pytest --cov=src/runpod_flash/cli/utils/skeleton`
 
 **Hidden files require explicit glob patterns**
 - Pattern `**/.*` needed in pyproject.toml to include `.env`, `.gitignore`, `.flashignore`
-- Verify with: `unzip -l dist/tetra_rp-*.whl | grep skeleton_template`
+- Verify with: `unzip -l dist/runpod_flash-*.whl | grep skeleton_template`
 
 ## Pre-Release Checklist