feat(skills): install and manage project-local GraphForge skills

[DecisionNerd]

Objective

Ship atomic project-local GraphForge skill lifecycle from one canonical source in both Python and npm distributions.

Acceptance criteria

1. Canonical project skills install under .agents/skills/ with a versioned managed manifest, compatibility metadata, and hashes.
2. skills install|status|update|remove are atomic, idempotent, offline-capable once installed/packed, and never overwrite user edits or unrelated skills without explicit conflict resolution.
3. init installs missing compatible skills unless --no-skills is supplied and never blanket-ignores .agents/skills/.
4. Python installs packaged assets directly without Node/NPX; npm installs its packaged assets directly.
5. CI proves byte/manifest parity from one checked-in source plus clean-environment and conflict/recovery behavior; docs and [Unreleased] are updated.

Relationships

• Parent and close gate: feat(dx): add repository-local GraphForge lifecycle CLIs and project skills #219
• Blocked by the ADR/schema and binding CLI slices.

Ontology lifecycle scope boundary

• feat(api): add deterministic ontology suggestion, validation, and export #236 owns Rust runtime-catalog inspection, deterministic ontology suggestion, non-mutating validation, and explicit YAML/JSON ontology-document export.
• feat(bindings): expose ontology lifecycle parity in Python and Node #237 owns thin Python and Node parity over feat(api): add deterministic ontology suggestion, validation, and export #236, including the existing durable ontology adopt/clear behavior.
• Project-local skills must distinguish those ontology-document operations from feat(dx): add repository-local GraphForge lifecycle CLIs and project skills #219 whole-project repository export/import, and must never infer, adopt, clear, or change ontology authority as a side effect of repository sync, project interchange, configuration validation, or IaC.

Non-goals

• Global user skill installation or host-specific behavior beyond documented project-local adapters.
• Reimplementing or extending the ontology lifecycle owned by feat(api): add deterministic ontology suggestion, validation, and export #236/feat(bindings): expose ontology lifecycle parity in Python and Node #237.

[coderabbitai]

🔗 Related PRs

#204 - chore: prepare npm packages for publishing [merged]
#220 - feat(bindings): expose embedded write modes [merged]
#234 - feat: add portable project interchange [open]
#235 - feat(cli): add Python and Node lifecycle launchers [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!