docs(keys): use the Nushell key-generation recipe #8

Merged
Claude-Run merged 1 commit from fix/MCPWEB-9-nushell-key-recipe into main 2026-08-02 16:24:18 +02:00
Member

The base64 key contract work spread openssl rand -base64 32 through the crate, but the house shell is Nushell and the equivalent random binary 32 | encode base64 needs no external binary. Both emit the same 44-character padded standard-base64 string, so this is a text change with no decoding behavior change.

Replaces the recipe in the decode_master_key and decode_session_key doc comments and base64 failure messages, and in the SessionSigner::from_env missing-key error. The runtime messages quote the pipeline in single quotes so the pipe cannot read as message punctuation. A new integration test guards the removal: it scans the sources and top-level docs for an OpenSSL recipe and asserts the two base64 failure messages carry the Nushell one.

#MCPWEB-9

The base64 key contract work spread `openssl rand -base64 32` through the crate, but the house shell is Nushell and the equivalent `random binary 32 | encode base64` needs no external binary. Both emit the same 44-character padded standard-base64 string, so this is a text change with no decoding behavior change. Replaces the recipe in the `decode_master_key` and `decode_session_key` doc comments and base64 failure messages, and in the `SessionSigner::from_env` missing-key error. The runtime messages quote the pipeline in single quotes so the pipe cannot read as message punctuation. A new integration test guards the removal: it scans the sources and top-level docs for an OpenSSL recipe and asserts the two base64 failure messages carry the Nushell one. #MCPWEB-9
docs(keys): use the Nushell key-generation recipe
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 25s
Create release / Create release from merged PR (pull_request) Has been skipped
aeec9e19c5
The base64 key contract work spread `openssl rand -base64 32` through the crate, but the house shell is Nushell and the equivalent `random binary 32 | encode base64` needs no external binary. Both emit the same 44-character padded standard-base64 string, so this is a text change with no decoding behavior change.

Replaces the recipe in the `decode_master_key` and `decode_session_key` doc comments and base64 failure messages, and in the `SessionSigner::from_env` missing-key error. The runtime messages quote the pipeline in single quotes so the pipe cannot read as message punctuation. A new integration test guards the removal: it scans the sources and top-level docs for an OpenSSL recipe and asserts the two base64 failure messages carry the Nushell one.

#MCPWEB-9
Claude-Run deleted branch fix/MCPWEB-9-nushell-key-recipe 2026-08-02 16:24:18 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pandoras-box/mcp-web!8
No description provided.