Fix/standardize advisor terminology 1618 - #1693
Conversation
|
@MILAN-123865 is attempting to deploy a commit to the csxark's projects Team on Vercel. A member of the Team first needs to authorize it. |
🎉 Thank You for Your ContributionHello @MILAN-123865, Thank you for submitting a Pull Request to CryptoViz. We appreciate the time and effort you've invested in contributing to the project. Your Pull Request has been received successfully and will be reviewed by the maintainers as soon as possible. 📋 Pull Request Checklist
Ensuring these requirements are met helps streamline the review process and enables maintainers to review your contribution more efficiently. ❤️ Support CryptoVizIf you find CryptoViz helpful, consider supporting the project by:
Your support helps increase the project's visibility and encourages continued development. Thank you for being a part of the CryptoViz community! Thank you once again for contributing to CryptoViz. We appreciate your support and look forward to reviewing your contribution. |
|
Warning Review limit reachedNext included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (18)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🎉 Pull Request MergedHello @MILAN-123865, Thank you for your contribution to CryptoViz. Your Pull Request has been reviewed and successfully merged into the project. We sincerely appreciate the time and effort you invested in improving the project. Contributions like yours help make CryptoViz better for the entire community. We look forward to your future contributions and hope to collaborate with you again. ❤️ Support CryptoVizIf you find CryptoViz helpful, consider supporting the project by:
Your support helps increase the project's visibility and encourages continued development. Thank you for being a part of the CryptoViz community! |
Pull Request
Description
Please provide a brief summary of your changes.
Related Issue
Closes #
Scope
This PR touches exactly one of the following. If it touches more than
one, split it into separate PRs — multi-scope PRs are the pattern that
introduces inconsistent architecture and will not be reviewed as-is.
lib/cipher/**)app/**,components/**)lib/workers/**,hooks/use*Worker.ts)docs/**,*.md, MDX content)tests/**)Changes Made
Testing
npm testpasses locally.npm run typecheckpasses locally.npm run lintpasses locally.lib/cipher/**file stays at or above 80%.A PR that adds functionality without a corresponding test in the same PR will not be merged. "Will add tests later" is not accepted.
Simulation vs. Live Data
Screenshots
If applicable, attach screenshots or screen recordings.
Checklist
Applicable Checklist
Complete the checklist matching the scope above, then paste the completed
checklist (or a link to it) here:
Architecture Review Checklist
Before adding another domain suite or feature suite, please identify and document the following to prevent code duplication:
Additional Notes
Add any additional information for reviewers here.
Description
This PR addresses fragmented application taxonomy by standardizing all algorithm selection and recommendation tools to use the canonical term Advisor. This brings the UI into strict alignment with Section 1 of
docs/product-vocabulary-architecture.md.Changes
app/advisor/page.tsx: Updated template parameters to featureAlgorithm Advisor(title/breadcrumbs) andDecision Support System(eyebrow).app/security-recommendation/page.tsx: Replaced "Engine" references withSecurity Architecture Advisor(title),Cryptographic Migration Advisor(eyebrow), andSecurity Advisor(breadcrumbs).components/layout/footer.tsx&lib/layout/navigation.ts: Verified layout boundaries to enforce uniform, predictable routing labels.Verification Results
Closes #1618