fix(ui): don't redact valid repo/login names in miner commands

[galuis116]

Closes #456.

sanitizeMinerCommand's private-term redaction had an optional value-assignment group, so it matched bare standalone words (wallet, hotkey, coldkey, mnemonic, trust-score, …). Since login/repoFullName are already validated by safeGitHubLogin/safeRepoFullName, a legitimate name containing one of those words got corrupted while the command stayed marked copyable: true, state: "ready" — so the user copies a broken command with [redacted] in place of their real repo/login. Common in a Bittensor/crypto ecosystem (e.g. metamask/wallet-adapter).

Changes

• Require the term=value / term: value form so only real secret leakage is redacted, not validated names.
• Add a test with login trust-score and repo metamask/wallet-adapter asserting the names survive and the command stays runnable.

Verification

• Full unit suite green (1247 passed). The new test fails against the old code (old output redacted wallet-adapter → [redacted]-adapter).

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#457 is no longer open.	No action.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[JSONbored]

@galuis116 the sanitizer fix matches the bug in #456.

A few notes:

• Requiring term=value / term: value before redaction preserves valid repo/login names like wallet-adapter and trust-score.
• The regression test covers the broken command case well.
• This still changes visible command output in the UI, so the PR needs screenshot evidence in the PR description.

Required changes:

• Add JPG/PNG UI evidence showing the affected command surface with a valid repo/login containing one of the previously redacted terms.
• Keep the screenshot in the PR description, not committed to the repo.

Validation expected:

• Rerun the focused miner command test and the UI checks relevant to the command surface.

[galuis116]

@galuis116 the sanitizer fix matches the bug in #456.

A few notes:

• Requiring term=value / term: value before redaction preserves valid repo/login names like wallet-adapter and trust-score.
• The regression test covers the broken command case well.
• This still changes visible command output in the UI, so the PR needs screenshot evidence in the PR description.

Required changes:

• Add JPG/PNG UI evidence showing the affected command surface with a valid repo/login containing one of the previously redacted terms.
• Keep the screenshot in the PR description, not committed to the repo.

Validation expected:

• Rerun the focused miner command test and the UI checks relevant to the command surface.

screenshot added.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[JSONbored]

@galuis116 this is ready from my side on the rebased head.\n\nA few notes:\n- The sanitizer now targets assignment-style sensitive values instead of redacting legitimate repo/login words.\n- The regression test covers the important Bittensor-adjacent case: login trust-score and repo metamask/wallet-adapter stay runnable and copyable.\n- I rebased the branch through GitHub update-branch, and the current head has green validate and non-Gittensory checks.\n\nNo code changes requested.