fix: zapstore.yaml to work with zsp

[im-adithya]

Summary by CodeRabbit

• Chores
  • Updated configuration schema with field reorganization and format migration.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 23db8a4a-9711-4747-b9b9-347d2f0148f0

📥 Commits

Reviewing files that changed from the base of the PR and between 573be3b and 59b8234.

📒 Files selected for processing (1)

• zapstore.yaml

---

📝 Walkthrough

Walkthrough

zapstore.yaml is migrated from the zapstore-cli format: the identifier and blossom_server fields are removed, the remaining fields (repository, name, description, license) are reordered, and a migration comment is added at the top of the file.

Changes

zapstore.yaml schema migration

Layer / File(s)	Summary
Remove deprecated fields and reorder metadata zapstore.yaml	Removes identifier and blossom_server fields, reorders repository, name, description, license keys, and adds a # Migrated from zapstore-cli format header comment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 Hop, hop, the old fields are gone,
identifier and blossom_server moved on.
The YAML is tidy, the schema feels right,
repository first, in the fresh morning light.
A comment declares: "migrated today!" 🌿

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/zapstore

---

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.}