Update changelog and zapstore file

[grunch]

Summary by CodeRabbit

• Style
  • Minor formatting updates to changelog and configuration files to improve consistency and readability.

[coderabbitai]

Walkthrough

This PR contains two formatting adjustments: the changelog version heading is updated from [1.0.2] to [v1.0.2], and the zapstore manifest's feature list is restructured from top-level bullets to nested indented items. Both are cosmetic changes with no functional impact.

Changes

Cohort / File(s)	Change Summary
Manifest & Changelog Formatting CHANGELOG.md, zapstore.yaml	Updated changelog heading format to include version prefix (v1.0.2); restructured zapstore feature list from top-level to nested indented bullet format

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add zapstore spec file #302: Added the zapstore.yaml manifest file that this PR modifies with formatting updates.

Poem

🐰✨ A dash here, a v there,
Formatting polish with utmost care!
Nested lists now indent with grace,
Version tags find their proper place.
Small tweaks that make the whole diff fair! 📋

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Update changelog and zapstore file" is directly related to the changeset, as it accurately identifies the two files being modified: CHANGELOG.md and zapstore.yaml. The title is concise, clear, and avoids unnecessary noise. However, the title is only partially related in that it describes which files were updated without specifying the nature of the updates—the changes consist of formatting adjustments (version heading format change and list indentation restructuring) rather than substantive content changes. The title is specific enough that a teammate reviewing pull request history would clearly understand which files were altered, even if not the exact nature of those alterations.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changelog-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.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38d677f and d4816d5.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• zapstore.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (1)

zapstore.yaml (1)

13-21: Feature list formatting restructured cleanly.

The feature list has been reformatted with proper indentation as nested items within the description field. The YAML syntax is valid, emojis are preserved, and the change is purely cosmetic with no functional impact on the manifest structure.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Inconsistent version prefix breaks changelog format convention.

Line 8 introduces [v1.0.2] with a v prefix, but all other version headings in the file (e.g., [1.0.1] on line 56, [1.0.0+14] on line 97) omit this prefix. This breaks the established formatting pattern and could impact tooling that parses the changelog.

Either remove the v prefix from this entry to match the existing convention, or update all version headings consistently (larger scope change).

---

🏁 Script executed:

#!/bin/bash
# Verify the changelog format and version heading consistency
if [ -f "CHANGELOG.md" ]; then
  echo "=== Line 8 and surrounding context ==="
  sed -n '6,10p' CHANGELOG.md
  
  echo ""
  echo "=== Version headings across file ==="
  grep -n "^##" CHANGELOG.md | head -20
else
  echo "CHANGELOG.md not found"
fi

Length of output: 502

---

Remove v prefix from version heading to match established changelog format.

Line 8 has [v1.0.2] with a v prefix, while all other version headings in the file use the format without it—[1.0.1] (line 56), [1.0.0+14] (line 97), etc. This breaks the established pattern. Remove the v to align with the rest of the changelog.

🤖 Prompt for AI Agents

In CHANGELOG.md around line 8, the version heading currently reads "[v1.0.2]"
which includes an unwanted "v" prefix differing from the file's established
format; edit that heading to remove the "v" so it reads "[1.0.2]" to match the
other version entries.