Remove emoji usage from CLI, TUI, and documentation

[italoag]

Summary

• replace emoji-based status messages in CLI wallet generation, benchmarking, and KDF reporting with plain text
• update TUI components and logging to render textual indicators instead of emoji
• scrub README and KDF documentation of emoji icons to keep messaging consistent

Testing

• go test ./...

---

https://chatgpt.com/codex/tasks/task_e_68e6cd4106ec8331b887d6afe75f5c04

[amazon-q-developer]

⏳ Code review in progress. Analyzing for code quality issues and best practices. Detailed findings will be posted upon completion.

Using Amazon Q Developer for GitHub

Amazon Q Developer¹ is an AI-powered assistant that integrates directly into your GitHub workflow, enhancing your development process with intelligent features for code development, review, and transformation.

Slash Commands

Command	Description
/q <message>	Chat with the agent to ask questions or request revisions
/q review	Requests an Amazon Q powered code review
/q help	Displays usage information

Features

Agentic Chat
Enables interactive conversation with Amazon Q to ask questions about the pull request or request specific revisions. Use /q <message> in comment threads or the review body to engage with the agent directly.

Code Review
Analyzes pull requests for code quality, potential issues, and security concerns. Provides feedback and suggested fixes. Automatically triggered on new or reopened PRs (can be disabled for AWS registered installations), or manually with /q review slash command in a comment.

Customization

You can create project-specific rules for Amazon Q Developer to follow:

1. Create a .amazonq/rules folder in your project root.
2. Add Markdown files in this folder to define rules (e.g., cdk-rules.md).
3. Write detailed prompts in these files, such as coding standards or best practices.
4. Amazon Q Developer will automatically use these rules when generating code or providing assistance.

Example rule:

All Amazon S3 buckets must have encryption enabled, enforce SSL, and block public access.
All Amazon DynamoDB Streams tables must have encryption enabled.
All Amazon SNS topics must have encryption enabled and enforce SSL.
All Amazon SNS queues must enforce SSL.

Feedback

To provide feedback on Amazon Q Developer, create an issue in the Amazon Q Developer public repository.

For more detailed information, visit the Amazon Q for GitHub documentation.

Footnotes

1. Amazon Q Developer uses generative AI. You may need to verify generated code before using it in your environment. See the AWS Responsible AI Policy. ↩

[amazon-q-developer]

Code Review Summary

This PR successfully removes emoji usage across the CLI, TUI, and documentation components, which improves accessibility and ensures consistent rendering across different terminals and environments. The changes are comprehensive and well-executed overall.

Critical Issues Found:

1. Makefile Syntax Error: The tab character was replaced with spaces in the demo target, breaking Make syntax requirements
2. Function Naming: The getSecurityLevelIcon function name should be updated to reflect its new text-based purpose

Suggestions for Improvement:

1. Consistent Status Indicators: Consider adding text-based prefixes (e.g., "[SUCCESS]", "[ERROR]") to maintain visual distinction in TUI components
2. Documentation Completeness: Some documentation sections still contain checkmarks and warning symbols that should be converted to text
3. Log Level Consistency: The debug logging function should include a "DEBUG:" prefix for consistency

Positive Aspects:

• Comprehensive coverage across all components
• Maintains functionality while improving accessibility
• Good preservation of information hierarchy through text formatting
• Consistent approach to emoji removal

The changes align well with the stated goal of removing emoji usage. Once the critical Makefile syntax issue is addressed, this will be a solid improvement to the codebase's accessibility and cross-platform compatibility.