Merge pull request #2 from renbytes/dev-changeName

Change name

Author: bordumb

.gitignore

@@ -19,7 +19,7 @@ coverage/
 # Plugin / local logs
 # ------------------------------
 *.log
-spex_debug.log
+boot_debug.log
 
 # ------------------------------
 # Environment files

Cargo.lock

@@ -1,11 +1,11 @@
 ### FILE: Cargo.toml
 [package]
-name = "spex-rust"
+name = "boot-rust"
 version = "0.1.0"
 edition = "2021"
 
 [[bin]]
-name = "spex-rust"
+name = "boot-rust"
 path = "src/main.rs"
 
 [dependencies]

Cargo.toml

@@ -1,12 +1,12 @@
-# Spex-Rust Developer Guide
+# BootCode-Rust Developer Guide
 
-This guide provides technical details for developing and troubleshooting the `spex-rust` plugin.
+This guide provides technical details for developing and troubleshooting the `boot-rust` plugin.
 
 ---
 
 ## The Handshake Contract
 
-`spex-core` discovers and communicates with plugins based on a simple contract:
+`boot-core` discovers and communicates with plugins based on a simple contract:
 
 - **First line on `stdout`**: Must be the handshake string in the format `1|1|tcp|HOST:PORT|grpc`.
 - **All other output**: All logs, warnings, and errors **must** be sent to `stderr`. This keeps `stdout` clean so the handshake is not corrupted.
@@ -18,8 +18,8 @@ This guide provides technical details for developing and troubleshooting the `sp
 You can quickly test that the binary is producing the correct handshake and that logs are properly sent to `stderr`.
 
 ```bash
-# From the spex-rust project root, run the release binary and grab the first line of stdout
-./target/release/spex-rust 2>/dev/null | head -1
+# From the boot-rust project root, run the release binary and grab the first line of stdout
+./target/release/boot-rust 2>/dev/null | head -1
 ```
 
 **Expected Output:**
@@ -34,36 +34,36 @@ You can quickly test that the binary is producing the correct handshake and that
 
 ## Debugging Plugin Discovery
 
-`spex-core` discovers the plugin by finding an executable named `spex-rust` on its `PATH`.
+`boot-core` discovers the plugin by finding an executable named `boot-rust` on its `PATH`.
 
-### Verify what `spex-core` Sees
+### Verify what `boot-core` Sees
 
-From the `spex-core` directory, run this command to see which `spex-rust` executable Poetry's environment will use:
+From the `boot-core` directory, run this command to see which `boot-rust` executable Poetry's environment will use:
 
 ```bash
-poetry run which -a spex-rust
+poetry run which -a boot-rust
 ```
 
 ### Alternative: Running Without Installing
 
-For rapid testing, you can run `spex-core` and temporarily add your local plugin build to the `PATH` for that single command:
+For rapid testing, you can run `boot-core` and temporarily add your local plugin build to the `PATH` for that single command:
 
 ```bash
-# Run this from the spex-core directory
-poetry run env PATH="/path/to/your/spex-rust/target/release:$PATH" \
-  spex generate my_rust_spec.toml
+# Run this from the boot-core directory
+poetry run env PATH="/path/to/your/boot-rust/target/release:$PATH" \
+  boot generate my_rust_spec.toml
 ```
 
 ### Removing Stale Binaries
 
-If `which spex-rust` points to an old version, remove it:
+If `which boot-rust` points to an old version, remove it:
 
 ```bash
 # If installed via cargo
-cargo uninstall spex-rust
+cargo uninstall boot-rust
 
 # Or remove a manually copied file
-rm -f ~/.cargo/bin/spex-rust
+rm -f ~/.cargo/bin/boot-rust
 
 # Clear the shell's command cache
 hash -r
@@ -79,8 +79,8 @@ hash -r
 
 ---
 
-## Common `spex-core` Errors
+## Common `boot-core` Errors
 
-- **`Plugin executable not found`**: This is a `PATH` issue. `spex-core` cannot find the `spex-rust` binary. Ensure you have run `cargo install --path . --force` and that `~/.cargo/bin` is in your shell's `PATH`.
+- **`Plugin executable not found`**: This is a `PATH` issue. `boot-core` cannot find the `boot-rust` binary. Ensure you have run `cargo install --path . --force` and that `~/.cargo/bin` is in your shell's `PATH`.
 
 - **`Invalid handshake` / `not enough values to unpack`**: This means the plugin wrote something to `stdout` before the handshake string. Use the "Testing the Binary" command above to verify the output is clean.

DEVELOPER_GUIDE.md

@@ -1,10 +1,10 @@
-# spex-rust
+# boot-rust
 
-A "Prompt Provider" plugin for **Spex**.
+A "Prompt Provider" plugin for **BootCode**.
 
-This Rust application is a lightweight gRPC server that serves language-specific prompt components to `spex-core`. Its sole responsibility is to provide the building blocks that the core application uses to construct high-quality prompts for generating Rust code.
+This Rust application is a lightweight gRPC server that serves language-specific prompt components to `boot-core`. Its sole responsibility is to provide the building blocks that the core application uses to construct high-quality prompts for generating Rust code.
 
-- **Handshake (stdout)**: Prints a single handshake line required by `spex-core` to establish a connection.
+- **Handshake (stdout)**: Prints a single handshake line required by `boot-core` to establish a connection.
 - **Logs (stderr)**: All logging is directed to stderr to keep stdout clean.
 - **Prompts**: All prompt logic is contained in simple text files within the `/prompts` directory.
 
@@ -21,20 +21,20 @@ This Rust application is a lightweight gRPC server that serves language-specific
 cargo build --release
 ```
 
-### Install for `spex-core`:
+### Install for `boot-core`:
 
-To make the `spex-rust` executable discoverable by `spex-core`, install it to your cargo binary path.
+To make the `boot-rust` executable discoverable by `boot-core`, install it to your cargo binary path.
 
 ```bash
 # Install the binary
 cargo install --path . --force
 
 # Verify it's in your path
-which spex-rust
+which boot-rust
 ```
 
 Expected output:
 ```
-spex-rust % which spex-rust
-/Users/your_user_name/.cargo/bin/spex-rust
+boot-rust % which boot-rust
+/Users/your_user_name/.cargo/bin/boot-rust
 ```