Update zapstore config file

[grunch]

Update changelog with new version

Summary by CodeRabbit

• New Features

  • Multi-Mostro instance support with multi-node connectivity
  • Editable premium/discount indicators
  • Expanded payment methods
  • Updated screenshots and UI

• Bug Fixes

  • Improved metadata verification and persistence
  • Enhanced price and order validation
  • Restored chat functionality
  • Fixed payment submission behavior

• Changed

  • Updated Settings screen node selector
  • Updated app/store metadata: website, expanded images, and supported protocol flags

• Documentation

  • Added Multi-Mostro Support Guide
  • Updated compliance documentation

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This PR adds a v1.1.1 changelog entry and restructures zapstore.yaml, removing several top-level fields (homepage, name, summary, description, icon, changelog, blossom_servers, assets) and introducing grouped fields (website, images, supported_nips, metadata_sources).

Changes

Cohort / File(s)	Summary
Changelog Entry CHANGELOG.md	Adds v1.1.1 release notes: Multi‑Mostro instance support, editable premium/discount indicator, expanded payment methods, updated screenshots, multiple fixes (metadata persistence, price/order validation, chat restoration, payment submission), settings node selector changes, and documentation additions.
Manifest Restructuring zapstore.yaml	Replaces many top-level manifest fields with a consolidated structure: removes homepage, name, summary, description, icon, changelog, blossom_servers, assets; adds website, unified images list, supported_nips, and metadata_sources. Reflows tags and image entries.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Add zapstore spec file #302: Edits zapstore.yaml fields (homepage/name/description/icon/changelog/assets) that this PR restructures.
• Update zapstore.yaml file with split apk files #362: Modifies manifest keys like blossom_servers and APK asset entries that this PR removes/consolidates.

Poem

🐇✨ I hopped through changelogs, nibbling lines so spry,
New images gathered, old keys waved goodbye,
A website stitched, NIPs lined in a row,
Mostro hums along as versions gently grow,
🥕📦 — from a rabbit's grin, release notes aglow.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title 'Update zapstore config file' is only partially related to the changeset. While zapstore.yaml is modified, the PR's primary objective is to update the changelog with a new version (v1.1.1), which is a separate and significant change not reflected in the title.	Consider revising the title to reflect both main changes, such as 'Update CHANGELOG and zapstore config for v1.1.1' to better represent the full scope of the PR.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-zapstore-config-file

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Around line 8-33: The CHANGELOG entry for "AGENTS.md" is missing the PR
reference and colon; update the line for the "**AGENTS.md** Code block language
specifier for MD040 compliance" entry to match the pattern used elsewhere by
adding the PR number in parentheses (e.g. (`#NNN`)) and a colon before the
description — locate the line referencing "AGENTS.md" in the v1.1.1 changelog
and change it to the format "**AGENTS.md** (`#PR`): Code block language specifier
for MD040 compliance".