Update and rename step.md to aura_mcp-poem.md

[osmandkitay]

Ode to AURA & MCP

🚀 Pull Request

Thank you for contributing to AURA Protocol! Your contribution helps build a more open, interoperable web.

📋 Description

What does this PR do?

Why is this change needed?

How does this change work?

🎯 Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update (changes to documentation only)
• 🎨 Code style/formatting (changes that do not affect the meaning of the code)
• ♻️ Refactoring (code change that neither fixes a bug nor adds a feature)
• ⚡ Performance improvement
• 🧪 Test addition/improvement
• 🔧 Build/CI/tooling changes
• 🌐 Community/project management

📦 Package Impact

• @aura/protocol (Core TypeScript interfaces and JSON Schema)
• reference-server (Next.js reference implementation)
• reference-client (Example client with LLM integration)
• CLI tools (aura-validate)
• Documentation
• Multiple packages
• Project infrastructure

🔗 Related Issues

• Fixes #
• Relates to #

🧪 Testing

Test Coverage:

• All existing tests pass
• New tests added for new functionality
• Tests cover edge cases
• Manual testing performed

Testing Performed:

• Unit tests:
• Integration tests:
• Manual testing:
• Cross-platform testing:

Test Commands:

# Commands used to test this change
pnpm test --run
pnpm --filter affected-package test

📖 Documentation

• Code comments updated/added
• README.md updated
• Package-specific documentation updated
• API documentation updated
• Examples updated/added
• No documentation changes needed

✅ Checklist

Code Quality:

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works

Protocol Compliance:

• Changes maintain backward compatibility (or breaking changes are clearly documented)
• JSON Schema updated if TypeScript interfaces changed
• URI Template/JSON Pointer compliance maintained (RFC 6570, RFC 6901)
• Reference implementations updated to reflect protocol changes

Project Standards:

• My commits have descriptive messages
• I have updated the version numbers appropriately (if applicable)
• I have checked that my changes don't break existing functionality

🔄 Breaking Changes

Is this a breaking change?

• Yes, this introduces breaking changes
• No, this is backward compatible

If yes, describe the breaking changes:

Migration Guide:

// Before
const oldWay = {};

// After  
const newWay = {};

🎪 Use Cases & Examples

Example Usage:

// Show how your changes would be used
import { NewFeature } from '@aura/protocol';

const example = new NewFeature({
  // configuration
});

Benefits:

📊 Performance Impact

• No performance impact
• Performance improvement (describe)
• Potential performance impact (describe and justify)

Benchmarks/Measurements:

🌍 Community Impact

Who benefits from this change?

• New AURA users
• Experienced implementers
• Framework integrators
• Tool builders
• All users

Community Considerations:

🔒 Security Considerations

• No security implications
• Security improvement
• Potential security impact (describe)

Security Review:

📝 Additional Notes

Implementation Details:

Future Considerations:

Questions for Reviewers:

---

🤝 Contributor Agreement

By submitting this pull request, I confirm that:

• I have read and agree to follow the project's Code of Conduct
• I have read the Contributing Guidelines
• My contribution is licensed under the MIT License
• I understand that my contribution may be used in derivative works

---

Thank you for contributing to AURA Protocol! 🚀

Building a more open, interoperable web together.