chore: add archive notice

[ymc9]

Summary by CodeRabbit

• Documentation
  • This repository is now archived and unpublished. Development for V3 has been merged into the main repository.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A documentation note was added to README.md indicating that V3 development has merged back to the main repository and this repository is archived and unpublished.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Added note indicating V3 development has merged to the main repository and this repository is archived and unpublished.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 The V3 journey comes full circle round,
Back to the main where it's homeward bound,
This archive now rests, its purpose complete,
A gentle goodbye, bittersweet and neat! 🏛️✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/archive-notice

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @ymc9's task —— View job

---

Pull Request Review

Todo List:

• Read the modified README.md file to understand current state
• Examine the specific changes made (git diff)
• Analyze changes against review criteria
• Provide comprehensive feedback and recommendations

Review Summary

This PR adds a critical archive notice to the README.md file, informing users that V3 development has been merged back to the main repository and this repo is now archived.

Detailed Review

✅ Code Quality & Best Practices

• Clean implementation: The change is minimal and focused - adds exactly what's needed without unnecessary modifications
• Appropriate placement: The warning is positioned prominently at the top of the document, immediately after the header section
• Consistent formatting: Uses the existing blockquote syntax pattern (>) that's already used elsewhere in the README

✅ Content & Documentation

• Clear messaging: The warning uses appropriate visual indicators (⚠️⚠️⚠️) and bold formatting to grab attention
• Actionable information: Provides a direct link to the main repository where users should go
• Unambiguous language: Clearly states the repository status and what users should expect

✅ User Experience

• High visibility: Placed strategically where users will see it immediately when visiting the repository
• Prevents confusion: Addresses potential user confusion about which repository to use for ongoing development

✅ No Concerns Found

• Security: No security implications (documentation-only change)
• Performance: No performance impact (static README content)
• Test coverage: Not applicable for documentation changes
• Breaking changes: None - purely additive documentation update

Recommendations

✅ Current Implementation is Excellent

The implementation is well-executed and needs no changes. The archive notice:

• Is prominently positioned
• Uses clear, direct language
• Provides actionable next steps for users
• Follows good documentation practices

💡 Optional Future Considerations

While not necessary for this PR, consider adding a similar notice to:

• Package.json descriptions (if not already planned)
• GitHub repository description/topics
• Any published npm packages (deprecation notices)

Conclusion

Approved ✅ - This is a well-implemented archive notice that effectively communicates the repository status to users. The change is clean, necessary, and properly executed.

---

[Copilot]

Pull request overview

Adds an archive notice to the repository README to direct users to the main ZenStack repository going forward.

Changes:

• Add a prominent archive/deprecation notice with a link to the main repo.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The phrasing "V3's development is merged back" is grammatically awkward. Consider using past/perfect tense (e.g., "has been merged back" / "was merged back") to make the notice read clearly.

Suggested change

	> ⚠️⚠️⚠️ **V3's development is merged back to the [main repo](https://github.com/zenstackhq/zenstack). This repository is archived and will no longer receive updates.**
	> ⚠️⚠️⚠️ **V3's development has been merged back into the [main repo](https://github.com/zenstackhq/zenstack). This repository is archived and will no longer receive updates.**