[github-data] chore: bump version to 0.0.6 (#30)

Cuts the v0.0.6 release. Bundles two features that landed since v0.0.5:

- Opt-in background sync (PR #28). Closes out the v0.2 design milestone -- five-minute heartbeat with three frequency tiers, off by default, rate-limit-gated. No new endpoints.
- Charter hydration (PR #29). First v0.3 milestone -- vault files opt in via `github_repo: owner/repo` frontmatter and receive a fixed `gh_*` block populated from already-synced data. Idempotent, body-preserving, allowlist-gated. No new GitHub calls.

Plus the doc updates from PRs #26 / #27 (ROADMAP.md added, SOP-progress note).

Manifest + package.json + versions.json bumped. CHANGELOG [Unreleased] content moved into a [0.0.6] - 2026-04-30 section, leaving [Unreleased] empty for the next round.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: bit-incarnas

CHANGELOG.md

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.6] - 2026-04-30
+
+Two-feature release: opt-in background sync (closing v0.2) and charter hydration (opening v0.3). No new GitHub egress endpoints; both features operate over already-documented data flows.
+
 ### Added (charter hydration -- v0.3 milestone start)
 - **`src/sync/charter-hydrator.ts`** -- new pure module. `buildHydrationPlans({ vaultFiles, allowlist, nowIso })` returns one `HydrationPlan` per opt-in vault file (any markdown file with `github_repo: owner/repo` in its frontmatter). Each plan carries either `status: "ok"` with the merged `gh_*` frontmatter to write, or `status: "skipped"` with a reason (empty marker / non-string marker / unallowlisted repo / no synced data / no change since last hydration). No Obsidian imports; 100% unit-testable. The companion `applyHydrationUpdates(fm, updates)` mutates a frontmatter object in place, designed for use inside `processFrontMatter`'s mutate callback.
 - **Opt-in marker only.** Charters self-select by adding `github_repo: owner/repo` to their frontmatter. The plugin does not iterate `03_PROJECTS/` or any project folder; it iterates the vault's full markdown set and filters by the marker. Lets users put the marker on any file -- charter, HUD, daily-note template -- without configuration surface.

manifest.json

@@ -1,7 +1,7 @@
 {
 	"id": "github-data",
 	"name": "GitHub Data",
-	"version": "0.0.5",
+	"version": "0.0.6",
 	"minAppVersion": "1.0.0",
 	"description": "Mirror GitHub state (repos, issues, PRs, releases, Dependabot, Actions, contribution activity) into vault-native markdown. Pull-in only; vault data stays in the vault.",
 	"author": "bit-incarnas",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-github-data",
-  "version": "0.0.5",
+  "version": "0.0.6",
   "description": "Mirror GitHub state (repos, issues, PRs, releases, Dependabot, Actions, contribution activity) into vault-native markdown. Pull-in only; vault data stays in the vault.",
   "main": "main.js",
   "scripts": {

versions.json

@@ -3,5 +3,6 @@
 	"0.0.2": "1.0.0",
 	"0.0.3": "1.0.0",
 	"0.0.4": "1.0.0",
-	"0.0.5": "1.0.0"
+	"0.0.5": "1.0.0",
+	"0.0.6": "1.0.0"
 }