v0.6.3 — watch mode + CI indexing

agentforge-graph 0.6.3 — keep the graph fresh, automatically

Theme: freshness / ops. 0.6.2 made it one command to connect the graph to
your agent; 0.6.3 makes it automatic to keep it current. Re-indexing was
already cheap and incremental — now you don't have to remember to run it. A local
ckg watch loop tracks your working copy; a scaffolded CI workflow keeps the
shared central index fresh. The two target different stores, and the engine keeps
them apart.

Highlights

ckg watch — local freshness on a trigger you choose (feat-014)

pip install "agentforge-graph[watch]"
ckg watch                       # re-index on a trigger (on-commit by default)
ckg watch --trigger on-idle     # or reflect uncommitted edits when you pause
ckg watch --status              # trigger · store · last indexed commit · dirty?
ckg watch --once                # one refresh if dirty, then exit

• Won't churn or burn spend. Default trigger is on-commit — ordinary saves
  do nothing; the graph tracks committed state. on-idle / on-save /
  interval / manual are there when you want them, all debounced and
  single-flight so bursts coalesce. A watch refresh is structural-only by
  default (embed_on_watch / enrich_on_watch off), so it never runs embeddings
  or LLM enrichment per save.
• Branch-gated. Watches feature branches, skips main / release/* by
  default (watch.branches).
• Can't corrupt a shared store. ckg watch refuses a central
  (store.central_root) or read-only store — that split is enforced in the
  engine, so a developer's loop never races writes into the authoritative graph.

ckg ci init — deterministic central indexing (feat-014)

ckg ci init                     # write .github/workflows/ckg-index.yml
ckg ci init --print             # preview, write nothing
ckg ci init --extra bedrock --enrich

Scaffolds a self-contained workflow that indexes into the central store on
merge-to-main + nightly, single-writer (concurrency group, no write
races), incremental (only the diff since the last indexed commit). CI is the sole
authoritative writer, so read-only consumers can trust it. Managed-marker +
idempotent; won't clobber a hand-edited file without --force.

See the new guide: Watch mode & CI indexing.

Fixed

• Post-release verification no longer false-alarms (#148). postrelease.yml
  now triggers off the Release workflow completing successfully
  (workflow_run) instead of the GitHub release: published event — under
  on-demand OIDC publishing the release exists before the artifact reaches PyPI,
  so the old trigger polled too early and auto-opened a spurious failure issue
  each release.