chore: bump version to 0.0.3

[bit-incarnas]

Summary

• Bumps manifest.json, package.json, package-lock.json, versions.json from 0.0.2 → 0.0.3
• Bundles PR feat(http): rate-limit discipline -- tracker, retry, circuit, concurr… #17 (rate-limit) + feat(sync): activity aggregator -- daily rollup from contributionsCol… #18 (activity aggregator) + feat(codeblock): github-issue / github-pr / github-release / github-d… #19 (codeblock processor)

What's in 0.0.3 vs 0.0.2

Slice	PR	What
Rate-limit discipline	#17	RateLimitTracker + CircuitBreaker + Semaphore + wrapWithRateLimit; failure-mode table
Activity aggregator	#18	Sync activity command; GraphQL contributionsCollection; per-day rollup files
Codeblock processor	#19	Four github-* Markdown codeblocks; metadataCache-only, zero new egress

Behind the scenes: vault-side Telemetry Grid card + GitHub Console year-view heatmap wire the activity files into the existing focus/energy/sleep telemetry surface (no plugin change required).

Test plan

• npm ci && npm run build passes (typecheck + esbuild prod)
• npx jest passes — 429 tests across 24 suites
• manifest.json / package.json / package-lock.json / versions.json all show 0.0.3
• After merge: tag 0.0.3, attach main.js + manifest.json + versions.json to the GitHub release

🤖 Generated with Claude Code

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0bb647f3-ddff-4ef8-a724-e9e4187b0e26

📥 Commits

Reviewing files that changed from the base of the PR and between b2c698f and 66fb2a4.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• manifest.json
• package.json
• versions.json

📜 Recent review details

⏰ 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 + Test

🔇 Additional comments (4)

package.json (1)

3-3: LGTM! Version bump is consistent across configuration files.

The version update from 0.0.2 to 0.0.3 is clean and aligns with the changes in manifest.json and versions.json.

versions.json (2)

3-4: LGTM! Version mapping is correct.

The new "0.0.3": "1.0.0" entry correctly maintains the minimum Obsidian API version requirement at 1.0.0, which is appropriate since no new Obsidian API features are required. The trailing comma on line 3 follows JSON best practices for future additions.

---

1-5: package-lock.json has been properly updated.

Verification confirms package-lock.json contains version 0.0.3 with no stray references to older versions, indicating the lockfile was correctly synchronized.

manifest.json (1)

4-4: LGTM! Manifest version is correctly synchronized.

The version bump to 0.0.3 is consistent with package.json and the new entry in versions.json. The minAppVersion of 1.0.0 correctly matches the mapping defined in versions.json.

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Version bumped to 0.0.3

Walkthrough

The extension and package versions are incremented from 0.0.2 to 0.0.3 across multiple configuration files: manifest.json, package.json, and versions.json. No functional code or dependencies are altered.

Changes

Cohort / File(s)	Summary
Version Bump manifest.json, package.json, versions.json	Version incremented from 0.0.2 to 0.0.3; new version mapping added to versions.json with adjusted formatting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: bump version to 0.0.2 #16: Both PRs perform identical version bumping across the same configuration files (manifest.json, package.json, versions.json).

Poem

🐰 A hop, a skip, a version bump so fine,
From 0.0.2 to 0.0.3 in line,
The manifest and package dance with grace,
While versions.json finds its perfect place! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title accurately and concisely summarizes the main change: bumping the version from 0.0.2 to 0.0.3 across configuration files.
Description check	✅ Passed	The description is directly related to the changeset, providing detailed context about the version bump and the bundled PRs (#17, #18, #19) that are included in this release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-0.0.3

---

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