source-graph-consolidation

name	source-graph-consolidation
description	Use when consolidating scattered skills, agents, hooks, concepts, instructions, plugin manifests, promotion records, duplicate queues, or provenance.

Source Graph Consolidation

Use this skill to move scattered AI tooling primitives toward this repository as the source of truth. Consolidation is evidence-first: inventory before moving, promote before cleanup, validate before trusting, and preserve provenance in Git and manifests instead of leaving dead source in place as evidence.

Operating Contract

• Do not delete, rewrite, or replace unrelated external originals during promotion.
• When cleanup is in scope and replacement is proven, remove dead authored source instead of retaining it for archaeology.
• Treat generated inventory and consolidation reports as evidence, not as the final decision.
• Promote primitives into canonical roots under source/: source/skills/, source/agents/, source/hooks/, and source/concepts/.
• Keep plugins referential. They may compose primitives, but they must not own the only copy of a primitive.
• Record every promotion in garden/manifests/promotions.json with source paths and first-party handling when applicable.
• Treat every persisted JSON edit as schema-driven. node source/tools/validate-source-graph.mjs or a focused repository helper must cover the changed file.
• Do not raw-copy OpenAI, Anthropic, or other first-party material. Rename, rewrite, and preserve source paths as provenance.

Workflow

1. Refresh the evidence. Run inventory and consolidation generation before deciding what to promote. Compare the generated queue to the existing canonical roots.

2. Pick a coherent family. Promote related primitives together only when they form a useful capability family. Avoid mixing unrelated cleanup just because it appears nearby in the queue.

3. Inspect sources. Read the candidate source paths and any existing canonical equivalent. Decide whether to keep, rewrite, synthesize, split, or ignore the candidate.

4. Promote into canonical roots. Place reusable skills, agents, hooks, and concepts where they remain useful without a plugin. Extract provider-specific or language-specific details into references or scoped subdirectories.

5. Compose by reference. Add or update source/adaptable.marketplace.json and source/plugins/*/plugin.json after the independent primitive exists. Use direct primitive paths, not payload copies.

6. Record provenance. Update garden/manifests/promotions.json for promoted material. If the source is a first-party distribution, include firstPartyHandling and use a local non-colliding canonical name.

7. Validate and regenerate. Run the validation set, inspect counts, and update summary docs when the inventory changes.

8. Clean up dead source deliberately. If the current scope includes cleanup and the canonical replacement is proven, remove stale authored source and validate the source graph. Use garden/manifests/cleanup-ledger.json for risky runtime, symlink, or cross-root replacement handoffs that need an approval and rollback boundary.

Reference Routing

• Load review-queue.md when interpreting garden/docs/consolidation-queue.md or generated report priorities.
• Load promotion-records.md when editing garden/manifests/promotions.json or handling first-party source material.
• Load cleanup-handoff.md before proposing symlink replacement, source deletion, or cleanup ledger entries.

Completion Criteria

• The promoted primitive is independent of plugins.
• Plugins and marketplace entries reference canonical primitives directly.
• Provenance is recorded before any cleanup is considered.
• Generated inventory and consolidation reports are current.
• Manifest validation proves schema coverage, local references, and first-party collision checks.
• Dead source is not retained merely as historical evidence.